I only wondered because I had a situation recently where I had to create a trigger based on an event in an application (don't want to initiate the trigger processing until other stuff has happened in the environment), and if I'd had the CREATE OR REPLACE I could have avoided the step of checking if the trigger existed already (I had CREAT OR REPLACE on the trigger function). But that's certainly not a hardship, and probably more "correct", anyway!
Thanks. - DAP >-----Original Message----- >From: Tom Lane [mailto:[EMAIL PROTECTED] >Sent: Sunday, March 27, 2005 1:50 AM >To: David Parker >Cc: postgres general >Subject: Re: [GENERAL] create or replace trigger? > >"David Parker" <[EMAIL PROTECTED]> writes: >> Is there a technical reason that the "or replace" syntax isn't >> supported for CREATE TRIGGER? > >Lack of round tuits. > >Does it seem like a high priority to you? I'd think that >changes in the trigger function (which you *can* do with >CREATE OR REPLACE) would be much more common than alterations >in the trigger parameters per se. > > regards, tom lane > ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
