Re: Revisited: Transactions, insert unique.

rmcm@compsoft.com.au wrote:
>
> Doesn't
>
>      SET TRANSACTION ISOLATION LEVEL SERIALIZABLE;
>
> have to come within transaction - ie
>
>      BEGIN;
>      SET TRANSACTION ISOLATION LEVEL SERIALIZABLE;
>
> In this order your test seems to behave correctly - only 1 row inserted.

Yes, my initial ordering was in error.  But even after reordering, the
point is not that only 1 row was inserted, but rather that Transaction A
was able to see the effects of transaction B when it clearly should not.

Regards,
Ed Loehr