That is my point exactly. That is why (windows?) connection pooling breaks this
model. It wouldn't be a problem if there were a way to undefine currval() for
all sequences... It would be a command issued by the ODBC driver when the
connection is made (best), or by the connecting process as its first order of
business (do-able).
CG
--- Oliver Elphick <olly@lfix.co.uk> wrote:
> On Thu, 2003-09-04 at 16:29, Chris Gamache wrote:
>
> > If sequences are used to keep track of the row last inserted, isn't it
> critical
> > to be able to insure the value of currval() doesn't belong to someone
> else's
> > connection?
>
> That can't happen. currval() is _guaranteed_ to return only the last
> value generated during your own current session. That is why you cannot
> use it unless you have used nextval() first in the same session.
>
> --
> Oliver Elphick Oliver.Elphick@lfix.co.uk
> Isle of Wight, UK http://www.lfix.co.uk/oliver
> GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C
> ========================================
> "If any of you lack wisdom, let him ask of God, who
> gives to all men generously and without reproach, and
> it will be given to him." James 1:5
>
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com