From: Michael Glaesemann <grzm@seespotcode.net>
To: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: Weber, Johann (ISS Kassel) <jweber@iss.net>
Cc: pgsql-sql@postgresql.org
Subject: Re: Atomar SQL Statement
Date: Sat, 8 Jul 2006 00:17:12 -0400
Message-ID: <6738B213-C52B-4F71-9134-85B45A4922B9@seespotcode.net> (raw)
In-Reply-To: <20060707105847.J77811@megazone.bigpanda.com>
References: <B8ADDBDA8696F546BDAC69B469D7F0512E06F3@kasmaiexcp01.iss.net>
<279E27B5-183F-4520-BC43-A726A50646EF@seespotcode.net>
<20060707105847.J77811@megazone.bigpanda.com>
On Jul 7, 2006, at 14:07 , Stephan Szabo wrote:
> I don't think he is, because I don't think the issue is the SERIAL
> behavior, but instead the NOT EXISTS behavior.
I guess I should have been clearer in the issue I was addressing,
which is whether or not a separate transaction could slip in and
interrupt his transaction, which my understanding is that it can't. I
personally would handle the insert if necessary/select in a different
way, but I don't see anything necessarily wrong with his statement. I
assumed that he does have a UNIQUE constraint on the email address
field. I should definitely know better than to make assumption.
Sorry, Johann, for not addressing your complete email, but rather
just a portion of it.
Michael Glaesemann
grzm seespotcode net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: grzm@seespotcode.net, sszabo@megazone.bigpanda.com, jweber@iss.net
Subject: Re: Atomar SQL Statement
In-Reply-To: <6738B213-C52B-4F71-9134-85B45A4922B9@seespotcode.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox