Update man page to prefer old over current.

diff --git a/doc/src/sgml/ref/create_rule.sgml b/doc/src/sgml/ref/create_rule.sgml
index 6ecbdf4f768b4e8290173370a5fa0dda267cc443..84fd499fafdacc782fd3fcf151082e06102676f8 100644 (file)
--- a/doc/src/sgml/ref/create_rule.sgml
+++ b/doc/src/sgml/ref/create_rule.sgml
@@ -1,5 +1,5 @@
 
 
@@ -71,7 +71,7 @@ CREATE RULE name AS ON 
       
        
    Any SQL WHERE clause, new or
-   current can appear instead of an instance
+   old can appear instead of an instance
    variable whenever an instance variable is permissible in SQL.
        
       
@@ -81,7 +81,7 @@ CREATE RULE name AS ON 
       
        
    Any SQL statement, new or
-   current can appear instead of an instance
+   old can appear instead of an instance
    variable whenever an instance variable is permissible in SQL.
        
       
@@ -133,17 +133,17 @@ CREATE
 
   
    The semantics of a rule is that at the time an individual instance is
-   accessed, inserted, updated, or deleted, there is a current instance (for
+   accessed, inserted, updated, or deleted, there is a old instance (for
    selects, updates and deletes) and a new instance (for inserts and
   updates).
   If the event
    specified in the ON clause and the
    condition specified in the
-   WHERE clause are true for the current instance, the
+   WHERE clause are true for the old instance, the
    action part of the rule is
-   executed. First, however, values from fields in the current instance
+   executed. First, however, values from fields in the old instance
    and/or the new instance are substituted for
-   current.attribute-name
+   old.attribute-name
    and new.attribute-name.
   
 
@@ -167,7 +167,7 @@ CREATE
     condition and
     action parts of a rule,
     they are all considered different tuple variables. More accurately,
-    new and current are the only tuple
+    new and old are the only tuple
     variables that are shared between these clauses. For example, the following
     two rules have the same semantics:
     
@@ -263,7 +263,7 @@ SELECT * FROM emp;
    
    
 CREATE RULE example_1 AS
-    ON UPDATE emp.salary WHERE current.name = "Joe"
+    ON UPDATE emp.salary WHERE old.name = "Joe"
     DO 
    UPDATE emp 
    SET salary = new.salary
@@ -271,7 +271,7 @@ CREATE RULE example_1 AS
    
 
    At the time Joe receives a salary adjustment, the event
-   will become true and Joe's current instance and proposed
+   will become true and Joe's old instance and proposed
    new instance are available to the execution routines.
    Hence, his new salary is substituted into the action part
    of the rule which is subsequently executed.  This propagates
@@ -282,7 +282,7 @@ CREATE RULE example_1 AS
    
 CREATE RULE example_2 AS
     ON SELECT TO EMP.salary
-    WHERE current.name = "Bill"
+    WHERE old.name = "Bill"
     DO INSTEAD
    SELECT emp.salary
    FROM emp
@@ -297,7 +297,7 @@ CREATE RULE example_2 AS
 CREATE RULE example_3 AS
     ON 
    SELECT TO emp.salary
-       WHERE current.dept = "shoe" AND current_user = "Joe"
+       WHERE old.dept = "shoe" AND current_user = "Joe"
     DO INSTEAD NOTHING;