Re: Retrieving last InsertedID : INSERT... RETURNING safe ?

From: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>
To: "Paul Tomblin" <ptomblin(at)gmail(dot)com>
Cc: <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Retrieving last InsertedID : INSERT... RETURNING safe ?
Date: 2008-02-20 12:27:34
Message-ID: 47BC1CB6.6070007@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Paul Tomblin wrote:
> Dave Cramer wrote:
>>> Well, that other solution is dangerous in case multiple inserts
>>> to that table are done concurrently; a quite common usage pattern
>>> with java web applications handling multiple HTTP requests with
>>> concurrent java threads..
>>>
>> No it is not dangerous. It is the right way to do it. There is
>> absolutely no danger in using currval in this manner.
>
> Unless you have autocommit on.

No, autocommit has nothing to do with it.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Dave Cramer 2008-02-20 12:28:18 Re: Retrieving last InsertedID : INSERT... RETURNING safe ?
Previous Message Paul Tomblin 2008-02-20 12:19:16 Re: Retrieving last InsertedID : INSERT... RETURNING safe ?