Author: jstephens
Date: 2006-02-20 12:20:11 +0100 (Mon, 20 Feb 2006)
New Revision: 1400
Log:
RENAME DATABASE / RENAME SCHEMA does not migrate stored routines or events.
(Thanks, Andrey!)
Modified:
trunk/refman-5.1/events.xml
trunk/refman-5.1/restrictions.xml
trunk/refman-5.1/sql-syntax.xml
Modified: trunk/refman-5.1/events.xml
===================================================================
--- trunk/refman-5.1/events.xml 2006-02-19 21:52:08 UTC (rev 1399)
+++ trunk/refman-5.1/events.xml 2006-02-20 11:20:11 UTC (rev 1400)
@@ -1362,6 +1362,13 @@
SCHEMA</literal> drops all events associated with the dropped
schema.
</para>
+
+ <para>
+ As with stored routines, events are not migrated to the new
+ schema by the <literal>RENAME SCHEMA</literal> (or
+ <literal>RENAME DATABASE</literal>) statement. See
+ <xref linkend="rename-database"/>.
+ </para>
</section>
Modified: trunk/refman-5.1/restrictions.xml
===================================================================
--- trunk/refman-5.1/restrictions.xml 2006-02-19 21:52:08 UTC (rev 1399)
+++ trunk/refman-5.1/restrictions.xml 2006-02-20 11:20:11 UTC (rev 1400)
@@ -239,6 +239,12 @@
which cannot return a value. To exit a trigger immediately, use
the <literal>LEAVE</literal> statement.
</para>
+
+ <para>
+ The <literal>RENAME DATABASE</literal> statement does not migrate
+ stored routines to the new schema name. See
+ <xref linkend="rename-database"/>.
+ </para>
</section>
Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml 2006-02-19 21:52:08 UTC (rev 1399)
+++ trunk/refman-5.1/sql-syntax.xml 2006-02-20 11:20:11 UTC (rev 1400)
@@ -3692,6 +3692,34 @@
<literal>RENAME DATABASE</literal> does not change any account
privileges listed in the system tables.
</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"/>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1400 - trunk/refman-5.1 | jon | 20 Feb |
