Author: paul
Date: 2006-01-18 00:31:23 +0100 (Wed, 18 Jan 2006)
New Revision: 883
Log:
r6325@frost: paul | 2006-01-17 17:30:29 -0600
General revisions.
Modified:
trunk/
trunk/refman-4.1/sql-syntax.xml
trunk/refman-5.0/installing.xml
trunk/refman-5.0/sql-syntax.xml
trunk/refman-5.0/stored-procedures.xml
trunk/refman-5.0/triggers.xml
trunk/refman-5.0/views.xml
trunk/refman-5.1/sql-syntax.xml
trunk/refman-5.1/stored-procedures.xml
trunk/refman-5.1/triggers.xml
trunk/refman-5.1/views.xml
trunk/refman-common/titles.en.ent
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6324
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2265
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6325
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2265
Modified: trunk/refman-4.1/sql-syntax.xml
===================================================================
--- trunk/refman-4.1/sql-syntax.xml 2006-01-17 23:30:44 UTC (rev 882)
+++ trunk/refman-4.1/sql-syntax.xml 2006-01-17 23:31:23 UTC (rev 883)
@@ -7533,7 +7533,7 @@
<literal>INSERT</literal>, <literal>REPLACE</literal>, and
<literal>UPDATE</literal>. A more comprehensive discussion of
restrictions on subquery use is given in
- <xref linkend="restrictions"/>.
+ <xref linkend="subquery-restrictions"/>.
</para>
<section id="scalar-subqueries">
Modified: trunk/refman-5.0/installing.xml
===================================================================
--- trunk/refman-5.0/installing.xml 2006-01-17 23:30:44 UTC (rev 882)
+++ trunk/refman-5.0/installing.xml 2006-01-17 23:31:23 UTC (rev 883)
@@ -12276,8 +12276,8 @@
<listitem>
<para>
- Upgrade to MySQL 5.0.10 to be able to access trigger
- information in the
+ Upgrade to MySQL 5.0.10 or later to be able to access
+ trigger information in the
<literal>INFORMATION_SCHEMA.TRIGGERS</literal> table.
(It should work even for pre-5.0.10 triggers.)
</para>
Modified: trunk/refman-5.0/sql-syntax.xml
===================================================================
--- trunk/refman-5.0/sql-syntax.xml 2006-01-17 23:30:44 UTC (rev 882)
+++ trunk/refman-5.0/sql-syntax.xml 2006-01-17 23:31:23 UTC (rev 883)
@@ -7974,7 +7974,7 @@
<literal>INSERT</literal>, <literal>REPLACE</literal>, and
<literal>UPDATE</literal>. A more comprehensive discussion of
restrictions on subquery use is given in
- <xref linkend="restrictions"/>.
+ <xref linkend="subquery-restrictions"/>.
</para>
<section id="scalar-subqueries">
Modified: trunk/refman-5.0/stored-procedures.xml
===================================================================
--- trunk/refman-5.0/stored-procedures.xml 2006-01-17 23:30:44 UTC (rev 882)
+++ trunk/refman-5.0/stored-procedures.xml 2006-01-17 23:31:23 UTC (rev 883)
@@ -88,7 +88,7 @@
All syntax described in this chapter is supported and any
limitations and extensions are documented where appropriate. Further
discussion of restrictions on use of stored routines is given in
- <xref linkend="restrictions"/>.
+ <xref linkend="routine-restrictions"/>.
</para>
<para>
Modified: trunk/refman-5.0/triggers.xml
===================================================================
--- trunk/refman-5.0/triggers.xml 2006-01-17 23:30:44 UTC (rev 882)
+++ trunk/refman-5.0/triggers.xml 2006-01-17 23:31:23 UTC (rev 883)
@@ -45,8 +45,8 @@
This chapter describes the syntax for creating and dropping
triggers, and shows some examples of how to use them. Discussion of
restrictions on use of triggers is given in
- <xref linkend="restrictions"/>. Remarks regarding binary logging as
- it applies to triggers are given in
+ <xref linkend="routine-restrictions"/>. Remarks regarding binary
+ logging as it applies to triggers are given in
<xref linkend="stored-procedure-logging"/>.
</para>
@@ -83,8 +83,9 @@
This statement creates a new trigger. A trigger is a named
database object that is associated with a table, and that
activates when a particular event occurs for the table.
- <literal>CREATE TRIGGER</literal> was added in MySQL 5.0.2. Its
- use requires the <literal>SUPER</literal> privilege.
+ <literal>CREATE TRIGGER</literal> was added in MySQL 5.0.2.
+ Currently, its use requires the <literal>SUPER</literal>
+ privilege.
</para>
<para>
@@ -95,8 +96,9 @@
</para>
<para>
- The <literal>DEFINER</literal> clause determines the privileges
- that apply when the trigger is activated.
+ When the trigger is activated, the <literal>DEFINER</literal>
+ clause determines the privileges that apply, as described later in
+ this section.
</para>
<para>
@@ -158,7 +160,7 @@
<para>
A potentially confusing example of this is the <literal>INSERT
- INTO .. ON DUPLICATE UPDATE ...</literal> syntax: a
+ INTO .. ON DUPLICATE UPDATE …</literal> syntax: a
<literal>BEFORE INSERT</literal> trigger will activate for every
row, followed by either an <literal>AFTER INSERT</literal> trigger
or both the <literal>BEFORE UPDATE</literal> and <literal>AFTER
@@ -178,7 +180,7 @@
<para>
<replaceable>trigger_stmt</replaceable> is the statement to
execute when the trigger activates. If you want to execute
- multiple statements, use the <literal>BEGIN ... END</literal>
+ multiple statements, use the <literal>BEGIN … END</literal>
compound statement construct. This also enables you to use the
same statements that are allowable within stored routines. See
<xref linkend="begin-end"/>.
@@ -213,7 +215,7 @@
INSERT INTO test2 SET a2 = NEW.a1;
DELETE FROM test3 WHERE a3 = NEW.a1;
UPDATE test4 SET b4 = b4 + 1 WHERE a4 = NEW.a1;
- END
+ END;
|
DELIMITER ;
@@ -315,12 +317,13 @@
</para>
<para>
- The <literal>DEFINER</literal> clause specifies the account to be
- used when checking access privileges at trigger activation time.
- It was added in MySQL 5.0.17. If a <replaceable>user</replaceable>
- value is given, it should be a MySQL account in
+ The <literal>DEFINER</literal> clause specifies the MySQL account
+ to be used when checking access privileges at trigger activation
+ time. It was added in MySQL 5.0.17. If a
+ <replaceable>user</replaceable> value is given, it should be a
+ MySQL account in
<literal>'<replaceable>user_name</replaceable>'@'<replaceable>host_name</replaceable>'</literal>
- format (the same format as for the <literal>GRANT</literal>
+ format (the same format used in the <literal>GRANT</literal>
statement). The <replaceable>user_name</replaceable> and
<replaceable>host_name</replaceable> values both are required.
<literal>CURRENT_USER</literal> also can be given as
@@ -359,6 +362,12 @@
</itemizedlist>
+ <para>
+ Note: Because MySQL currently requires the
+ <literal>SUPER</literal> privilege for the use of <literal>CREATE
+ TRIGGER</literal>, only the second of the preceding rules applies.
+ </para>
+
<remark role="todo">
For future implementation in trigger privilege checking: (i) When
we have a TRIGGER privilege, that will be required for the subject
@@ -529,8 +538,9 @@
<para>
Support for triggers is included beginning with MySQL 5.0.2. This
- section discusses how to use triggers and what limitations exist
- regarding their use.
+ section discusses how to use triggers and some limitations
+ regarding their use. Additional information about trigger
+ limitations is given in <xref linkend="routine-restrictions"/>.
</para>
<para>
@@ -642,7 +652,7 @@
<para>
In this case, the value of <literal>@sum</literal> after the
<literal>INSERT</literal> statement has executed is <literal>14.98
- + 1937.50 - 100</literal> or <literal>1852.48</literal>.
+ + 1937.50 - 100</literal>, or <literal>1852.48</literal>.
</para>
<para>
@@ -670,9 +680,9 @@
triggers or two <literal>AFTER UPDATE</literal> triggers for a
table. This should rarely be a significant limitation, because it
is possible to define a trigger that executes multiple statements
- by using the <literal>BEGIN ... END</literal> compound statement
- construct after <literal>FOR EACH ROW</literal>. (An example
- appears later in this section.)
+ by using the <literal>BEGIN … END</literal> compound
+ statement construct after <literal>FOR EACH ROW</literal>. (An
+ example appears later in this section.)
</para>
<para>
@@ -717,21 +727,21 @@
</para>
<para>
- By using the <literal>BEGIN ... END</literal> construct, you can
- define a trigger that executes multiple statements. Within the
+ By using the <literal>BEGIN … END</literal> construct, you
+ can define a trigger that executes multiple statements. Within the
<literal>BEGIN</literal> block, you also can use other syntax that
is allowed within stored routines such as conditionals and loops.
However, just as for stored routines, if you use the
<command>mysql</command> program to define a trigger that executes
multiple statements, it is necessary to redefine the
<command>mysql</command> statement delimiter so that you can use
- the ‘<literal>;</literal>’ character within the
- trigger definition. The following example illustrates these
- points. It defines an <literal>UPDATE</literal> trigger that
- checks the new value to be used for updating each row, and
- modifies the value to be within the range from 0 to 100. This must
- be a <literal>BEFORE</literal> trigger because the value needs to
- be checked before it is used to update the row:
+ the <literal>;</literal> statement delimiter within the trigger
+ definition. The following example illustrates these points. It
+ defines an <literal>UPDATE</literal> trigger that checks the new
+ value to be used for updating each row, and modifies the value to
+ be within the range from 0 to 100. This must be a
+ <literal>BEFORE</literal> trigger because the value needs to be
+ checked before it is used to update the row:
</para>
<programlisting>
@@ -819,7 +829,7 @@
<para>
An error during either a <literal>BEFORE</literal> or
<literal>AFTER</literal> trigger results in failure of the
- whole statement that caused trigger invocation.
+ entire statement that caused trigger invocation.
</para>
</listitem>
Modified: trunk/refman-5.0/views.xml
===================================================================
--- trunk/refman-5.0/views.xml 2006-01-17 23:30:44 UTC (rev 882)
+++ trunk/refman-5.0/views.xml 2006-01-17 23:31:23 UTC (rev 883)
@@ -55,7 +55,7 @@
<para>
Discussion of restrictions on use of views is given in
- <xref linkend="restrictions"/>.
+ <xref linkend="view-restrictions"/>.
</para>
<para>
Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml 2006-01-17 23:30:44 UTC (rev 882)
+++ trunk/refman-5.1/sql-syntax.xml 2006-01-17 23:31:23 UTC (rev 883)
@@ -8537,7 +8537,7 @@
<literal>INSERT</literal>, <literal>REPLACE</literal>, and
<literal>UPDATE</literal>. A more comprehensive discussion of
restrictions on subquery use is given in
- <xref linkend="restrictions"/>.
+ <xref linkend="subquery-restrictions"/>.
</para>
<section id="scalar-subqueries">
Modified: trunk/refman-5.1/stored-procedures.xml
===================================================================
--- trunk/refman-5.1/stored-procedures.xml 2006-01-17 23:30:44 UTC (rev 882)
+++ trunk/refman-5.1/stored-procedures.xml 2006-01-17 23:31:23 UTC (rev 883)
@@ -88,7 +88,7 @@
All syntax described in this chapter is supported and any
limitations and extensions are documented where appropriate. Further
discussion of restrictions on use of stored routines is given in
- <xref linkend="restrictions"/>.
+ <xref linkend="routine-restrictions"/>.
</para>
<para>
Modified: trunk/refman-5.1/triggers.xml
===================================================================
--- trunk/refman-5.1/triggers.xml 2006-01-17 23:30:44 UTC (rev 882)
+++ trunk/refman-5.1/triggers.xml 2006-01-17 23:31:23 UTC (rev 883)
@@ -44,8 +44,8 @@
This chapter describes the syntax for creating and dropping
triggers, and shows some examples of how to use them. Discussion of
restrictions on use of triggers is given in
- <xref linkend="restrictions"/>. Remarks regarding binary logging as
- it applies to triggers are given in
+ <xref linkend="routine-restrictions"/>. Remarks regarding binary
+ logging as it applies to triggers are given in
<xref linkend="stored-procedure-logging"/>.
</para>
@@ -81,7 +81,7 @@
<para>
This statement creates a new trigger. A trigger is a named
database object that is associated with a table, and that
- activates when a particular event occurs for the table.
+ activates when a particular event occurs for the table. Currently,
<literal>CREATE TRIGGER</literal> requires the
<literal>SUPER</literal> privilege.
</para>
@@ -94,8 +94,9 @@
</para>
<para>
- The <literal>DEFINER</literal> clause determines the privileges
- that apply when the trigger is activated.
+ When the trigger is activated, the <literal>DEFINER</literal>
+ clause determines the privileges that apply, as described later in
+ this section.
</para>
<para>
@@ -157,7 +158,7 @@
<para>
A potentially confusing example of this is the <literal>INSERT
- INTO .. ON DUPLICATE UPDATE ...</literal> syntax: a
+ INTO .. ON DUPLICATE UPDATE …</literal> syntax: a
<literal>BEFORE INSERT</literal> trigger will activate for every
row, followed by either an <literal>AFTER INSERT</literal> trigger
or both the <literal>BEFORE UPDATE</literal> and <literal>AFTER
@@ -177,7 +178,7 @@
<para>
<replaceable>trigger_stmt</replaceable> is the statement to
execute when the trigger activates. If you want to execute
- multiple statements, use the <literal>BEGIN ... END</literal>
+ multiple statements, use the <literal>BEGIN … END</literal>
compound statement construct. This also enables you to use the
same statements that are allowable within stored routines. See
<xref linkend="begin-end"/>.
@@ -211,7 +212,7 @@
INSERT INTO test2 SET a2 = NEW.a1;
DELETE FROM test3 WHERE a3 = NEW.a1;
UPDATE test4 SET b4 = b4 + 1 WHERE a4 = NEW.a1;
- END
+ END;
|
DELIMITER ;
@@ -313,12 +314,12 @@
</para>
<para>
- The <literal>DEFINER</literal> clause specifies the account to be
- used when checking access privileges at trigger activation time.
- If a <replaceable>user</replaceable> value is given, it should be
- a MySQL account in
+ The <literal>DEFINER</literal> clause specifies the MySQL account
+ to be used when checking access privileges at trigger activation
+ time. If a <replaceable>user</replaceable> value is given, it
+ should be a MySQL account in
<literal>'<replaceable>user_name</replaceable>'@'<replaceable>host_name</replaceable>'</literal>
- format (the same format as for the <literal>GRANT</literal>
+ format (the same format used in the <literal>GRANT</literal>
statement). The <replaceable>user_name</replaceable> and
<replaceable>host_name</replaceable> values both are required.
<literal>CURRENT_USER</literal> also can be given as
@@ -357,6 +358,12 @@
</itemizedlist>
+ <para>
+ Note: Because MySQL currently requires the
+ <literal>SUPER</literal> privilege for the use of <literal>CREATE
+ TRIGGER</literal>, only the second of the preceding rules applies.
+ </para>
+
<remark role="todo">
For future implementation in trigger privilege checking: (i) When
we have a TRIGGER privilege, that will be required for the subject
@@ -491,7 +498,9 @@
<para>
This section discusses how to use triggers in MySQL
- ¤t-series; and what limitations exist regarding their use.
+ ¤t-series; and some limitations regarding their use.
+ Additional information about trigger limitations is given in
+ <xref linkend="routine-restrictions"/>.
</para>
<para>
@@ -603,7 +612,7 @@
<para>
In this case, the value of <literal>@sum</literal> after the
<literal>INSERT</literal> statement has executed is <literal>14.98
- + 1937.50 - 100</literal> or <literal>1852.48</literal>.
+ + 1937.50 - 100</literal>, or <literal>1852.48</literal>.
</para>
<para>
@@ -631,9 +640,9 @@
triggers or two <literal>AFTER UPDATE</literal> triggers for a
table. This should rarely be a significant limitation, because it
is possible to define a trigger that executes multiple statements
- by using the <literal>BEGIN ... END</literal> compound statement
- construct after <literal>FOR EACH ROW</literal>. (An example
- appears later in this section.)
+ by using the <literal>BEGIN … END</literal> compound
+ statement construct after <literal>FOR EACH ROW</literal>. (An
+ example appears later in this section.)
</para>
<para>
@@ -678,21 +687,21 @@
</para>
<para>
- By using the <literal>BEGIN ... END</literal> construct, you can
- define a trigger that executes multiple statements. Within the
+ By using the <literal>BEGIN … END</literal> construct, you
+ can define a trigger that executes multiple statements. Within the
<literal>BEGIN</literal> block, you also can use other syntax that
is allowed within stored routines such as conditionals and loops.
However, just as for stored routines, if you use the
<command>mysql</command> program to define a trigger that executes
multiple statements, it is necessary to redefine the
<command>mysql</command> statement delimiter so that you can use
- the ‘<literal>;</literal>’ character within the
- trigger definition. The following example illustrates these
- points. It defines an <literal>UPDATE</literal> trigger that
- checks the new value to be used for updating each row, and
- modifies the value to be within the range from 0 to 100. This must
- be a <literal>BEFORE</literal> trigger because the value needs to
- be checked before it is used to update the row:
+ the <literal>;</literal> statement delimiter within the trigger
+ definition. The following example illustrates these points. It
+ defines an <literal>UPDATE</literal> trigger that checks the new
+ value to be used for updating each row, and modifies the value to
+ be within the range from 0 to 100. This must be a
+ <literal>BEFORE</literal> trigger because the value needs to be
+ checked before it is used to update the row:
</para>
<programlisting>
@@ -773,7 +782,7 @@
<para>
An error during either a <literal>BEFORE</literal> or
<literal>AFTER</literal> trigger results in failure of the
- whole statement that caused trigger invocation.
+ entire statement that caused trigger invocation.
</para>
</listitem>
Modified: trunk/refman-5.1/views.xml
===================================================================
--- trunk/refman-5.1/views.xml 2006-01-17 23:30:44 UTC (rev 882)
+++ trunk/refman-5.1/views.xml 2006-01-17 23:31:23 UTC (rev 883)
@@ -54,7 +54,7 @@
<para>
Discussion of restrictions on use of views is given in
- <xref linkend="restrictions"/>.
+ <xref linkend="view-restrictions"/>.
</para>
<para>
Modified: trunk/refman-common/titles.en.ent
===================================================================
--- trunk/refman-common/titles.en.ent 2006-01-17 23:30:44 UTC (rev 882)
+++ trunk/refman-common/titles.en.ent 2006-01-17 23:31:23 UTC (rev 883)
@@ -30,7 +30,7 @@
<!ENTITY title-alpha-dec-osf1 "Alpha-DEC-OSF/1 Notes">
<!ENTITY title-alpha-dec-unix "Alpha-DEC-UNIX Notes (Tru64)">
<!ENTITY title-alter-database "<literal>ALTER DATABASE</literal> Syntax">
-<!ENTITY title-alter-procedure "<literal>ALTER PROCEDURE</literal> and <literal>ALTER FUNCTION</literal>">
+<!ENTITY title-alter-procedure "<literal>ALTER PROCEDURE</literal> and <literal>ALTER FUNCTION</literal> Syntax">
<!ENTITY title-alter-table "<literal>ALTER TABLE</literal> Syntax">
<!ENTITY title-alter-table-problems "Problems with <literal>ALTER TABLE</literal>">
<!ENTITY title-alter-view "<literal>ALTER VIEW</literal> Syntax">
@@ -71,7 +71,7 @@
<!ENTITY title-bdb-start "<literal>BDB</literal> Startup Options">
<!ENTITY title-bdb-storage-engine "The <literal>BDB</literal> (<literal>BerkeleyDB</literal>) Storage Engine">
<!ENTITY title-bdb-todo "Things We Need to Fix for <literal>BDB</literal>">
-<!ENTITY title-begin-end "<literal>BEGIN … END</literal> Compound Statement">
+<!ENTITY title-begin-end "<literal>BEGIN … END</literal> Compound Statement Syntax">
<!ENTITY title-beos "BeOS Notes">
<!ENTITY title-binary-log "The Binary Log">
<!ENTITY title-binary-notes-linux "Linux Binary Distribution Notes">
@@ -108,7 +108,7 @@
<!ENTITY title-c-thread-functions "C API Threaded Function Descriptions">
<!ENTITY title-cache-index "<literal>CACHE INDEX</literal> Syntax">
<!ENTITY title-calculating-days "Calculating Visits Per Day">
-<!ENTITY title-call "<literal>CALL</literal> Statement">
+<!ENTITY title-call "<literal>CALL</literal> Statement Syntax">
<!ENTITY title-can-not-connect-to-server "<literal>Can't connect to [local] MySQL server</literal>">
<!ENTITY title-can-not-connect-to-server-on-windows "<literal>Connection to MySQL Server Failing on Windows</literal>">
<!ENTITY title-cannot-create "<literal>Can't create/write to file</literal>">
@@ -265,7 +265,7 @@
<!ENTITY title-create-database "<literal>CREATE DATABASE</literal> Syntax">
<!ENTITY title-create-function "<literal>CREATE FUNCTION</literal> Syntax">
<!ENTITY title-create-index "<literal>CREATE INDEX</literal> Syntax">
-<!ENTITY title-create-procedure "<literal>CREATE PROCEDURE</literal> and <literal>CREATE FUNCTION</literal>">
+<!ENTITY title-create-procedure "<literal>CREATE PROCEDURE</literal> and <literal>CREATE FUNCTION</literal> Syntax">
<!ENTITY title-create-table "<literal>CREATE TABLE</literal> Syntax">
<!ENTITY title-create-trigger "<literal>CREATE TRIGGER</literal> Syntax">
<!ENTITY title-create-user "<literal>CREATE USER</literal> Syntax">
@@ -299,7 +299,7 @@
<!ENTITY title-datetime "The <literal>DATETIME</literal>, <literal>DATE</literal>, and <literal>TIMESTAMP</literal> Types">
<!ENTITY title-debugging-client "Debugging a MySQL Client">
<!ENTITY title-debugging-server "Debugging a MySQL Server">
-<!ENTITY title-declare "<literal>DECLARE</literal> Statement">
+<!ENTITY title-declare "<literal>DECLARE</literal> Statement Syntax">
<!ENTITY title-declare-conditions "<literal>DECLARE</literal> Conditions">
<!ENTITY title-declare-cursors "Declaring Cursors">
<!ENTITY title-declare-handlers "<literal>DECLARE</literal> Handlers">
@@ -329,7 +329,7 @@
<!ENTITY title-drop-database "<literal>DROP DATABASE</literal> Syntax">
<!ENTITY title-drop-function "<literal>DROP FUNCTION</literal> Syntax">
<!ENTITY title-drop-index "<literal>DROP INDEX</literal> Syntax">
-<!ENTITY title-drop-procedure "<literal>DROP PROCEDURE</literal> and <literal>DROP FUNCTION</literal>">
+<!ENTITY title-drop-procedure "<literal>DROP PROCEDURE</literal> and <literal>DROP FUNCTION</literal> Syntax">
<!ENTITY title-drop-table "<literal>DROP TABLE</literal> Syntax">
<!ENTITY title-drop-trigger "<literal>DROP TRIGGER</literal> Syntax">
<!ENTITY title-drop-user "<literal>DROP USER</literal> Syntax">
@@ -1508,7 +1508,7 @@
<!ENTITY title-show-collation "<literal>SHOW COLLATION</literal> Syntax">
<!ENTITY title-show-columns "<literal>SHOW COLUMNS</literal> Syntax">
<!ENTITY title-show-create-database "<literal>SHOW CREATE DATABASE</literal> Syntax">
-<!ENTITY title-show-create-procedure "<literal>SHOW CREATE PROCEDURE</literal> and <literal>SHOW CREATE FUNCTION</literal>">
+<!ENTITY title-show-create-procedure "<literal>SHOW CREATE PROCEDURE</literal> and <literal>SHOW CREATE FUNCTION</literal> Syntax">
<!ENTITY title-show-create-table "<literal>SHOW CREATE TABLE</literal> Syntax">
<!ENTITY title-show-create-view "<literal>SHOW CREATE VIEW</literal> Syntax">
<!ENTITY title-show-databases "<literal>SHOW DATABASES</literal> Syntax">
@@ -1523,7 +1523,7 @@
<!ENTITY title-show-master-status "<literal>SHOW MASTER STATUS</literal> Syntax">
<!ENTITY title-show-open-tables "<literal>SHOW OPEN TABLES</literal> Syntax">
<!ENTITY title-show-privileges "<literal>SHOW PRIVILEGES</literal> Syntax">
-<!ENTITY title-show-procedure-status "<literal>SHOW PROCEDURE STATUS</literal> and <literal>SHOW FUNCTION STATUS</literal>">
+<!ENTITY title-show-procedure-status "<literal>SHOW PROCEDURE STATUS</literal> and <literal>SHOW FUNCTION STATUS</literal> Syntax">
<!ENTITY title-show-processlist "<literal>SHOW PROCESSLIST</literal> Syntax">
<!ENTITY title-show-slave-hosts "<literal>SHOW SLAVE HOSTS</literal> Syntax">
<!ENTITY title-show-slave-status "<literal>SHOW SLAVE STATUS</literal> Syntax">
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r883 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-common | paul | 18 Jan |
