svn commit - mysqldoc@docsrva: r3384 - trunk/refman-5.1

[jon]

Author: jstephens
Date: 2006-09-17 07:56:49 +0200 (Sun, 17 Sep 2006)
New Revision: 3384

Log:

Documenting Event Scheduler bugfixes:
  Bug #16394, Bug #16409, Bug #16417, Bug #18683, Bug #18896

Updated Event Scheduler Limitations (stored routines, triggers not
allowed in Event DDL).



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-09-16 17:52:19 UTC (rev 3383)
+++ trunk/refman-5.1/events.xml	2006-09-17 05:56:49 UTC (rev 3384)
Changed blocks: 2, Lines Added: 9, Lines Deleted: 2; 1037 bytes

@@ -782,6 +782,12 @@
         </listitem>
 
       </itemizedlist>
+      
+      <para>
+        The <literal>ON SCHEDULE</literal> clause may not use
+        subselects. This is true for both <literal>CREATE
+          EVENT</literal> and <literal>ALTER EVENT</literal>
statements.        
+      </para>
 
       <para>
         Normally, once an event has expired, it is immediately dropped.

@@ -1513,8 +1519,9 @@
 
     <para>
       An event may not be created, altered, or dropped by a trigger,
-      stored routine, or another event. This is by design. However, an
-      event may create, alter, or drop triggers and stored routines.
+      stored routine, or another event. An event also may not create,
+      alter, or drop triggers or stored routines. (Bug #16409, Bug
+      #18896)
     </para>
 
     <para>


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2006-09-16 17:52:19 UTC (rev 3383)
+++ trunk/refman-5.1/news-5.1.xml	2006-09-17 05:56:49 UTC (rev 3384)
Changed blocks: 1, Lines Added: 38, Lines Deleted: 0; 1877 bytes

@@ -683,6 +683,44 @@
 REPAIR TABLE <replaceable>tbl_name</replaceable> QUICK;
 </programlisting>
       </listitem>
+      
+      <listitem>
+        <para>
+          Memory used by scheduled events was not freed when the events
+          were dropped. (Bug #18683)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          A scheduled event that took longer to execute than the length
+          of time scheduled between successive executions could
+          <quote>skip</quote> executions. For example, an event
+          defined with <literal>EVERY 1 SECOND</literal> &mdash; but
+          which required longer than 1 second to complete &mdash; might
+          be excuted only once every 2 seconds. (Bug #16417)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          When used in the <literal>DO</literal> clause of a
<literal>CREATE
+            EVENT</literal> statement, the statements <literal>CREATE
+              EVENT</literal>, <literal>CREATE FUNCTION</literal>, and
+          <literal>CREATE PROCEDURE</literal> caused the server to
+          crash. (These statements are not permitted inside <literal>CREATE
+            EVENT</literal>.) (Bug #16409, Bug #18896) 
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          A subselect used in the <literal>ON SCHEDULE</literal> clause
+          of a <literal>CREATE EVENT</literal> or <literal>ALTER
+            EVENT</literal> statement caused the server to crash, rather
+          than producing an error as expected. (Bug #16394)
+        </para>
+      </listitem>
 
       <listitem>
         <para>