From: Luke O. <lu...@me...> - 2003-06-05 04:28:40
|
There is an old version of psycopg compiled for windows at http://www.stickpeople.com/projects/python/psycopg/ we use it here for similar purposes (build on windows, deploy on linux) with complete success. (Just unpack the zip file and copy psycopg.pyd and libpq.dll to your site-packages directory.) I know we had trouble using pyPgSQL instead in the past with SQLObject, largely I think because pyPgSQL does some odd stuff with creating it's own PgTypes for a lot of return values (as I recall, might have been something else...) psycopg is much much faster for us, as a bonus. - Luke Quoting xtian <xt...@to...>: > Hi - > > It looks like the PostGreSQL support for SQLObject expects psycopg - is > there any particular reason for this? I'm doing development on Windows > (although we'll eventually be deploying on Linux), and I don't think I > can go through the compilation process required for psycopg. (Unless > anyone has some compiled binaries for windows/Python2.2 lying around?) > > It doesn't look like it would take much to make PostgresConnection use > PyPgSQL.PgSQL (which has binaries for windows), although I haven't > looked closely. Are there any nasty gotchas I should know about? Have > braver men tried and failed? > > Thanks, > Christian > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Etnus, makers of TotalView, The best > thread debugger on the planet. Designed with thread debugging features > you've never dreamed of, try TotalView 6 free at www.etnus.com. > _______________________________________________ > sqlobject-discuss mailing list > sql...@li... > https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss > -- i find your contempt for naked feet curious. |