From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
Cc: | Paul Tomblin <ptomblin(at)gmail(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Atomic operations? |
Date: | 2008-03-19 11:25:40 |
Message-ID: | D1937C2E-5870-4493-BF37-C89BDC88423E@fastcrypt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On 18-Mar-08, at 7:18 PM, Oliver Jowett wrote:
> Dave Cramer wrote:
>> On 18-Mar-08, at 9:40 AM, Paul Tomblin wrote:
>
>>> PreparedStatement ps = conn.prepareStatement(
>>> "DELETE FROM venue WHERE venueid = ? ; INSERT INTO VENUE
>>> (venueid, .... ) VALUES(?, ?, ?, ?)");
>
>>> Does that work? Will that be atomic so that nobody else can insert
>>> one with that venueid in between the delete and the insert?
>>>
>> I don't think so,
>
> Actually it's fine the implicit transaction created by the server to
> support autocommit wraps both queries in a single transaction and
> does not commit/rollback until the end of the second query.
>
Yeah, using v3 protocol this is presented as one prepare/execute.
Thanks for catching that.
> -O
>
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
From | Date | Subject | |
---|---|---|---|
Next Message | Woody Woodring | 2008-03-19 21:13:10 | Re: JDBC rewriting a bad query? |
Previous Message | Oliver Jowett | 2008-03-18 23:18:19 | Re: Atomic operations? |