|
1 |
| -<!-- $PostgreSQL: pgsql/doc/src/sgml/rules.sgml,v 1.51 2007/02/01 19:10:24 momjian Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/rules.sgml,v 1.52 2008/12/16 03:12:08 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="rules">
|
4 | 4 | <title>The Rule System</title>
|
@@ -1869,13 +1869,9 @@ GRANT SELECT ON phone_number TO secretary;
|
1869 | 1869 | </para>
|
1870 | 1870 |
|
1871 | 1871 | <para>
|
1872 |
| - On the other hand, a trigger that is fired on |
1873 |
| - <command>INSERT</command> on a view can do the same as a rule: put |
1874 |
| - the data somewhere else and suppress the insert in the view. But |
1875 |
| - it cannot do the same thing on <command>UPDATE</command> or |
1876 |
| - <command>DELETE</command>, because there is no real data in the |
1877 |
| - view relation that could be scanned, and thus the trigger would |
1878 |
| - never get called. Only a rule will help. |
| 1872 | + On the other hand, a trigger cannot be created on views because |
| 1873 | + there is no real data in a view relation; however INSERT, UPDATE, |
| 1874 | + and DELETE rules can be created on views. |
1879 | 1875 | </para>
|
1880 | 1876 |
|
1881 | 1877 | <para>
|
|