Thread: interfaces for python
I'd like to know if anyone has recommendations for which Python DB-API 2.0 interface to use with PostGreSQL-7.4.5. The database and tools to interact with it will be hosted on a MacOS 10.3.x machine. The db schema represents a small production studio environment with only a handful of users. db connection will be intermittent. pyPgSQL? PyGreSQL? Anything I should consider? Thanks in advance! Scott
I'd advise psycopg as the fastest one (by a factor of 10x on large selects). On Wed, 6 Oct 2004 21:13:02 -0700, Scott Frankel <leknarf@pacbell.net> wrote: > > I'd like to know if anyone has recommendations for which Python DB-API > 2.0 > interface to use with PostGreSQL-7.4.5. > > The database and tools to interact with it will be hosted on a MacOS > 10.3.x machine. > The db schema represents a small production studio environment with only > a handful > of users. db connection will be intermittent. > > pyPgSQL? > PyGreSQL? > > Anything I should consider? > > Thanks in advance! > Scott > > > ---------------------------(end of broadcast)--------------------------- > TIP 8: explain analyze is your friend >
On Thu, 2004-10-07 at 06:13, Scott Frankel wrote: > PyGreSQL? I will recommend pygresql, as the only thing don't like about it is its funny name :-) It's fast and quite feature complete, and have been used for big projects like Zope. /BL
* Pierre-Frédéric Caillaud <lists@boutiquenumerique.com> [2004-10-07 10:45:57 +0200]: > I'd advise psycopg as the fastest one (by a factor of 10x on large > selects). I second this recommendation. -- Steven Klassen - Lead Programmer Command Prompt, Inc. - http://www.commandprompt.com/ PostgreSQL Replication & Support Services, (503) 667-4564
Thanks for the responses! I have selected psycopg based on: - your recommendations (though massively parallel connections aren't currently likely in my environment - my success in building the target (with kudos & props to their install documentation) - my ability to pronounce its name ;) Now back to the schema ... Thanks Scott On Oct 6, 2004, at 9:13 PM, Scott Frankel wrote: > > I'd like to know if anyone has recommendations for which Python DB-API > 2.0 > interface to use with PostGreSQL-7.4.5. > > The database and tools to interact with it will be hosted on a MacOS > 10.3.x machine. > The db schema represents a small production studio environment with > only a handful > of users. db connection will be intermittent. > > pyPgSQL? > PyGreSQL? > > Anything I should consider? > > Thanks in advance! > Scott > > > ---------------------------(end of > broadcast)--------------------------- > TIP 8: explain analyze is your friend >
Steven Klassen wrote: > * Pierre-Frédéric Caillaud <lists@boutiquenumerique.com> [2004-10-07 10:45:57 +0200]: > > >>I'd advise psycopg as the fastest one (by a factor of 10x on large >>selects). > > > I second this recommendation. > Also because this interface is not affected by the "idle in transaction", indeed as the last JDBC interface version this interface delay the transaction open at the first statement. I think that the new postgres rpm shall insert this interface instead the PyGres one. Regards Gaetano Mendola
I've been using psycopg for a few years and it works very well. I agree with the other posters. I would also add that a quick look at SQLObject is worthwhile for a python programmer. Very handy. http://sqlobject.org I have no affiliation with the product but I am a fan. Been using it as my CGI interface until Zope sorts out whether it wants to use DTML or TAL for its web interface. Brian On Oct 6, 2004, at 10:13 PM, Scott Frankel wrote: > > I'd like to know if anyone has recommendations for which Python DB-API > 2.0 > interface to use with PostGreSQL-7.4.5. > > The database and tools to interact with it will be hosted on a MacOS > 10.3.x machine. > The db schema represents a small production studio environment with > only a handful > of users. db connection will be intermittent. > > pyPgSQL? > PyGreSQL? > > Anything I should consider? > > Thanks in advance! > Scott > > > ---------------------------(end of > broadcast)--------------------------- > TIP 8: explain analyze is your friend >