Re: Should this require CASCADE?
От | Tom Lane |
---|---|
Тема | Re: Should this require CASCADE? |
Дата | |
Msg-id | 12013.1026357540@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Should this require CASCADE? (Bruce Momjian <pgman@candle.pha.pa.us>) |
Ответы |
Re: Should this require CASCADE?
Re: Should this require CASCADE? |
Список | pgsql-hackers |
Bruce Momjian <pgman@candle.pha.pa.us> writes: > As far as this question, seems with no RESTRICT/CASCADE, it fails, with > RESTRICT it drops the trigger, and with CASCADE it drops the referencing > table. Is that accurate? Not at all. CASCADE would drop the foreign key constraint (including the triggers that implement it), but not the other table. In my mind the issue is whether RESTRICT mode should do the same, or report an error. I'm not eager to accept the idea that DROP-without-either-option should behave in some intermediate fashion. I want it to be the same as RESTRICT. regards, tom lane
В списке pgsql-hackers по дате отправления: