mirror of
https://github.com/postgres/postgres.git
synced 2025-05-17 06:41:24 +03:00
Documentation fix: s/event_object_name/event_object_table/g
This commit is contained in:
parent
9e4caa5abe
commit
d45693fb55
@ -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">
|
<chapter id="information-schema">
|
||||||
<title>The Information Schema</title>
|
<title>The Information Schema</title>
|
||||||
@ -3822,7 +3822,7 @@ ORDER BY c.ordinal_position;
|
|||||||
</row>
|
</row>
|
||||||
|
|
||||||
<row>
|
<row>
|
||||||
<entry><literal>event_object_name</literal</entry>
|
<entry><literal>event_object_table</literal</entry>
|
||||||
<entry><type>sql_identifier</type></entry>
|
<entry><type>sql_identifier</type></entry>
|
||||||
<entry>Name of the table that the trigger is defined on</entry>
|
<entry>Name of the table that the trigger is defined on</entry>
|
||||||
</row>
|
</row>
|
||||||
@ -3901,7 +3901,7 @@ ORDER BY c.ordinal_position;
|
|||||||
event. As a consequence of these two issues, the primary key of
|
event. As a consequence of these two issues, the primary key of
|
||||||
the view <literal>triggers</literal> is really
|
the view <literal>triggers</literal> is really
|
||||||
<literal>(trigger_catalog, trigger_schema, trigger_name,
|
<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>,
|
<literal>(trigger_catalog, trigger_schema, trigger_name)</literal>,
|
||||||
which is what the SQL standard specifies. Nonetheless, if you
|
which is what the SQL standard specifies. Nonetheless, if you
|
||||||
define your triggers in a manner that conforms with the SQL
|
define your triggers in a manner that conforms with the SQL
|
||||||
|
Loading…
x
Reference in New Issue
Block a user