Re: Adding the optional clause 'AS' in CREATE TRIGGER - Mailing list pgsql-hackers

From Okano, Naoki
Subject Re: Adding the optional clause 'AS' in CREATE TRIGGER
Date
Msg-id 0B4917A40C80E34BBEC4BE1A7A9AB7E276F5D9@g01jpexmbkw05
Whole thread Raw
In response to Re: Adding the optional clause 'AS' in CREATE TRIGGER  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] Adding the optional clause 'AS' in CREATE TRIGGER
List 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



pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: pgsql: Add putenv support for msvcrt from Visual Studio 2013
Next
From: Noah Misch
Date:
Subject: Re: Document how to set up TAP tests for Perl 5.8.8