Doug, thanks for the reply!
Bruce, back me up (or shoot me down..): currval() should be undefined when a
connection is first made for any given sequence. If a connection is recycled,
shouldn't currval() be undefined for any given sequence to simulate the
behavior of a connection first being made?
CG
--- Doug McNaught <doug@mcnaught.org> wrote:
> 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
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
