Re: Document transition table triggers are not allowed on views/foreign tables
От | Ashutosh Bapat |
---|---|
Тема | Re: Document transition table triggers are not allowed on views/foreign tables |
Дата | |
Msg-id | CAExHW5sHB=meuDrAw=xf9My0GS9uvLrFSJG8Z=5B489ZF4d3UQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Document transition table triggers are not allowed on views/foreign tables (Etsuro Fujita <etsuro.fujita@gmail.com>) |
Ответы |
Re: Document transition table triggers are not allowed on views/foreign tables
|
Список | pgsql-hackers |
On Wed, Jul 23, 2025 at 4:16 PM Etsuro Fujita <etsuro.fujita@gmail.com> wrote: > > On Tue, Jul 15, 2025 at 4:55 PM Etsuro Fujita <etsuro.fujita@gmail.com> wrote: > > Another thing I noticed about transition tables is that while we > > prohibit transition tables on views/foreign tables, there is no > > description about that in the user-facing documentation. So I would > > like to propose to do $SUBJECT in create_trigger.sgml. Attached is a > > patch for that. I think the restriction should be specified in a manner similar to how restriction on CONSTRAINT option for foreign tables is specified i.e. in " This option is only allowed for an AFTER trigger that is not a constraint trigger; also, if the trigger is an UPDATE trigger, it must not specify a column_name list.". But that sentence is already a bit complex because of ; also, ... part. How about splitting the sentence into two and mentioning restriction like below? "This option is only allowed for an AFTER trigger on tables other than views or foreign tables. The trigger should not be a constraint trigger. If the trigger is an UPDATE trigger, it must not specify a column_name list when using this option." -- Best Wishes, Ashutosh Bapat
В списке pgsql-hackers по дате отправления: