diff options
| author | Bruce Momjian <bruce@momjian.us> | 2001-11-29 22:18:14 +0000 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2001-11-29 22:18:14 +0000 |
| commit | d1a2a01f3853995905ff9040f4ca7ab47de6aef8 (patch) | |
| tree | 6737aa0b7763dc4c5ec0a372cf56e910834f2008 | |
| parent | 636a939fe54d317099e8574997d96975a54c792b (diff) | |
| download | postgresql-d1a2a01f3853995905ff9040f4ca7ab47de6aef8.tar.gz postgresql-d1a2a01f3853995905ff9040f4ca7ab47de6aef8.zip | |
Add mention of no SELECT triggers.
| -rw-r--r-- | doc/src/sgml/ref/create_trigger.sgml | 32 |
1 files changed, 17 insertions, 15 deletions
diff --git a/doc/src/sgml/ref/create_trigger.sgml b/doc/src/sgml/ref/create_trigger.sgml index d6e2905a49b..fb074c2983f 100644 --- a/doc/src/sgml/ref/create_trigger.sgml +++ b/doc/src/sgml/ref/create_trigger.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_trigger.sgml,v 1.18 2001/11/19 03:58:25 tgl Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_trigger.sgml,v 1.19 2001/11/29 22:18:14 momjian Exp $ Postgres documentation --> @@ -117,20 +117,22 @@ CREATE </para> <para> - The trigger can be specified to fire either before BEFORE the - operation is attempted on a tuple (before constraints - are checked and the <command>INSERT</command>, <command>UPDATE</command> or - <command>DELETE</command> is attempted) or - AFTER the operation has been attempted (e.g., after constraints - are checked and the <command>INSERT</command>, - <command>UPDATE</command> or <command>DELETE</command> has - completed). If the - trigger fires before the event, the trigger may - skip the operation for the current tuple, or change the tuple - being inserted (for <command>INSERT</command> and - <command>UPDATE</command> operations only). If - the trigger fires after the event, all changes, including the - last insertion, update, or deletion, are <quote>visible</quote> to the trigger. + The trigger can be specified to fire either before BEFORE the + operation is attempted on a tuple (before constraints are checked and + the <command>INSERT</command>, <command>UPDATE</command> or + <command>DELETE</command> is attempted) or AFTER the operation has + been attempted (e.g., after constraints are checked and the + <command>INSERT</command>, <command>UPDATE</command> or + <command>DELETE</command> has completed). If the trigger fires before + the event, the trigger may skip the operation for the current tuple, + or change the tuple being inserted (for <command>INSERT</command> and + <command>UPDATE</command> operations only). If the trigger fires + after the event, all changes, including the last insertion, update, + or deletion, are <quote>visible</quote> to the trigger. + </para> + <para> + <command>SELECT</command> does not modify any rows so you can not + create <command>SELECT</command> triggers. </para> <para> |