| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Why no INSTEAD OF triggers on tables? |
| Date: | 2013-12-17 03:53:08 |
| Message-ID: | CA+TgmoZPkiq8H0Jn2f8BrTzSwu0nCpzVWaiq-=zd7X8tVW8hRg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Dec 16, 2013 at 9:16 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> On 12/16/2013 04:22 PM, Tom Lane wrote:
>> Josh Berkus <josh(at)agliodbs(dot)com> writes:
>>> I've looked in the archives, but I can't find a reason why INSTEAD OF
>>> triggers were never enabled for tables.
>>
>> What would that mean exactly? And how would you do the actual update
>> when it came time to?
>
> Well, I'm specifically thinking of master partition tables. In that
> case, we really want an INSTEAD OF trigger.
/me scratches head.
So, put a BEFORE trigger, and make it return NULL. Same effect,
different notation.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-12-17 04:01:16 | Re: Changeset Extraction Interfaces |
| Previous Message | Robert Haas | 2013-12-17 03:52:00 | Re: planner missing a trick for foreign tables w/OR conditions |