From: Cristian Gafton <gafton@rpath.com>
To: pgsql-interfaces@postgresql.org
Cc: sdavis2@mail.nih.gov
Subject: Re: Python interfaces
Date: Mon, 18 Sep 2006 06:02:52 -0400 (EDT)
Message-ID: <Pine.LNX.4.61.0609180557440.16307@alienpad.rpath.com> (raw)
In-Reply-To: <20060915145140.4cb86e12.darcy@druid.net>
References: <200609151352.20668.sdavis2@mail.nih.gov>
<20060915145140.4cb86e12.darcy@druid.net>
On Fri, 15 Sep 2006, D'Arcy J.M. Cain wrote:
>> I am in the process of moving development from perl to python. Under perl,
>> there was DBI, the be-all-end-all of database interfaces. Under python,
>> there is a plethora of options. Is there a recommended one for postgres? It
>> will be mainly used in a web environment, so the ability to work
>> asynchronously is not that important. I am interested in maintaining
>> database introspection (which the DB-API 2.0 is conspicuously short on)
>> tools, as well as niceties such as automatic escape-quoting, etc, that are
>> pretty standard in perl. Any suggestions?
>
> I maintain PyGreSQL which used to be the one shipped with PostgreSQL
> before we split it off into a separate project. http://PyGreSQL.org/.
I maintain a further split from PyGreSQL that supports native bind
parameters and prepared statements at:
http://cheeseshop.python.org/pypi/python-pgsql
(using bind parameters eliminates many worries about escape quoting...)
Cristian
--
Cristian Gafton
rPath, Inc.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: gafton@rpath.com, sdavis2@mail.nih.gov
Subject: Re: Python interfaces
In-Reply-To: <Pine.LNX.4.61.0609180557440.16307@alienpad.rpath.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox