Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE

Поиск
Список
Период
Сортировка
От Thom Brown
Тема Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE
Дата
Msg-id AANLkTilKw6C8RqNrFy3RSgJ_87fED3CuTmDCI9mKEeP_@mail.gmail.com
обсуждение исходный текст
Ответ на Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE  (Grzegorz Jaśkiewicz <gryzman@gmail.com>)
Ответы Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE  (Grzegorz Jaśkiewicz <gryzman@gmail.com>)
Список 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 по дате отправления:

Предыдущее
От: Teodor Macicas
Дата:
Сообщение: Re: what is the meaning of Datum?
Следующее
От: Grzegorz Jaśkiewicz
Дата:
Сообщение: Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE