2010/6/23 Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)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