Re: Why no INSTEAD OF triggers on tables?
От | Robert Haas |
---|---|
Тема | Re: Why no INSTEAD OF triggers on tables? |
Дата | |
Msg-id | CA+TgmoZPkiq8H0Jn2f8BrTzSwu0nCpzVWaiq-=zd7X8tVW8hRg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Why no INSTEAD OF triggers on tables? (Josh Berkus <josh@agliodbs.com>) |
Ответы |
Re: Why no INSTEAD OF triggers on tables?
|
Список | pgsql-hackers |
On Mon, Dec 16, 2013 at 9:16 PM, Josh Berkus <josh@agliodbs.com> wrote: > On 12/16/2013 04:22 PM, Tom Lane wrote: >> Josh Berkus <josh@agliodbs.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
В списке pgsql-hackers по дате отправления: