36.1 Overview of Trigger Behavior
Subparagraph 8:
I suggest to replace
"BEFORE row-level triggers to execute"
with
"row-level BEFORE triggers to execute"
for consistency.
Subparagraph 14:
While WHEN can be used with INSERT too, I suggest to replace
"However, in an AFTER trigger, the WHEN condition is
evaluated just after the row update occurs, and it determines
whether an event is queued to fire the trigger at the end of
statement."
with
"However, in an AFTER trigger, the WHEN condition is
evaluated just after the row inserted or updated, and it determines
whether an event is queued to fire the trigger at the end of
statement."
--
// Dmitry.
On 08/11/2015 05:51 AM, Dmitry Igrishin wrote:
Subparagraph 8:
I suggest to replace
"BEFORE row-level triggers to execute"
with
"row-level BEFORE triggers to execute"
for consistency.
Fixed that one. Wasn't so sure about the one below.
Subparagraph 14:
While WHEN can be used with INSERT too, I suggest to replace
"However, in an AFTER trigger, the WHEN condition is
evaluated just after the row update occurs, and it determines
whether an event is queued to fire the trigger at the end of
statement."
with
"However, in an AFTER trigger, the WHEN condition is
evaluated just after the row inserted or updated, and it determines
whether an event is queued to fire the trigger at the end of
statement."
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs