| List: | Internals | « Previous MessageNext Message » | |
| From: | jon | Date: | July 30 2005 7:07am |
| Subject: | bk commit - mysqldoc@docsrva tree (jon:1.3133) | ||
| View as plain text | |||
Below is the list of changes that have just been committed into a local mysqldoc repository of jon. When jon does a push these changes will be propagated to the main repository and, within 24 hours after the push, to the public repository. For information on how to access the public repository see http://www.mysql.com/doc/I/n/Installing_source_tree.html ChangeSet 1.3133 05/07/30 15:07:41 jon@stripped +2 -0 INFORMATION_SCHEMA: Corrections to TRIGGERS table info. refman/information-schema.xml 1.10 05/07/30 15:07:40 jon@stripped +55 -34 Sync. refman-5.0/information-schema.xml 1.10 05/07/30 15:07:40 jon@stripped +36 -15 Corrections to TRIGGERS table info. # This is a BitKeeper patch. What follows are the unified diffs for the # set of deltas contained in the patch. The rest of the patch, the part # that BitKeeper cares about, is below these diffs. # User: jon # Host: gigan. # Root: /home/jon/bk/mysqldoc --- 1.9/refman-5.0/information-schema.xml 2005-07-29 22:42:01 +10:00 +++ 1.10/refman-5.0/information-schema.xml 2005-07-30 15:07:40 +10:00 @@ -3013,9 +3013,13 @@ <para> The <literal>TRIGGERS</literal> table provides information about - triggers. This table was first implemented in MySQL 5.0.10. + triggers. </para> - + + <para> + This table was first implemented in MySQL 5.0.10. + </para> + <para> You must have the <literal>SUPER</literal> privilege to view this table. @@ -3065,16 +3069,16 @@ <row> <entry><literal>TRIGGER_SCHEMA</literal></entry> <entry/> - <entry><literal>NULL</literal></entry> + <entry/> </row> <row> <entry><literal>TRIGGER_NAME</literal></entry> + <entry><literal>Trigger</literal></entry> <entry/> - <entry><literal>NULL</literal></entry> </row> <row> <entry><literal>EVENT_MANIPULATION</literal></entry> - <entry/> + <entry><literal>Event</literal></entry> <entry/> </row> <row> @@ -3089,13 +3093,13 @@ </row> <row> <entry><literal>EVENT_OBJECT_TABLE</literal></entry> - <entry/> + <entry><literal>Table</literal></entry> <entry/> </row> <row> <entry><literal>ACTION_ORDER</literal></entry> <entry/> - <entry><literal>NULL</literal></entry> + <entry><literal>0</literal></entry> </row> <row> <entry><literal>ACTION_CONDITION</literal></entry> @@ -3104,17 +3108,17 @@ </row> <row> <entry><literal>ACTION_STATEMENT</literal></entry> - <entry/> + <entry><literal>Statement</literal></entry> <entry/> </row> <row> <entry><literal>ACTION_ORIENTATION</literal></entry> <entry/> - <entry/> + <entry><literal>ROW</literal></entry> </row> <row> <entry><literal>ACTION_TIMING</literal></entry> - <entry/> + <entry><literal>Timing</literal></entry> <entry/> </row> <row> @@ -3140,7 +3144,8 @@ <row> <entry><literal>CREATED</literal></entry> <entry/> - <entry><literal>NULL</literal></entry> + <entry><literal>NULL</literal> + (<literal>0</literal>)</entry> </row> </tbody> </tgroup> @@ -3175,7 +3180,19 @@ associated with exactly one table. The <literal>EVENT_OBJECT_SCHEMA</literal> and <literal>EVENT_OBJECT_TABLE</literal> columns contain the - database that this table is in, and the table's name. + database in which this table occurs, and the table's name. + </para> + </listitem> + + <listitem> + <para> + The <literal>ACTION_ORDER</literal> statement contains the + ordinal position of the trigger's action within the list + of all similar triggers on the same table. Currently, this + value is always <literal>0</literal>, because it is not + possible to have more than one trigger with the same + <literal>EVENT_MANIPULATION</literal> and + <literal>ACTION_TIMING</literal> on the same table. </para> </listitem> @@ -3209,7 +3226,11 @@ <para> The columns <literal>ACTION_REFERENCE_OLD_ROW</literal> and <literal>ACTION_REFERENCE_NEW_ROW</literal> contain - the old and new column identifiers, respectively. + the old and new column identifiers, respectively. This + means that <literal>ACTION_REFERENCE_OLD_ROW</literal> + always contains the value <literal>'OLD'</literal> and + <literal>ACTION_REFERENCE_NEW_ROW</literal> always + contains the value <literal>'NEW'</literal>. </para> </listitem> @@ -3219,11 +3240,11 @@ <literal>NULL</literal>: <literal>TRIGGER_CATALOG</literal>, <literal>EVENT_OBJECT_CATALOG</literal>, - <literal>ACTION_ORDER</literal>, <literal>ACTION_CONDITION</literal>, <literal>ACTION_REFERENCE_OLD_TABLE</literal>, <literal>ACTION_REFERENCE_NEW_TABLE</literal>, and - <literal>CREATED</literal>, + <literal>CREATED</literal> (displayed for this column as + <literal>0</literal>). </para> </listitem> --- 1.9/refman/information-schema.xml 2005-07-29 22:42:01 +10:00 +++ 1.10/refman/information-schema.xml 2005-07-30 15:07:40 +10:00 @@ -2992,25 +2992,29 @@ </section> <section id="triggers-table"> - + <title id="title-triggers-table">&title-triggers-table;</title> - + <indexterm type="function"> <primary>TRIGGERS</primary> <secondary>INFORMATION_SCHEMA table</secondary> </indexterm> - + <para> The <literal>TRIGGERS</literal> table provides information about - triggers. This table was first implemented in MySQL 5.0.10. + triggers. </para> - + + <para> + This table was first implemented in MySQL 5.0.10. + </para> + <para> You must have the <literal>SUPER</literal> privilege to view this table. </para> - -<!-- + + <!-- NOTE: Table schema as suggested by http://lists.mysql.com/internals/25556: @@ -3034,7 +3038,7 @@ Additional info from WL#1996. --> - + <informaltable> <tgroup cols="3"> <colspec colwidth="40*"/> @@ -3054,16 +3058,16 @@ <row> <entry><literal>TRIGGER_SCHEMA</literal></entry> <entry/> - <entry><literal>NULL</literal></entry> + <entry/> </row> <row> <entry><literal>TRIGGER_NAME</literal></entry> + <entry><literal>Trigger</literal></entry> <entry/> - <entry><literal>NULL</literal></entry> </row> <row> <entry><literal>EVENT_MANIPULATION</literal></entry> - <entry/> + <entry><literal>Event</literal></entry> <entry/> </row> <row> @@ -3078,13 +3082,13 @@ </row> <row> <entry><literal>EVENT_OBJECT_TABLE</literal></entry> - <entry/> + <entry><literal>Table</literal></entry> <entry/> </row> <row> <entry><literal>ACTION_ORDER</literal></entry> <entry/> - <entry><literal>NULL</literal></entry> + <entry><literal>0</literal></entry> </row> <row> <entry><literal>ACTION_CONDITION</literal></entry> @@ -3093,17 +3097,17 @@ </row> <row> <entry><literal>ACTION_STATEMENT</literal></entry> - <entry/> + <entry><literal>Statement</literal></entry> <entry/> </row> <row> <entry><literal>ACTION_ORIENTATION</literal></entry> <entry/> - <entry/> + <entry><literal>ROW</literal></entry> </row> <row> <entry><literal>ACTION_TIMING</literal></entry> - <entry/> + <entry><literal>Timing</literal></entry> <entry/> </row> <row> @@ -3129,17 +3133,18 @@ <row> <entry><literal>CREATED</literal></entry> <entry/> - <entry><literal>NULL</literal></entry> + <entry><literal>NULL</literal> + (<literal>0</literal>)</entry> </row> </tbody> </tgroup> </informaltable> - + <para> <emphasis role="bold">Notes</emphasis>: - + <itemizedlist> - + <listitem> <para> The <literal>TRIGGER_SCHEMA</literal> and @@ -3148,7 +3153,7 @@ trigger name, respectively. </para> </listitem> - + <listitem> <para> The <literal>EVENT_MANIPULATION</literal> column contains @@ -3157,17 +3162,29 @@ <literal>'UPDATE'</literal>. </para> </listitem> - + <listitem> <para> As noted in <xref linkend="triggers"/>, every trigger is associated with exactly one table. The <literal>EVENT_OBJECT_SCHEMA</literal> and <literal>EVENT_OBJECT_TABLE</literal> columns contain the - database that this table is in, and the table's name. + database in which this table occurs, and the table's name. </para> </listitem> - + + <listitem> + <para> + The <literal>ACTION_ORDER</literal> statement contains the + ordinal position of the trigger's action within the list + of all similar triggers on the same table. Currently, this + value is always <literal>0</literal>, because it is not + possible to have more than one trigger with the same + <literal>EVENT_MANIPULATION</literal> and + <literal>ACTION_TIMING</literal> on the same table. + </para> + </listitem> + <listitem> <para> The <literal>ACTION_STATEMENT</literal> column contains @@ -3178,14 +3195,14 @@ UTF-8 encoding. </para> </listitem> - + <listitem> <para> The <literal>ACTION_ORIENTATION</literal> column always contains the value <literal>'ROW'</literal>. </para> </listitem> - + <listitem> <para> The <literal>ACTION_TIMING</literal> column contains one @@ -3193,36 +3210,40 @@ <literal>'AFTER'</literal>. </para> </listitem> - + <listitem> <para> The columns <literal>ACTION_REFERENCE_OLD_ROW</literal> and <literal>ACTION_REFERENCE_NEW_ROW</literal> contain - the old and new column identifiers, respectively. + the old and new column identifiers, respectively. This + means that <literal>ACTION_REFERENCE_OLD_ROW</literal> + always contains the value <literal>'OLD'</literal> and + <literal>ACTION_REFERENCE_NEW_ROW</literal> always + contains the value <literal>'NEW'</literal>. </para> </listitem> - + <listitem> <para> The following columns currently always contain <literal>NULL</literal>: <literal>TRIGGER_CATALOG</literal>, <literal>EVENT_OBJECT_CATALOG</literal>, - <literal>ACTION_ORDER</literal>, <literal>ACTION_CONDITION</literal>, <literal>ACTION_REFERENCE_OLD_TABLE</literal>, <literal>ACTION_REFERENCE_NEW_TABLE</literal>, and - <literal>CREATED</literal>, + <literal>CREATED</literal> (displayed for this column as + <literal>0</literal>). </para> </listitem> - + </itemizedlist> </para> - + <para> See also <xref linkend="show-triggers"/>. </para> - + </section> <section id="other-information-schema-tables">
| Thread | ||
|---|---|---|
| • bk commit - mysqldoc@docsrva tree (jon:1.3133) | jon | 30 Jul |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.540 sec. using MySQL 5.1.14-beta-log