Confusion over Python drivers
in [PgSql]
|
From: Andres Freund on 5 Feb 2010 19:39 On Friday 05 February 2010 21:34:53 Marko Kreen wrote: > On 2/5/10, Josh Berkus <josh(a)agliodbs.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Jeff Davis on 5 Feb 2010 14:32 On Fri, 2010-02-05 at 10:35 -0800, Josh Berkus wrote: > I'm not as concerned about "confusion" as the fact that *all* of the > various Python drivers suck in different, and crippling, ways. I don't > care how many drivers we have, as long as we have at least one 1st-class > driver. Absolutely. And I would prefer that it can provide all (or nearly all) of the capabilities of libpq. PyGreSQL apparently doesn't even offer parameterized queries! http://pygresql.org/pg.html That was based on a quick glance at the document; I hope I'm mistaken. Regards, Jeff Davis -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Tim Bunce on 5 Feb 2010 09:45 On Fri, Feb 05, 2010 at 09:19:26AM -0500, Bruce Momjian wrote: > My son has brought to my attention that our current crop of Python > client libraries is inadequate/confusing. I took a look myself, and > asked on our IRC channel, and am now convinced this area needs > attention. > > http://wiki.postgresql.org/wiki/Python > The Python-hosted PostgreSQL page has similar problems: > http://wiki.python.org/moin/PostgreSQL > > Does Perl have a similar mess? I don't think so. The primary database interface is DBI and as far as I can see there's only one DBI PostgreSQL driver: http://search.cpan.org/dist/DBD-Pg/ The only non-DBI interfaces I could find (by skimming the 384 results for postgresql on search.cpan.org) were: Postgres: http://search.cpan.org/dist/Postgres/ last updated in 1998. Pg: http://search.cpan.org/dist/pgsql_perl5/ last updated in 2000. Tim. -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Bruce Momjian on 5 Feb 2010 09:45 Peter Eisentraut wrote: > On fre, 2010-02-05 at 09:19 -0500, Bruce Momjian wrote: > > While I realize experienced people can easily navigate this confusion, > > I > > am concerned about new Postgres adopters being very confused by this > > and > > it is hurting our database adoption in general. > > > > What is really needed is for someone to take charge of one of these > > projects and make a best-of-breed Python driver that can gain general > > acceptance as our preferred driver. I feel Python is too important a > > language to be left in this state. > > The situation is unfortunate, but you might as well argue that too many > Linux desktops or Linux distributions confuse new users and hurt > adoption. These alternatives all exist for a reason, and it will be > difficult to get some of them to abandon their work with the aim of > reducing the overall "confusion". Agreed, but can't we do a better job of steering new users and improving the novice experience for the most popular of them, i.e. think Ubuntu. -- Bruce Momjian <bruce(a)momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Bruce Momjian on 5 Feb 2010 09:46
Tim Bunce wrote: > On Fri, Feb 05, 2010 at 09:19:26AM -0500, Bruce Momjian wrote: > > My son has brought to my attention that our current crop of Python > > client libraries is inadequate/confusing. I took a look myself, and > > asked on our IRC channel, and am now convinced this area needs > > attention. > > > > http://wiki.postgresql.org/wiki/Python > > The Python-hosted PostgreSQL page has similar problems: > > http://wiki.python.org/moin/PostgreSQL > > > > Does Perl have a similar mess? > > I don't think so. > > The primary database interface is DBI and as far as I can see there's > only one DBI PostgreSQL driver: http://search.cpan.org/dist/DBD-Pg/ > > The only non-DBI interfaces I could find (by skimming the 384 results > for postgresql on search.cpan.org) were: > Postgres: http://search.cpan.org/dist/Postgres/ last updated in 1998. > Pg: http://search.cpan.org/dist/pgsql_perl5/ last updated in 2000. Yes, that's what I thought, and am glad to here it. -- Bruce Momjian <bruce(a)momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |