Author: jstephens
Date: 2006-06-28 09:03:18 +0200 (Wed, 28 Jun 2006)
New Revision: 2538
Log:
Documenting Event Scheduler bugfixes:
Bug #16992, Bug #18897
Documenting change in schema of I_S.EVENTS (Andrey/PeterG)
Modified:
trunk/refman-5.1/events.xml
trunk/refman-5.1/information-schema.xml
trunk/refman-common/news-5.1.xml
Modified: trunk/refman-5.1/events.xml
===================================================================
--- trunk/refman-5.1/events.xml 2006-06-28 05:55:22 UTC (rev 2537)
+++ trunk/refman-5.1/events.xml 2006-06-28 07:03:18 UTC (rev 2538)
@@ -1295,26 +1295,35 @@
> <userinput>WHERE EVENT_NAME='e_store_ts'</userinput>
> <userinput>AND EVENT_SCHEMA='myschema'\G</userinput>
*************************** 1. row ***************************
- EVENT_CATALOG: NULL
- EVENT_SCHEMA: myschema
- EVENT_NAME: e_store_ts
- DEFINER: jon@ghidora
- EVENT_BODY: INSERT INTO myschema.mytable VALUES (UNIX_TIMESTAMP())
- EVENT_TYPE: RECURRING
- EXECUTE_AT: NULL
-INTERVAL_VALUE: 5
-INTERVAL_FIELD: INTERVAL_SECOND
- SQL_MODE: NULL
- STARTS: 0000-00-00 00:00:00
- ENDS: 0000-00-00 00:00:00
- STATUS: ENABLED
- ON_COMPLETION: NOT PRESERVE
- CREATED: 2006-02-09 22:36:06
- LAST_ALTERED: 2006-02-09 22:36:06
- LAST_EXECUTED: NULL
- EVENT_COMMENT:
+ EVENT_CATALOG: NULL
+ EVENT_SCHEMA: myschema
+ EVENT_NAME: e_store_ts
+ DEFINER: jon@ghidora
+ EVENT_BODY: SQL
+EVENT_DEFINITION: INSERT INTO myschema.mytable VALUES (UNIX_TIMESTAMP())
+ EVENT_TYPE: RECURRING
+ EXECUTE_AT: NULL
+ INTERVAL_VALUE: 5
+ INTERVAL_FIELD: INTERVAL_SECOND
+ SQL_MODE: NULL
+ STARTS: 0000-00-00 00:00:00
+ ENDS: 0000-00-00 00:00:00
+ STATUS: ENABLED
+ ON_COMPLETION: NOT PRESERVE
+ CREATED: 2006-02-09 22:36:06
+ LAST_ALTERED: 2006-02-09 22:36:06
+ LAST_EXECUTED: NULL
+ EVENT_COMMENT:
1 row in set (0.00 sec)
</programlisting>
+
+ <para>
+ (<emphasis role="bold">Note</emphasis>: Prior to MySQL 5.1.12,
+ there was no <literal>EVENT_DEFINITION</literal> column, and
+ <literal>EVENT_BODY</literal> contained the SQL statement or
+ statements to be executed. See <xref linkend="events-table"/>, for
+ more information.)
+ </para>
<para>
To rescind the <literal>EVENT</literal> privilege, use the
Modified: trunk/refman-5.1/information-schema.xml
===================================================================
--- trunk/refman-5.1/information-schema.xml 2006-06-28 05:55:22 UTC (rev 2537)
+++ trunk/refman-5.1/information-schema.xml 2006-06-28 07:03:18 UTC (rev 2538)
@@ -3966,6 +3966,11 @@
<entry>MySQL extension</entry>
</row>
<row>
+ <entry><literal>EVENT_DEFINITION</literal></entry>
+ <entry/>
+ <entry>MySQL extension</entry>
+ </row>
+ <row>
<entry><literal>EVENT_TYPE</literal></entry>
<entry><literal>Type</literal></entry>
<entry>MySQL extension</entry>
@@ -4078,10 +4083,30 @@
<listitem>
<para>
- <literal>EVENT_BODY</literal>: The text of the SQL statement
+ <literal>EVENT_BODY</literal>: The language used for the
+ statements in the event's <literal>DO</literal> clause; in
+ MySQL ¤t-series;, this is always <literal>SQL</literal>.
+ </para>
+
+ <para>
+ This column was added in MySQL 5.1.12. It is not to be
+ confused with the column of the same name (now named
+ <literal>EVENT_DEFINITION</literal>) that existed in earlier
+ MySQL versions.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>EVENT_DEFINITION</literal>: The text of the SQL statement
making up the event's <literal>DO</literal> clause; in other
words, the statement executed by this event.
</para>
+
+ <para>
+ <emphasis role="bold">Note</emphasis>: Prior to MySQL 5.1.12,
+ this column was named <literal>EVENT_BODY</literal>.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-06-28 05:55:22 UTC (rev 2537)
+++ trunk/refman-common/news-5.1.xml 2006-06-28 07:03:18 UTC (rev 2538)
@@ -129,6 +129,29 @@
<xref linkend="plugin-writing"/>.
</para>
</listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Incompatible change</emphasis>: In the
+ <literal>INFORMATION_SCHEMA.EVENTS</literal> table, the
+ <literal>EVENT_DEFINITION</literal> column now contains the
+ SQL executed by a scheduled event.
+ </para>
+
+ <para>The <literal>EVENT_BODY</literal> column now contains the
+ language used for the statement or statements shown in
+ <literal>EVENT_DEFINITION</literal>. In MySQL 5.1, the value
+ shown in <literal>EVENT_BODY</literal> is always
+ <literal>SQL</literal>.
+ </para>
+
+ <para>
+ These changes were made to bring this table into line with the
+ <literal>INFORMATION_SCHEMA.ROUTINES</literal> table, and that
+ table's <literal>ROUTINE_BODY</literal> and
+ <literal>ROUTINE_DEFINITION</literal> columns. (Bug #16992)
+ </para>
+ </listitem>
<listitem>
<para>
@@ -251,6 +274,15 @@
<listitem>
<para>
+ It was possible using <literal>ALTER EVENT ... RENAME
+ ...</literal> to move an event to a database on which the
+ user did not have the <literal>EVENT</literal> privilege. (Bug
+ #18897)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal> (Disk Data): The failure of a
<literal>CREATE TABLESPACE</literal> or <literal>CREATE
LOGFILE GROUP</literal> statement did not revert all changes
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r2538 - in trunk: refman-5.1 refman-common | jon | 28 Jun |
