- 5.1 Key changes in MySQL 5.0 releases
- 5.1.1 Changes in MySQL 5.0.90 (15 January 2010)
- 5.1.2 Changes in MySQL 5.0.88 (04 November 2009)
- 5.1.3 Changes in MySQL 5.0.87sp1 [QSP] (03 February 2010)
- 5.1.4 Changes in MySQL 5.0.87 (15 October 2009)
- 5.1.5 Changes in MySQL 5.0.84 (07 July 2009)
- 5.1.6 Changes in MySQL 5.0.77 (28 January 2009)
- 5.1.7 Changes in MySQL 5.0.75 (17 December 2008)
- 5.1.8 Changes in MySQL 5.0.72 [MRU] (24 October 2008)
- 5.1.9 Changes in MySQL 5.0.70 [MRU] (27 September 2008)
- 5.1.10 Changes in MySQL 5.0.68 [MRU] (13 August 2008)
- 5.1.11 Changes in MySQL 5.0.67 (04 August 2008)
- 5.1.12 Changes in MySQL 5.0.66sp1 [QSP] (23 October 2008)
- 5.1.13 Changes in MySQL 5.0.66 [MRU] (09 July 2008)
- 5.1.14 Changes in MySQL 5.0.64 [MRU] (10 June 2008)
- 5.1.15 Changes in MySQL 5.0.60 [MRU] (28 April 2008)
- 5.1.16 Changes in MySQL 5.0.56sp1 [QSP] (30 March 2008)
- 5.1.17 Changes in MySQL 5.0.54a [MRU] (11 January 2008)
- 5.1.18 Changes in MySQL 5.0.54 [MRU] (14 December 2007)
- 5.1.19 Changes in MySQL 5.0.52 [MRU] (30 November 2007)
- 5.1.20 Changes in MySQL 5.0.51a (11 January 2008)
- 5.1.21 Changes in MySQL 5.0.51 (15 November 2007)
- 5.1.22 Changes in MySQL 5.0.50sp1 [QSP] (12 December 2007)
- 5.1.23 Changes in MySQL 5.0.50 [MRU] (19 October 2007)
- 5.1.24 Changes in MySQL 5.0.48 [MRU] (27 August 2007)
- 5.1.25 Changes in MySQL 5.0.45 (04 July 2007)
- 5.1.26 Changes in MySQL 5.0.44 [MRU] (21 June 2007)
- 5.1.27 Changes in MySQL 5.0.42 [MRU] (23 May 2007)
- 5.1.28 Changes in MySQL 5.0.41 (01 May 2007)
- 5.1.29 Changes in MySQL 5.0.38 [MRU] (20 March 2007)
- 5.1.30 Changes in MySQL 5.0.37 (27 February 2007)
- 5.1.31 Changes in MySQL 5.0.36 [MRU] (20 February 2007)
- 5.1.32 Changes in MySQL 5.0.33 (09 January 2007)
- 5.1.33 Changes in MySQL 5.0.32 [MRU] (20 December 2006)
- 5.1.34 Changes in MySQL 5.0.30sp1 [QSP] (19 January 2007)
- 5.1.35 Changes in MySQL 5.0.25 (15 September 2006)
- 5.1.36 Changes in MySQL 5.0.24 (27 July 2006)
- 5.1.37 Changes in MySQL 5.0.23 (Not released)
- 5.1.38 Changes in MySQL 5.0.22 (24 May 2006)
- 5.1.39 Changes in MySQL 5.0.21 (02 May 2006)
- 5.1.40 Changes in MySQL 5.0.19 (04 March 2006)
- 5.1.41 Changes in MySQL 5.0.15 (19 October 2005 Production)
Functionality added or changed:
-
Incompatible Change: MySQL Cluster: The
LockPagesInMainMemoryconfiguration parameter has changed its type and possible values. For more information, seeLockPagesInMainMemory.Important
The values
trueandfalseare no longer accepted for this parameter. If you were using this parameter and had it set tofalsein a previous release, you must change it to0. If you had this parameter set totrue, you should instead use1to obtain the same behavior as previously, or2to take advantage of new functionality introduced with this release, as described in the section cited above. Incompatible Change: Previously, the
DATE_FORMAT()function returned a binary string. Now it returns a string with a character set and collation given bycharacter_set_connectionandcollation_connectionso that it can return month and weekday names containing non-ASCII characters. (Bug#22646)
Bugs fixed:
-
Security Fix: Using an
INFORMATION_SCHEMAtable withORDER BYin a subquery could cause a server crash.We would like to thank Oren Isacson of Flowgate Security Consulting and Stefan Streichsbier of SEC Consult for informing us of this problem. (Bug#24630, Bug#26556, CVE-2007-1420)
Incompatible Change: For
ENUMcolumns that had enumeration values containing commas, the commas were mapped to0xffinternally. However, this rendered the commas indistinguishable from true0xffcharacters in the values. This no longer occurs. However, the fix requires that you dump and reload any tables that haveENUMcolumns containing any true0xffvalues. Dump the tables using mysqldump with the current server before upgrading from a version of MySQL 5.0 older than 5.0.36 to version 5.0.36 or newer. (Bug#24660)
