From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
Cc: | pgsql-patches(at)postgresql(dot)org |
Subject: | Re: CREATE OR REPLACE TRIGGER |
Date: | 2002-08-11 15:27:39 |
Message-ID: | 13124.1029079659@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Gavin Sherry <swm(at)linuxworld(dot)com(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Gavin Sherry | 2002-08-11 15:39:14 | Re: CREATE OR REPLACE TRIGGER |
Previous Message | Tom Lane | 2002-08-11 15:12:57 | Re: Open 7.3 items |
From | Date | Subject | |
---|---|---|---|
Next Message | Gavin Sherry | 2002-08-11 15:39:14 | Re: CREATE OR REPLACE TRIGGER |
Previous Message | Gavin Sherry | 2002-08-11 15:09:58 | Re: CREATE OR REPLACE TRIGGER |