svn commit - mysqldoc@docsrva: r1686 - in trunk: refman-5.1 refman-common

[jon]

Author: jstephens
Date: 2006-03-27 16:35:03 +0200 (Mon, 27 Mar 2006)
New Revision: 1686

Log:

Documenting bugfixes:
  Partitioning: Bug #16806
  Event Scheduler: Bug #16415



Modified:
   trunk/refman-5.1/events.xml
   trunk/refman-common/news-5.1.xml

Modified: trunk/refman-5.1/events.xml
===================================================================
--- trunk/refman-5.1/events.xml	2006-03-27 14:04:41 UTC (rev 1685)
+++ trunk/refman-5.1/events.xml	2006-03-27 14:35:03 UTC (rev 1686)
@@ -1386,6 +1386,20 @@
       DATABASE</literal>) statement. See
       <xref linkend="rename-database"/>.
     </para>
+    
+    <para>
+      Beginning with MySQL 5.1.8, event names are handled in
+      case-insensitive fashion. For example, this means that you cannot
+      have two events in the same database and with the same definer,
+      and having the names <literal>anEvent</literal> and
+      <literal>AnEvent</literal>. 
+      <emphasis role="bold">Important</emphasis>: If you have events
+      created in MySQL 5.1.7 or earlier, which are assigned to the same
+      database and have the same definer, and whose names differ only
+      with respect to lettercase, then you must rename these events to
+      respect case-sensitive handling before upgrading to MySQL 5.1.8 or
+      later.  
+    </para>
 
   </section>
 

Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml	2006-03-27 14:04:41 UTC (rev 1685)
+++ trunk/refman-common/news-5.1.xml	2006-03-27 14:35:03 UTC (rev 1686)
@@ -246,6 +246,16 @@
       
       <listitem>
         <para>
+          <emphasis role="bold">Security Enhancement</emphasis>: Checks
+          for permissions on database operations were performed in a
+          case-insensitive manner, meaning that a user with permissions
+          on database <literal>MYDATABASE</literal> also had permissions
+          on database <literal>myDataBase</literal>. (Bug #17279)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
           The <literal>NDBCluster</literal> storage engine now supports
           <literal>INSERT IGNORE</literal> and <literal>REPLACE</literal>
           statements. Previously, these statements failed with an error. (Bug
@@ -260,6 +270,15 @@
           beginning of the Unix epoch.) (Bug #16396)
         </para>
       </listitem>
+      
+      <listitem>
+        <para>
+          Event names are now case-insenstive. That is (for example),
+          you cannot have events with the names
+          <literal>Myevent</literal> and <literal>MyEvent</literal>
+          belonging to the same database and definer. (Bug #16415)
+        </para>
+      </listitem>
 
       <listitem>
         <para>
@@ -465,16 +484,6 @@
 
       <listitem>
         <para>
-          <emphasis role="bold">Security Enhancement</emphasis>: Checks
-          for permissions on database operations were performed in a
-          case-insensitive manner, meaning that a user with permissions
-          on database <literal>MYDATABASE</literal> also had permissions
-          on database <literal>myDataBase</literal>. (Bug #17279)
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
           The client API will now attempt to reconnect on TCP/IP if the
           <literal>reconnect</literal> flag is set, as is the case with
           sockets. (Bug #2845)
@@ -488,6 +497,13 @@
     </para>
 
     <itemizedlist>
+      
+      <listitem>
+        <para>
+          <literal>ALTER TABLE ... ADD COLUMN ... AFTER ...</literal>
+          failed when used on partitioned tables. (Bug #16806)
+        </para>
+      </listitem>
 
       <listitem>
         <para>