Chris Gamache <cgg007@yahoo.com> writes:
> 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?
If this happens, your application code is broken. You should always
call nextval() before calling currval() on a given connection. These
are server-side functions (not variables) and the ODBC driver can't
"reset" them.
-Doug
