From f503b6a8211f2815a55ab998f50214a86fe73032 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 4 Mar 2004 14:32:12 +0000
Subject: [PATCH] Better document INSTEAD behavior for rules.

---
 doc/src/sgml/ref/create_rule.sgml | 31 +++++++++++++++++++++----------
 1 file changed, 21 insertions(+), 10 deletions(-)

diff --git a/doc/src/sgml/ref/create_rule.sgml b/doc/src/sgml/ref/create_rule.sgml
index fbaa16cecd..412ebcd66b 100644
--- a/doc/src/sgml/ref/create_rule.sgml
+++ b/doc/src/sgml/ref/create_rule.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_rule.sgml,v 1.42 2003/11/29 19:51:38 pgsql Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/create_rule.sgml,v 1.43 2004/03/04 14:32:12 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -42,15 +42,15 @@ CREATE [ OR REPLACE ] RULE <replaceable class="parameter">name</replaceable> AS
    define an alternate action to be performed on insertions, updates,
    or deletions in database tables.  Roughly speaking, a rule causes
    additional commands to be executed when a given command on a given
-   table is executed.  Alternatively, a rule can replace a given
-   command by another, or cause a command not to be executed at all.
-   Rules are used to implement table views as well.  It is important
-   to realize that a rule is really a command transformation
-   mechanism, or command macro.  The transformation happens before the
-   execution of the commands starts.  If you actually want an
-   operation that fires independently for each physical row, you
-   probably want to use a trigger, not a rule.  More information about
-   the rules system is in <xref linkend="rules">.
+   table is executed.  Alternatively, an <literal>INSTEAD</literal>
+   rule can replace a given command by another, or cause a command 
+   not to be executed at all.  Rules are used to implement table 
+   views as well.  It is important to realize that a rule is really 
+   a command transformation mechanism, or command macro.  The 
+   transformation happens before the execution of the commands starts.  
+   If you actually want an operation that fires independently for each 
+   physical row, you probably want to use a trigger, not a rule.  
+   More information about the rules system is in <xref linkend="rules">.
   </para>
   
   <para>
@@ -140,6 +140,17 @@ CREATE [ OR REPLACE ] RULE <replaceable class="parameter">name</replaceable> AS
     </listitem>
    </varlistentry>
 
+   <varlistentry>
+    <term><option>INSTEAD</option></term>
+    <listitem>
+     <para>
+      <literal>INSTEAD</literal> indicates that the commands should be
+      executed <emphasis>instead</> of the original command, not in
+      addition to the original command.
+     </para>
+    </listitem>
+   </varlistentry>
+
    <varlistentry>
     <term><replaceable class="parameter">command</replaceable></term>
     <listitem>
-- 
2.40.0