From: | Euler Taveira <euler(at)timbira(dot)com(dot)br> |
---|---|
To: | igorludi(at)gmail(dot)com |
Cc: | pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Typo in trigger docs |
Date: | 2017-05-25 15:03:36 |
Message-ID: | CAHE3wgjo1HY2AhgJJ2sFpAqmOqLMXve+Ad0sPbpRnzLfeV8+DA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
2017-05-23 7:40 GMT-03:00 <igorludi(at)gmail(dot)com>:
>
> I believe that ("statement" is wrong):
>
> "Row-level BEFORE triggers fire immediately before a particular row is
> operated on, while row-level AFTER triggers fire at the end of the
> statement
> (but before any statement-level AFTER triggers)."
>
>
> should be:
>
> "Row-level BEFORE triggers fire immediately before a particular row is
> operated on, while row-level AFTER triggers fire after the row has been
> operated on (but before any statement-level AFTER triggers)."
The documentation is correct. Execute the attached script to understand how
trigger visibility works. AFTER row-level triggers will see all data
changes [1].
[1] https://www.postgresql.org/docs/9.6/static/trigger-datachanges.html
--
Euler Taveira Timbira -
http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
<http://www.timbira.com.br>
Attachment | Content-Type | Size |
---|---|---|
a.sql | application/sql | 1.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2017-05-25 15:44:12 | Re: Legal Notice page in 10 not "backwards compatible" in online docs |
Previous Message | Magnus Hagander | 2017-05-25 14:14:48 | Re: Legal Notice page in 10 not "backwards compatible" in online docs |