pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Typo in trigger docs
2+ messages / 2 participants
[nested] [flat]

* Typo in trigger docs
@ 2017-05-23 10:40  igorludi@gmail.com
  0 siblings, 1 reply; 2+ messages in thread

From: igorludi@gmail.com @ 2017-05-23 10:40 UTC (permalink / raw)
  To: pgsql-docs

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/9.6/static/trigger-definition.html
Description:


https://www.postgresql.org/docs/9.6/static/trigger-definition.html


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)."


BR,

Igor

-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs


^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: Typo in trigger docs
@ 2017-05-25 15:03  Euler Taveira <euler@timbira.com.br>
  parent: igorludi@gmail.com
  0 siblings, 0 replies; 2+ messages in thread

From: Euler Taveira @ 2017-05-25 15:03 UTC (permalink / raw)
  To: igorludi@gmail.com; +Cc: pgsql-docs

2017-05-23 7:40 GMT-03:00 <igorludi@gmail.com>:

>
> I believe that (&quot;statement&quot; is wrong):
>
> &quot;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).&quot;
>
>
> should be:
>
> &quot;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).&quot;


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;

-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

Attachments:

  a.sql (application/sql, 1.5K) download

^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2017-05-25 15:03 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2017-05-23 10:40 Typo in trigger docs igorludi@gmail.com
2017-05-25 15:03 ` Euler Taveira <euler@timbira.com.br>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox