From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
---|---|
To: | Mike Clements <mclement(at)progress(dot)com> |
Cc: | PostgreSQL JDBC List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Fetching generated keys |
Date: | 2007-03-05 21:08:50 |
Message-ID: | 45EC86E2.8020506@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Mike Clements wrote:
> Up to now, we were selecting the current value of the sequence
> immediately after the insert. I thought this was safe because
> transactions should be isolated. But now I realize this could
> potentially fail because the default transaction isolation is "read
> committed". Thus if another connection inserts into the same table,
> causing the sequence to increment, if it commits before we read the
> sequence value, we might read the wrong value (the value as incremented
> by the other transaction, not the value as it was for our own insert).
You should use the lastval-function. It retrieves the last value
returned in your connection. "SELECT lastval('sequence')"
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Clements | 2007-03-05 21:39:51 | Re: Fetching generated keys |
Previous Message | Mike Clements | 2007-03-05 20:08:58 | Fetching generated keys |