Re: ALTER TRIGGER DISABLE/ENABLE
От | Tino Wildenhain |
---|---|
Тема | Re: ALTER TRIGGER DISABLE/ENABLE |
Дата | |
Msg-id | 316748750.1038310663@liza обсуждение исходный текст |
Ответ на | ALTER TRIGGER DISABLE/ENABLE (Christoph Dalitz <christoph.dalitz@hs-niederrhein.de>) |
Список | pgsql-general |
Hi, --On Dienstag, 26. November 2002 09:43 +0100 Christoph Dalitz <christoph.dalitz@hs-niederrhein.de> wrote: > Hello, > > while there have been suggested some hacks on the system catalog > for disabling/enabling triggers, these have two serious disadvantages: > > - they cannot be done by the owner of the trigger > (only the DBA has write access to the system catalog) > - messing in the system catalog for simple DB schema changes makes > most users feel uneasy > > Oracle has an SQL command "ALTER TRIGGER triggername DISABLE|ENABLE". > Were it possible to put this command on the TODO list for a future PG > release? Sounds reasonable, but should a form ALTER TABLE DISABLE|ENABLE [ALL] TRIGGER or something like that be available too? This could be done for RI-Triggers on a table while restoring data. Regards Tino
В списке pgsql-general по дате отправления: