postgres.git / summary / log / commit / refs

commit    69bdfc4090816d77a3d08684a30bfb05f8b1e104
Author:   Peter Eisentraut <peter_e@gmx.net>
Date:     Wed Aug 03 16:29:15 2016 +0000

    doc: Change recommendation to put NOTIFY into a rule
    
    Suggest a statement trigger instead.


 doc/src/sgml/ref/notify.sgml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/src/sgml/ref/notify.sgml b/doc/src/sgml/ref/notify.sgml
index 4dd560838b1..3389aa055ca 100644
--- a/doc/src/sgml/ref/notify.sgml
+++ b/doc/src/sgml/ref/notify.sgml
@@ -68,7 +68,7 @@ NOTIFY <replaceable class="PARAMETER">channel</replaceable> [ , <replaceable cla
   <para>
    When <command>NOTIFY</command> is used to signal the occurrence of changes
    to a particular table, a useful programming technique is to put the
-   <command>NOTIFY</command> in a rule that is triggered by table updates.
+   <command>NOTIFY</command> in a statement trigger that is triggered by table updates.
    In this way, notification happens automatically when the table is changed,
    and the application programmer cannot accidentally forget to do it.
   </para>


[parent: c93d8737be47]