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: 201002060140.02703.andres@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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.

Andres

In response to

Responses

Browse pgsql-hackers by date

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