Re: Duplicate key issue in a transaction block

In response to Vyacheslav Kalinin <vka(at)mgcp(dot)com>:

> On Mon, Jun 8, 2009 at 8:33 PM, Bill Moran <wmoran(at)potentialtech(dot)com> wrote:
>
> >
> > Perhaps you want to take an exclusive lock on the table? The operation
> > you describe seems to suggest that you'd want to guarantee exclusive
> > write access to the table.
>
> Exclusive table lock is a bit excessive IMO. Locking particular group
> should be good, though it is not quite straightforward to achieve. I'd use
> advisory locks or would lock a row in a parent group table (if such table
> exists, if not - it might be worth to make one) referenced by rows in
> question.

Perhaps, but sounds like a lot of unnecessary complexity to me.

... and I didn't say exclusive table lock, I said "exclusive write" Big
difference there.

--
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/