| From: | "Okano, Naoki" <okano(dot)naoki(at)jp(dot)fujitsu(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Adding the optional clause 'AS' in CREATE TRIGGER |
| Date: | 2016-11-16 07:31:00 |
| Message-ID: | 0B4917A40C80E34BBEC4BE1A7A9AB7E276F5D9@g01jpexmbkw05 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> But in any case it would be a serious mistake to do this without first
> implementing CREATE OR REPLACE TRIGGER. I think that's an entirely separate
> proposal and you would be well advised to treat it as such.
I see. There are more problems than I expected...
Let me start with 'OR REPLACE' clause.
At least, adding only 'OR REPLACE' clause has the following advantages.
* It enables users to redefine a trigger in single command.
* The trigger can always be referenced when redefining a trigger.
# But it is not so when using 'DROP' and 'CREATE' commands.
It is useful when users change the function or change the condition of 'WHEN' clause.
Regard,
Okano Naoki
Fujitsu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2016-11-16 07:32:43 | Re: Document how to set up TAP tests for Perl 5.8.8 |
| Previous Message | Noah Misch | 2016-11-16 07:22:46 | Re: pgsql: Add putenv support for msvcrt from Visual Studio 2013 |