Re: BUG #1953: trigger action on delete

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BUG #1953: trigger action on delete
Дата
Msg-id 17045.1129173620@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: BUG #1953: trigger action on delete  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: BUG #1953: trigger action on delete  (Jan Wieck <JanWieck@Yahoo.com>)
Список 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 по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: BUG #1953: trigger action on delete
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: BUG #1956: Plpgsql top-level DECLARE does not share scope