| 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:01:16 |
| Message-ID: | 12915.1029078076@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:
> 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...)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2002-08-11 15:05:02 | Re: stand-alone composite types patch (was [HACKERS] Proposal: |
| Previous Message | Florian Weimer | 2002-08-11 15:00:40 | Re: [SECURITY] DoS attack on backend possible (was: Re: |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2002-08-11 15:05:02 | Re: stand-alone composite types patch (was [HACKERS] Proposal: |
| Previous Message | Tom Lane | 2002-08-11 14:44:17 | Re: stand-alone composite types patch (was [HACKERS] Proposal: |