database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-17 06:41:24 +03:00
Code

Documentation fix: s/event_object_name/event_object_table/g

Browse Source
This commit is contained in:
Peter Eisentraut 2005-12-08 20:44:18 +00:00
parent 9e4caa5abe
commit d45693fb55
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/src/sgml/information_schema.sgml
View File

@ -1,4 +1,4 @@
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/information_schema.sgml,v 1.10.2.3 2004/06/13 17:51:16 tgl Exp $ -->
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/information_schema.sgml,v 1.10.2.4 2005/12/08 20:44:18 petere Exp $ -->
<chapter id="information-schema">
<title>The Information Schema</title>
@ -3822,7 +3822,7 @@ ORDER BY c.ordinal_position;
</row>
<row>
<entry><literal>event_object_name</literal</entry>
<entry><literal>event_object_table</literal</entry>
<entry><type>sql_identifier</type></entry>
<entry>Name of the table that the trigger is defined on</entry>
</row>
@ -3901,7 +3901,7 @@ ORDER BY c.ordinal_position;
event. As a consequence of these two issues, the primary key of
the view <literal>triggers</literal> is really
<literal>(trigger_catalog, trigger_schema, trigger_name,
event_object_name, event_manipulation)</literal> instead of
event_object_table, event_manipulation)</literal> instead of
<literal>(trigger_catalog, trigger_schema, trigger_name)</literal>,
which is what the SQL standard specifies. Nonetheless, if you
define your triggers in a manner that conforms with the SQL