RE: [Pypgsql-users] pypgsql and postgresql 8

[jose <jo...@cy...>]

If I've read this correctly the implication is that PyPgSQL is not =
really
going to be maintained any longer.  Bummer really it is a very nice
interface.  If it is not going to be maintained, is there any
recommendations as to which API to switch to?

Jose



-----Original Message-----
From: pyp...@li...
[mailto:pyp...@li...] On Behalf Of Karsten
Hilbert
Sent: Wednesday, January 19, 2005 1:11 AM
To: pyp...@li...
Subject: Re: [Pypgsql-users] pypgsql and postgresql 8


> while testing postgresql 8 i was wondering if s.b. could provide some=20
> info if there are plans to finish an updated version of pypgsql which=20
> works with postgresql 8.
I assume you mean "takes advantage of the new binary protocol" ? I =
second
that interest.

Due to slow support (which may have very legitimate reasons) I have
considered moving GnuMed to another DB-API module. Doing so will likely =
make
our code more generic and thus switching back easier if later we ever so
desire. We are already carrying a patch and a workaround in our CVS tree
that apparently don't make it into pyPgSQL proper. A second patch is on =
the
way in. All of them were posted on this list.

PyPgSQL has served us well so far, however, including delivering =
NOTIFYs.

Thanks,
Karsten
--=20
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE
limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and =
FREE --
well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Pypgsql-users mailing list
Pyp...@li...
https://lists.sourceforge.net/lists/listinfo/pypgsql-users