Re: WIP: Triggers on VIEWs
От | Dean Rasheed |
---|---|
Тема | Re: WIP: Triggers on VIEWs |
Дата | |
Msg-id | AANLkTi=N8LOAWpFrt2nBm6Ci5owp+nM+DPNo9Z416x7Y@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: WIP: Triggers on VIEWs (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
On 16 August 2010 18:50, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Dean Rasheed <dean.a.rasheed@gmail.com> writes: >> On 15 August 2010 18:38, Dean Rasheed <dean.a.rasheed@gmail.com> wrote: >>> There are still a number of things left todo: >>> - extend ALTER VIEW with enable/disable trigger commands > >> On further reflection, I wonder if the ability to disable VIEW >> triggers is needed/wanted at all. > > AFAIK the only real use for disabling triggers is in connection with > trigger-based replication systems. A view wouldn't be carrying > replication-related triggers anyway, so I think this could certainly > be left out of a first cut. > > You aren't saying that you can see some reason why this couldn't be > added later, if wanted, correct? > Yes. It should be easy to add later if wanted. I just don't see much use for it, and I don't want to add more to an already quite big patch, if it's not really needed. Regards, Dean
В списке pgsql-hackers по дате отправления: