| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WIP: Triggers on VIEWs |
| Date: | 2010-08-16 17:50:28 |
| Message-ID: | 18215.1281981028@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> writes:
> On 15 August 2010 18:38, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)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?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-08-16 18:11:12 | Re: Todays git migration results |
| Previous Message | Tom Lane | 2010-08-16 17:47:25 | Re: Git migration timeline |