On Friday, March, 2001-03-02 at 14:16:02, Joel Burton wrote:
> On Wed, 28 Feb 2001, [iso-8859-2] Marek Pętlicki wrote:
>
> > Has anybody used http://sourceforge.net/projects/pgsql ?
> > I maintain production system based on Python and PostgreSQL.
> >
> > I currently use PoPy, but for a few reasons it doesn't satysfy me fully.
> > The pgsql seems OK at first sight (especially libpq-to-Python API) but
> > for the production system I need Python DB API 2.0 compliant library.
> > Has anybody tested it yet? What is the status of PostgreSQL 7.1
> > compliance for today?
> >
> > Any Python geeks out here? ;-)
>
> Partially a Python geek here.
>
> I use PoPy and think it's dandy. I also thought it *was* the DB API 2.0--
> am I mistaken here?
yes, it _is_ compliant, when complaining about compatibility I meant
pgsql's libpq-to-Python API, which in my opinion is very cool thing (but
as I said I need DB API 2.0).
What I don't like in PoPy is its oversimplistic approach towards more
complex types in PostgreSQL. Returning Numerics as strings for example
is a little bit too much for me...
> PyGreSQL is more commonly used, and has (IMHO) a simpler, more dict-like
> interface, but isn't (AFAIK) thread-safe, nor DB API compliant.
yes, it is commonly used partly because it is distributed together with
PostgreSQL :-)
Anyway I must say, after a few glances at http://sourceforge.net/projects/pgsql
that it is very interesting project, especially because of its better
support of PostgreSQL types (like Numeric, Money or arrays), aspecially
better from PoPy, which I have most experience with. A few
improvements should be added to it though to make it really the best
PostgreSQL API for Python, IMO.
regards
--
Marek Pętlicki <marpet@buy.pl>