Re: CREATE OR REPLACE TRIGGER - Mailing list pgsql-patches

From Tom Lane
Subject Re: CREATE OR REPLACE TRIGGER
Date
Msg-id 13124.1029079659@sss.pgh.pa.us
Whole thread Raw
In response to Re: CREATE OR REPLACE TRIGGER  (Gavin Sherry <swm@linuxworld.com.au>)
Responses Re: CREATE OR REPLACE TRIGGER  (Gavin Sherry <swm@linuxworld.com.au>)
List pgsql-patches
Gavin Sherry <swm@linuxworld.com.au> writes:
> On Sun, 11 Aug 2002, Tom Lane wrote:
>> Why would we need that, given that we now have CREATE OR REPLACE
>> FUNCTION?  It's not like anything could depend on a trigger
>> (other than FK constraints, and I don't think I want people replacing
>> trigger definitions that are part of an FK constraint...)

> I thought it conceivable that one may want to point the trigger at a
> different function, change BEFORE or AFTER, or change the event(s) upon
> which the trigger fires.

But there is no reason you can't just drop and recreate the trigger
to do those things.

Given the lack of popular demand (I don't think I've yet heard anyone
ask for this feature), I can't get excited about expending code bulk
and complexity on it --- the patch seems to make CreateTrigger
significantly messier, and that will cost us in maintenance effort
down the road.

            regards, tom lane

pgsql-patches by date:

Previous
From: Gavin Sherry
Date:
Subject: Re: CREATE OR REPLACE TRIGGER
Next
From: Gavin Sherry
Date:
Subject: Re: CREATE OR REPLACE TRIGGER