Re: [Pypgsql-users] Upgrade to pg7.2.1 broke apps

[Gerhard <ger...@gm...>]

* James Thompson <ja...@gn...> [2002-05-02 11:28 -0500]:
> 
> Hello,
> 
> I recently moved from pg 7.1.3 to 7.2.1.  Now my win32 and solaris app
> that used pypgsql has become very flaky with regard to pulling data from
> the database.  The only tables that seem affected are those with text
> fields in them.  The app still seems to work using either pygresql or
> psycopg.

What is the problem you see? Wrong characters in the text fields?

> I have tried rebuilding the postgresql client libs on the solaris box then
> reinstalling pypgsql.  This did not solve the problem.
> 
> Any Ideas?

Not currently, but I'll try to debug this. I need additional data,
however.

Could you please construct a minimal test case that shows this problem,
including:
- the schema of the table
- one or more entries in the table where this problem occurs
- the pyPgSQL code you use to query the table

That would help us to look at this problem, try to reproduce it and fix
the problem in pyPgSQL.

You can then post this to the list or submit it as a bug at Sourceforge
(if you submit it as a bug at SF, please drop me a note, too).

You're using the 2.0 release of pyPgSQL, right?

Gerhard
-- 
mail:   gerhard <at> bigfoot <dot> de       registered Linux user #64239
web:    http://www.cs.fhm.edu/~ifw00065/    OpenPGP public key id AD24C930
public key fingerprint: 3FCC 8700 3012 0A9E B0C9  3667 814B 9CAA AD24 C930
reduce(lambda x,y:x+y,map(lambda x:chr(ord(x)^42),tuple('zS^BED\nX_FOY\x0b')))