| From: | James William Pye <lists(at)jwp(dot)name> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: Confusion over Python drivers |
| Date: | 2010-02-05 19:08:31 |
| Message-ID: | F3E121C4-0E21-4285-8E06-4DAA0F37630D@jwp.name |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Feb 5, 2010, at 8:00 AM, Peter Eisentraut 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.
Yep.
> The DB-SIG at Python that ought to drive all this is also quite dead,
From reading messages that come into that list(not-so-lately), I've gotten the impression that they are content with DB-API 2. Aside from the TPC interfaces, the last round of activity that I know of was dbapi3[1 (which was a long while ago)].
> possibly because everyone has moved on to SQLAlchemy.
Yeah. AFAICT, that is the general direction encouraged by DB-SIG. Write an abstraction on top of DB-API. SQLAlchemy, SQLObject, anysql, and I'm sure there are others.
[1] http://wiki.python.org/moin/Aug2001DbApi3Strawman
http://wiki.python.org/moin/DbApi3
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2010-02-05 19:09:08 | Re: [COMMITTERS] pgsql: Remove tabs in SGML. |
| Previous Message | Alvaro Herrera | 2010-02-05 19:04:22 | Re: [COMMITTERS] pgsql: Remove tabs in SGML. |