Re: ODBC Connection Pooling (Windows 2000 MDAC 2.7 patched,

From: Oliver Elphick <olly(at)lfix(dot)co(dot)uk>
To: cgg007(at)yahoo(dot)com
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-odbc(at)postgresql(dot)org
Subject: Re: ODBC Connection Pooling (Windows 2000 MDAC 2.7 patched,
Date: 2003-09-04 18:13:45
Message-ID: 1062699224.10618.142.camel@linda.lfix.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)Elphick(at)lfix(dot)co(dot)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

In response to

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Jeff Eckermann 2003-09-04 20:40:46 Re: Change connection (IP, or Databasename)
Previous Message Chris Gamache 2003-09-04 15:29:34 Re: ODBC Connection Pooling (Windows 2000 MDAC 2.7 patched, pgodbc-7.02.00.05)