Author: jstephens
Date: 2006-12-04 06:57:43 +0100 (Mon, 04 Dec 2006)
New Revision: 4101
Log:
Reformat
Modified:
trunk/refman-5.1/events.xml
trunk/refman-5.1/news-5.1.xml
Modified: trunk/refman-5.1/events.xml
===================================================================
--- trunk/refman-5.1/events.xml 2006-12-04 05:54:11 UTC (rev 4100)
+++ trunk/refman-5.1/events.xml 2006-12-04 05:57:43 UTC (rev 4101)
Changed blocks: 19, Lines Added: 101, Lines Deleted: 106; 11313 bytes
@@ -12,11 +12,11 @@
<chapter id="events">
<title>Event Scheduler</title>
-
+
<indexterm>
<primary>Event Scheduler</primary>
</indexterm>
-
+
<indexterm>
<primary>events</primary>
</indexterm>
@@ -102,12 +102,12 @@
<section id="events-overview">
<title>Event Scheduler Overview</title>
-
- <indexterm>
- <primary>Event Scheduler</primary>
- <secondary>concepts</secondary>
- </indexterm>
+ <indexterm>
+ <primary>Event Scheduler</primary>
+ <secondary>concepts</secondary>
+ </indexterm>
+
<para>
MySQL Events are tasks that run according to a schedule.
Therefore, we sometimes refer to them as
@@ -226,18 +226,17 @@
<literal>SUPER</literal> privilege in the output of <literal>SHOW
PROCESSLIST</literal>, as shown in the discussion that follows.
</para>
-
-
- <indexterm>
- <primary>Event Scheduler</primary>
- <secondary>enabling and disabling</secondary>
- </indexterm>
-
- <indexterm>
- <primary>Event Scheduler</primary>
- <secondary>starting and stopping</secondary>
- </indexterm>
+ <indexterm>
+ <primary>Event Scheduler</primary>
+ <secondary>enabling and disabling</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>Event Scheduler</primary>
+ <secondary>starting and stopping</secondary>
+ </indexterm>
+
<para id="events-event-scheduler-option">
The global variable <literal>event_scheduler</literal> determines
whether the Event Scheduler is enabled and running on the server.
@@ -270,12 +269,12 @@
<literal>ON</literal>: The Event Scheduler is started; the
event scheduler thread runs and executes all scheduled events.
</para>
-
- <indexterm>
- <primary>Event Scheduler</primary>
- <secondary>and <literal>SHOW PROCESSLIST</literal></secondary>
- </indexterm>
+ <indexterm>
+ <primary>Event Scheduler</primary>
+ <secondary>and <literal>SHOW PROCESSLIST</literal></secondary>
+ </indexterm>
+
<para>
When the Event Scheduler is <literal>ON</literal>, the event
scheduler thread is listed in the output of <literal>SHOW
@@ -512,14 +511,12 @@
<section id="events-syntax">
<title>Event Scheduler Syntax</title>
-
-
-
- <indexterm>
- <primary>Event Scheduler</primary>
- <secondary>SQL statements</secondary>
- </indexterm>
+ <indexterm>
+ <primary>Event Scheduler</primary>
+ <secondary>SQL statements</secondary>
+ </indexterm>
+
<para>
MySQL 5.1.6 and later provides several SQL statements for working
with scheduled events:
@@ -568,22 +565,21 @@
<section id="create-event">
<title><literal>CREATE EVENT</literal> Syntax</title>
-
-
-
- <indexterm>
- <primary>Event Scheduler</primary>
- <secondary>creating events</secondary>
- </indexterm>
- <indexterm>
- <primary>events</primary>
- <secondary>creating</secondary>
- </indexterm>
-
- <indexterm>
- <primary><literal>CREATE EVENT</literal></primary>
- </indexterm>
+ <indexterm>
+ <primary>Event Scheduler</primary>
+ <secondary>creating events</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>events</primary>
+ <secondary>creating</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary><literal>CREATE EVENT</literal></primary>
+ </indexterm>
+
<programlisting>
CREATE EVENT [IF NOT EXISTS] <replaceable>event_name</replaceable>
ON SCHEDULE <replaceable>schedule</replaceable>
@@ -881,7 +877,7 @@
such expressions, nor may you use any table references; however,
you may use <literal>SELECT FROM DUAL</literal>. This is true
for both <literal>CREATE EVENT</literal> and <literal>ALTER
- EVENT</literal> statements. Beginning with MySQL 5.1.13,
+ EVENT</literal> statements. Beginning with MySQL 5.1.13,
references to stored routines, user-defined functions, and
tables in such cases is specifically disallowed, and fail with
an error (see Bug #22830).
@@ -933,7 +929,7 @@
DO
DELETE FROM site_activity.sessions;
</programlisting>
-
+
<para>
A <literal>CREATE EVENT</literal> statement that contains an
<literal>ALTER EVENT</literal> statement in its
@@ -1056,21 +1052,21 @@
<section id="alter-event">
<title><literal>ALTER EVENT</literal> Syntax</title>
-
- <indexterm>
- <primary>Event Scheduler</primary>
- <secondary>altering events</secondary>
- </indexterm>
-
- <indexterm>
- <primary>events</primary>
- <secondary>altering</secondary>
- </indexterm>
-
- <indexterm>
- <primary><literal>ALTER EVENT</literal></primary>
- </indexterm>
+ <indexterm>
+ <primary>Event Scheduler</primary>
+ <secondary>altering events</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>events</primary>
+ <secondary>altering</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary><literal>ALTER EVENT</literal></primary>
+ </indexterm>
+
<programlisting>
ALTER EVENT <replaceable>event_name</replaceable>
[ON SCHEDULE <replaceable>schedule</replaceable>]
@@ -1165,12 +1161,12 @@
such expressions, nor may you use any table references; however,
you may use <literal>SELECT FROM DUAL</literal>. This is true
for both <literal>ALTER EVENT</literal> and <literal>CREATE
- EVENT</literal> statements. Beginning with MySQL 5.1.13,
+ EVENT</literal> statements. Beginning with MySQL 5.1.13,
references to stored routines, user-defined functions, and
tables in such cases is specifically disallowed, and fail with
an error (see Bug #22830).
</para>
-
+
<para>
An <literal>ALTER EVENT</literal> statement that contains
another <literal>ALTER EVENT</literal> statement in its
@@ -1246,16 +1242,16 @@
<section id="drop-event">
<title><literal>DROP EVENT</literal> Syntax</title>
-
+
<indexterm>
<primary><literal>DROP EVENT</literal></primary>
</indexterm>
-
+
<indexterm>
<primary>Event Scheduler</primary>
<secondary>dropping events</secondary>
</indexterm>
-
+
<indexterm>
<primary>events</primary>
<secondary>dropping</secondary>
@@ -1293,16 +1289,14 @@
</section>
<section id="events-metadata">
-
-
<title>Event Metadata</title>
-
+
<indexterm>
<primary>Event Scheduler</primary>
<secondary>event metadata</secondary>
</indexterm>
-
+
<indexterm>
<primary>events</primary>
<secondary>metadata</secondary>
@@ -1347,55 +1341,56 @@
</itemizedlist>
</section>
-
+
<section id="events-status-info">
+
<title>Event Scheduler Status</title>
-
- <indexterm>
- <primary>Event Scheduler</primary>
- <secondary>obtaining status information</secondary>
- </indexterm>
-
+
<indexterm>
+ <primary>Event Scheduler</primary>
+ <secondary>obtaining status information</secondary>
+ </indexterm>
+
+ <indexterm>
<primary>SHOW SCHEDULER STATUS</primary>
</indexterm>
-
- <indexterm>
- <primary>Event Scheduler</primary>
- <secondary>and <command>mysqladmin debug</command></secondary>
- </indexterm>
-
+
+ <indexterm>
+ <primary>Event Scheduler</primary>
+ <secondary>and <command>mysqladmin debug</command></secondary>
+ </indexterm>
+
<para>
Information about the state of the Event Scheduler for debugging
and troubleshooting purposes can be obtained as follows:
</para>
-
+
<itemizedlist>
+
<listitem>
<para>
In MySQL 5.1.11 <literal>-debug</literal> builds, you can use
- the <literal>SHOW SCHEDULER STATUS</literal> statement; see
+ the <literal>SHOW SCHEDULER STATUS</literal> statement; see
<xref linkend="show-scheduler-status"/>.
</para>
-
+
<para>
<emphasis role="bold">Important</emphasis>: This statement was
removed in MySQL 5.1.12. We intend to implement an SQL
statement providing similar functionality in a future MySQL
- release.
+ release.
</para>
</listitem>
-
+
<listitem>
<para>
- Beginning with MySQL 5.1.12, event scheduler
- status information can be obtained by running the
- <command>mysqladmin debug</command> (see
- <xref linkend="mysqladmin"/>); after running this command, the
- error log contains output relating to the Event Scheduler,
- similar to what is shown here:
+ Beginning with MySQL 5.1.12, event scheduler status
+ information can be obtained by running the <command>mysqladmin
+ debug</command> (see <xref linkend="mysqladmin"/>); after
+ running this command, the error log contains output relating
+ to the Event Scheduler, similar to what is shown here:
</para>
-
+
<programlisting>
Events status:
LLA = Last Locked At LUA = Last Unlocked At
@@ -1421,15 +1416,15 @@
Next activation : 0000-00-00 00:00:00
</programlisting>
</listitem>
+
</itemizedlist>
-
+
</section>
-
-
+
<section id="events-privileges">
<title>The Event Scheduler and MySQL Privileges</title>
-
+
<indexterm>
<primary>Event Scheduler</primary>
<secondary>and MySQL privileges</secondary>
@@ -1540,7 +1535,7 @@
<errortext>ERROR 1142 (42000): INSERT command denied to user
'jon'@'ghidora' for table 'mytable'</errortext>
</programlisting>
-
+
<indexterm>
<primary><literal>EVENTS</literal></primary>
<secondary><literal>INFORMATION_SCHEMA</literal> table</secondary>
@@ -1630,7 +1625,7 @@
<literal>e_insert</literal> continues to execute, inserting a new
row into <literal>mytable</literal> each seven seconds.
</para>
-
+
<indexterm>
<primary><literal>mysql.event</literal> table</primary>
</indexterm>
@@ -1697,7 +1692,7 @@
<remark role="todo">
[js] Move to status variables section.
</remark>
-
+
<indexterm>
<primary>events</primary>
<secondary>status variables</secondary>
@@ -1770,7 +1765,7 @@
<section id="events-limitations-restrictions">
<title>Event Scheduler Limitations and Restrictions</title>
-
+
<indexterm>
<primary>events</primary>
<secondary>limitations</secondary>
@@ -1879,12 +1874,12 @@
respect case-sensitive handling before upgrading to MySQL 5.1.8 or
later.
</para>
-
+
<para>
References to stored routines, user-defined functions, and tables
in the <literal>ON SCHEDULE</literal> clauses of <literal>CREATE
- EVENT</literal> and <literal>ALTER EVENT</literal> statements
- are not supported. Beginning with MySQL 5.1.13, these sorts of
+ EVENT</literal> and <literal>ALTER EVENT</literal> statements are
+ not supported. Beginning with MySQL 5.1.13, these sorts of
references are disallowed. (See Bug #22830 for more information.)
</para>
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2006-12-04 05:54:11 UTC (rev 4100)
+++ trunk/refman-5.1/news-5.1.xml 2006-12-04 05:57:43 UTC (rev 4101)
Changed blocks: 3, Lines Added: 12, Lines Deleted: 12; 2030 bytes
@@ -76,34 +76,34 @@
please see
<ulink url="http://www.mysql.com/network/advisors.html"/>.
</para>
-
+
<para>
Functionality added or changed:
</para>
<itemizedlist>
-
+
<listitem>
<para>
Direct and indirect usage of stored routines, user-defined
- functions, and table references is now
- prohibited in <literal>CREATE EVENT</literal> and
- <literal>ALTER EVENT</literal> statements. (Bug #22830)
+ functions, and table references is now prohibited in
+ <literal>CREATE EVENT</literal> and <literal>ALTER
+ EVENT</literal> statements. (Bug #22830)
</para>
-
+
<para>
- See <xref linkend="create-event"/>, and
+ See <xref linkend="create-event"/>, and
<xref linkend="alter-event"/>, for more specific information.
</para>
</listitem>
-
+
<listitem>
<para>
<literal>DROP TRIGGER</literal> now supports an <literal>IF
EXISTS</literal> clause. (Bug #23703)
</para>
</listitem>
-
+
</itemizedlist>
<para>
@@ -124,8 +124,8 @@
<para>
<literal>IN()</literal> and <literal>CHAR()</literal> can
return <literal>NULL</literal>, but did not signal that to the
- query processor, causing incorrect results for
- <literal>IS NULL</literal> operations. (Bug #17047)
+ query processor, causing incorrect results for <literal>IS
+ NULL</literal> operations. (Bug #17047)
</para>
</listitem>
@@ -811,7 +811,7 @@
(Bug #17544, Bug #21785)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (Disk Data): In the event of an
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r4101 - trunk/refman-5.1 | jon | 4 Dec |
