| From: | Dmitry Igrishin <dmitigr(at)gmail(dot)com> |
|---|---|
| To: | pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
| Subject: | 36.1 Overview of Trigger Behavior |
| Date: | 2015-08-11 09:51:17 |
| Message-ID: | CAAfz9KNqLXAkygKatsTZTopNhKaCKfLiGkhrqTvEuP-OW_dtRg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitry Igrishin | 2015-08-11 10:18:22 | 36.2 Visibility of Data Changes |
| Previous Message | Haribabu Kommi | 2015-08-11 07:41:15 | Re: BUG #13541: There is a visibility issue when run some DDL and Query. The time window is very shot |