|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/information_schema.sgml,v 1.22 2005/10/15 20:12:32 neilc Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/information_schema.sgml,v 1.23 2005/12/08 20:48:10 petere Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="information-schema"> |
4 | 4 | <title>The Information Schema</title> |
@@ -3822,7 +3822,7 @@ ORDER BY c.ordinal_position; |
3822 | 3822 | </row> |
3823 | 3823 |
|
3824 | 3824 | <row> |
3825 | | - <entry><literal>event_object_name</literal></entry> |
| 3825 | + <entry><literal>event_object_table</literal></entry> |
3826 | 3826 | <entry><type>sql_identifier</type></entry> |
3827 | 3827 | <entry>Name of the table that the trigger is defined on</entry> |
3828 | 3828 | </row> |
@@ -3901,7 +3901,7 @@ ORDER BY c.ordinal_position; |
3901 | 3901 | event. As a consequence of these two issues, the primary key of |
3902 | 3902 | the view <literal>triggers</literal> is really |
3903 | 3903 | <literal>(trigger_catalog, trigger_schema, trigger_name, |
3904 | | -event_object_name, event_manipulation)</literal> instead of |
| 3904 | +event_object_table, event_manipulation)</literal> instead of |
3905 | 3905 | <literal>(trigger_catalog, trigger_schema, trigger_name)</literal>, |
3906 | 3906 | which is what the SQL standard specifies. Nonetheless, if you |
3907 | 3907 | define your triggers in a manner that conforms with the SQL |
|