> 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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
