Re: Inheritance of foregn key constraints - dropping isinternal triggers by a
От | Andrzej Mazurkiewicz |
---|---|
Тема | Re: Inheritance of foregn key constraints - dropping isinternal triggers by a |
Дата | |
Msg-id | 2729604.PO7CB1FP43@tata обсуждение исходный текст |
Ответ на | Re: Inheritance of foregn key constraints. (Fabrízio de Royes Mello <fabriziomello@gmail.com>) |
Список | pgsql-hackers |
On Tuesday 01 of April 2014 11:06:00 you wrote: > On Tue, Apr 1, 2014 at 9:13 AM, Andrzej Mazurkiewicz < > > andrzej@mazurkiewicz.org> wrote: > > It seems that if the trigger is internal (tgisinternal = true) it is not > > visible to the DROP TRIGGER command. So it cannot be deleted using DROP > > TRIGGER command, although the dependency type is DEPENDENCY_AUTOMATIC > > Try using a quoted identifier: > > DROP TRIGGER "RI_ConstraintTrigger_c_19322" ON master; > > Regards, > > -- > Fabrízio de Royes Mello > Consultoria/Coaching PostgreSQL Good Afternoon. Sorry for my mistake. I have forgotten about modifications of names to lower case. The owner of a table can drop trigger using the command DROP TRIGGER. However, where I can find information on philosophy of that approach. For me internal triggers are marked isinternal not to be accessed using SQL commands. Removing internals, f. e. FK triggers, by hand by a programmer and even by an administrator seems not to be a recommended practice. Kind Regards Andrzej Mazurkiewicz
В списке pgsql-hackers по дате отправления: