MySQL Server Version Reference :: 5 Key changes in MySQL releases :: 5.2 Key changes in MySQL 5.1 releases :: 5.2.4 Changes in MySQL 5.1.37 (13 July 2009)
Section Navigation [Toggle]
- 5.2 Key changes in MySQL 5.1 releases
- 5.2.1 Changes in MySQL 5.1.43 (15 January 2010)
- 5.2.2 Changes in MySQL 5.1.41 (05 November 2009)
- 5.2.3 Changes in MySQL 5.1.40 (06 October 2009)
- 5.2.4 Changes in MySQL 5.1.37 (13 July 2009)
- 5.2.5 Changes in MySQL 5.1.36 (16 June 2009)
- 5.2.6 Changes in MySQL 5.1.32 (14 February 2009)
- 5.2.7 Changes in MySQL 5.1.31sp1 [QSP] (19 March 2009)
- 5.2.8 Changes in MySQL 5.1.29 (11 October 2008)
- 5.2.9 Changes in MySQL 5.1.28 (28 August 2008)
- 5.2.10 Changes in MySQL 5.1.23 (29 January 2008)
- 5.2.11 Changes in MySQL 5.1.21 (16 August 2007)
- 5.2.12 Changes in MySQL 5.1.20 (25 June 2007)
- 5.2.13 Changes in MySQL 5.1.19 (25 May 2007)
- 5.2.14 Changes in MySQL 5.1.18 (08 May 2007)
- 5.2.15 Changes in MySQL 5.1.17 (04 April 2007)
- 5.2.16 Changes in MySQL 5.1.16 (26 February 2007)
- 5.2.17 Changes in MySQL 5.1.15 (25 January 2007)
- 5.2.18 Changes in MySQL 5.1.14 (05 December 2006)
- 5.2.19 Changes in MySQL 5.1.13 (Not released)
- 5.2.20 Changes in MySQL 5.1.12 (24 October 2006)
Bugs fixed:
-
Partitioning: Security Fix: Accessing a table having user-defined partitioning when the server SQL mode included
ONLY_FULL_GROUP_BYcaused the MySQL server to crash. For example, the following sequence of statements crashed the server:DROP TABLE IF EXISTS t1; SET SESSION SQL_MODE='ONLY_FULL_GROUP_BY'; CREATE TABLE t1 (id INT, KEY(id)) PARTITION BY HASH(id) PARTITIONS 2; Security Fix: The
strxnmov()library function could write a null byte after the end of the destination buffer. (Bug#44834)
