Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE - Mailing list pgsql-general

From Thom Brown
Subject Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE
Date
Msg-id AANLkTilKw6C8RqNrFy3RSgJ_87fED3CuTmDCI9mKEeP_@mail.gmail.com
Whole thread Raw
In response to Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE  (Grzegorz Jaśkiewicz <gryzman@gmail.com>)
Responses Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE
List pgsql-general
2010/6/23 Grzegorz Jaśkiewicz <gryzman@gmail.com>:
> well, change foob column name to something else, and try yourself. It
> still fails.
>

Wait a minute... it's deleting from foob, which is considered deleted
for the remainder of that transaction.  This cascades to fooa which
sets off the trigger before it does anything, and the result you're
getting out says that the same value is no longer is foob, which,
while not yet committed, is true as far as the transaction is
concerned.  This is confusing because I thought the default
transaction isolation level was READ COMMITTED. :/

Regards

Thom

pgsql-general by date:

Previous
From: Teodor Macicas
Date:
Subject: Re: what is the meaning of Datum?
Next
From: Grzegorz Jaśkiewicz
Date:
Subject: Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE