Documentation fix: s/event_object_name/event_object_table/g
authorPeter Eisentraut
Thu, 8 Dec 2005 20:48:10 +0000 (20:48 +0000)
committerPeter Eisentraut
Thu, 8 Dec 2005 20:48:10 +0000 (20:48 +0000)
doc/src/sgml/information_schema.sgml

index 7b97c70ed4e32d218b32472f8cb602ac14895e52..10617613716e15aa86ef29469ba38f8f4a375a90 100644 (file)
@@ -1,4 +1,4 @@
-
+
 
 
  The Information Schema
@@ -3822,7 +3822,7 @@ ORDER BY c.ordinal_position;
      
 
      
-      event_object_name
+      event_object_table
       sql_identifier
       Name of the table that the trigger is defined on
      
@@ -3901,7 +3901,7 @@ ORDER BY c.ordinal_position;
    event.  As a consequence of these two issues, the primary key of
    the view triggers is really
    (trigger_catalog, trigger_schema, trigger_name,
-   event_object_name, event_manipulation) instead of
+   event_object_table, event_manipulation) instead of
    (trigger_catalog, trigger_schema, trigger_name),
    which is what the SQL standard specifies.  Nonetheless, if you
    define your triggers in a manner that conforms with the SQL