Author: paul
Date: 2006-12-06 18:27:28 +0100 (Wed, 06 Dec 2006)
New Revision: 4135
Log:
r16770@polar: paul | 2006-12-06 11:22:33 -0600
Add note to upgrade sections to point out implications of
upgrade on function name resolution.
Modified:
trunk/refman-4.1/installing.xml
trunk/refman-5.0/installing-cs.xml
trunk/refman-5.1/installing.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:16769
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:13158
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:12611
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:16770
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:13158
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:12611
Modified: trunk/refman-4.1/installing.xml
===================================================================
--- trunk/refman-4.1/installing.xml 2006-12-06 17:27:16 UTC (rev 4134)
+++ trunk/refman-4.1/installing.xml 2006-12-06 17:27:28 UTC (rev 4135)
Changed blocks: 3, Lines Added: 31, Lines Deleted: 0; 2082 bytes
@@ -12078,6 +12078,23 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ If you have created a user-defined function (UDF) with a given
+ name and upgrade MySQL to a version that implements a new
+ built-in function with the same name, the UDF becomes
+ inaccessible. To correct this, use <literal>DROP
+ FUNCTION</literal> to drop the UDF, and then use
+ <literal>CREATE FUNCTION</literal> to re-create the UDF with a
+ different non-conflicting name. The same is true if the new
+ version of MySQL implements a built-in function with the same
+ name as an existing stored function. See
+ <xref linkend="function-resolution"/>, for the rules
+ describing how the server interprets references to different
+ kinds of functions.
+ </para>
+ </listitem>
+
</itemizedlist>
<para>
@@ -12179,6 +12196,13 @@
<listitem>
<para>
+ Check the items in <xref linkend="upgrade"/>, to see whether
+ any of them might affect your applications.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Check the items in the change lists found later in this
section to see whether any of them might affect your
applications. Note particularly any that are marked
@@ -13132,6 +13156,13 @@
<listitem>
<para>
+ Check the items in <xref linkend="upgrade"/>, to see whether
+ any of them might affect your applications.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Check the items in the change list found later in this
section to see whether any of them might affect your
applications. Note particularly any that are marked
Modified: trunk/refman-5.0/installing-cs.xml
===================================================================
--- trunk/refman-5.0/installing-cs.xml 2006-12-06 17:27:16 UTC (rev 4134)
+++ trunk/refman-5.0/installing-cs.xml 2006-12-06 17:27:28 UTC (rev 4135)
Changed blocks: 2, Lines Added: 24, Lines Deleted: 0; 1630 bytes
@@ -11156,6 +11156,23 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ If you have created a user-defined function (UDF) with a given
+ name and upgrade MySQL to a version that implements a new
+ built-in function with the same name, the UDF becomes
+ inaccessible. To correct this, use <literal>DROP
+ FUNCTION</literal> to drop the UDF, and then use
+ <literal>CREATE FUNCTION</literal> to re-create the UDF with a
+ different non-conflicting name. The same is true if the new
+ version of MySQL implements a built-in function with the same
+ name as an existing stored function. See
+ <xref linkend="function-resolution"/>, for the rules
+ describing how the server interprets references to different
+ kinds of functions.
+ </para>
+ </listitem>
+
</itemizedlist>
<para>
@@ -11260,6 +11277,13 @@
<listitem>
<para>
+ Check the items in <xref linkend="upgrade"/>, to see whether
+ any of them might affect your applications.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Check the items in the change lists found later in this
section to see whether any of them might affect your
applications. Note particularly any that are marked
Modified: trunk/refman-5.1/installing.xml
===================================================================
--- trunk/refman-5.1/installing.xml 2006-12-06 17:27:16 UTC (rev 4134)
+++ trunk/refman-5.1/installing.xml 2006-12-06 17:27:28 UTC (rev 4135)
Changed blocks: 3, Lines Added: 24, Lines Deleted: 8; 2122 bytes
@@ -11768,14 +11768,6 @@
<itemizedlist>
- <remark role="todo">
- If and when separate editions of the RefMan are prepared for
- 3.23 and 4.0, change the last sentence to something like, "For
- information on upgrading between release series earlier than
- MySQL 4.1, see the edition of the MySQL Reference Manual
- corresponding to that release series."
- </remark>
-
<listitem>
<para>
Before upgrading from MySQL &previous-series; to
@@ -11846,6 +11838,23 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ If you have created a user-defined function (UDF) with a given
+ name and upgrade MySQL to a version that implements a new
+ built-in function with the same name, the UDF becomes
+ inaccessible. To correct this, use <literal>DROP
+ FUNCTION</literal> to drop the UDF, and then use
+ <literal>CREATE FUNCTION</literal> to re-create the UDF with a
+ different non-conflicting name. The same is true if the new
+ version of MySQL implements a built-in function with the same
+ name as an existing stored function. See
+ <xref linkend="function-resolution"/>, for the rules
+ describing how the server interprets references to different
+ kinds of functions.
+ </para>
+ </listitem>
+
</itemizedlist>
<para>
@@ -11944,6 +11953,13 @@
<listitem>
<para>
+ Check the items in <xref linkend="upgrade"/>, to see whether
+ any of them might affect your applications.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Check the items in the change lists found later in this
section to see whether any of them might affect your
applications. Note particularly any that are marked
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r4135 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 6 Dec |
