Re: BUG #6048: TRUNCATE vs TRUNCATE CASCADE: misleading message

Поиск
Список
Период
Сортировка
От Artiom Makarov
Тема Re: BUG #6048: TRUNCATE vs TRUNCATE CASCADE: misleading message
Дата
Msg-id BANLkTin5M=Y-saC+REkBZEfpibhm-ghDOw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #6048: TRUNCATE vs TRUNCATE CASCADE: misleading message  (Alexey Klyukin <alexk@commandprompt.com>)
Ответы Re: BUG #6048: TRUNCATE vs TRUNCATE CASCADE: misleading message  (Alexey Klyukin <alexk@commandprompt.com>)
Re: BUG #6048: TRUNCATE vs TRUNCATE CASCADE: misleading message  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-bugs
2011/6/2 Alexey Klyukin <alexk@commandprompt.com>:

> What would you expect to happen for TRUNCATE .. CASCADE?
>
> One thing I find potentially surprising is that TRUNCATE CASCADE doesn't =
follow the semantics of 'ON DELETE' clause for the foreign key, i.e. it wou=
ld truncate the dependent table even with ON DELETE RESTRICT foreign key. D=
o we need a similar 'ON TRUNCATE' =A0FK clause?
>

Yes, cascade truncating taked place without ON DELETE RESTRICT
checking. No matter.
Either TRUNCATE must show message with full objects tree - correct
behavior like DROP, or TRUNCATE CASCADE should not delete anything
(strict constraint checking).

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Marc Cousin
Дата:
Сообщение: Re: collation problem on 9.1-beta1
Следующее
От: Alexey Klyukin
Дата:
Сообщение: Re: BUG #6048: TRUNCATE vs TRUNCATE CASCADE: misleading message