diff options
| author | Peter Eisentraut <peter_e@gmx.net> | 2016-08-03 12:29:15 -0400 |
|---|---|---|
| committer | Peter Eisentraut <peter_e@gmx.net> | 2016-08-03 12:29:15 -0400 |
| commit | 69bdfc4090816d77a3d08684a30bfb05f8b1e104 (patch) | |
| tree | 938c453db669f5fa9487a87120470c6b6ec2e78d | |
| parent | c93d8737be47667091b36f5852fd706146514008 (diff) | |
| download | postgresql-69bdfc4090816d77a3d08684a30bfb05f8b1e104.tar.gz postgresql-69bdfc4090816d77a3d08684a30bfb05f8b1e104.zip | |
doc: Change recommendation to put NOTIFY into a rule
Suggest a statement trigger instead.
| -rw-r--r-- | doc/src/sgml/ref/notify.sgml | 2 |
1 files changed, 1 insertions, 1 deletions
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> |