From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Josh Silver <josh(dot)ag(at)paladin(dot)insure> |
Cc: | Pg Docs <pgsql-docs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Clarification of triggers with 'OF column_name' in 'Overview of Trigger Behavior' |
Date: | 2022-05-03 01:55:09 |
Message-ID: | CAKFQuwZg7rh9UsyLEn7+=fc-fvT2f4MDtbFehvCvrGte+YUTpQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Mon, May 2, 2022 at 6:33 PM Josh Silver <josh(dot)ag(at)paladin(dot)insure> wrote:
>
> and the 'Overview of Trigger Behavior pages says of before triggers
>
>> In row-level triggers the WHEN condition can examine the old and/or new
>> values of columns of the row. (Statement-level triggers can also have
>> WHEN conditions, although the feature is not so useful for them.) In a
>> BEFORE trigger, the WHEN condition is evaluated just before the function
>> is or would be executed, so using WHEN is not materially different from
>> testing the same condition at the beginning of the trigger function.
>
>
> but does not even mention column specific triggers by name.
>
>
The previous paragraph reads in part:
"If more than one trigger is defined for the same event on the same
relation, the triggers will be fired in alphabetical order by trigger name."
I'll say that we don't provide a granular definition of what an "event" is
here - namely the "INSERT/UPDATE/DELETE/SELECT + any column limitation".
So, it is covered if you understand the column aspect is rolled into
"trigger event".
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2022-05-03 02:10:53 | Re: Clarification of triggers with 'OF column_name' in 'Overview of Trigger Behavior' |
Previous Message | Josh Silver | 2022-05-03 01:32:58 | Re: Clarification of triggers with 'OF column_name' in 'Overview of Trigger Behavior' |