We have a problem where the value of currval() transitions from one pooled
connection to another with pgodbc-7.02.00.05. I am wondering if pgodbc has been
fixed to wipe connection-related variables like currval and nextval when a
pooled connection is recycled. Is there perhaps some setting that I am missing?
Also, I can't find a definitive changelog describing all the various
improvements between 7.02.00.05 and the current stable version. That makes it
difficult to assess the dangers of upgrading!
CG
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com