From: jon
Date: May 30 2006 3:43pm
Subject: svn commit - mysqldoc@docsrva: r2229 - trunk/refman-5.1
List-Archive: http://lists.mysql.com/commits/7020
Message-Id: <200605301543.k4UFhbVs004116@docsrva.mysql.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Author: jstephens
Date: 2006-05-30 17:43:36 +0200 (Tue, 30 May 2006)
New Revision: 2229

Log:

Andrey's review of Events chapter:
  - Table references in event action clauses
  - SHOW FULL EVENTS went away in 5.1.12
  - More info about event execution timings



Modified:
   trunk/refman-5.1/events.xml
   trunk/refman-5.1/sql-syntax.xml

Modified: trunk/refman-5.1/events.xml
===================================================================
--- trunk/refman-5.1/events.xml	2006-05-30 08:25:47 UTC (rev 2228)
+++ trunk/refman-5.1/events.xml	2006-05-30 15:43:36 UTC (rev 2229)
@@ -842,9 +842,12 @@
       </para>
 
       <para>
-        <emphasis role="bold">Note</emphasis>: Any reference to a table
-        in the <literal>DO</literal> clause must be qualified with the
-        name of the schema in which the table occurs.
+        Any reference in the <literal>DO</literal> clause to a table in
+        other than the same database schema to which the event belongs
+        must be qualified with the name of the schema in which the table
+        occurs. (In MySQL 5.1.6, all tables referenced in event
+        <literal>DO</literal> clauses had to include a reference to the
+        database.)
       </para>
 
       <para>
@@ -1146,8 +1149,7 @@
 
       <listitem>
         <para>
-          Using of the <literal>SHOW EVENTS</literal> and <literal>SHOW
-          FULL EVENTS</literal> statements. See
+          Using the <literal>SHOW EVENTS</literal> statement. See
           <xref linkend="show-events"/>.
         </para>
       </listitem>
@@ -1505,13 +1507,16 @@
       stored routine, or another event. This is by design. However, an
       event may create, alter, or drop triggers and stored routines.
     </para>
-
+    
     <para>
-      The resolution of event schedules is measured in seconds. There is
-      no way to cause events scheduled to occur at the same second to
-      execute in a given order. In addition, due to rounding, the nature
-      of threaded applications, and the fact that a non-zero length of
-      time is required to create events and to signal their execution,
+      Event timings using the intervals <literal>YEAR</literal>,
+      <literal>QUARTER</literal>, <literal>MONTH</literal>, and
+      <literal>YEAR_MONTH</literal> are resolved in months; those using
+      any other interval are resolved in seconds. There is no way to
+      cause events scheduled to occur at the same second to execute in a
+      given order. In addition &mdash; due to rounding, the nature of
+      threaded applications, and the fact that a non-zero length of time
+      is required to create events and to signal their execution &mdash;
       events may be delayed by as much as 1 or 2 seconds. However, the
       time shown in the <literal>INFORMATION_SCHEMA.EVENTS</literal>
       table's <literal>LAST_EXECUTED</literal> column or the

Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml	2006-05-30 08:25:47 UTC (rev 2228)
+++ trunk/refman-5.1/sql-syntax.xml	2006-05-30 15:43:36 UTC (rev 2229)
@@ -17464,13 +17464,12 @@
         <title>&title-show-events;</title>
 
 <programlisting>
-SHOW [FULL] EVENTS [FROM <replaceable>schema_name</replaceable>] [LIKE <replaceable>pattern</replaceable>]
+SHOW EVENTS [FROM <replaceable>schema_name</replaceable>] [LIKE <replaceable>pattern</replaceable>]
 </programlisting>
 
         <para>
           In its simplest form, <literal>SHOW EVENTS</literal> lists all
-          of the events in the current schema for which the current user
-          is the definer:
+          of the events in the current schema:
         </para>
 
 <programlisting>
@@ -17632,7 +17631,7 @@
           To see events for a different schema, you can use the
           <literal>FROM</literal> clause. For example, if the
           <literal>test</literal> schema had been selected in the
-          preceding example, the user could view his events on
+          preceding example, you could view events defined on
           <literal>myschema</literal> using the following statement:
         </para>
 
@@ -17645,20 +17644,6 @@
           event name using <literal>LIKE</literal> plus a pattern.
         </para>
 
-        <remark role="note">
-          [js] Commenting out following para until we figure out what is
-          what.
-        </remark>
-
-<!-- 
-      <para>
-        Normally, only the events for which the current user is the
-        definer are shown. A user with the <literal>PROCESS</literal>
-        privilege can view events defined by all users on a given schema
-        using <literal>SHOW FULL EVENTS</literal>.
-      </para> 
--->
-
         <para>
           This statement was added in MySQL 5.1.6.
         </para>
@@ -17666,6 +17651,15 @@
         <para>
           See also <xref linkend="events-table"/>.
         </para>
+        
+      <para>
+        <emphasis role="bold">Note</emphasis>: In MySQL 5.1.11 and
+        earlier, <literal>SHOW EVENTS</literal> displayed only those
+        events for which the current user was the definer, and the
+        <literal>SHOW FULL EVENTS</literal> statement was used for
+        viewing events defined by all users on a given schema.
+        <literal>SHOW FULL EVENTS</literal> was removed in MySQL 5.1.12. 
+      </para> 
 
       </section>