bk commit - mysqldoc@docsrva tree (paul:1.3139)

#1

Below is the list of changes that have just been committed into a local
mysqldoc repository of paul. When paul 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/Install...urce_tree.html

ChangeSet
1.3139 05/07/26 23:50:58 paul (AT) frost (DOT) snake.net +11 -0
Kill Texinfo quotes.

refman/maxdb.xml
1.4 05/07/26 23:50:56 paul (AT) frost (DOT) snake.net +6 -5
Kill Texinfo quotes.

refman/information-schema.xml
1.7 05/07/26 23:50:56 paul (AT) frost (DOT) snake.net +85 -85
Kill Texinfo quotes.

refman/extending-mysql.xml
1.5 05/07/26 23:50:56 paul (AT) frost (DOT) snake.net +10 -10
Kill Texinfo quotes.

refman/client-side-scripts.xml
1.8 05/07/26 23:50:55 paul (AT) frost (DOT) snake.net +1 -1
Kill Texinfo quotes.

refman-5.0/maxdb.xml
1.4 05/07/26 23:50:55 paul (AT) frost (DOT) snake.net +6 -5
Kill Texinfo quotes.

refman-5.0/information-schema.xml
1.7 05/07/26 23:50:55 paul (AT) frost (DOT) snake.net +134 -127
Kill Texinfo quotes.

refman-5.0/extending-mysql.xml
1.5 05/07/26 23:50:55 paul (AT) frost (DOT) snake.net +10 -10
Kill Texinfo quotes.

refman-5.0/client-side-scripts.xml
1.8 05/07/26 23:50:55 paul (AT) frost (DOT) snake.net +1 -1
Kill Texinfo quotes.

refman-4.1/maxdb.xml
1.4 05/07/26 23:50:54 paul (AT) frost (DOT) snake.net +6 -5
Kill Texinfo quotes.

refman-4.1/extending-mysql.xml
1.5 05/07/26 23:50:54 paul (AT) frost (DOT) snake.net +10 -10
Kill Texinfo quotes.

refman-4.1/client-side-scripts.xml
1.6 05/07/26 23:50:54 paul (AT) frost (DOT) snake.net +1 -1
Kill Texinfo quotes.

# 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: paul
# Host: frost.snake.net
# Root: /Volumes/frost2/MySQL/bk/mysqldoc

--- 1.5/refman-4.1/client-side-scripts.xml 2005-07-19 10:57:14 -05:00
+++ 1.6/refman-4.1/client-side-scripts.xml 2005-07-26 23:50:54 -05:00
@@ -4259,7 +4259,7 @@
first <command>mysql</command> process terminates, the server
drops the temporary table. When the second
<command>mysql</command> process attempts to use the table, the
- server reports ``unknown table.''
+ server reports <quote>unknown table.</quote>
</para>

<para>

--- 1.4/refman-4.1/extending-mysql.xml 2005-07-19 10:57:15 -05:00
+++ 1.5/refman-4.1/extending-mysql.xml 2005-07-26 23:50:54 -05:00
@@ -830,11 +830,11 @@
<para>
For each function that you want to use in SQL statements, you
should define corresponding C (or C++) functions. In the
- following discussion, the name ``xxx'' is used for an example
- function name. To distinguish between SQL and C/C++ usage,
- <literal>XXX()</literal> (uppercase) indicates an SQL function
- call, and <literal>xxx()</literal> (lowercase) indicates a C/C++
- function call.
+ following discussion, the name <quote>xxx</quote> is used for an
+ example function name. To distinguish between SQL and C/C++
+ usage, <literal>XXX()</literal> (uppercase) indicates an SQL
+ function call, and <literal>xxx()</literal> (lowercase)
+ indicates a C/C++ function call.
</para>

<para>
@@ -2130,11 +2130,11 @@
lines to <filename>sql_yacc.yy</filename>. One indicates the
preprocessor symbol that <command>yacc</command> should
define (this should be added at the beginning of the file).
- Then define the function parameters and add an ``item'' with
- these parameters to the <literal>simple_expr</literal>
- parsing rule. For an example, check all occurrences of
- <literal>ATAN</literal> in <filename>sql_yacc.yy</filename>
- to see how this is done.
+ Then define the function parameters and add an
+ <quote>item</quote> with these parameters to the
+ <literal>simple_expr</literal> parsing rule. For an example,
+ check all occurrences of <literal>ATAN</literal> in
+ <filename>sql_yacc.yy</filename> to see how this is done.
</para>
</listitem>

--- 1.3/refman-4.1/maxdb.xml 2005-07-19 10:57:19 -05:00
+++ 1.4/refman-4.1/maxdb.xml 2005-07-26 23:50:54 -05:00
@@ -253,7 +253,7 @@
</row>
<row>
<entry><literal>@</literal></entry>
- <entry>Can prefix identifier, like ``@table''</entry>
+ <entry>Can prefix identifier, like <quote>@table</quote></entry>
<entry>Not allowed</entry>
</row>
<row>
@@ -449,11 +449,12 @@
</row>
<row>
<entry><literal>LIKE</literal> wildcards</entry>
- <entry>MaxDB supports ``%'', ``_'', ``Control-underline'', ``Control-up
- arrow'', ``*'', and ``?'' as wildcards in
+ <entry>MaxDB supports <quote>%</quote>, <quote>_</quote>,
+ <quote>Control-underline</quote>, <quote>Control-up
+ arrow</quote>, <quote>*</quote>, and <quote>?</quote> as
+ wildcards in <literal>LIKE</literal> comparisons</entry>
+ <entry>MySQL supports <quote>%</quote>, and <quote>_</quote> as wildcards in
<literal>LIKE</literal> comparisons</entry>
- <entry>MySQL supports ``%'', and ``_'' as wildcards in <literal>LIKE</literal>
- comparisons</entry>
</row>
<row>
<entry><literal>LPAD()</literal></entry>

--- 1.7/refman-5.0/client-side-scripts.xml 2005-07-26 14:51:06 -05:00
+++ 1.8/refman-5.0/client-side-scripts.xml 2005-07-26 23:50:55 -05:00
@@ -4280,7 +4280,7 @@
first <command>mysql</command> process terminates, the server
drops the temporary table. When the second
<command>mysql</command> process attempts to use the table, the
- server reports <quote><literal>unknown table</literal></quote>.
+ server reports <quote>unknown table</quote>.
</para>

<para>

--- 1.4/refman-5.0/extending-mysql.xml 2005-07-19 10:57:28 -05:00
+++ 1.5/refman-5.0/extending-mysql.xml 2005-07-26 23:50:55 -05:00
@@ -829,11 +829,11 @@
<para>
For each function that you want to use in SQL statements, you
should define corresponding C (or C++) functions. In the
- following discussion, the name ``xxx'' is used for an example
- function name. To distinguish between SQL and C/C++ usage,
- <literal>XXX()</literal> (uppercase) indicates an SQL function
- call, and <literal>xxx()</literal> (lowercase) indicates a C/C++
- function call.
+ following discussion, the name <quote>xxx</quote> is used for an
+ example function name. To distinguish between SQL and C/C++
+ usage, <literal>XXX()</literal> (uppercase) indicates an SQL
+ function call, and <literal>xxx()</literal> (lowercase)
+ indicates a C/C++ function call.
</para>

<para>
@@ -2129,11 +2129,11 @@
lines to <filename>sql_yacc.yy</filename>. One indicates the
preprocessor symbol that <command>yacc</command> should
define (this should be added at the beginning of the file).
- Then define the function parameters and add an ``item'' with
- these parameters to the <literal>simple_expr</literal>
- parsing rule. For an example, check all occurrences of
- <literal>ATAN</literal> in <filename>sql_yacc.yy</filename>
- to see how this is done.
+ Then define the function parameters and add an
+ <quote>item</quote> with these parameters to the
+ <literal>simple_expr</literal> parsing rule. For an example,
+ check all occurrences of <literal>ATAN</literal> in
+ <filename>sql_yacc.yy</filename> to see how this is done.
</para>
</listitem>

--- 1.6/refman-5.0/information-schema.xml 2005-07-20 13:55:25 -05:00
+++ 1.7/refman-5.0/information-schema.xml 2005-07-26 23:50:55 -05:00
@@ -39,11 +39,20 @@
</para>

<para>
- <firstterm>Metadata</firstterm> is data about the data, such as the
- name of a database or table, the data type of a column, or access
- privileges. Other terms that sometimes are used for this information
- are <firstterm>data dictionary</firstterm> or <firstterm>system
- catalog</firstterm>.
+ <firstterm>Metadata</firstterm>
+
+ is data about the data, such as the name of a database or table, the
+ data type of a column, or access privileges. Other terms that
+ sometimes are used for this information are
+
+ <firstterm>data dictionary</firstterm>
+
+ or
+
+ <firstterm>system
+ catalog</firstterm>
+
+ .
</para>

<para>
@@ -87,9 +96,9 @@
</para>

<para>
- <literal>INFORMATION_SCHEMA</literal> is the information
- database, the place that stores information about all the other
- databases that the MySQL server maintains. Inside
+ <literal>INFORMATION_SCHEMA</literal> is the information database,
+ the place that stores information about all the other databases that
+ the MySQL server maintains. Inside
<literal>INFORMATION_SCHEMA</literal> there are several read-only
tables. They are actually views, not base tables, so you won't
actually see any file associated with them.
@@ -171,9 +180,9 @@
<para>
The implementation for the <literal>INFORMATION_SCHEMA</literal>
table structures in MySQL follows the ANSI/ISO SQL:2003 standard
- Part 11 <citetitle>Schemata</citetitle>. Our intent is approximate compliance with
- SQL:2003 core feature F021 <citetitle>Basic information
- schema</citetitle>.
+ Part 11 <citetitle>Schemata</citetitle>. Our intent is approximate
+ compliance with SQL:2003 core feature F021 <citetitle>Basic
+ information schema</citetitle>.
</para>

<para>
@@ -190,7 +199,7 @@
</para>

<para>
- In effect, we have a new database named
+ In effect, we have a new database named
<literal>INFORMATION_SCHEMA</literal>, though there is never a need
to make a file by that name. It is possible to select
<literal>INFORMATION_SCHEMA</literal> as the default database with a
@@ -232,22 +241,22 @@

<listitem>
<para>
- <quote>Standard Name</quote> indicates the standard SQL name for the
- column.
+ <quote>Standard Name</quote> indicates the standard SQL name
+ for the column.
</para>
</listitem>

<listitem>
<para>
- <quote><literal>SHOW</literal> name</quote> indicates what the
- equivalent field name is in the closest
+ <quote><literal>SHOW</literal> name</quote> indicates what the
+ equivalent field name is in the closest
<literal>SHOW</literal> statement, if any.
</para>
</listitem>

<listitem>
<para>
- <quote>Remarks</quote> provides additional information where
+ <quote>Remarks</quote> provides additional information where
applicable.


+
<informaltable>
<tgroup cols="3">
<colspec colwidth="40*"/>
@@ -3124,107 +3135,103 @@
</tbody>
</tgroup>
</informaltable>
-
- <para>
- <emphasis role="bold">Notes</emphasis>:
-
- <itemizedlist>
-
- <listitem>
- <para>
- The <literal>TRIGGER_SCHEMA</literal> and
- <literal>TRIGGER_NAME</literal> columns contain the
- name of the database in which the trigger occurs, and
- the trigger name, respectively.
- </para>
- </listitem>
-
- <listitem>
- <para>
- The <literal>EVENT_MANIPULATION</literal> column
- contains one of the values
- <literal>'INSERT'</literal>,
- <literal>'DELETE'</literal>, or
- <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.
- </para>
- </listitem>
-
- <listitem>
- <para>
- The <literal>ACTION_STATEMENT</literal> column
- contains the statement to be executed when the trigger
- is invoked. This is the same as the text displayed in
- the <literal>Statement</literal> column of the output
- from <literal>SHOW TRIGGERS</literal>. Note that this
- text uses 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 of the two values <literal>'BEFORE'</literal> or
- <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.
- </para>
- </listitem>
-
- <listitem>
- <para>
- The date and time of the trigger's creation is stored
- in the <literal>CREATED</literal> column.
- </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>, and
- <literal>ACTION_REFERENCE_NEW_TABLE</literal>,
- </para>
- </listitem>
-
-
- </itemizedlist>
- </para>
-
- <para>
- See also <xref linkend="show-triggers"/>.
- </para>
-
-
+
+ <para>
+ <emphasis role="bold">Notes</emphasis>:
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ The <literal>TRIGGER_SCHEMA</literal> and
+ <literal>TRIGGER_NAME</literal> columns contain the name
+ of the database in which the trigger occurs, and the
+ trigger name, respectively.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>EVENT_MANIPULATION</literal> column contains
+ one of the values <literal>'INSERT'</literal>,
+ <literal>'DELETE'</literal>, or
+ <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.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>ACTION_STATEMENT</literal> column contains
+ the statement to be executed when the trigger is invoked.
+ This is the same as the text displayed in the
+ <literal>Statement</literal> column of the output from
+ <literal>SHOW TRIGGERS</literal>. Note that this text uses
+ 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
+ of the two values <literal>'BEFORE'</literal> or
+ <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.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The date and time of the trigger's creation is stored in
+ the <literal>CREATED</literal> column.
+ </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>, and
+ <literal>ACTION_REFERENCE_NEW_TABLE</literal>,
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </para>
+
+ <para>
+ See also <xref linkend="show-triggers"/>.
+ </para>
+
</section>
-
+
<section id="other-information-schema-tables">

<title id='title-other-information-schema-tables'>&title-other-information-schema-tables;</title>

--- 1.3/refman-5.0/maxdb.xml 2005-07-19 10:57:30 -05:00
+++ 1.4/refman-5.0/maxdb.xml 2005-07-26 23:50:55 -05:00
@@ -253,7 +253,7 @@
</row>
<row>
<entry><literal>@</literal></entry>
- <entry>Can prefix identifier, like ``@table''</entry>
+ <entry>Can prefix identifier, like <quote>@table</quote></entry>
<entry>Not allowed</entry>
</row>
<row>
@@ -449,11 +449,12 @@
</row>
<row>
<entry><literal>LIKE</literal> wildcards</entry>
- <entry>MaxDB supports ``%'', ``_'', ``Control-underline'', ``Control-up
- arrow'', ``*'', and ``?'' as wildcards in
+ <entry>MaxDB supports <quote>%</quote>, <quote>_</quote>,
+ <quote>Control-underline</quote>, <quote>Control-up
+ arrow</quote>, <quote>*</quote>, and <quote>?</quote> as
+ wildcards in <literal>LIKE</literal> comparisons</entry>
+ <entry>MySQL supports <quote>%</quote>, and <quote>_</quote> as wildcards in
<literal>LIKE</literal> comparisons</entry>
- <entry>MySQL supports ``%'', and ``_'' as wildcards in <literal>LIKE</literal>
- comparisons</entry>
</row>
<row>
<entry><literal>LPAD()</literal></entry>

--- 1.7/refman/client-side-scripts.xml 2005-07-26 14:51:06 -05:00
+++ 1.8/refman/client-side-scripts.xml 2005-07-26 23:50:55 -05:00
@@ -4259,7 +4259,7 @@
first <command>mysql</command> process terminates, the server
drops the temporary table. When the second
<command>mysql</command> process attempts to use the table, the
- server reports ``unknown table.''
+ server reports <quote>unknown table.</quote>
</para>

<para>

--- 1.4/refman/extending-mysql.xml 2005-07-19 10:57:38 -05:00
+++ 1.5/refman/extending-mysql.xml 2005-07-26 23:50:56 -05:00
@@ -830,11 +830,11 @@
<para>
For each function that you want to use in SQL statements, you
should define corresponding C (or C++) functions. In the
- following discussion, the name ``xxx'' is used for an example
- function name. To distinguish between SQL and C/C++ usage,
- <literal>XXX()</literal> (uppercase) indicates an SQL function
- call, and <literal>xxx()</literal> (lowercase) indicates a C/C++
- function call.
+ following discussion, the name <quote>xxx</quote> is used for an
+ example function name. To distinguish between SQL and C/C++
+ usage, <literal>XXX()</literal> (uppercase) indicates an SQL
+ function call, and <literal>xxx()</literal> (lowercase)
+ indicates a C/C++ function call.
</para>

<para>
@@ -2130,11 +2130,11 @@
lines to <filename>sql_yacc.yy</filename>. One indicates the
preprocessor symbol that <command>yacc</command> should
define (this should be added at the beginning of the file).
- Then define the function parameters and add an ``item'' with
- these parameters to the <literal>simple_expr</literal>
- parsing rule. For an example, check all occurrences of
- <literal>ATAN</literal> in <filename>sql_yacc.yy</filename>
- to see how this is done.
+ Then define the function parameters and add an
+ <quote>item</quote> with these parameters to the
+ <literal>simple_expr</literal> parsing rule. For an example,
+ check all occurrences of <literal>ATAN</literal> in
+ <filename>sql_yacc.yy</filename> to see how this is done.
</para>
</listitem>

--- 1.6/refman/information-schema.xml 2005-07-20 13:55:25 -05:00
+++ 1.7/refman/information-schema.xml 2005-07-26 23:50:56 -05:00
@@ -39,10 +39,10 @@
</para>

<para>
- ``Metadata'' is data about the data, such as the name of a database
- or table, the data type of a column, or access privileges. Other
- terms that sometimes are used for this information are ``data
- dictionary'' or ``system catalog.''
+ <quote>Metadata</quote> is data about the data, such as the name of
+ a database or table, the data type of a column, or access
+ privileges. Other terms that sometimes are used for this information
+ are <quote>data dictionary</quote> or <quote>system catalog.</quote>
</para>

<para>
@@ -86,9 +86,9 @@
</para>

<para>
- <literal>INFORMATION_SCHEMA</literal> is the ``information
- database'', the place that stores information about all the other
- databases that the MySQL server maintains. Inside
+ <literal>INFORMATION_SCHEMA</literal> is the <quote>information
+ database</quote>, the place that stores information about all the
+ other databases that the MySQL server maintains. Inside
<literal>INFORMATION_SCHEMA</literal> there are several read-only
tables. They are actually views, not base tables, so you won't
actually see any file associated with them.
@@ -170,8 +170,9 @@
<para>
The implementation for the <literal>INFORMATION_SCHEMA</literal>
table structures in MySQL follows the ANSI/ISO SQL:2003 standard
- Part 11 ``Schemata.'' Our intent is approximate compliance with
- SQL:2003 core feature F021 ``Basic information schema.''
+ Part 11 <quote>Schemata.</quote> Our intent is approximate
+ compliance with SQL:2003 core feature F021 <quote>Basic information
+ schema.</quote>
</para>

<para>
@@ -188,7 +189,7 @@
</para>

<para>
- In effect, we have a new ``database'' named
+ In effect, we have a new <quote>database</quote> named
<literal>information_schema</literal>, though there is never a need
to make a file by that name. It is possible to select
<literal>INFORMATION_SCHEMA</literal> as the default database with a
@@ -230,22 +231,23 @@

<listitem>
<para>
- ``Standard Name'' indicates the standard SQL name for the
- column.
+ <quote>Standard Name</quote> indicates the standard SQL name
+ for the column.
</para>
</listitem>

<listitem>
<para>
- ``<literal>SHOW</literal> name'' indicates what the equivalent
- field name is in the closest <literal>SHOW</literal>
- statement, if any.
+ <quote><literal>SHOW</literal> name</quote> indicates what the
+ equivalent field name is in the closest
+ <literal>SHOW</literal> statement, if any.
</para>
</listitem>

<listitem>
<para>
- ``Remarks'' provides additional information where applicable.
+ <quote>Remarks</quote> provides additional information where
+ applicable.


+
<informaltable>
<tgroup cols="3">
<colspec colwidth="40*"/>
@@ -3120,118 +3124,114 @@
</tbody>
</tgroup>
</informaltable>
-
+
<para>
<emphasis role="bold">Notes</emphasis>:
-
+
<itemizedlist>
-
+
<listitem>
<para>
- The <literal>TRIGGER_SCHEMA</literal> and
- <literal>TRIGGER_NAME</literal> columns contain the
- name of the database in which the trigger occurs, and
- the trigger name, respectively.
+ The <literal>TRIGGER_SCHEMA</literal> and
+ <literal>TRIGGER_NAME</literal> columns contain the name
+ of the database in which the trigger occurs, and the
+ trigger name, respectively.
</para>
</listitem>
-
+
<listitem>
<para>
- The <literal>EVENT_MANIPULATION</literal> column
- contains one of the values
- <literal>'INSERT'</literal>,
- <literal>'DELETE'</literal>, or
+ The <literal>EVENT_MANIPULATION</literal> column contains
+ one of the values <literal>'INSERT'</literal>,
+ <literal>'DELETE'</literal>, or
<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.
+ 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.
</para>
</listitem>
-
+
<listitem>
<para>
- The <literal>ACTION_STATEMENT</literal> column
- contains the statement to be executed when the trigger
- is invoked. This is the same as the text displayed in
- the <literal>Statement</literal> column of the output
- from <literal>SHOW TRIGGERS</literal>. Note that this
- text uses UTF-8 encoding.
+ The <literal>ACTION_STATEMENT</literal> column contains
+ the statement to be executed when the trigger is invoked.
+ This is the same as the text displayed in the
+ <literal>Statement</literal> column of the output from
+ <literal>SHOW TRIGGERS</literal>. Note that this text uses
+ UTF-8 encoding.
</para>
</listitem>
-
+
<listitem>
<para>
- The <literal>ACTION_ORIENTATION</literal> column
- always contains the value <literal>'ROW'</literal>.
+ 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 of the two values <literal>'BEFORE'</literal> or
+ The <literal>ACTION_TIMING</literal> column contains one
+ of the two values <literal>'BEFORE'</literal> or
<literal>'AFTER'</literal>.
</para>
</listitem>
-
+
<listitem>
<para>
- The columns
- <literal>ACTION_REFERENCE_OLD_ROW</literal> and
- <literal>ACTION_REFERENCE_NEW_ROW</literal> contain
+ The columns <literal>ACTION_REFERENCE_OLD_ROW</literal>
+ and <literal>ACTION_REFERENCE_NEW_ROW</literal> contain
the old and new column identifiers, respectively.
</para>
</listitem>
-
+
<listitem>
<para>
- The date and time of the trigger's creation is stored
- in the <literal>CREATED</literal> column.
+ The date and time of the trigger's creation is stored in
+ the <literal>CREATED</literal> column.
</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>, and
+ 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>, and
<literal>ACTION_REFERENCE_NEW_TABLE</literal>,
</para>
</listitem>
-
-
+
</itemizedlist>
</para>
-
- <para>
- See also <xref linkend="show-triggers"/>.
- </para>
-
-
+
+ <para>
+ See also <xref linkend="show-triggers"/>.
+ </para>
+
</section>
-
+
<section id="other-information-schema-tables">
-
+
<title id='title-other-information-schema-tables'>&title-other-information-schema-tables;</title>
-
+
<para>
We will add more <literal>INFORMATION_SCHEMA</literal> tables
soon. Particularly, we acknowledge the need for
<literal>INFORMATION_SCHEMA.PARAMETERS</literal> and for
<literal>INFORMATION_SCHEMA.REFERENTIAL_CONSTRAINT S</literal>.
</para>
-
+
</section>

</section>

--- 1.3/refman/maxdb.xml 2005-07-19 10:57:41 -05:00
+++ 1.4/refman/maxdb.xml 2005-07-26 23:50:56 -05:00
@@ -253,7 +253,7 @@
</row>
<row>
<entry><literal>@</literal></entry>
- <entry>Can prefix identifier, like ``@table''</entry>
+ <entry>Can prefix identifier, like <quote>@table</quote></entry>
<entry>Not allowed</entry>
</row>
<row>
@@ -449,11 +449,12 @@
</row>
<row>
<entry><literal>LIKE</literal> wildcards</entry>
- <entry>MaxDB supports ``%'', ``_'', ``Control-underline'', ``Control-up
- arrow'', ``*'', and ``?'' as wildcards in
+ <entry>MaxDB supports <quote>%</quote>, <quote>_</quote>,
+ <quote>Control-underline</quote>, <quote>Control-up
+ arrow</quote>, <quote>*</quote>, and <quote>?</quote> as
+ wildcards in <literal>LIKE</literal> comparisons</entry>
+ <entry>MySQL supports <quote>%</quote>, and <quote>_</quote> as wildcards in
<literal>LIKE</literal> comparisons</entry>
- <entry>MySQL supports ``%'', and ``_'' as wildcards in <literal>LIKE</literal>
- comparisons</entry>
</row>
<row>
<entry><literal>LPAD()</literal></entry>

--
MySQL Internals Mailing List
For list archives: http://lists.mysql.com/internals
To unsubscribe: http://lists.mysql.com/internals?uns...ie.nctu.edu.tw

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

bk commit - mysqldoc@docsrva tree (paul:1.3139)

mailing.database.mysql-internals mailing.database.mysql-internals

bk commit - mysqldoc@docsrva tree (paul:1.3139) - 07-26-2005 , 11:51 PM