SQLObject

Replying to my own post... looks like under Windows (both cygwin and 
regular win32) the sqliteconnection.py comes with with bad 
path/filenames sometimes like '/c:/pathto\filename'. The solution/hack 
I've come up with is simply to extract the prior '/' char if there is a 
drive designator in the path name. Here's some code to be inserted into 
sqliteconnection.py @ line 23:
SQLiteConnection.__init__:
 >>after
        self.module = sqlite
 >>insert
        # for windows - check for '/c:\\path\filename' situation
        spos = filename.find('//')
        cpos = filename.find(':')
        if spos and spos < cpos:
            filename = filename[cpos+1:]
 >> before
        self.filename = filename  # full path to sqlite-db-file

    Might be a cleaner way of doing this but it worked for me. Also, the 
test run fails if there is not a data directory under tests (which does 
not automatically get created with the current svn source). The latest 
oddity is that I have SEVERAL (36/84) tests fail when running py.test in 
batch mode but individual executions seem to work. For example, in batch 
mode (just run 'py.test')  test_select.py fails 6 of 8 tests but running 
'py.test test_select.py' explicitly passes all 8 tests. Finally, I can't 
seem to get the test output to show me what the SQL looks like or 
general output from my test (like debug printing).

    thanx & later,

       Ben Scherrey

Benjamin Scherrey wrote:

> Web page fixes:
>
> Under the link: 
> http://sqlobject.org/docs/SQLObject.html#using-sqlobject-an-introduction
> The link to PySQLite is broken and should be http://pysqlite.org/
> Also, PySQLite should be listed about in the requirements section 
> alond with psycopg & SQLite.
>
> Meanwhile, I'm discovering this as I'm trying to figure out how to get 
> the tests to run. I have SQLite-3.2.2 and Pysqlite 2.0.3 for Python 
> 2.4 installed along with the latest py lib svn tree. Running 
> everything under cygwin in Windows but using the Windows version of 
> Python 2.4.1, not the cygwin version. When I run the tests I get a lot 
> of 'FAILED TO LOAD MODULE' reports and the listings all show 
> OperationalError: unable to open database file msgs under the 
> sqlite.connect( self.filename, **opts ) line 42 of sqliteconnection.py.
>
> I've gone through all the docs I can findso am not sure what the 
> problem is. Do I have version compatibility issues? Am I supposed to 
> pass something to the command line when I run py.test? Not sure how to 
> proceed here.
>   thanx & later,
>
>       Ben Scherrey
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the 'Do More With Dual!' webinar 
> happening
> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
> core and dual graphics technology at this free one hour event hosted 
> by HP,
> AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
> _______________________________________________
> sqlobject-discuss mailing list
> sqlobject-discuss@...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>

On Thu, Jul 14, 2005 at 05:09:58PM -0400, Benjamin Scherrey wrote:
>    Replying to my own post... looks like under Windows (both cygwin and 
> regular win32) the sqliteconnection.py comes with with bad 
> path/filenames sometimes like '/c:/pathto\filename'.

   In what version of SQLObject? I think I've fixed that long ago in SVN.

Oleg.
-- 
     Oleg Broytmann            http://phd.pp.ru/            phd@...
           Programmers don't die, they just GOSUB without RETURN.

Per the earlier msg - this is the latest svn source as of less than a 
week ago. Any clues as to the other issues? I take it that the win32 
environment is the bastard child of target platforms for SQLObject? :)

    -- Ben Scherrey

Oleg Broytmann wrote:

>On Thu, Jul 14, 2005 at 05:09:58PM -0400, Benjamin Scherrey wrote:
>  
>
>>   Replying to my own post... looks like under Windows (both cygwin and 
>>regular win32) the sqliteconnection.py comes with with bad 
>>path/filenames sometimes like '/c:/pathto\filename'.
>>    
>>
>
>   In what version of SQLObject? I think I've fixed that long ago in SVN.
>
>Oleg.
>  
>

Until fairly recently, I was using sqlite on Windows and it worked
just fine. I even just confirmed that the paths I was using were full
paths with the drive letter.

However, I was instantiating sqliteconnections myself (not using a
URI). Are you using a URI to open the connection?


On 7/14/05, Benjamin Scherrey <scherrey@...> wrote:
> Per the earlier msg - this is the latest svn source as of less than a
> week ago. Any clues as to the other issues? I take it that the win32
> environment is the bastard child of target platforms for SQLObject? :)
>=20
>     -- Ben Scherrey
>=20
> Oleg Broytmann wrote:
>=20
> >On Thu, Jul 14, 2005 at 05:09:58PM -0400, Benjamin Scherrey wrote:
> >
> >
> >>   Replying to my own post... looks like under Windows (both cygwin and
> >>regular win32) the sqliteconnection.py comes with with bad
> >>path/filenames sometimes like '/c:/pathto\filename'.
> >>
> >>
> >
> >   In what version of SQLObject? I think I've fixed that long ago in SVN=
.
> >
> >Oleg.
> >
> >
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dclic=
k
> _______________________________________________
> sqlobject-discuss mailing list
> sqlobject-discuss@...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>

Kevin,

    I'm not entirely certain as I'm just trying to get the py.test 
environment running for SQLObject so its whatever the tests are using. 
Since I'm running into difficulties getting certain types of debug 
output I'm not exactly sure what mechanism its using to open the 
connections. You can read my initial email in this thread to get more 
details about my setup.

    -- Ben Scherrey

Kevin Dangoor wrote:

>Until fairly recently, I was using sqlite on Windows and it worked
>just fine. I even just confirmed that the paths I was using were full
>paths with the drive letter.
>
>However, I was instantiating sqliteconnections myself (not using a
>URI). Are you using a URI to open the connection?
>
>
>On 7/14/05, Benjamin Scherrey <scherrey@...> wrote:
>  
>
>>Per the earlier msg - this is the latest svn source as of less than a
>>week ago. Any clues as to the other issues? I take it that the win32
>>environment is the bastard child of target platforms for SQLObject? :)
>>
>>    -- Ben Scherrey
>>    
>>

Sorry for both the lateness of my reply and the fact that I missed
that you were just trying to run the tests. Though my sqlite
application runs under Windows, I've only touched SQLObject itself on
my Mac, which doesn't have the c: problem.

I was hoping that os.path.normpath might correct for this, but it
doesn't. I'd rather be explicit about fixing this, on the off chance
that someone actually has a ":" in their filename...

if filename[0] =3D=3D "/" and filename[2] =3D =3D ":":
    filename =3D filename[1:]

Even better would be a fix for this in the URI parser, which I think
is where the leading slash came from to begin with.

It looks like you can get debugging output by adding -S or -O
parameters to your py.test commandline. (Take a look at
sqlobject/tests/conftest.py).

Kevin

On 7/14/05, Ben Scherrey <scherrey@...> wrote:
> Kevin,
>=20
>     I'm not entirely certain as I'm just trying to get the py.test
> environment running for SQLObject so its whatever the tests are using.
> Since I'm running into difficulties getting certain types of debug
> output I'm not exactly sure what mechanism its using to open the
> connections. You can read my initial email in this thread to get more
> details about my setup.
>=20
>     -- Ben Scherrey
>=20
> Kevin Dangoor wrote:
>=20
> >Until fairly recently, I was using sqlite on Windows and it worked
> >just fine. I even just confirmed that the paths I was using were full
> >paths with the drive letter.
> >
> >However, I was instantiating sqliteconnections myself (not using a
> >URI). Are you using a URI to open the connection?
> >
> >
> >On 7/14/05, Benjamin Scherrey <scherrey@...> wrote:
> >
> >
> >>Per the earlier msg - this is the latest svn source as of less than a
> >>week ago. Any clues as to the other issues? I take it that the win32
> >>environment is the bastard child of target platforms for SQLObject? :)
> >>
> >>    -- Ben Scherrey
> >>
> >>
>=20
>