[PyGreSQL] ValueError - among other things - update

Fred Wilson Horch fhorch at ecoaccess.org
Thu Aug 21 17:18:31 EDT 2003


On Wed, 2002-03-06 at 08:44, Thys Meintjes wrote in part:
> A while ago I queried this list on the problem discussed at length below. I
> fixed the 'bug' and because it is such a insidious bastard I thought I'd
> share the solution.
> 
> It has to do (I think) with the thread safety of postgress or PyGreSQL. To 
> make a short story shorter I used a singleton 'DBBroker' object throughout my
> multithreaded App to handle all DB interaction (a fairly large +7M wxPython
> based GUI). Needless to say once I gave each thread its own DB connection my
> problem went away.
> 
> Why all these lead to ValueErrors etc. I haven't bothered to investigate.

Just curious if the problem happens if you use psycopg instead of
PyGreSQL (see http://initd.org/Software/psycopg).  Also, does anyone on
this list have experience switching from or to psycopg?  Are the latest
versions of PyGresSQL and psycopg "plug compatible", i.e. can you write
to the Python DBAPI and be able to swap out PyGreSQL for psycopg and
vice versa?

Thanks!
Fred
-- 
Fred Wilson Horch			mailto:fhorch at ecoaccess.org
Executive Director, EcoAccess		http://ecoaccess.org/
P.O. Box 2823, Durham, NC 27715-2823	phone: 919.419-8567





More information about the PyGreSQL mailing list