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

From Gavin Sherry
Subject Re: CREATE OR REPLACE TRIGGER
Date
Msg-id Pine.LNX.4.21.0208120105040.14282-100000@linuxworld.com.au
Whole thread Raw
In response to Re: CREATE OR REPLACE TRIGGER  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: CREATE OR REPLACE TRIGGER  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
On Sun, 11 Aug 2002, Tom Lane wrote:

> Gavin Sherry <swm@linuxworld.com.au> writes:
> > Attached is a basic patch implementing create or replace trigger.
>
> 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.

Gavin


pgsql-patches by date:

Previous
From: Joe Conway
Date:
Subject: Re: stand-alone composite types patch (was [HACKERS] Proposal:
Next
From: Tom Lane
Date:
Subject: Re: CREATE OR REPLACE TRIGGER