Author: paul
Date: 2006-01-20 20:35:17 +0100 (Fri, 20 Jan 2006)
New Revision: 951
Log:
r6485@frost: paul | 2006-01-20 12:10:35 -0600
Point out an incompatibility in the 4.1 -> 5.0 upgrade section. (Bug#15610)
Modified:
trunk/
trunk/refman-5.0/installing.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6472
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2387
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6485
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2387
Modified: trunk/refman-5.0/installing.xml
===================================================================
--- trunk/refman-5.0/installing.xml 2006-01-20 17:46:29 UTC (rev 950)
+++ trunk/refman-5.0/installing.xml 2006-01-20 19:35:17 UTC (rev 951)
@@ -12465,6 +12465,23 @@
<listitem>
<para>
+ <emphasis role="bold">Incompatible change:</emphasis> Before
+ MySQL 5.0.13,
+ <literal>GREATEST(<replaceable>x</replaceable>,NULL)</literal>
+ and
+ <literal>LEAST(<replaceable>x</replaceable>,NULL)</literal>
+ return <replaceable>x</replaceable> when
+ <replaceable>x</replaceable> is a
+ non-<literal>NULL</literal> value. As of 5.0.3, both
+ functions return <literal>NULL</literal> if any argument is
+ <literal>NULL</literal>, the same as Oracle. This change can
+ cause problems for applications that rely on the old
+ behavior.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Some keywords are reserved in MySQL ¤t-series; that
were not reserved in MySQL &previous-series;. See
<xref linkend="reserved-words"/>.
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r951 - in trunk: . refman-5.0 | paul | 20 Jan |