On Wed, Aug 15, 2001 at 06:01:58PM -0400, Fernando Nasser wrote:
> > If it has taken months for someone report report it and fix it, it can't
> > be that major.
Many PyGreSQL users aren't aware of the fact that it's part of PostgreSQL. I
sent a message to the mailing list recommending that they report bugs w/ the
PostgreSQL bug tracker in the future, not only on the mailing list.
> Maybe people are using the old interface pg.py and that one is not broken?
It's broken as well.
> Or people tried to use the new interface (pgdb.py) and gave up because it
> didn't work (and went on to use some other DBMS)?
I personally (and many others) switched to using different PostgreSQL/Python
interface. There are three alternatives to the one include in PG. I prefer
http://sourceforge.net/projects/pypgsql which is decidedly less buggy.
> It took us a couple weeks to get the first customer complaint, which is a
> very short time. We sent them Gerhard's patch and they are quite happy now
> (thanks Gerhard!).
You're welcome :-)
I also think that the bug is a major one. There were at least three complaints
at the mailing list, but it seems the PyGreSQL maintainer doesn't have much
time.
Gerhard
--
mail: gerhard <at> bigfoot <dot> de registered Linux user #64239
web: http://www.cs.fhm.edu/~ifw00065/ public key at homepage
public key fingerprint: DEC1 1D02 5743 1159 CD20 A4B6 7B22 6575 86AB 43C0
reduce(lambda x,y:x+y,map(lambda x:chr(ord(x)^42),tuple('zS^BED\nX_FOY\x0b')))
