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 Berkus||Date: 2010-02-06 00:42:35|
|Subject: Re: Confusion over Python drivers|
|Previous:||From: Heikki Linnakangas||Date: 2010-02-06 00:24:57|
|Subject: Re: WIP patch for system-catalog vacuuming via a relation