| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Jan Wieck <JanWieck(at)Yahoo(dot)com>, incheol yang <zoar(at)paran(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #1953: trigger action on delete |
| Date: | 2005-10-13 03:20:20 |
| Message-ID: | 17045.1129173620@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
I wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>> It isn't so much the alphabetical order, since there is only one
>> trigger, but the concept that we now group all the _before_ triggers
>> before the _after_ triggers.
> But we've always done that. Has the example ever been correct?
> I was intending to try it on older versions, but I don't actually
> think it's ever acted like the docs said.
After digging in the CVS archives, I find that it did work like that
up till this 7.0 patch:
1999-09-29 12:05 wieck
This is part #1 for of the DEFERRED CONSTRAINT TRIGGER support.
Implements the CREATE CONSTRAINT TRIGGER and SET CONSTRAINTS
commands.
So the example was probably correct when put in, but no one's noticed it
was wrong since 7.0 :-(
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-10-13 03:32:20 | Re: BUG #1956: Plpgsql top-level DECLARE does not share scope |
| Previous Message | Tom Lane | 2005-10-13 03:04:38 | Re: BUG #1953: trigger action on delete |