Skip site navigation (1) Skip section navigation (2)

Re: Confusion over Python drivers

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Marko Kreen <markokr(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>
Subject: Re: Confusion over Python drivers
Date: 2010-02-06 00:39:53
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Friday 05 February 2010 21:34:53 Marko Kreen wrote:
> On 2/5/10, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> >  > I think another difference is that the Perl DBI interface is very
> >  > rich, whereas the Python DB-API is quite minimal and almost forces
> >  > people to write (incompatible) extensions.  The DB-SIG at Python that
> >  > ought to drive all this is also quite dead, possibly because everyone
> >  > has moved on to SQLAlchemy.
> > 
> > For people who use Python a lot, could I have a list of the deficiencies
> > 
> >  in DBAPI?  I've got my horse and lance ready.
> Psycopg was the leader, especially in web-environments,
> but it has non-obvious license and with dead website it does not
> seem that attractive.  Although it is well-maintained still.
Imho a big problem is that it does way too much itself - i.e. it does not use 
things like PQExecParams but does escaping/parsing itself...
Other people may think thats a good idea - I definitely do not think so.


In response to


pgsql-hackers by date

Next:From: Josh BerkusDate: 2010-02-06 00:42:35
Subject: Re: Confusion over Python drivers
Previous:From: Heikki LinnakangasDate: 2010-02-06 00:24:57
Subject: Re: WIP patch for system-catalog vacuuming via a relation map

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group