Re: ODBC Connection Pooling (Windows 2000 MDAC 2.7 patched, - Mailing list pgsql-odbc

From Oliver Elphick
Subject Re: ODBC Connection Pooling (Windows 2000 MDAC 2.7 patched,
Date
Msg-id 1062699224.10618.142.camel@linda.lfix.co.uk
Whole thread Raw
In response to Re: ODBC Connection Pooling (Windows 2000 MDAC 2.7 patched, pgodbc-7.02.00.05)  (Chris Gamache <cgg007@yahoo.com>)
Responses Re: ODBC Connection Pooling (Windows 2000 MDAC 2.7 patched, pgodbc-7.02.00.05)  (Chris Gamache <cgg007@yahoo.com>)
List pgsql-odbc
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


pgsql-odbc by date:

Previous
From: Chris Gamache
Date:
Subject: Re: ODBC Connection Pooling (Windows 2000 MDAC 2.7 patched, pgodbc-7.02.00.05)
Next
From: "E. Zorn (RDG-rational)"
Date:
Subject: Change connection (IP, or Databasename)