Re: TRIGGER TRUNCATE -- CASCADE or RESTRICT

Поиск
Список
Период
Сортировка
От Albe Laurenz
Тема Re: TRIGGER TRUNCATE -- CASCADE or RESTRICT
Дата
Msg-id A737B7A37273E048B164557ADEF4A58B366193DC@ntex2010i.host.magwien.gv.at
обсуждение исходный текст
Ответ на TRIGGER TRUNCATE -- CASCADE or RESTRICT  (Andreas Ulbrich <andreas.ulbrich@matheversum.de>)
Ответы Re: TRIGGER TRUNCATE -- CASCADE or RESTRICT  (Melvin Davidson <melvin6925@gmail.com>)
Список pgsql-general
Andreas Ulbrich wrote:
> I'm in a handle for a trigger for TRUNCATE. Is it possible to find out
> whether the TRUNCATE TABLE ist called with CASCADE?

I don't think there is.

But you can find out the table where the trigger is defined and examine
if any foreign key constraints are referring to it.

If yes, then the trigger was called with CASCADE.
If no, it might have been called either way, but the effect would be the same.

Yours,
Laurenz Albe

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

Предыдущее
От: Rémi Cura
Дата:
Сообщение: Re: pl/python composite type array as input parameter
Следующее
От: Filipe Pina
Дата:
Сообщение: Re: pl/python composite type array as input parameter