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

[stefan]

Author: shinz
Date: 2006-02-20 18:14:01 +0100 (Mon, 20 Feb 2006)
New Revision: 1407

Log:
Make warnings about RENAME SCHEMA limitations show up more, uh, phat

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

Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml	2006-02-20 16:49:49 UTC (rev 1406)
+++ trunk/refman-5.1/sql-syntax.xml	2006-02-20 17:14:01 UTC (rev 1407)
@@ -3680,48 +3680,58 @@
       </para>
 
       <para>
-        When the server receives this statement, it creates the new
+        When the server receives this statement, it creates a new
         database. Then it moves tables and other database objects such
         as triggers to the new database. It also updates the
         <literal>Db</literal> column in the system tables for objects
         such as stored routines and events. Finally, the server drops
         the old database.
       </para>
-
+      
       <para>
-        <literal>RENAME DATABASE</literal> does not change any account
-        privileges listed in the system tables.
+        <emphasis role="bold">Note that currently there are these
limitations:</emphasis>
+        <itemizedlist>
+          <listitem>
+            <para>
+              <literal>RENAME DATABASE</literal> does not change any account
+              privileges listed in the system tables. This needs to be changed
+              manually.
+            </para>
+          </listitem>
+          <listitem>
+            <para>
+              <literal>RENAME DATABASE</literal> does not migrate any stored
+              routines or events to the new schema name. This means that:
+              <itemizedlist>
+                
+                <listitem>
+                  <para>
+                    For stored routines, it does not change any values in the
+                    <literal>ROUTINE_SCHEMA</literal> column of the
+                    <literal>INFORMATION_SCHEMA.ROUTINES</literal> table, or
in
+                    the <literal>db</literal> column of the
+                    <literal>mysql.proc</literal> table.
+                  </para>
+                </listitem>
+                
+                <listitem>
+                  <para>
+                    For events, it does not change any values in the
+                    <literal>EVENT_SCHEMA</literal> column of the
+                    <literal>INFORMATION_SCHEMA.EVENTS</literal> table, or in
+                    the <literal>db</literal> column of the
+                    <literal>mysql.event</literal> table.
+                  </para>
+                </listitem>
+                
+              </itemizedlist>
+              
+            </para>
+          </listitem>
+        </itemizedlist>
+        
       </para>
 
-      <para>
-        This statement does not migrate any stored routines or events to
-        the new schema name. This means that:
-      </para>
-
-      <itemizedlist>
-
-        <listitem>
-          <para>
-            For stored routines, it does not change any values in the
-            <literal>ROUTINE_SCHEMA</literal> column of the
-            <literal>INFORMATION_SCHEMA.ROUTINES</literal> table, or in
-            the <literal>db</literal> column of the
-            <literal>mysql.proc</literal> table.
-          </para>
-        </listitem>
-
-        <listitem>
-          <para>
-            For events, it does not change any values in the
-            <literal>EVENT_SCHEMA</literal> column of the
-            <literal>INFORMATION_SCHEMA.EVENTS</literal> table, or in
-            the <literal>db</literal> column of the
-            <literal>mysql.event</literal> table.
-          </para>
-        </listitem>
-
-      </itemizedlist>
-
       <remark role="help-description-end"/>
 
       <para>