From: Peter Eisentraut Date: Thu, 8 Dec 2005 20:48:10 +0000 (+0000) Subject: Documentation fix: s/event_object_name/event_object_table/g X-Git-Tag: REL8_2_BETA1~1787 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=dbd1c1abd64aaaf78eaa3cb84f2e0180754e3258;p=postgresql Documentation fix: s/event_object_name/event_object_table/g --- diff --git a/doc/src/sgml/information_schema.sgml b/doc/src/sgml/information_schema.sgml index 7b97c70ed4..1061761371 100644 --- a/doc/src/sgml/information_schema.sgml +++ b/doc/src/sgml/information_schema.sgml @@ -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