Re: BUG #1953: trigger action on delete - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #1953: trigger action on delete
Date
Msg-id 17045.1129173620@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #1953: trigger action on delete  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #1953: trigger action on delete
List pgsql-bugs
I wrote:
> Bruce Momjian <pgman@candle.pha.pa.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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #1953: trigger action on delete
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #1956: Plpgsql top-level DECLARE does not share scope