Re: WIP: Triggers on VIEWs
Dean Rasheed <dean.a.rasheed@gmail.com>
From: Dean Rasheed <dean.a.rasheed@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org
Date: 2010-08-16T18:35:57Z
Lists: 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