| From: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: CREATE OR REPLACE TRIGGER |
| Date: | 2002-08-11 15:09:58 |
| Message-ID: | Pine.LNX.4.21.0208120105040.14282-100000@linuxworld.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Sun, 11 Aug 2002, Tom Lane wrote:
> Gavin Sherry <swm(at)linuxworld(dot)com(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-08-11 15:12:57 | Re: Open 7.3 items |
| Previous Message | Joe Conway | 2002-08-11 15:05:02 | Re: stand-alone composite types patch (was [HACKERS] Proposal: |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-08-11 15:27:39 | Re: CREATE OR REPLACE TRIGGER |
| Previous Message | Joe Conway | 2002-08-11 15:05:02 | Re: stand-alone composite types patch (was [HACKERS] Proposal: |