站内搜索: 请输入搜索关键词
当前页面: 在线文档首页 > MySQL 4.1参考手册英文版

Appendix聽B.聽MySQL Change History - MySQL 4.1参考手册英文版

Appendix聽B.聽MySQL Change History

Table of Contents

B.1. Changes in release 4.1.x (Production)
B.1.1. Changes in release 4.1.23 (Not yet released)
B.1.2. Changes in release 4.1.22 (02 November 2006)
B.1.3. Changes in release 4.1.21 (19 July 2006)
B.1.4. Changes in release 4.1.20 (24 May 2006)
B.1.5. Changes in release 4.1.19 (29 April 2006)
B.1.6. Changes in release 4.1.18 (27 January 2006)
B.1.7. Changes in release 4.1.17 (Not released)
B.1.8. Changes in release 4.1.16 (29 November 2005)
B.1.9. Changes in release 4.1.15 (13 October 2005)
B.1.10. Changes in release 4.1.14 (17 August 2005)
B.1.11. Changes in release 4.1.13 (15 July 2005)
B.1.12. Changes in release 4.1.12 (13 May 2005)
B.1.13. Changes in release 4.1.11 (01 April 2005)
B.1.14. Changes in release 4.1.10 (12 February 2005)
B.1.15. Changes in release 4.1.9 (11 January 2005)
B.1.16. Changes in release 4.1.8 (14 December 2004)
B.1.17. Changes in release 4.1.7 (23 October 2004: Production)
B.1.18. Changes in release 4.1.6 (10 October 2004)
B.1.19. Changes in release 4.1.5 (16 September 2004)
B.1.20. Changes in release 4.1.4 (26 August 2004: Gamma)
B.1.21. Changes in release 4.1.3 (28 June 2004: Beta)
B.1.22. Changes in release 4.1.2 (28 May 2004)
B.1.23. Changes in release 4.1.1 (01 December 2003)
B.1.24. Changes in release 4.1.0 (03 April 2003: Alpha)
B.2. Changes in release 4.0.x
B.2.1. Changes in release 4.0.30 (12 February 2007)
B.2.2. Changes in release 4.0.29 (Not released)
B.2.3. Changes in release 4.0.28 (Not released)
B.2.4. Changes in release 4.0.27 (06 May 2006)
B.2.5. Changes in release 4.0.26 (08 September 2005)
B.2.6. Changes in release 4.0.25 (05 July 2005)
B.2.7. Changes in release 4.0.24 (04 March 2005)
B.2.8. Changes in release 4.0.23 (18 December 2004)
B.2.9. Changes in release 4.0.22 (27 October 2004)
B.2.10. Changes in release 4.0.21 (06 September 2004)
B.2.11. Changes in release 4.0.20 (17 May 2004)
B.2.12. Changes in release 4.0.19 (04 May 2004)
B.2.13. Changes in release 4.0.18 (12 February 2004)
B.2.14. Changes in release 4.0.17 (14 December 2003)
B.2.15. Changes in release 4.0.16 (17 October 2003)
B.2.16. Changes in release 4.0.15 (03 September 2003)
B.2.17. Changes in release 4.0.14 (18 July 2003)
B.2.18. Changes in release 4.0.13 (16 May 2003)
B.2.19. Changes in release 4.0.12 (15 March 2003: Production)
B.2.20. Changes in release 4.0.11 (20 February 2003)
B.2.21. Changes in release 4.0.10 (29 January 2003)
B.2.22. Changes in release 4.0.9 (09 January 2003)
B.2.23. Changes in release 4.0.8 (07 January 2003)
B.2.24. Changes in release 4.0.7 (20 December 2002)
B.2.25. Changes in release 4.0.6 (14 December 2002: Gamma)
B.2.26. Changes in release 4.0.5 (13 November 2002)
B.2.27. Changes in release 4.0.4 (29 September 2002)
B.2.28. Changes in release 4.0.3 (26 August 2002: Beta)
B.2.29. Changes in release 4.0.2 (01 July 2002)
B.2.30. Changes in release 4.0.1 (23 December 2001)
B.2.31. Changes in release 4.0.0 (October 2001: Alpha)
B.3. Changes in release 3.23.x
B.3.1. Changes in release 3.23.59 (Not yet released)
B.3.2. Changes in release 3.23.58 (11 September 2003)
B.3.3. Changes in release 3.23.57 (06 June 2003)
B.3.4. Changes in release 3.23.56 (13 March 2003)
B.3.5. Changes in release 3.23.55 (23 January 2003)
B.3.6. Changes in release 3.23.54 (05 December 2002)
B.3.7. Changes in release 3.23.53 (09 October 2002)
B.3.8. Changes in release 3.23.52 (14 August 2002)
B.3.9. Changes in release 3.23.51 (31 May 2002)
B.3.10. Changes in release 3.23.50 (21 April 2002)
B.3.11. Changes in release 3.23.49 (14 February 2002)
B.3.12. Changes in release 3.23.48 (07 February 2002)
B.3.13. Changes in release 3.23.47 (27 December 2001)
B.3.14. Changes in release 3.23.46 (29 November 2001)
B.3.15. Changes in release 3.23.45 (22 November 2001)
B.3.16. Changes in release 3.23.44 (31 October 2001)
B.3.17. Changes in release 3.23.43 (04 October 2001)
B.3.18. Changes in release 3.23.42 (08 September 2001)
B.3.19. Changes in release 3.23.41 (11 August 2001)
B.3.20. Changes in release 3.23.40 (18 July 2001)
B.3.21. Changes in release 3.23.39 (12 June 2001)
B.3.22. Changes in release 3.23.38 (09 May 2001)
B.3.23. Changes in release 3.23.37 (17 April 2001)
B.3.24. Changes in release 3.23.36 (27 March 2001)
B.3.25. Changes in release 3.23.35 (15 March 2001)
B.3.26. Changes in release 3.23.34a (11 March 2001)
B.3.27. Changes in release 3.23.34 (10 March 2001)
B.3.28. Changes in release 3.23.33 (09 February 2001)
B.3.29. Changes in release 3.23.32 (22 January 2001)
B.3.30. Changes in release 3.23.31 (17 January 2001: Production)
B.3.31. Changes in release 3.23.30 (04 January 2001)
B.3.32. Changes in release 3.23.29 (16 December 2000)
B.3.33. Changes in release 3.23.28 (22 November 2000: Gamma)
B.3.34. Changes in release 3.23.27 (24 October 2000)
B.3.35. Changes in release 3.23.26 (18 October 2000)
B.3.36. Changes in release 3.23.25 (29 September 2000)
B.3.37. Changes in release 3.23.24 (08 September 2000)
B.3.38. Changes in release 3.23.23 (01 September 2000)
B.3.39. Changes in release 3.23.22 (31 July 2000)
B.3.40. Changes in release 3.23.21 (04 July 2000)
B.3.41. Changes in release 3.23.20 (28 June 2000: Beta)
B.3.42. Changes in release 3.23.19
B.3.43. Changes in release 3.23.18 (11 June 2000)
B.3.44. Changes in release 3.23.17 (07 June 2000)
B.3.45. Changes in release 3.23.16 (16 May 2000)
B.3.46. Changes in release 3.23.15 (08 May 2000)
B.3.47. Changes in release 3.23.14 (09 April 2000)
B.3.48. Changes in release 3.23.13 (14 March 2000)
B.3.49. Changes in release 3.23.12 (07 March 2000)
B.3.50. Changes in release 3.23.11 (16 February 2000)
B.3.51. Changes in release 3.23.10 (30 January 2000)
B.3.52. Changes in release 3.23.9 (29 January 2000)
B.3.53. Changes in release 3.23.8 (02 January 2000)
B.3.54. Changes in release 3.23.7 (10 December 1999)
B.3.55. Changes in release 3.23.6 (15 December 1999)
B.3.56. Changes in release 3.23.5 (20 October 1999)
B.3.57. Changes in release 3.23.4 (28 September 1999)
B.3.58. Changes in release 3.23.3 (13 September 1999)
B.3.59. Changes in release 3.23.2 (09 August 1999)
B.3.60. Changes in release 3.23.1 (08 July 1999)
B.3.61. Changes in release 3.23.0 (05 July 1999: Alpha)
B.4. Changes in InnoDB
B.4.1. Changes in MySQL/InnoDB-4.0.21, September 10, 2004
B.4.2. Changes in MySQL/InnoDB-4.1.4, August 31, 2004
B.4.3. Changes in MySQL/InnoDB-4.1.3, June 28, 2004
B.4.4. Changes in MySQL/InnoDB-4.1.2, May 30, 2004
B.4.5. Changes in MySQL/InnoDB-4.0.20, May 18, 2004
B.4.6. Changes in MySQL/InnoDB-4.0.19, May 4, 2004
B.4.7. Changes in MySQL/InnoDB-4.0.18, February 13, 2004
B.4.8. Changes in MySQL/InnoDB-5.0.0, December 24, 2003
B.4.9. Changes in MySQL/InnoDB-4.0.17, December 17, 2003
B.4.10. Changes in MySQL/InnoDB-4.1.1, December 4, 2003
B.4.11. Changes in MySQL/InnoDB-4.0.16, October 22, 2003
B.4.12. Changes in MySQL/InnoDB-3.23.58, September 15, 2003
B.4.13. Changes in MySQL/InnoDB-4.0.15, September 10, 2003
B.4.14. Changes in MySQL/InnoDB-4.0.14, July 22, 2003
B.4.15. Changes in MySQL/InnoDB-3.23.57, June 20, 2003
B.4.16. Changes in MySQL/InnoDB-4.0.13, May 20, 2003
B.4.17. Changes in MySQL/InnoDB-4.1.0, April 3, 2003
B.4.18. Changes in MySQL/InnoDB-3.23.56, March 17, 2003
B.4.19. Changes in MySQL/InnoDB-4.0.12, March 18, 2003
B.4.20. Changes in MySQL/InnoDB-4.0.11, February 25, 2003
B.4.21. Changes in MySQL/InnoDB-4.0.10, February 4, 2003
B.4.22. Changes in MySQL/InnoDB-3.23.55, January 24, 2003
B.4.23. Changes in MySQL/InnoDB-4.0.9, January 14, 2003
B.4.24. Changes in MySQL/InnoDB-4.0.8, January 7, 2003
B.4.25. Changes in MySQL/InnoDB-4.0.7, December 26, 2002
B.4.26. Changes in MySQL/InnoDB-4.0.6, December 19, 2002
B.4.27. Changes in MySQL/InnoDB-3.23.54, December 12, 2002
B.4.28. Changes in MySQL/InnoDB-4.0.5, November 18, 2002
B.4.29. Changes in MySQL/InnoDB-3.23.53, October 9, 2002
B.4.30. Changes in MySQL/InnoDB-4.0.4, October 2, 2002
B.4.31. Changes in MySQL/InnoDB-4.0.3, August 28, 2002
B.4.32. Changes in MySQL/InnoDB-3.23.52, August 16, 2002
B.4.33. Changes in MySQL/InnoDB-4.0.2, July 10, 2002
B.4.34. Changes in MySQL/InnoDB-3.23.51, June 12, 2002
B.4.35. Changes in MySQL/InnoDB-3.23.50, April 23, 2002
B.4.36. Changes in MySQL/InnoDB-3.23.49, February 17, 2002
B.4.37. Changes in MySQL/InnoDB-3.23.48, February 9, 2002
B.4.38. Changes in MySQL/InnoDB-3.23.47, December 28, 2001
B.4.39. Changes in MySQL/InnoDB-4.0.1, December 23, 2001
B.4.40. Changes in MySQL/InnoDB-3.23.46, November 30, 2001
B.4.41. Changes in MySQL/InnoDB-3.23.45, November 23, 2001
B.4.42. Changes in MySQL/InnoDB-3.23.44, November 2, 2001
B.4.43. Changes in MySQL/InnoDB-3.23.43, October 4, 2001
B.4.44. Changes in MySQL/InnoDB-3.23.42, September 9, 2001
B.4.45. Changes in MySQL/InnoDB-3.23.41, August 13, 2001
B.4.46. Changes in MySQL/InnoDB-3.23.40, July 16, 2001
B.4.47. Changes in MySQL/InnoDB-3.23.39, June 13, 2001
B.4.48. Changes in MySQL/InnoDB-3.23.38, May 12, 2001
B.5. Changes in MySQL Cluster
B.5.1. Changes in MySQL Cluster-5.0.7 (10 June 2005)
B.5.2. Changes in MySQL Cluster-5.0.6 (26 May 2005)
B.5.3. Changes in MySQL Cluster-5.0.5 (Not released)
B.5.4. Changes in MySQL Cluster-5.0.4 (16 April 2005)
B.5.5. Changes in MySQL Cluster-5.0.3 (23 March 2005: Beta)
B.5.6. Changes in MySQL Cluster-5.0.1 (27 July 2004)
B.5.7. Changes in MySQL Cluster-4.1.13 (15 July 2005)
B.5.8. Changes in MySQL Cluster-4.1.12 (13 May 2005)
B.5.9. Changes in MySQL Cluster-4.1.11 (01 April 2005)
B.5.10. Changes in MySQL Cluster-4.1.10 (12 February 2005)
B.5.11. Changes in MySQL Cluster-4.1.9 (13 January 2005)
B.5.12. Changes in MySQL Cluster-4.1.8 (14 December 2004)
B.5.13. Changes in MySQL Cluster-4.1.7 (23 October 2004)
B.5.14. Changes in MySQL Cluster-4.1.6 (10 October 2004)
B.5.15. Changes in MySQL Cluster-4.1.5 (16 September 2004)
B.5.16. Changes in MySQL Cluster-4.1.4 (31 August 2004)
B.5.17. Changes in MySQL Cluster-4.1.3 (28 June 2004)
B.6. MySQL Connector/ODBC (MyODBC) Change History
B.6.1. Changes in Connector/ODBC 5.0.11 (31 January 2007)
B.6.2. Changes in Connector/ODBC 5.0.10 (14 December 2006)
B.6.3. Changes in Connector/ODBC 5.0.9 (22 November 2006)
B.6.4. Changes in Connector/ODBC 5.0.8 (17 November 2006)
B.6.5. Changes in Connector/ODBC 5.0.7 (08 November 2006)
B.6.6. Changes in Connector/ODBC 5.0.6 (03 November 2006)
B.6.7. Changes in Connector/ODBC 5.0.5 (17 October 2006)
B.6.8. Changes in Connector/ODBC 5.0.3 (Connector/ODBC 5.0 Alpha 3) (20 June 2006)
B.6.9. Changes in Connector/ODBC 5.0.2 (Never released)
B.6.10. Changes in Connector/ODBC 5.0.1 (Connector/ODBC 5.0 Alpha 2) (05 June 2006)
B.6.11. Changes in Connector/ODBC 3.51.15 (Not yet released)
B.6.12. Changes in Connector/ODBC 3.51.14 (08 March 2007)
B.6.13. Changes in Connector/ODBC 3.51.13 (Never released)
B.6.14. Changes in Connector/ODBC 3.51.12
B.6.15. Changes in Connector/ODBC 3.51.11
B.7. Connector/NET Change History
B.7.1. Changes in MySQL Connector/NET Version 5.0.7 (Not yet released)
B.7.2. Changes in MySQL Connector/NET Version 5.0.6 (22 March 2007)
B.7.3. Changes in MySQL Connector/NET Version 5.0.5 (07 March 2007)
B.7.4. Changes in MySQL Connector/NET Version 5.0.4 (Not released)
B.7.5. Changes in MySQL Connector/NET Version 5.0.3 (05 January 2007)
B.7.6. Changes in MySQL Connector/NET Version 5.0.2 (06 November 2006)
B.7.7. Changes in MySQL Connector/NET Version 5.0.1 (01 October 2006)
B.7.8. Changes in MySQL Connector/NET Version 5.0.0 (08 August 2006)
B.7.9. Changes in MySQL Connector/NET Version 1.0.10 (Not yet released)
B.7.10. Changes in MySQL Connector/NET Version 1.0.9 (02 February 2007
B.7.11. Changes in MySQL Connector/NET Version 1.0.8 (20 October 2006)
B.7.12. Changes in MySQL Connector/NET Version 1.0.7 (21 November 2005)
B.7.13. Changes in MySQL Connector/NET Version 1.0.6 (03 October 2005)
B.7.14. Changes in MySQL Connector/NET Version 1.0.5 (29 August 2005)
B.7.15. Changes in MySQL Connector/NET Version 1.0.4 (20 January 2005)
B.7.16. Changes in MySQL Connector/NET Version 1.0.3-gamma (12 October 2004)
B.7.17. Changes in MySQL Connector/NET Version 1.0.2-gamma (15 November 2004)
B.7.18. Changes in MySQL Connector/NET Version 1.0.1-beta2 (27 October 2004)
B.7.19. Changes in MySQL Connector/NET Version 1.0.0 (01 September 2004)
B.7.20. Changes in MySQL Connector/NET Version 0.9.0 (30 August 2004)
B.7.21. Changes in MySQL Connector/NET Version 0.76
B.7.22. Changes in MySQL Connector/NET Version 0.75
B.7.23. Changes in MySQL Connector/NET Version 0.74
B.7.24. Changes in MySQL Connector/NET Version 0.71
B.7.25. Changes in MySQL Connector/NET Version 0.70
B.7.26. Changes in MySQL Connector/NET Version 0.68
B.7.27. Changes in MySQL Connector/NET Version 0.65
B.7.28. Changes in MySQL Connector/NET Version 0.60
B.7.29. Changes in MySQL Connector/NET Version 0.50
B.8. MySQL Connector/J Change History
B.8.1. Changes in MySQL Connector/J 5.1.x
B.8.2. Changes in MySQL Connector/J 5.0.x
B.8.3. Changes in MySQL Connector/J 3.1.x
B.8.4. Changes in MySQL Connector/J 3.0.x
B.8.5. Changes in MySQL Connector/J 2.0.x
B.8.6. Changes in MySQL Connector/J 1.2b (04 July 1999)
B.8.7. Changes in MySQL Connector/J 1.2.x and lower

This appendix lists the changes from version to version in the MySQL source code through the latest version of MySQL 4.1.

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Note that we tend to update the manual at the same time we make changes to MySQL. If you find a recent version of MySQL listed here that you can't find on our download page (http://dev.mysql.com/downloads/), it means that the version has not yet been released.

The date mentioned with a release version is the date of the last BitKeeper ChangeSet on which the release was based, not the date when the packages were made available. The binaries are usually made available a few days after the date of the tagged ChangeSet, because building and testing all packages takes some time.

The manual included in the source and binary distributions may not be fully accurate when it comes to the release changelog entries, because the integration of the manual happens at build time. For the most up-to-date release changelog, please refer to the online version instead.

B.1.聽Changes in release 4.1.x (Production)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Version 4.1 of the MySQL server includes many enhancements and new features. Binaries for this version are available for download at http://dev.mysql.com/downloads/mysql-4.1.html.

For a full list of changes, please refer to the changelog sections for each individual 4.1.x release.

B.1.1.聽Changes in release 4.1.23 (Not yet released)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

This is a bugfix release for the MySQL 4.1 release family.

Functionality added or changed:

  • Incompatible change: Previously, the DATE_FORMAT() function returned a binary string. Now it returns a string with a character set and collation given by character_set_connection and collation_connection so that it can return month and weekday names containing non-ASCII characters. (Bug#22646)

  • Incompatible change: The prepared_stmt_count system variable has been converted to the Prepared_stmt_count global status variable (viewable with the SHOW GLOBAL STATUS statement). (Bug#23159)

  • mysqldump --single-transaction now uses START TRANSACTION /*!40100 WITH CONSISTENT SNAPSHOT */ rather than BEGIN to start a transaction, so that a consistent snapshot will be used on those servers that support it. (Bug#19660)

  • Important: When using MERGE tables the definition of the MERGE table and the MyISAM tables are checked each time the tables are opened for access (including any SELECT or INSERT statement. Each table is compared for column order, types, sizes and associated. If there is a difference in any one of the tables then the statement will fail.

  • The --memlock option relies on system calls that are unreliable on some operating systems. If a crash occurs, the server now checks whether --memlock was specified and if so issues some information about possible workarounds. (Bug#22860)

  • The server now includes a timestamp in error messages that are logged as a result of unhandled signals (such as mysqld got signal 11 messages). (Bug#24878)

Bugs fixed:

  • Security fix: The requirement of the DROP privilege for RENAME TABLE was not being enforced. (Bug#27515)

  • Incompatible change: For ENUM columns that had enumeration values containing commas, the commas were mapped to 0xff internally. However, this rendered the commas indistinguishable from true 0xff characters in the values. This no longer occurs. However, the fix requires that you dump and reload any tables that have ENUM columns containing true 0xff in their values: Dump the tables using mysqldump with the current server before upgrading from a version of MySQL 4.1 older than 4.1.23 to version 4.1.23 or newer. (Bug#24660)

  • Incompatible change: INSERT DELAYED statements are not supported for MERGE tables, but the MERGE storage engine was not rejecting such statements, resulting in table corruption. Applications previously using INSERT DELAYED into MERGE table will break when upgrading to versions with this fix. To avoid the problem, remove DELAYED from such statements. (Bug#26464)

  • For MERGE tables defined on underlying tables that contained a short VARCHAR column (shorter than four characters), using ALTER TABLE on at least one but not all of the underlying tables caused the table definitions to be considered different from that of the MERGE table, even if the ALTER TABLE did not change the definition. Also, when the underlying tables contained a TINYINT or CHAR(1) column, the MERGE storage engine incorrectly reported that they differed from the MERGE table in certain cases. (Bug#26881)

  • The patch for Bug#21789 was reverted.

  • Comparisons using row constructors could fail for rows containing NULL values. (Bug#27704)

  • The range optimizer could consume a combinatorial amount of memory for certain classes of WHERE clauses. (Bug#26624)

  • Conversion of DATETIME values in numeric contexts sometimes did not produce a double (YYYYMMDDHHMMSS.uuuuuu) value. (Bug#16546)

  • Passing nested row expressions with different structures to an IN predicate caused a server crash. (Bug#27484)

  • A subquery could get incorrect values for references to outer query columns when it contained aggregate functions that were aggregated in outer context. (Bug#27321)

  • Incorrect results could be returned for some queries that contained a select list expression with IN or BETWEEN together with an ORDER BY or GROUP BY on the same expression using NOT IN or NOT BETWEEN. (Bug#27532)

  • GRANT statements were not replicated if the server was started with the --replicate-ignore-table or --replicate-wild-ignore-table option. (Bug#25482)

  • For MyISAM tables, COUNT(*) could return an incorrect value if the WHERE clause compared an indexed TEXT column to the empty string (''). This happened if the column contained empty strings and also strings starting with control characters such as tab or newline. (Bug#26231)

  • Duplicate entries were not assessed correctly in a MEMORY table with a BTREE primary key on a utf8 ENUM column. (Bug#24985)

  • Storing NULL values in spatial fields caused excessive memory allocation and crashes on some systems. (Bug#27164)

  • In a MEMORY table, using a BTREE index to scan for updatable rows could lead to an infinite loop. (Bug#26996)

  • The range optimizer could cause the server to run out of memory. (Bug#26625)

  • Difficult repair or optimization operations could cause an assertion failure, resulting in a server crash. (Bug#25289)

  • DOUBLE values such as 20070202191048.000000 were being treated as illegal arguments by WEEK(). (Bug#23616)

  • If a thread previously serviced a connection that was killed, excessive memory and CPU use by the thread occurred if it later serviced a connection that had to wait for a table lock. (Bug#25966)

  • LOAD DATA INFILE sent an okay to the client before writing the binary log and committing the changes to the table had finished, thus violating ACID requirements. (Bug#26050)

  • In certain cases it could happen that deleting a row corrupted an RTREE index. This affected indexes on spatial columns. (Bug#25673)

  • Added support for --debugger=dbx for mysql-test-run.pl and fixed support for --debugger=devenv, --debugger=DevEnv, and --debugger=/path/to/devenv. (Bug#26792)

  • X() IS NULL and Y() IS NULL comparisons failed when X() and Y() returned NULL. (Bug#26038)

  • UNHEX() IS NULL comparisons failed when UNHEX() returned NULL. (Bug#26537)

  • A reference to a non-existent column in the ORDER BY clause of an UPDATE ... ORDER BY statement could cause a server crash. (Bug#25126)

  • The creation of MySQL system tables was not checked for by mysql-test-run.pl. (Bug#20166)

  • NOW() returned the wrong value in statements executed at server startup with the --init-file option. (Bug#23240)

  • For ALTER TABLE, using ORDER BY expression could cause a server crash. Now the ORDER BY clause allows only column names to be specified as sort criteria (which was the only documented syntax, anyway). (Bug#24562)

  • Storing values specified as hexadecimal values 64 or more bits long into BIGINT or BIGINT UNSIGNED columns did not raise any warning or error if the value was out of range. (Bug#22533)

  • ISNULL(DATE(NULL)) and ISNULL(CAST(NULL AS DATE)) erroneously returned false. (Bug#23938)

  • If a slave server closed its relay log (for example, due to an error during log rotation), the I/O thread did not recognize this and still tried to write to the log, causing a server crash. (Bug#10798)

  • Foreign key identifiers for InnoDB tables could not contain certain characters. (Bug#24299)

  • The number of setsockopt() calls performed for reads and writes to the network socket was reduced to decrease system call overhead. (Bug#22943)

  • ORDER BY on DOUBLE or DECIMAL values could change the set of rows returned by a query. (Bug#19690)

  • The InnoDB parser sometimes did not account for null bytes, causing spurious failure of some queries. (Bug#25596)

  • perror crashed on some platforms due to failure to handle a NULL pointer. (Bug#25344)

  • mysql_stmt_fetch() did an invalid memory deallocation when used with the embedded server. (Bug#25492)

  • mysqld_multi and mysqlaccess looked for option files in /etc even if the --sysconfdir option for configure had been given to specify a different directory. (Bug#24780)

  • The arguments of the ENCODE() and the DECODE() functions were not printed correctly, causing problems in the output of EXPLAIN EXTENDED. (Bug#23409)

  • A return value of -1 from user-defined handlers was not handled well and could result in conflicts with server code. (Bug#24987)

  • The server might fail to use an appropriate index for DELETE when ORDER BY, LIMIT, and a non-restricting WHERE are present. (Bug#17711)

  • For BOOLEAN mode full-text searches on non-indexed columns, NULL rows generated by a LEFT JOIN caused incorrect query results. (Bug#25637; see also Bug#14708)

  • SHOW COLUMNS reported some NOT NULL columns as NULL. (Bug#22377)

  • If an ORDER BY or GROUP BY list included a constant expression being optimized away and, at the same time, containing single-row subselects that return more that one row, no error was reported. If a query requires sorting by expressions containing single-row subselects that return more than one row, execution of the query may cause a server crash. (Bug#24653)

  • Attempts to access a MyISAM table with a corrupt column definition caused a server crash. (Bug#24401)

  • Accessing a fixed record format table with a crashed key definition results in server/myisamchk segmentation fault. (Bug#24855)

  • When opening a corrupted .frm file during a query, the server crashes. (Bug#24358)

  • If there was insufficient memory to store or update a blob record in a MyISAM table then the table will marked as crashed. (Bug#23196)

  • When updating a table that used a JOIN of the table itself (for example, when building trees) and the table was modified on one side of the expression, the table would either be reported as crashed or the wrong rows in the table would be updated. (Bug#21310)

  • No warning was issued for use of the DATA DIRECTORY or INDEX DIRECTORY table options on a platform that does not support them. (Bug#17498)

  • Hebrew-to-Unicode conversion failed for some characters. Definitions for the following Hebrew characters (as specified by the ISO/IEC 8859-8:1999) were added: LEFT-TO-RIGHT MARK (LRM), RIGHT-TO-LEFT MARK (RLM) (Bug#24037)

  • Certain joins using Range checked for each record in the query execution plan could cause the server to crash. (Bug#24776)

  • If there was insufficient memory available to mysqld, this could sometimes cause the server to hang during startup. (Bug#24751)

  • Optimizations that are legal only for subqueries without tables and WHERE conditions were applied for any subquery without tables. (Bug#24670)

  • NDB Cluster: Some queries that updated multiple tables were not backed up correctly. (Bug#27748)

  • NDB Cluster: The management client command node_id STATUS displayed the message Node node_id: not connected when node_id was not the node ID of a data node. (Bug#21715)

    Note

    The ALL STATUS command in the cluster management client still displays status information for data nodes only. This is by design. See Section聽15.7.2, 鈥淐ommands in the MySQL Cluster Management Client鈥, for more information.

  • NDB Cluster (Cluster APIs): libndbclient.so was not versioned. (Bug#13522)

  • NDB Cluster: In some circumstances, shutting down the cluster could cause connected mysqld processes to crash. (Bug#25668)

  • mysqltest incorrectly tried to retrieve result sets for some queries where no result set was available. (Bug#19410)

  • mysqltest crashed with a stack overflow. (Bug#24498)

  • The server was built even when configure was run with the --without-server option. (Bug#23973)

  • A table created with the ROW_FORMAT = FIXED table option lost the option if an index was added or dropped with CREATE INDEX or DROP INDEX. (Bug#23404)

  • The BUILD/check-cpu script did not recognize Celeron processors. (Bug#20061)

  • InnoDB exhibited thread thrashing with more than 50 concurrent connections under an update-intensive workload. (Bug#22868)

  • InnoDB showed substandard performance with multiple queries running concurrently. (Bug#15815)

  • mysql_fix_privilege_tables did not handle a password containing embedded space or apostrophe characters. (Bug#17700)

  • Changing the value of MI_KEY_BLOCK_LENGTH in myisam.h and recompiling MySQL resulted in a myisamchk that saw existing MyISAM tables as corrupt. (Bug#22119)

  • SET lc_time_names = value allowed only exact literal values, not expression values. (Bug#22647)

  • Changes to the lc_time_names system variable were not replicated. (Bug#22645)

  • mysqldump --order-by-primary failed if the primary key name was an identifier that required quoting. (Bug#13926)

  • Re-execution of CREATE DATABASE, CREATE TABLE, and ALTER TABLE statements as prepared statements caused incorrect results or crashes. (Bug#22060)

  • The internal functions for table preparation, creation, and alteration were not re-execution friendly, causing problems in code that: repeatedly altered a table; repeatedly created and dropped a table; opened and closed a cursor on a table, altered the table, and then reopened the cursor. (Bug#4968, Bug#6895, Bug#19182, Bug#19733)

  • A deadlock could occur, with the server hanging on Closing tables, with a sufficient number of concurrent INSERT DELAYED, FLUSH TABLES, and ALTER TABLE operations. (Bug#23312)

  • Referencing an ambiguous column alias in an expression in the ORDER BY clause of a query caused the server to crash. (Bug#25427)

  • User-defined variables could consume excess memory, leading to a crash caused by the exhaustion of resources available to the MEMORY storage engine, due to the fact that this engine is used by MySQL for variable storage and intermediate results of GROUP BY queries. Where SET had been used, such a condition could instead give rise to the misleading error message You may only use constant expressions with SET, rather than Out of memory (Needed NNNNNN bytes). (Bug#23443)

  • InnoDB: During a restart of the MySQL Server that followed the creation of a temporary table using the InnoDB storage engine, MySQL failed to clean up in such a way that InnoDB still attempted to find the files associated with such tables. (Bug#20867)

  • A compressed MyISAM table that became corrupted could crash myisamchk and possibly the MySQL Server. (Bug#23139)

  • A crash of the MySQL Server could occur when unpacking a BLOB column from a row in a corrupted MyISAM table. This could happen when trying to repair a table using either REPAIR TABLE or myisamchk; it could also happen when trying to access such a 鈥broken鈥 row using statements like SELECT if the table was not marked as crashed. (Bug#22053)

  • Trailing spaces were not removed from Unicode CHAR column values when used in indexes. This resulted in excessive usage of storage space, and could affect the results of some ORDER BY queries that made use of such indexes.

    Note: When upgrading, it is necessary to re-create any existing indexes on Unicode CHAR columns in order to take advantage of the fix. This can be done by using a REPAIR TABLE statement on each affected table.

    (Bug#22052)

  • The stack size for NetWare binaries was increased to 128KB to prevent problems caused by insufficient stack size. (Bug#23504)

  • ALTER ENABLE KEYS or ALTER TABLE DISABLE KEYS combined with another ALTER TABLE option other than RENAME TO did nothing. In addition, if ALTER TABLE was used on a table having disabled keys, the keys of the resulting table were enabled. (Bug#24395)

  • Queries using a column alias in an expression as part of an ORDER BY clause failed, an example of such a query being SELECT mycol + 1 AS mynum FROM mytable ORDER BY 30 - mynum. (Bug#22457)

  • STR_TO_DATE() returned NULL if the format string contained a space following a non-format character. (Bug#22029)

  • Selecting into variables sometimes returned incorrect wrong results. (Bug#20836)

  • A server crash occurred when using LOAD DATA to load a table containing a NOT NULL spatial column, when the statement did not load the spatial column. Now a NULL supplied to NOT NULL column error occurs. (Bug#22372)

  • The --extern option for mysql-test-run.pl did not function correctly. (Bug#24354)

  • ALTER TABLE statements that performed both RENAME TO and {ENABLE|DISABLE} KEYS operations caused a server crash. (Bug#24089)

  • There was a race condition in the InnoDB fil_flush_file_spaces() function. (Bug#24089)

  • Some small double precision numbers (such as 1.00000001e-300) that should have been accepted were truncated to zero. (Bug#22129)

  • LAST_DAY('0000-00-00') could cause a server crash. (Bug#23653)

  • Through the C API, the member strings in MYSQL_FIELD for a query that contains expressions may return incorrect results. (Bug#21635)

  • IN() can return NULL, but did not signal that to the query processor, causing incorrect results for IS NULL operations. (Bug#17047)

  • The server could send incorrect column count information to the client for queries that produce a larger number of columns than can fit in a two-byte number. (Bug#19216)

  • SQL statements close to the size of max_allowed_packet could produce binary log events larger than max_allowed_packet that could not be read by slave servers. (Bug#19402)

  • If elements in a non-top-level IN subquery were accessed by an index and the subquery result set included a NULL value, the quantified predicate that contained the subquery was evaluated to NULL when it should return a non-NULL value. (Bug#23478)

  • Metadata for columns calculated from scalar subqueries was limited to integer, double, or string, even if the actual type of the column was different. (Bug#11032)

  • For ODBC compatibility, MySQL supports use of WHERE col_name IS NULL for DATE or DATETIME columns that are NOT NULL, to allow column values of '0000-00-00' or '0000-00-00 00:00:00' to be selected. However, this was not working for WHERE clauses in DELETE statements. (Bug#23412)

  • mysql did not check for errors when fetching data during result set printing. (Bug#22913)

  • Adding a day, month, or year interval to a DATE value produced a DATE, but adding a week interval produced a DATETIME value. Now all produce a DATE value. (Bug#21811)

  • For not-yet-authenticated connections, the Time column in SHOW PROCESSLIST was a random value rather than NULL. (Bug#23379)

  • The Handler_rollback status variable sometimes was incremented when no rollback had taken place. (Bug#22728)

  • Lack of validation for input and output TIME values resulted in several problems: SEC_TO_TIME() within subqueries incorrectly clipped large values; SEC_TO_TIME() treated BIGINT UNSIGNED values as signed; only truncation warnings were produced when both truncation and out-of-range TIME values occurred. (Bug#11655, Bug#20927)

  • Range searches on columns with an index prefix could miss records. (Bug#20732)

  • Transient errors in replication from master to slave may trigger multiple Got fatal error 1236: 'binlog truncated in the middle of event' errors on the slave. (Bug#4053)

  • If COMPRESS() returned NULL, subsequent invocations of COMPRESS() within a result set or within a trigger also returned NULL. (Bug#23254)

  • mysql would lose its connection to the server if its standard output was not writable. (Bug#17583)

  • mysql-test-run did not work correctly for RPM-based installations. (Bug#17194)

  • The return value from my_seek() was ignored. (Bug#22828)

  • MySQL would fail to build on the Alpha platform. (Bug#23256)

B.1.2.聽Changes in release 4.1.22 (02 November 2006)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

This is a bugfix release for the MySQL 4.1 release family.

This section documents all changes and bug fixes that have been applied since the last official MySQL release. If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise.

Functionality added or changed:

  • If the user specified the server options --max-connections=N or --table-open-cache=M, a warning would be given in some cases that some values were recalculated, with the result that --table-open-cache could be assigned greater value.

    It should be noted that, in such cases, both the warning and the increase in the --table-open-cache value were completely harmless. Note also that it is not possible for the MySQL Server to predict or to control limitations on the maximum number of open files, since this is determined by the operating system.

    The recalculation code has now been fixed to ensure that the value of --table-open-cache is no longer increased automatically, and that a warning is now given only if some values had to be decreased due to operating system limits.

    (Bug#21915)

  • The mysqld manpage has been reclassified from volume 1 to volume 8. (Bug#21220)

  • MySQL now can do stack dumps on x86_64 and i386/NPTL systems. (Bug#21250)

  • The LOAD DATA FROM MASTER and LOAD TABLE FROM MASTER statements are deprecated. See Section聽13.6.2.2, 鈥LOAD DATA FROM MASTER Syntax鈥, for recommended alternatives. (Bug#18822, Bug#9125, Bug#12187, Bug#14399, Bug#15025, Bug#20596)

  • A warning now is issued if the client attempts to set the SQL_LOG_OFF variable without the SUPER privilege. (Bug#16180)

Bugs fixed:

  • Certain malformed INSERT statements could crash the mysql client. (Bug#21142)

  • Deleting entries from a large MyISAM index could cause index corruption when it needed to shrink. Deletes from an index can happen when a record is deleted, when a key changes and must be moved, and when a key must be un-inserted because of a duplicate key. This can also happen in REPAIR TABLE when a duplicate key is found and in myisamchk when sorting the records by an index. (Bug#22384)

  • Setting myisam_repair_threads caused any repair operation on a MyISAM table to fail to update the cardinality of indexes, instead making them always equal to 1. (Bug#18874)

  • Within a prepared statement, SELECT (COUNT(*) = 1) (or similar use of other aggregate functions) did not return the correct result for statement re-execution. (Bug#21354)

  • DELETE IGNORE could hang for foreign key parent deletes. (Bug#18819)

  • Redundant binary log LAST_INSERT_ID events could be generated; LAST_INSERT_ID(expr) didn't return the value of expr; LAST_INSERT_ID() could return the value generated by the current statement if the call happens after value generation, as in:

    CREATE TABLE t1 (i INT AUTO_INCREMENT PRIMARY KEY, j INT);
    INSERT INTO t1 VALUES (NULL, 0), (NULL, LAST_INSERT_ID());
    

    (Bug#21726)

  • FROM_UNIXTIME() did not accept arguments up to POWER(2,31)-1, which it had previously. (Bug#9191)

  • A literal string in a GROUP BY clause could be interpreted as a column name. (Bug#14019)

  • WITH ROLLUP could group unequal values. (Bug#20825)

  • LIKE searches failed for indexed utf8 character columns. (Bug#20471)

  • The optimizer sometimes mishandled R-tree indexes for GEOMETRY data types, resulting in a server crash. (Bug#21888)

  • Entries in the slow query log could have an incorrect Rows_examined value. (Bug#12240)

  • Insufficient memory (myisam_sort_buffer_size) could cause a server crash for several operations on MyISAM tables: repair table, create index by sort, repair by sort, parallel repair, bulk insert. (Bug#23175)

  • REPAIR TABLE ... USE_FRM could cause a server crash or hang when used for a MyISAM table in a database other than the default database. (Bug#22562)

  • OPTIMIZE TABLE with myisam_repair_threads > 1 could result in MyISAM table corruption. (Bug#8283)

  • The result for CAST() when casting a value to UNSIGNED was limited to the maximum signed BIGINT value (9223372036854775808), not the maximum unsigned value (18446744073709551615). (Bug#8663)

  • For multiple-table UPDATE statements, storage engines were not notified of duplicate-key errors. (Bug#21381)

  • Successive invocations of a COUNT(*) query containing a join on two MyISAM tables and a WHERE clause of the form WHERE (table1.column1 = table2.column2) OR table2.column2 IS NULL yielded different results. (Bug#21019)

  • Using ALTER TABLE to add an ENUM column with an enumeration value containing 0xFF caused the name of the first table column to be lost. (Bug#20922)

  • PROCEDURE ANALYSE() returned incorrect values of M FLOAT(M, D) and DOUBLE(M, D). (Bug#20305)

  • A query that used GROUP BY and an ALL or ANY quantified subquery in a HAVING clause could trigger an assertion failure. (Bug#21853)

  • For an ENUM column that used the ucs2 character set, using ALTER TABLE to modify the column definition caused the default value to be lost. (Bug#20108)

  • Creating a TEMPORARY table with the same name as an existing table that was locked by another client could result in a lock conflict for DROP TEMPORARY TABLE because the server unnecessarily tried to acquire a name lock. (Bug#21096)

  • Incorporated some portability fixes into the definition of __attribute__ in my_global.h. (Bug#2717)

  • In the package of pre-built time zone tables that is available for download at http://dev.mysql.com/downloads/timezones.html, the tables now explicitly use the utf8 character set so that they work the same way regardless of the system character set value. (Bug#21208)

  • The build process incorrectly tried to overwrite sql/lex_hash.h. This caused the build to fail when using a shadow link tree pointing to original sources that were owned by another account. (Bug#18888)

  • Execution of a prepared statement that uses an IN subquery with aggregate functions in the HAVING clause could cause a server crash. (Bug#22085)

  • Selecting from a MERGE table could result in a server crash if the underlying tables had fewer indexes than the MERGE table itself. (Bug#21617, Bug#22937)

  • SUBSTR() results sometimes were stored improperly into a temporary table when multi-byte character sets were used. (Bug#20204)

  • Parallel builds occasionally failed on Solaris. (Bug#16282)

  • The source distribution failed to compile when configured with the --without-geometry option. (Bug#12991)

  • The server returns a more informative error message when it attempts to open a MERGE table that has been defined to use non-MyISAM tables. (Bug#10974)

  • On Mac OS X, zero-byte read() or write() calls to an SMB-mounted filesystem could return a non-standard return value, leading to data corruption. Now such calls are avoided. (Bug#12620)

  • For INSERT ... ON DUPLICATE KEY UPDATE, use of VALUES(col_name) within the UPDATE clause sometimes was handled incorrectly. (Bug#21555)

  • Table aliases in multiple-table DELETE statements sometimes were not resolved. (Bug#21392)

  • EXPORT_SET() did not accept arguments with coercible character sets. (Bug#21531)

  • The --collation-server server option was being ignored. With the fix for this problem, if you choose a non-default character set with --character-set-server, you should also use --collation-server to specify the collation. (Bug#15276)

  • A subquery that uses an index for both the WHERE and ORDER BY clauses produced an empty result. (Bug#21180)

  • Queries containing a subquery that used aggregate functions could return incorrect results. (Bug#16792)

  • The MD5(), SHA1(), and ENCRYPT() functions should return a binary string, but the result sometimes was converted to the character set of the argument. MAKE_SET() and EXPORT_SET() now use the correct character set for their default separators, resulting in consistent result strings which can be coerced according to normal character set rules. (Bug#20536)

  • For a MyISAM table with a FULLTEXT index, compression with myisampack or a check with myisamchk after compression resulted in table corruption. (Bug#19702)

  • The optimizer could produce an incorrect result after AND with collations such as latin1_german2_ci, utf8_czech_ci, and utf8_lithianian_ci. (Bug#9509)

  • character_set_results can be NULL to signify 鈥no conversion,鈥 but some code did not check for NULL, resulting in a server crash. (Bug#21913)

  • The myisam_stats_method variable was mishandled when set from an option file or on the command line. (Bug#21054)

  • libmysqld produced some warnings to stderr which could not be silenced. These warnings now are suppressed. (Bug#13717)

  • If a column definition contained a character set declaration, but a DEFAULT value began with an introducer, the introducer character set was used as the column character set. (Bug#20695)

  • Some Linux-x86_64-icc packages (of previous releases) mistakenly contained 32-bit binaries. Only ICC builds are affected, not gcc builds. Solaris and FreeBSD x86_64 builds are not affected. (Bug#22238)

  • For TIME_FORMAT(), the %H and %k format specifiers can return values larger than two digits (if the hour is greater than 99), but for some query results that contained three-character hours, column values were truncated. (Bug#19844)

  • For table-format output, mysql did not always calculate columns widths correctly for columns containing multi-byte characters in the column name or contents. (Bug#17939)

  • Views could not be updated within a stored function or trigger. (Bug#17591)

  • Usernames have a maximum length of 16 characters (even if they contain multi-byte characters), but were being truncated to 16 bytes. (Bug#20393)

  • When using tables created under MySQL 4.1 with a 5.0 server, if the tables contained VARCHAR columns, for some queries the metadata sent to the client could have an empty column name. (Bug#14897)

  • On 64-bit systems, use of the cp1250 character set with a primary key column in a LIKE clause caused a server crash for patterns having letters in the range 128..255. (Bug#19741)

  • A subquery in the WHERE clause of the outer query and using IN and GROUP BY returned an incorrect result. (Bug#16255)

  • COUNT(*) queries with ORDER BY and LIMIT could return the wrong result. (Bug#21787)

    Note: This problem was introduced by the fix for Bug#9676, which limited the rows stored in a temporary table to the LIMIT clause. This optimization is not applicable to non-group queries with aggregate functions. The current fix disables the optimization in such cases.

  • Running SHOW MASTER LOGS at the same time as binary log files were being switched would cause mysqld to hang. (Bug#21965)

  • Adding ORDER BY to a SELECT DISTINCT(expr) query could produce incorrect results. (Bug#21456)

  • For InnoDB tables, the server could crash when executing NOT IN () subqueries. (Bug#21077)

  • mysqld --flush failed to flush MyISAM table changes to disk following an UPDATE statement for which no updated column had an index. (Bug#20060)

  • The --with-collation option was not honored for client connections. (Bug#7192)

  • NDB Cluster: The ndb_size.pl script did not account for TEXT and BLOB column values correctly. (Bug#21204)

  • NDB Cluster: Attempting to create an NDB table on a MySQL with an existing non-Cluster table with the same name in the same database could result in data loss or corruption. MySQL now issues a warning when a SHOW TABLES or other statement causing table discovery finds such a table. (Bug#21378)

  • NDB Cluster (NDB API): Attempting to read a nonexistent tuple using Commit mode for NdbTransaction::execute() caused node failures. (Bug#22672)

  • NDB Cluster: Restoring a cluster failed if there were any tables with 128 or more columns. (Bug#23502)

  • NDB Cluster: INSERT ... ON DUPLICATE KEY UPDATE on an NDB table could lead to deadlocks and memory leaks. (Bug#23200)

  • NDB Cluster: If a node restart could not be performed from the REDO log, no node takeover took place. This could cause partitions to be left empty during a system restart. (Bug#22893)

  • NDB Cluster: Multiple node restarts in rapid succession could cause a system restart to fail (Bug#22892), or induce a race condition (Bug#23210).

  • NDB Cluster: The node recovery algorithm was missing a version check for tables in the ALTER_TABLE_COMMITTED state (as opposed to the TABLE_ADD_COMMITTED state, which has the version check). This could cause inconsistent schemas across nodes following node recovery. (Bug#21756)

  • NDB Cluster: The output for the --help option used with NDB executable programs (ndbd, ndb_mgm, ndb_restore, ndb_config, and so on) referred to the Ndb.cfg file, instead of my.cnf. (Bug#21585)

  • NDB Cluster: The ndb_mgm management client did not set the exit status on errors, always returning 0 instead. (Bug#21530)

  • NDB Cluster: Cluster logs were not rotated following the first rotation cycle. (Bug#21345)

  • NDB Cluster: When inserting a row into an NDB table with a duplicate value for a non-primary unique key, the error issued would reference the wrong key. (Bug#21072)

  • NDB Cluster: Under some circumstances, local checkpointing would hang, keeping any unstarted nodes from being started. (Bug#20895)

  • NDB Cluster: In some cases where SELECT COUNT(*) from an NDB table should have yielded an error, MAX_INT was returned instead. (Bug#19914)

  • NDB Cluster: ndb_restore did not always make clear that it had recovered successfully from temporary errors while restoring a cluster backup. (Bug#19651)

  • NDB Cluster: A problem with takeover during a system restart caused ordered indexes to be rebuilt incorrectly. (Bug#15303)

  • NDB Cluster: The ndb_mgm program was included in both the MySQL-ndb-tools and MySQL-ndb-management RPM packages, resulting in a conflict if both were installed. Now ndb_mgm is included only in MySQL-ndb-tools. (Bug#21058)

  • NDB Cluster: ndb_size.pl and ndb_error_reporter were missing from RPM packages. (Bug#20426)

  • NDB Cluster: Setting TransactionDeadlockDetectionTimeout to a value greater than 12000 would cause scans to deadlock, time out, fail to release scan records, until the cluster ran out of scan records and stopped processing. (Bug#21800)

  • NDB Cluster: The server provided a non-descriptive error message when encountering a fatally corrupted REDO log. (Bug#21615)

  • NDB Cluster: A partial rollback could lead to node restart failures. (Bug#21536)

  • NDB Cluster: The failure of a unique index read due to an invalid schema version could be handled incorrectly in some cases, leading to unpredictable results. (Bug#21384)

  • NDB Cluster: In a cluster with more than 2 replicas, a manual restart of one of the data nodes could fail and cause the other nodes in its nodegroup to shut down. (Bug#21213)

  • NDB Cluster: When the redo buffer ran out of space, a Pointer too large error was raised and the cluster could become unusable until restarted with --initial. (Bug#20892)

  • NDB Cluster: In some situations with a high disk-load, writing of the redo log could hang, causing a crash with the error message GCP STOP detected. (Bug#20904)

  • NDB Cluster: ndb_size.pl and ndb_error_reporter were missing from RPM packages. (Bug#20426)

  • NDB Cluster: The server failed with a non-descriptive error message when out of data memory. (Bug#18475)

  • NDB Cluster: SELECT ... FOR UPDATE failed to lock the selected rows. (Bug#18184)

  • NDB Cluster: Some queries involving joins on very large NDB tables could crash the MySQL server. (Bug#21059)

  • Character set collation was ignored in GROUP BY clauses. (Bug#20709)

  • A query using WHERE column = constant OR column IS NULL did not return consistent results on successive invocations. The column in each part of the WHERE clause could be either the same column, or two different columns, for the effect to be observed. (Bug#21019)

  • A query using WHERE NOT (column < ANY (subquery)) yielded a different result from the same query using the same column and subquery with WHERE (column > ANY (subquery)). (Bug#20975)

  • Using the extended syntax for TRIM() 鈥 that is, TRIM(... FROM ...) 鈥 caused erroneous output from EXPLAIN EXTENDED statements. (Bug#17526)

  • DELETE with WHERE condition on a BTREE-indexed column for a MEMORY table deleted only the first matched row. (Bug#9719)

  • For cross-database multiple-table UPDATE statements, a user with all privileges for the default database could update tables in another database for which the user did not have UPDATE privileges. (Bug#7391)

  • mysql_install_db incorrectly had a blank first line. (Bug#20721)

  • Under heavy load (executing more than 1024 simultaneous complex queries), a problem in the code that handles internal temporary tables could lead to writing beyond allocated space and memory corruption. (Bug#21206)

  • Multiple invocations of the REVERSE() function could return different results. (Bug#18243)

  • Conversion of TIMESTAMP values between UTC and the local time zone resulted in some values having the year 2069 rather than 1969. (Bug#16327)

  • Under certain circumstances, AVG(key_val) returned a value but MAX(key_val) returned an empty set due to incorrect application of MIN()/MAX() optimization. (Bug#20954)

  • Using aggregate functions in subqueries yielded incorrect results under certain circumstances due to incorrect application of MIN()/MAX() optimization. (Bug#20792)

  • Using > ALL with subqueries that return no rows yielded incorrect results under certain circumstances due to incorrect application of MIN()/MAX() optimization. (Bug#18503)

  • Using ANY with 鈥non-table鈥 subqueries such as SELECT 1 yielded incorrect results under certain circumstances due to incorrect application of MIN()/MAX() optimization. (Bug#16302)

  • The use of WHERE col_name IS NULL in SELECT statements reset the value of LAST_INSERT_ID() to zero. (Bug#14553)

  • Use of the join cache in favor of an index for ORDER BY operations could cause incorrect result sorting. (Bug#17212)

  • libmysqld returned TEXT columns to the client as number of bytes, not number of characters (which can be different for multi-byte character sets). (Bug#19983)

B.1.3.聽Changes in release 4.1.21 (19 July 2006)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

This is a bugfix release for the MySQL 4.1 release family.

This section documents all changes and bug fixes that have been applied since the last official MySQL release. If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise.

Functionality added or changed:

  • For spatial data types, the server formerly returned these as VARSTRING values with a binary collation. Now the server returns spatial values as BLOB values. (Bug#10166)

  • Added the --set-charset option to mysqlbinlog to allow the character set to be specified for processing binary log files. (Bug#18351)

  • For a table with an AUTO_INCREMENT column, SHOW CREATE TABLE now shows the next AUTO_INCREMENT value to be generated. (Bug#19025)

  • The mysqldumpslow script has been moved from client RPM packages to server RPM packages. This corrects a problem where mysqldumpslow could not be used with a client-only RPM install, because it depends on my_print_defaults which is in the server RPM. (Bug#20216)

  • A new system variable, lc_time_names, specifies the locale that controls the language used to display day and month names and abbreviations. This variable affects the output from the DATE_FORMAT(), DAYNAME() and MONTHNAME() functions. See Section聽5.10.9, 鈥淢ySQL Server Locale Support鈥.

Bugs fixed:

  • Security fix: On Linux, and possibly other platforms using case-sensitive filesystems, it was possible for a user granted rights on a database to create or access a database whose name differed only from that of the first by the case of one or more letters. (CVE-2006-4226, Bug#17647)

  • Security fix: If a user has access to MyISAM table t, that user can create a MERGE table m that accesses t. However, if the user's privileges on t are subsequently revoked, the user can continue to access t by doing so through m. If this behavior is undesirable, you can start the server with the new --skip-merge option to disable the MERGE storage engine. (Bug#15195)

  • Security fix: Invalid arguments to DATE_FORMAT() caused a server crash. (CVE-2006-3469, Bug#20729) Thanks to Jean-David Maillefer for discovering and reporting this problem to the Debian project and to Christian Hammers from the Debian Team for notifying us of it.

  • Closing of temporary tables failed if binary logging was not enabled. (Bug#20919)

  • Repeated DROP TABLE statements in a stored procedure could sometimes cause the server to crash. (Bug#19399)

  • DATE_ADD() and DATE_SUB() returned NULL when the result date was on the day '9999-12-31'. (Bug#12356)

  • For a DATE parameter sent via a MYSQL_TIME data structure, mysql_stmt_execute() zeroed the hour, minute, and second members of the structure rather than treating them as read-only. (Bug#20152)

  • The DATA DIRECTORY table option did not work for TEMPORARY tables. (Bug#8706)

  • The mysql client did not ignore client-specific commands (such as use or help) that occurred as the first word on a line within multiple-line /* ... */ comments. (Bug#20432)

  • The mysql client did not understand help commands that had spaces at the end. (Bug#20328)

  • Failure to account for a NULL table pointer on big-endian machines could cause a server crash during type conversion. (Bug#21135)

  • Some memory leaks in the libmysqld embedded server were corrected. (Bug#16017)

  • When mysqldump disabled keys and locked a MyISAM table, the lock operation happened second. If another client performed a query on the table in the interim, it could take a long time due to indexes not being used. Now the lock operation happens first. (Bug#15977)

  • The length of the pattern string prefix for LIKE operations was calculated incorrectly for multi-byte character sets. As a result, the scanned range was wider than necessary if the prefix contained any multi-byte characters. (Bug#16674, Bug#18359)

  • For very complex SELECT statements could create temporary tables that were too big, but for which the temporary files did not get removed, causing subsequent queries to fail. (Bug#11824)

  • Using SELECT and a table join while running a concurrent INSERT operation would join incorrect rows. (Bug#14400)

  • Using SELECT on a corrupt MyISAM table using the dynamic record format could cause a server crash. (Bug#19835)

  • Checking a MyISAM table (using CHECK TABLE) having a spatial index and only one row would wrongly indicate that the table was corrupted. (Bug#17877)

  • For SELECT ... FOR UPDATE statements that used DISTINCT or GROUP BY over all key parts of a unique index (or primary key), the optimizer unnecessarily created a temporary table, thus losing the linkage to the underlying unique index values. This caused a Result set not updatable error. (The temporary table is unnecessary because under these circumstances the distinct or grouped columns must also be unique.) (Bug#16458)

  • Concatenating the results of multiple constant subselects produced incorrect results. (Bug#16716)

  • The use of MIN() and MAX() on columns with an index prefix produced incorrect results in some queries. (Bug#18206)

  • Use of MIN() or MAX() with GROUP BY on a ucs2 column could cause a server crash. (Bug#20076)

  • INSERT INTO ... SELECT ... LIMIT 1 could be slow because the LIMIT was ignored when selecting candidate rows. (Bug#9676)

  • NDB Cluster: A Cluster whose storage nodes were installed from the MySQL-ndb-storage-* RPMs could not perform CREATE or ALTER operations that made use of non-default character sets or collations. (Bug#14918)

  • NDB Cluster: The repeated creating and dropping of a table would eventually lead to NDB Error 826, Too many tables and attributes ... Insufficient space. (Bug#20847)

  • NDB Cluster: When attempting to restart the cluster following a data import, the cluster would fail during Phase 4 of the restart with Error 2334: Job buffer congestion. (Bug#20774)

  • NDB Cluster: A node failure during a scan could sometime cause the node to crash when restarting too quickly following the failure. (Bug#20197)

  • NDB Cluster: It was possible to use port numbers greater than 65535 for ServerPort in the config.ini file. (Bug#19164)

  • The omission of leading zeros in dates could lead to erroneous results when these were compared with the output of certain date and time functions. (Bug#16377)

  • Certain queries having a WHERE clause that included conditions on multi-part keys with more than 2 key parts could produce incorrect results and send [Note] Use_count: Wrong count for key at... messages to STDERR. (Bug#16168)

  • An invalid comparison between keys with index prefixes over multi-byte character fields could lead to incorrect result sets if the selected query execution plan used a range scan by an index prefix over a UTF8 character field. This also caused incorrect results under similar circumstances with many other character sets. (Bug#14896)

  • NDB Cluster: The cluster's data nodes would fail while trying to load data when NoOfFrangmentLogFiles was equal to 1. (Bug#19894)

  • NDB Cluster: A problem with error handling when ndb_use_exact_count was enabled could lead to incorrect values returned from queries using COUNT(). A warning is now returned in such cases. (Bug#19202)

  • NDB Cluster: LOAD DATA LOCAL failed to ignore duplicate keys in Cluster tables. (Bug#19496)

  • NDB Cluster: Repeated CREATE - INSERT - DROP operations tables could in some circumstances cause the MySQL table definition cache to become corrupt, so that some mysqld processes could access table information but others could not. (Bug#18595)

  • NDB Cluster: The mgm client command ALL CLUSTERLOG STATISTICS=15; had no effect. (Bug#20336)

  • NDB Cluster: TRUNCATE TABLE failed to reset the AUTO_INCREMENT counter. (Bug#18864)

  • NDB Cluster: The failure of a data node when preparing to commit a transaction (that is, while the node's status was CS_PREPARE_TO_COMMIT) could cause the failure of other cluster data nodes. (Bug#20185)

  • NDB Cluster: Renaming a table in such a way as to move it to a different database failed to move the table's indexes. (Bug#19967)

  • NDB Cluster: Resources for unique indexes on Cluster table columns were incorrectly allocated, so that only one-fourth as many unique indexes as indicated by the value of UniqueHashIndexes could be created. (Bug#19623)

  • NDB Cluster (NDBAPI): On big-endian platforms, NdbOperation::write_attr() did not update 32-bit fields correctly. (Bug#19537)

  • NDB Cluster: Some queries having a WHERE clause of the form c1=val1 OR c2 LIKE 'val2' were not evaluated correctly. (Bug # 17421)

  • NDB Cluster: Using 鈥stalemysqld .FRM files could cause a newly-restored cluster to fail. This situation could arise when restarting a MySQL Cluster using the --intial option while leaving connected mysqld processes running. (Bug#16875)

  • NDB Cluster: Repeated use of the SHOW and ALL STATUS commands in the ndb_mgm client could cause the mgmd process to crash. (Bug#18591)

  • NDB Cluster: An issue with ndb_mgmd prevented more than 27 mysqld processes from connecting to a single cluster at one time. (Bug#17150)

  • NDB Cluster: Data node failures could cause excessive CPU usage by ndb_mgmd. (Bug#13987)

  • NDB Cluster: TRUNCATE failed on tables having BLOB or TEXT columns with the error Lock wait timeout exceeded. (Bug#19201)

  • A cast problem caused incorrect results for prepared statements that returned float values when MySQL was compiled with gcc 4.0. (Bug#19694)

  • Improper character set initialization in the embedded server could result in a server crash. (Bug#20318)

  • Some queries that used ORDER BY and LIMIT performed quickly in MySQL 3.23, but slowly in MySQL 4.x/5.x due to an optimizer problem. (Bug#4981)

  • Queries using an indexed column as the argument for the MIN() and MAX() functions following an ALTER TABLE .. DISABLE KEYS statement returned Got error 124 from storage engine until ALTER TABLE ... ENABLE KEYS was run on the table. (Bug#20357)

  • A number of dependency issues in the RPM bench and test packages caused installation of these packages to fail. (Bug#20078)

  • The MD5() and SHA() functions treat their arguments as case-sensitive strings. But when they are compared, their arguments were compared as case-insensitive strings, which leads to two function calls with different arguments (and thus different results) compared as being identical. This can lead to a wrong decision made in the range optimizer and thus to an incorrect result set. (Bug#15351)

  • InnoDB unlocked its data directory before committing a transaction, potentially resulting in non-recoverable tables if a server crash occurred before the commit. (Bug#19727)

  • Multiple-table DELETE statements containing a subquery that selected from one of the tables being modified caused a server crash. (Bug#19225)

  • The ARCHIVE storage engine does not support TRUNCATE TABLE, but the server was not returning an appropriate error when truncation of an ARCHIVE table was attempted. (Bug#15558)

  • An update that used a join of a table to itself and modified the table on both sides of the join reported the table as crashed. (Bug#18036)

  • The fill_help_tables.sql file did not load properly if the ANSI_QUOTES SQL mode was enabled. (Bug#20542)

  • The fill_help_tables.sql file did not contain a SET NAMES 'utf8' statement to indicate its encoding. This caused problems for some settings of the MySQL character set such as big5. (Bug#20551)

  • The MySQL server startup script /etc/init.d/mysql (created from mysql.server) is now marked to ensure that the system services ypbind, nscd, ldap, and NTP are started first (if these are configured on the machine). (Bug#18810)

  • For a reference to a non-existent index in FORCE INDEX, the error message referred to a column, not an index. (Bug#17873)

  • In a multiple-row INSERT statement, LAST_INSERT_ID() should return the same value for each row. However, in some cases, the value could change if the table being inserted into had its own AUTO_INCREMENT column. (Bug#6880)

  • Invalid escape sequences in option files caused MySQL programs that read them to abort. (Bug#15328)

  • Binary log lacked character set information for table name when dropping temporary tables. (Bug#14157)

  • InnoDB did not increment the handler_read_prev counter. (Bug#19542)

  • Slave SQL thread cleanup was not handled properly on Mac OS X when a statement was killed, resulting in a slave crash. (Bug#16900)

  • mysqldump did not respect the order of tables named with the --tables option. (Bug#18536)

  • The server no longer uses a signal handler for signal 0 because it could cause a crash on some platforms. (Bug#15869)

  • LOAD_FILE() returned an error if the file did not exist, rather than NULL as it should according to the manual. (Bug#10418)

  • Use of uninitialized user variables in a subquery in the FROM clause results in bad entries in the binary log. (Bug#19136)

  • IS_USED_LOCK() could return an incorrect connection identifier. (Bug#16501)

  • Concurrent reading and writing of privilege structures could crash the server. (Bug#16372)

  • A statement containing GROUP BY and HAVING clauses could return incorrect results when the HAVING clause contained logic that returned FALSE for every row. (Bug#14927)

  • MONTHNAME(STR_TO_DATE(NULL, '%m')) could cause a server crash. (Bug#18501)

  • The ref optimizer could choose the ref_or_null access method in cases where it was not applicable. This could cause inconsistent EXPLAIN or SELECT results for a given statement. (Bug#16798)

  • ANALYZE TABLE for TEMPORARY tables had no effect. (Bug#15225)

  • When myisamchk needed to rebuild a table, AUTO_INCREMENT information was lost. (Bug#10405)

  • No error message was being issued for storage engines that do not support ALTER TABLE. Now an ER_NOT_SUPPORTED_YET error occurs. (Bug#7643)

  • The binary log would create an incorrect DROP query when creating temporary tables during replication. (Bug#17263)

  • SHOW CREATE TABLE did not display the AUTO_INCREMENT column attribute if the SQL mode was MYSQL323 or MYSQL40. This also affected mysqldump, which uses SHOW CREATE TABLE to get table definitions. (Bug#14515)

B.1.4.聽Changes in release 4.1.20 (24 May 2006)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

This is a security fix release for the MySQL 4.1 release family.

This section documents all changes and bug fixes that have been applied since the last official MySQL release. If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise.

Bugs fixed:

  • Security fix: An SQL-injection security hole has been found in multi-byte encoding processing. The bug was in the server, incorrectly parsing the string escaped with the mysql_real_escape_string() C API function. (CVE-2006-2753, Bug#8378)

    This vulnerability was discovered and reported by Josh Berkus and Tom Lane as part of the inter-project security collaboration of the OSDB consortium. For more information about SQL injection, please see the following text.

    Discussion: An SQL-injection security hole has been found in multi-byte encoding processing. An SQL-injection security hole can include a situation whereby when a user supplied data to be inserted into a database, the user might inject SQL statements into the data that the server will execute. With regards to this vulnerability, when character set unaware-escaping is used (for example, addslashes() in PHP), it is possible to bypass the escaping in some multi-byte character sets (for example, SJIS, BIG5 and GBK). As a result, a function such as addslashes() is not able to prevent SQL-injection attacks. It is impossible to fix this on the server side. The best solution is for applications to use character set-aware escaping offered by a function such mysql_real_escape_string().

    However, a bug was detected in how the MySQL server parses the output of mysql_real_escape_string(). As a result, even when the character set-aware function mysql_real_escape_string() was used, SQL injection was possible. This bug has been fixed.

    Workarounds: If you are unable to upgrade MySQL to a version that includes the fix for the bug in mysql_real_escape_string() parsing, but run MySQL 5.0.1 or higher, you can use the NO_BACKSLASH_ESCAPES SQL mode as a workaround. (This mode was introduced in MySQL 5.0.1.) NO_BACKSLASH_ESCAPES enables an SQL standard compatibility mode, where backslash is not considered a special character. The result will be that queries will fail.

    To set this mode for the current connection, enter the following SQL statement:

    SET sql_mode='NO_BACKSLASH_ESCAPES';
    

    You can also set the mode globally for all clients:

    SET GLOBAL sql_mode='NO_BACKSLASH_ESCAPES';
    

    This SQL mode also can be enabled automatically when the server starts by using the command-line option --sql-mode=NO_BACKSLASH_ESCAPES or by setting sql-mode=NO_BACKSLASH_ESCAPES in the server option file (for example, my.cnf or my.ini, depending on your system).

  • The patch for Bug#8303 broke the fix for Bug#8378 and was undone. (In string literals with an escape character (\) followed by a multi-byte character that has a second byte of (\), the literal was not interpreted correctly. The next byte now is escaped, not the entire multi-byte character. This means it a strict reverse of the mysql_real_escape_string() function.)

  • The dropping of a temporary table whose name contained a backtick ('`') character was not correctly written to the binary log, which also caused it not to be replicated correctly. (Bug#19188)

  • The client libraries had not been compiled for position-independent code on Solaris-SPARC and AMD x86_64 platforms. (Bug#13159, Bug#14202, Bug#18091)

  • Running myisampack followed by myisamchk with the --unpack option would corrupt the auto_increment key. (Bug#12633)

  • RPM packages had spurious dependencies on Perl modules and other programs. (Bug#13634)

B.1.5.聽Changes in release 4.1.19 (29 April 2006)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

This release includes the patches for recently reported security vulnerabilites in the MySQL client-server protocol. We would like to thank Stefano Di Paola for finding and reporting these to us.

Functionality added or changed:

  • Security enhancement: Added the global max_prepared_stmt_count system variable to limit the total number of prepared statements in the server. This limits the potential for denial-of-service attacks based on running the server out of memory by preparing huge numbers of statements. The current number of prepared statements is available through the prepared_stmt_count system variable. (Bug#16365)

  • The MySQL-shared-compat-4.1.X-.i386.rpm shared compatibility RPMs no longer contain libraries for MySQL 5.0 and up. It contains libraries for 3.23, 4.0, and 4.1.1. (Bug#19288)

  • Creating a table in an InnoDB database with a column name that matched the name of an internal InnoDB column (including DB_ROW_ID, DB_TRX_ID, DB_ROLL_PTR and DB_MIX_ID) would cause a crash. MySQL now returns error 1005 (cannot create table) with errno set to -1. (Bug#18934)

  • InnoDB now caches a list of unflushed files instead of scanning for unflushed files during a table flush operation. This improves performance when --innodb-file-per-table is set on a system with a large number of InnoDB tables. (Bug#15653)

  • New charset command added to mysql command-line client. By typing charset name or \C name (such as \C UTF8), the client character set can be changed without reconnecting. (Bug#16217)

  • Large file support was re-enabled for the MySQL server binary for the AIX 5.2 platform. (Bug#13571)

  • When using the GROUP_CONCAT() function where the group_concat_max_len system variable was greater than 512, the type of the result was BLOB only if the query included an ORDER BY clause; otherwise the result was a VARCHAR.

    The result type of the GROUP_CONCAT() function is now VARCHAR only if the value of the group_concat_max_len system variable is less than or equal to 512. Otherwise, this function returns a BLOB. (Bug#14169)

Bugs fixed:

  • Security fix: A malicious client, using specially crafted invalid login or COM_TABLE_DUMP packets was able to read uninitialized memory, which potentially, though unlikely in MySQL, could have led to an information disclosure. (CVE-2006-1516, CVE-2006-1517) Thanks to Stefano Di Paola for finding and reporting this bug.

  • NDB Cluster: A simultaneous DROP TABLE and table update operation utilising a table scan could trigger a node failure. (Bug#18597)

  • MySQL-shared-compat-4.1.15-0.i386.rpm, MySQL-shared-compat-4.1.16-0.i386.rpm, and MySQL-shared-compat-4.1.18-0.i386.rpm incorrectly depended on glibc 2.3 and could not be installed on a glibc 2.2 system. (Bug#16539)

  • IA-64 RPM packages for Red Hat and SuSE Linux that were built with the icc compiler incorrectly depended on icc runtime libraries. (Bug#16662)

  • Index prefixes for utf8 VARCHAR columns did not work for UPDATE statements. (Bug#19080)

  • MySQL would not compile on Linux distributions that use the tinfo library. (Bug#18912)

  • NDB Cluster: Backups could fail for large clusters with many tables, where the number of tables approached MaxNoOfTables. (Bug#17607)

  • For single-SELECT union constructs of the form (SELECT ... ORDER BY order_list1 [LIMIT n]) ORDER BY order_list2, the ORDER BY lists were concatenated and the LIMIT clause was ignored. (Bug#18767)

  • The IN-to-EXISTS transformation was making a reference to a parse tree fragment that was left out of the parse tree. This caused problems with prepared statements. (Bug#18492)

  • Attempting to set the default value of an ENUM or SET column to NULL caused a server crash. (Bug#19145)

  • Index corruption could occur in cases when key_cache_block_size was not a multiple of myisam_block_size (for example, with key_cache_block_size=1536 and myisam_block_size=1024). (Bug#19079)

  • UNCOMPRESS(NULL) could cause subsequent UNCOMPRESS() calls to return NULL for legal non-NULL arguments. (Bug#18643)

  • Conversion of a number to a CHAR UNICODE string returned an invalid result. (Bug#18691)

  • A call to MIN() with a CASE expression as its argument could return a non-minimum value. (Bug#17896)

  • A LOCK TABLES statement that failed could cause MyISAM not to update table statistics properly, causing a subsequent CHECK TABLE to report table corruption. (Bug#18544)

  • Avoid trying to include <asm/atomic.h> when it doesn't work in C++ code. (Bug#13621)

  • Executing SELECT on a large table that had been compressed within myisampack could cause a crash. (Bug#17917)

  • NDB Cluster: In a 2-node cluster with a node failure, restarting the node with a low value for StartPartialTimeout could cause the cluster to come up partitioned (鈥split-brain鈥 issue). (Bug#16447)

    A similar issue could occur when the cluster was first started with a sufficiently low value for this parameter. (Bug#18612)

  • NDB Cluster: On systems with multiple network interfaces, data nodes would get 鈥stuck鈥 in startup phase 2 if the interface connecting them to the management server was working on node startup while the interface interconnecting the data nodes experienced a temporary outage. (Bug#15695)

  • mysql_config returned incorrect libraries on x86_64 systems. (Bug#13158)

  • mysql_reconnect() sent a SET NAMES statement to the server, even for pre-4.1 servers that do not understand the statement. (Bug#18830)

  • During conversion from one character set to ucs2, multi-byte characters with no ucs2 equivalent were converted to multiple characters, rather than to 0x003F QUESTION MARK. (Bug#15375)

  • The mysql_close() C API function leaked handles for share-memory connections on Windows. (Bug#15846)

  • The euro sign () was not stored correctly in columns using the latin1_german1_ci or latin1_general_ci collation. (Bug#18321)

  • The server was always built as though --with-extra-charsets=complex had been specified. (Bug#12076)

  • SELECT ... WHERE column LIKE 'A%', when column had a key and used the latin2_czech_cs collation, caused the wrong number of rows to be returned. (Bug#17374)

  • A query using WHERE (column_1, column_2) IN ((value_1, value_2)[, (..., ...), ...]) would return incorrect results. (Bug#16248)

  • The -lmtmalloc library was removed from the output of mysql_config on Solaris, as it caused problems when building DBD::mysql (and possibly other applications) on that platform that tried to use dlopen() to access the client library. (Bug#18322)

  • When running a query that contained a GROUP_CONCAT( SELECT GROUP_CONCAT(...) ), the result was NULL except in the ROLLUP part of the result, if there was one. (Bug#15560)

  • CAST(double AS SIGNED INT) for large double values outside the signed integer range truncates the result to be within range, but the result sometimes had the wrong sign. (Bug#15098)

  • SET value definitions containing commas were not rejected. Now a definition such as SET('a,b','c,d') results in an error. (Bug#15316)

  • MyISAM: Keys for which the first part of the key was a CHAR or VARCHAR column using the UTF-8 character set and longer than 254 bytes could become corrupted. (Bug#17705)

  • NDB Cluster: A timeout in the handling of an ABORT condition with more that 32 operations could yield a node failure. (Bug#18414)

  • NDB Cluster: A node restart immediately following a CREATE TABLE would fail. Important: This fix supports 2-node Clusters only. (Bug#18385)

  • NDB Cluster: In event of a node failure during a rollback, a 鈥false鈥 lock could be established on the backup for that node, which lock could not be removed without restarting the node. (Bug#18352)

  • NDB Cluster: The cluster created a crashed replica of a table having an ordered index 鈥 or when logging was not enabled, of a table having a table or unique index 鈥 leading to a crash of the cluster following 8 successibe restarts. (Bug#18298)

  • NDB Cluster: When replacing a failed master node, the replacement node could cause the cluster to crash from a buffer overflow if it had an excessively large amount of data to write to the cluster log. (Bug#18118)

  • NDB Cluster: Restarting nodes were allowed to start and join the cluster too early. (Bug#16772)

  • If InnoDB encountered a HA_ERR_LOCK_TABLE_FULL error and rolled back a transaction, the transaction was still written to the binary log. (Bug#18283)

  • Connecting to a server with a UCS2 default character set with a client using a non-UCS2 character set crashed the server. (Bug#18004)

  • Character set conversion of string constants for UNION of constant and table column was not done when it was safe to do so. (Bug#15949)

  • Use of TRUNCATE TABLE for a TEMPORARY table on a master server was propagated to slaves properly, but slaves did not decrement the Slave_open_temp_tables counter properly. (Bug#17137)

  • SELECT COUNT(*) for a MyISAM table could return different results depending on whether an index was used. (Bug#14980)

  • Large file support did not work in AIX server binaries. (Bug#10776)

  • Security Improvement: GRANTs to users with wildcards in their host information could be erroneously applied to similar users with the same username and similar wildcards. For example, a privilege granted to foo@% are also applied to user foo@192.%. (Bug#14385)

  • NDB Cluster: Inserting and deleting BLOB column values while a backup was in process could cause the loss of an ndbd node. (Bug#14028)

  • Setting the myisam_repair_threads system variable to a value larger than 1 could cause corruption of large MyISAM tables. (Bug#11527)

  • Security improvement: In grant table comparisons, improper use of a latin1 collation caused some hostname matches to be true that should have been false. Thanks to Deomid Ryabkov for finding this bug and proposing a solution. (Bug#15756)

  • NDB Cluster: ndb_delete_all would run out of memory on tables containing BLOB columns. (Bug#16693)

  • mysqldump tried to dump data from a view. (In MySQL 4.1, this applies when connecting to a server from MySQL 5.0 or higher.) (Bug#16389)

  • NDB Cluster: An UPDATE with an inner join failed to match any records if both tables in the join did not have a primary key. (Bug#17257)

  • NDB Cluster: A DELETE with a join in the WHERE clause failed to retrieve any records if both tables in the join did not have a primary key. (Bug#17249)

  • NDB Cluster: In some cases, LOAD DATA INFILE did not load all data into NDB tables. (Bug#17081)

  • NDB Cluster: The REDO log would become corrupted (and thus unreadable) in some circumstances, due to a failure in the query handler. (Bug#17295)

  • NDB Cluster: No error message was generated for setting NoOfFragmentLogFiles too low. (Bug#13966)

  • NDB Cluster: No error message was generated for setting MaxNoOfAttributes too low. (Bug#13965)

  • Binary distributions for Solaris contained files with group ownership set to the non-existing wheel group. Now the bin group is used. (Bug#15562)

  • Killing a long-running query containing a subquery could cause a server crash. (Bug#14851)

  • Repeated invocation of my_init() and my_end() caused corruption of character set data and connection failure. (Bug#6536)

  • A FULLTEXT query in a prepared statement could result in unexpected behavior. (Bug#14496)

  • A FULLTEXT query in a UNION could result in unexpected behavior. (Bug#16893)

  • Server crash when dropping InnoDB constraints named TABLENAME_ibfk_0. (Bug#16387)

  • Corrected race condition when dropping the adaptive hash index for a B-tree page in InnoDB. (Bug#16582)

  • LOAD DATA FROM MASTER produced invalid warnings and Packet out of order errors when the database already existed on the slave. (Bug#15302)

  • A key on a MEMORY table would sometimes fail to match a row. (Bug#12796)

  • MYSQL_STMT objects were not preserved following a connection reset. Attempting to operate on them afterwards caused the server to crash. (Bug#12744)

B.1.6.聽Changes in release 4.1.18 (27 January 2006)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • NDB Cluster: More descriptive warnings are now issued when inappropriate logging parameters are set in config.ini. (Formerly, the warning issued was simply Could not add logfile destination .) (Bug#11331)

  • libmysqlclient now uses versioned symbols with GNU ld. (Bug#3074)

Bugs fixed:

  • The length of a VARCHAR() column that used the utf8 character set would increase each time the table was re-created in a stored procedure or prepared statement, eventually causing the CREATE TABLE statement to fail. (Bug#13134)

  • RPM packages had an incorrect zlib dependency. (Bug#15223)

  • STR_TO_DATE(1,NULL) caused a server crash. (CVE-2006-3081, Bug#15828)

  • The --replicate-do and --replicate-ignore options were not being enforced on multiple-table statements. (Bug#15699, Bug#16487)

  • Running out of diskspace in the location specified by the tmpdir option resulted in incorrect error message. (Bug#14634)

  • Test suite func_math test returned warnings when server not compiled with InnoDB support. (Bug#15429)

  • The MBROverlaps GIS function returned incorrect results. (Bug#14320)

  • A CREATE TABLE ... SELECT ... on an equation involving DOUBLE values could result in the table being created with columns too small to hold the equation result. (Bug#9855)

  • UPDATE statement crashed multi-byte character set FULLTEXT index if update value was almost identical to initial value only differing in some spaces being changed to &nbsp;. (Bug#16489)

  • Single table UPDATE statements without ORDER BY clauses which updated the same indexed column that was being filtered on were optimized with a full index scan instead of a more appropriate index range scan. (Bug#15935)

  • A prepared statement created from a SELECT ... LIKE query (such as PREPARE stmt1 FROM 'SELECT col_1 FROM tedd_test WHERE col_1 LIKE ?';) would begin to produce erratic results after being executed repeatedly numerous (thousands) of times. (Bug#12734)

B.1.7.聽Changes in release 4.1.17 (Not released)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • In the latin5_turkish_ci collation, the order of the characters A WITH CIRCUMFLEX, I WITH CIRCUMLEX, and U WITH CIRCUMFLEX was changed. If you have used these characters in any indexed columns, you should rebuild those indexes. (Bug#13421)

  • Support files for compiling with Visual Studio 6 have been removed. (Bug#15094)

  • Internal sha1_result function renamed to mysql_sha1_result to prevent conflicts with other projects. (Bug#13944)

Bugs fixed:

  • CAST(... AS TIME) operations returned different results when using versus not using prepared-statement protocol. (Bug#15805)

  • Performing a RENAME TABLE on an InnoDB table when the server is started with the --innodb-file-per-table option and the data directory is a symlink caused a server crash. (Bug#15991)

  • Characters in the gb2312 and euckr character sets which did not have Unicode mappings were truncated. (Bug#15377)

  • Piping the fill_help_tables.sql file into mysqld resulted in a syntax error. (Bug#15965)

  • NDBCluster: Upon the completion of a scan where a key request remained outstanding on the primary replica and a starting node died, the scan did not terminate. This caused incompleted error handling of the failed node. (Bug#15908)

  • Using CAST() to convert values with long fractional and/or exponent parts to TIME returned wrong results. (Bug#12440)

  • An INSERT ... SELECT statement between tables in a MERGE set can return errors when statement involves insert into child table from merge table or vice-versa. (Bug#5390)

  • Certain permission management statements could create a NULL hostname for a user, resulting in a server crash. (Bug#15598)

  • For InnoDB tables, using a column prefix for a utf8 column in a primary key caused Cannot find record errors when attempting to locate records. (Bug#14056)

  • Certain CREATE TABLE ... AS ... statements involving ENUM columns could cause server crash. (Bug#12913)

  • Using an aggregate function as the argument for a HAVING clause would result in the aggregate function always returning FALSE. (Bug#14274)

  • The COALESCE() function truncated data in a TINYTEXT column. (Bug#15581)

  • InnoDB: Comparison of indexed VARCHAR CHARACTER SET ucs2 COLLATE ucs2_bin columns using LIKE could fail. (Bug#14583)

  • Issuing a DROP USER command could cause some users to encounter a hostname is not allowed to connect to this MySQL server error. (Bug#15775)

  • Access Denied error could be erroneously returned with specific grant combinations under high load. (Bug#7209)

  • Symbolic links did not function properly on Windows platforms. (Bug#14960, Bug#14310)

  • BDB: A DELETE, INSERT, or UPDATE of a BDB table could cause the server to crash where the query contained a subquery using an index read. (Bug#15536)

  • DELETE could report full-text index corruption (Invalid key for table ...) if the index was built with repair-by-sort, the data in the full-text index used UCA collation, and some word appeared in the data terminated by a 0xC2A0 character as well as by other non-letter characters. (Bug#11336)

  • A race condition when creating temporary files caused a deadlock on Windows with threads in Opening tables or Waiting for table states. (Bug#12071)

  • InnoDB: If FOREIGN_KEY_CHECKS was 0, InnoDB allowed inconsistent foreign keys to be created. (Bug#13778)

  • NDB Cluster: A memory leak occurred when performing ordered index scans using indexes a columns larger than 32 bytes, which would eventually lead to the forced shutdown of all mysqld server processes used with the cluster. (Bug#13078)

  • NDB Cluster: Under some circumstances, it was possible for a restarting node to undergo a forced shutdown. (Bug#15632)

  • NDB Cluster: If an abort by the Transaction Coordinator timed out, the abort condition was incorrectly handled, causing the transacviton record to be released prematurely. (Bug#15685)

  • NDB Cluster: A node which failed during cluster startup was sometimes not removed from the internal list of active nodes. (Bug#15587)

  • NDB Cluster: There was a small window for a node failure to occur during a backup without an error being reported. (Bug#15425)

  • Multiple-table update operations were counting updates and not updated rows. As a result, if a row had several updates it was counted several times for the 鈥rows matched鈥 value but updated only once. (Bug#15028)

  • SELECT queries that began with an opening parenthesis were not being placed in the query cache. (Bug#14652)

B.1.8.聽Changes in release 4.1.16 (29 November 2005)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • The CHAR() function now takes an optional USING charset clause that may be used to produce a result in a specific character set rather than in the connection character set.

  • MySQL 4.1 now supports character set conversion for seven additional cp950 characters into the big5 character set: 0xF9D6, 0xF9D7, 0xF9D8, 0xF9D9, 0xF9DA, 0xF9DB, and 0xF9DC. Note: If you move data containing these additional characters to an older MySQL installation which does not support them, you may encounter errors. (Bug#12476)

  • NDBCluster: The perror utility included with the MySQL-Server RPM now provides support for the --ndb option, and so can be used to obtain error message text for MySQL Cluster error codes. (Bug#13740)

  • When executing single-table UPDATE or DELETE queries containing an ORDER BY ... LIMIT N clause, but not having any WHERE clause, MySQL can now take advantage of an index to read the first N rows in the ordering specified in the query. If an index is used, only the first N records will be read, as opposed to scanning the entire table. (Bug#12915)

  • The MySQL-server RPM now explicitly assigns the mysql system user to the mysql user group during the postinstallation process. This corrects an issue with upgrading the server on some Linux distributions whereby a previously existing mysql user was not changed to the mysql group, resulting in wrong groups for files created following the installation. (Bug#12823)

  • When a date column is set NOT NULL and contains 0000-00-00, it will be updated for UPDATE statements that contains columnname IS NULL in the WHERE clause. (Bug#14186)

Bugs fixed:

  • NDB Cluster: REPLACE failed when attempting to update a primary key value in a Cluster table. (Bug#14007)

  • When the DATE_FORMAT() function appeared in both the SELECT and ORDER BY clauses of a query but with arguments that differ by case (i.e. %m and %M), incorrect sorting may have occurred. (Bug#14016)

  • Make failed when attempting to build MySQL in different directory than source. (Bug#11827)

  • PROCEDURE ANALYSE() could suggest a data type with a negative display width. (Bug#10716)

  • InnoDB: During replication, There was a failure to record events in the binary log that still occurred even in the event of a ROLLBACK. For example, this sequence of commands:

    BEGIN;
    CREATE TEMPORARY TABLE t1 (a INT) ENGINE=INNODB;
    ROLLBACK;
    INSERT INTO t1 VALUES (1);
    

    would succeed on the replication master as expected. However, the INSERT would fail on the slave because the ROLLBACK would (erroneously) cause the CREATE TEMPORARY TABLE statement not to be written to the binlog. (Bug#7947)

  • NDB Cluster: Creating a table with packed keys failed silently. NDB now supports the PACK_KEYS option to CREATE TABLE correctly. (Bug#14514)

  • Non-latin1 object names were written with wrong character set to grant tables. (Bug#14406)

  • Issuing STOP SLAVE after having acquired a global read lock with FLUSH TABLES WITH READ LOCK caused a deadlock. Now STOP SLAVE is generates an error in such circumstances. (Bug#10942)

  • Portability fixes to support OpenSSL 0.9.8a. (Bug#14221)

  • Closed a memory leak in the SSL code. (Bug#14780)

  • Perform character set conversion of constant values whenever possible without data loss. (Bug#10446)

  • A UNION of DECIMAL columns could produce incorrect results. (Bug#14216)

  • InnoDB: Pad UTF-8 VARCHAR columns with 0x20. Pad UCS2 CHAR columns with 0x0020. (Bug#10511)

  • Full-text indexing/searching failed for words that end with more than one apostrophe. (Bug#5686)

  • Selecting from a table in both an outer query and a subquery could cause a server crash. (Bug#14482)

  • Creating a table containing an ENUM or SET column from within a stored procedure or prepared statement caused a server crash later when executing the procedure or statement. (Bug#14410)

  • mysql_fix_privilege_tables.sql contained an erroneous comment that resulted in an error when the file contents were processed. (Bug#14469)

  • On Windows, the server could crash during shutdown if both replication threads and normal client connection threads were active. (Re-fix of Bug#11796)

  • A LIMIT-related optimization failed to take into account that MyISAM table indexes can be disabled, causing Error 124 when it tried to use such an index. (Bug#14616)

  • For a table that had been opened with HANDLER OPEN, issuing OPTIMIZE TABLE, ALTER TABLE, or REPAIR TABLE caused a server crash. (Bug#14397)

  • CREATE TABLE tbl_name (...) SELECT ... could crash the server and write invalid data into the .frm file if the CREATE TABLE and SELECT both contained a column with the same name. Also, if a default value is specified in the column definition, it is now actually used. (Bug#14480)

  • For MyISAM tables, incorrect query results or incorrect updates could occur under these conditions: There is a multiple-column index that includes a BLOB column that is not the last column in the index, and the statement performs a lookup on the index using key column values that have NULL for the BLOB column and that provide values for all columns up to the BLOB column and at least the next column in the index. (Bug#13814)

  • Deletes from a CSV table could cause table corruption. (Bug#14672)

  • An update of a CSV table could cause a server crash. (Bug#13894)

  • mysqld_safe did not correctly start the -max version of the server (if it was present) if the --ledir option was given. (Bug#13774)

  • The endian byte in for spatial values in WKB format was not consistently respected. (Bug#12839)

  • An expression in an ORDER BY clause failed with Unknown column 'col_name' in 'order clause' if the expression referred to a column alias. (Bug#11694)

  • Statements of the form CREATE TABLE ... SELECT ... that created a column with a multi-byte character set could incorrectly calculate the maximum length of the column, resulting in a Specified key was too long error. (Bug#14139)

  • Use of col_name = VALUES(col_name) in the ON DUPLICATE KEY UPDATE clause of an INSERT statement failed with an Column 'col_name' in field list is ambiguous error. (Bug#13392)

  • On Windows, the server was not ignoring hidden or system directories that Windows may have created in the data directory, and would treat them as available databases. (Bug#4375)

  • LIKE operations did not work reliably for the cp1250 character set. (Bug#13347)

  • Maximum values were handled incorrectly for command-line options of type GET_LL. (Bug#12925)

  • Use of WITH ROLLUP PROCEDURE ANALYSE() could hang the server. (Bug#14138)

  • TIMEDIFF(), ADDTIME(), and STR_TO_DATE() were not reporting that they could return NULL, so functions that invoked them might misinterpret their results. (Bug#14009)

  • The example configuration files supplied with MySQL distributions listed the thread_cache_size variable as thread_cache. (Bug#13811)

  • LOAD DATA INFILE would not accept the same character for both the ESCAPED BY and the ENCLOSED BY clauses. (Bug#11203)

  • NDB Cluster: Repeated transactions using unique index lookups could cause a memory leak leading to error 288, Out of index operations in transaction coordinator. (Bug#14199)

  • SELECT DISTINCT CHAR(col_name) returned incorrect results after SET NAMES utf8. (Bug#13233)

  • Character set conversion was not being done for FIND_IN_SET(). (Bug#13751)

  • The default value of query_prealloc_size was set to 8192, lower than its minimum of 16384. The minimum has been lowered to 8192. (Bug#13334)

  • The server did not take character set into account in checking the width of the mysql.user.Password column. As a result, it could incorrectly generate long password hashes even if the column was not long enough to hold them. (Bug#13064)

  • CAST(1E+300 TO SIGNED INT) produced an incorrect result on little-endian machines. (Bug#13344)

  • mysqladmin and mysqldump would hang on SCO OpenServer. (Bug#13238)

  • Specifying --default-character-set=cp-932 for mysqld would cause SQL scripts containing comments written using that character set to fail with a syntax error. (Bug#13487)

  • Given a column col_name defined as NOT NULL, a SELECT ... FROM ... WHERE col_name IS NULL query following SHOW TABLE STATUS would erroneously return a non-empty result. (Bug#13535)

  • Corrected a memory-copying problem for big5 values when using icc compiler on Linux IA-64 systems. (Bug#10836)

  • On BSD systems, the system crypt() call could return an error for some salt values. The error was not handled, resulting in a server crash. (Bug#13619)

  • Character set file parsing during mysql_real_connect() read past the end of a memory buffer. (Bug#6413)

  • The --interactive-timeout and --slave-net-timeout options for mysqld were not being obeyed on Mac OS X and other BSD-based platforms. (Bug#8731)

  • Queries of the form (SELECT ...) ORDER BY ... were being treated as a UNION. This improperly resulted in only distinct values being returned (because UNION by default eliminates duplicate results). Also, references to column aliases in ORDER BY clauses following parenthesized SELECT statements were not resolved properly. (Bug#7672)

  • Multiple update queries using any type of subquery would be ignored by a replication slave when a condition such as --replicate-ignore-table like condition was used. (Bug#13236)

  • An UPDATE query using a join would be executed incorrectly on a replication slave. (Bug#12618)

  • NDBCluster: Placing multiple [TCP DEFAULT] sections in the cluster config.ini file crashed ndb_mgmd. (The process now exits gracefully with an appropriate error message.) (Bug#13611)

  • Multiple race conditions existed in OpenSSL, particularly noticeable on Solaris. (Bug#9270)

  • With --log-slave-updates Exec_master_log_pos of SQL thread lagged IO (Bug#13023)

  • PURGE MASTER LOGS statement that used subquery for date crashed server. (Bug#10308)

B.1.9.聽Changes in release 4.1.15 (13 October 2005)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • The limit of 255 characters on the input buffer for mysql on Windows has been lifted. The exact limit depends on what the system allows, but can be up to 64K characters. A typical limit is 16K characters. (Bug#12929)

  • Added the myisam_stats_method, which controls whether NULL values in indexes are considered the same or different when collecting statistics for MyISAM tables. This influences the query optimizer as described in Section聽7.4.7, 鈥MyISAM Index Statistics Collection鈥. (Bug#12232)

  • Better detection of connection timeout for replication servers on Windows allows elimination of extraneous Lost connection errors in the error log. (Bug#5588)

  • When using IF NOT EXISTS with CREATE DATABASE or CREATE TABLE, a warning now is generated if the database or table already exists. (Bug#6008):

  • A new command line argument was added to mysqld to ignore client character set information sent during handshake, and use server side settings instead, to reproduce 4.0 behavior (Bug#9948):

    mysqld --skip-character-set-client-handshake

  • RAND() no longer allows non-constant initializers. (Prior to MySQL 4.1.15, the effect of non-constant initializers is undefined.) (Bug#6172)

Bugs fixed:

  • A prepared statement failed with Illegal mix of collations if the client character set was utf8 and the statement used a table that had a character set of latin1. (Bug#12371)

  • If special characters such as '_' , '%', or the escape character were included within the prefix of a column index, LIKE pattern matching on the indexed column did not return the correct result. (Bug#13046, Bug#13919)

  • NDBCluster: Updating a text-type column during a cluster backup could cause the ndbd process to crash, due to the incorrect use of charset-normalized reads for. This could also lead to 鈥wrong鈥 data in the backup if such a column was updated during the backup; for example, supposing that the column used latin_ci, then 鈥aAa鈥 might be stored in the backup as 鈥AAA鈥. (Bug#12950)

  • NDBCluster: When performing a delete of a great many (tens of thousands of) rows at once from a Cluster table, an improperly dereferenced pointer could cause the mysqld process to crash. (Bug#9282)

  • Server could over-allocate memory when performing a FULLTEXT search for stopwords only. (Bug#13582)

  • UNION of two DECIMAL columns returned wrong field type. (Bug#13372)

  • CHECKSUM TABLE locked InnoDB tables and did not use a consistent read. (Bug#12669)

  • SHOW CREATE TABLE did not display any FOREIGN KEY clauses if a temporary file could not be created. Now SHOW CREATE TABLE displays an error message in an SQL comment if this occurs. (Bug#13002)

  • Display of the AUTO_INCREMENT attribute by SHOW CREATE TABLE was not controlled by the NO_FIELD_OPTIONS SQL mode as it should have been. (Bug#7977)

  • For VARCHAR columns with the ucs2 character set, InnoDB trimmed trailing 0x20 bytes rather than 0x0020 words, resulting in incorrect index lookups later. (Bug#12178)

  • MySQL programs in binary distributions for Solaris 8/9/10 x86 systems would not run on Pentium III machines. (Bug#6772)

  • NDB Cluster: Multiple ndb_mgmd processes in a cluster would not know each other's IP addresses. (Bug#12037)

  • NDB Cluster: With two mgmd processes in a cluster, ndb_mgm output for SHOW would display the same IP address for both processes, even when they were on different hosts. (Bug#11595)

  • The --replicate-rewrite-db and --replicate-do-table options did not work for statements in which tables were aliased to names other than those listed by the options. (Bug#11139)

  • After running configure with the --with-embedded-privilege-control option, the embedded server failed to build. (Bug#13501)

  • Queries against a MERGE table that has a composite index could produce incorrect results. (Bug#9112)

  • Comparisons involving row constructors containing constants could cause a server crash. (Bug#13356)

  • MySQL would pass an incorrect key length to storage engines for MIN(). This could cause warnings such as InnoDB: Warning: using a partial-field key prefix in search. in the .err log. (Bug#13218, same as Bug#11039 in MySQL 5.0.7)

  • NDB Cluster: LOAD DATA INFILE with a large data file failed. (Bug#10694)

  • NDB Cluster: Adding an index to a table with a large number of columns (more then 100) crashed the storage node. (Bug#13316)

  • Aggregate functions sometimes incorrectly were allowed in the WHERE clause of UPDATE and DELETE statements. (Bug#13180)

  • MIN() and MAX() sometimes returned a non-NULL value for an empty row set (for example, SELECT MAX(1) FROM empty_table). (Bug#12882)

  • LOAD DATA INFILE did not respect the NO_AUTO_VALUE_ON_ZERO SQL mode setting. (Bug#12053)

  • Use of a user-defined function within the HAVING clause of a query resulted in an Unknown column error. (Bug#11553)

  • The data type for DECIMAL columns was not respected when updating the column from another column. For example, updating a DECIMAL(10,1) column with the value from a DECIMAL(10,5) column resulted in a DECIMAL(10,5) value being stored. Similarly, altering a column with a DECIMAL(10,5) datatype to a DECIMAL(10,1) data type did not properly convert data values. (Bug#7598)

  • NDB: A cluster shutdown following the crash of a data node would fail to terminate the remaining node processes, even though ndb_mgm showed the shutdown request as having been completed. (Bug#10938, Bug#9996, Bug#11623)

  • For queries with DISTINCT and WITH ROLLUP, the DISTINCT should be applied after the rollup operation, but was not always. (Bug#12887)

  • The counters for the Key_read_requests, Key_reads, Key_write_requests, and Key_writes status variables were changed from unsigned long to unsigned longlong to accommodate larger values before the variables roll over and restart from 0. (Bug#12920)

  • A column that can be NULL was not handled properly for WITH ROLLUP in a subquery or view. (Bug#12885)

  • Shared-memory connections were not working on Windows. (Bug#12723)

  • A concurrency problem for CREATE ... SELECT could cause a server crash. (Bug#12845)

  • Performing an IS NULL check on the MIN() or MAX() of an indexed column in a complex query could produce incorrect results. (Bug#12695)

  • The NDB START BACKUP command could be interrupted by a SHOW command. (Bug#13054)

  • The LIKE ... ESCAPE syntax produced invalid results when escape character was larger than one byte. (Bug#12611)

  • A client connection thread cleanup problem caused the server to crash when closing the connection if the binary log was enabled. (Bug#12517)

  • CHECKSUM TABLE command returned incorrect results for tables with deleted rows. After upgrading, users who used stored checksum information to detect table changes should rebuild their checksum data. (Bug#12296)

  • The value of character_set_results could be set to NULL, but returned the string "NULL" when retrieved. (Bug#12363)

  • GROUP_CONCAT() ignored an empty string if it was the first value to occur in the result. (Bug#12863)

  • Outer join elimination was erroneously applied for some queries that used a NOT BETWEEN condition, an IN(value_list) condition, or an IF() condition. (Bug#12101, Bug#12102)

  • Reverted a change introduced in MySQL 4.1.13 to fix a problem of SHOW FIELDS truncating the TYPE column to 40 characters. This fix was reverted for MySQL 4.1 because it broke existing applications. The fix will be made to MySQL 5.0 instead (5.0.13). (Bug#7142, Bug#12817)

  • On HP-UX 11.x (PA-RISC), the -L option caused mysqlimport to crash. (Bug#12958)

  • After changing the character set with SET CHARACTER SET, the result of the GROUP_CONCAT() function was not converted to the proper character set. (Bug#12829)

  • myisampack did not properly pack BLOB values larger than 224 bytes. (Bug#4214)

  • The server crashed when one thread resized the query cache while another thread was using it. (Bug#12848)

  • mysqld_multi now quotes arguments on command lines that it constructs to avoid problems with arguments that contain shell metacharacters. (Bug#11280)

  • When any --replicate-wild-* option is used, the slave ignores SET ONE_SHOT TIME_ZONE statements as belonging to a non-replicated table. (Bug#12542)

  • Deadlock occurred when several account management statements were run (particularly between FLUSH PRIVILEGES/SET PASSWORD and GRANT/REVOKE statements). (Bug#12423)

  • On Windows, the server was preventing tables from being created if the table name was a prefix of a forbidden name. For example, nul is a forbidden name because it's the same as a Windows device name, but a table with the name of n or nu was being forbidden as well. (Bug#12325)

  • InnoDB was too permissive with LOCK TABLE ... READ LOCAL and allowed new inserts into the table. Now READ LOCAL is equivalent to READ for InnoDB. This will cause slightly more locking in mysqldump, but makes InnoDB table dumps consistent with MyISAM table dumps. (Bug#12410)

  • The have_innodb read-only system variable could not be selected with SELECT @@have_innodb. (Bug#9613)

  • A UNION of long utf8 VARCHAR columns was sometimes returned as a column with a LONGTEXT data type rather than VARCHAR. This could prevent such queries from working at all if selected into a MEMORY table because the MEMORY storage engine does not support the TEXT data types. (Bug#12537)

  • NDB Cluster: Corrected the parsing of the CLUSTERLOG command by ndb_mgm to allow multiple items. (Bug#12833)

  • NDB Cluster: Improved error messages related to filesystem issues. (Bug#11218)

  • NDB Cluster: When a schema was detected to be corrupt, ndb neglected to close it, resulting in a 鈥file already open鈥 error if the schema was opened again later. written. (Bug#12027)

  • NDB Cluster: When it could not copy a fragment, ndbd exited without printing a message about the condition to the error log. Now the message is written. (Bug#12900)

  • NDB Cluster: When a disk full condition occurred, ndbd exited without printing a message about the condition to the error log. Now the message is written. (Bug#12716)

  • If a client has opened an InnoDB table for which the .ibd file is missing, InnoDB would not honor a DROP TABLE statement for the table. (Bug#12852)

  • SELECT GROUP_CONCAT(...) FROM DUAL in a subquery could cause the client to hang. (Bug#12861)

  • NDB Cluster: Bad values in config.ini caused ndb_mdmd to crash. (Bug#12043)

  • TRUNCATE TABLE did not work with TEMPORARY InnoDB tables. (Bug#11816)

  • ALTER TABLE db_name.t RENAME t did not move the table to default database unless the new name was qualified with the database name. (Bug#11493)

  • Spatial index corruption could occur during updates. (Bug#9645)

  • If a DROP DATABASE fails on a master server due to the presence of a non-database file in the database directory, the master have the database tables deleted, but not the slaves. To deal with failed database drops, we now write DROP TABLE statements to the binary log for the tables so that they are dropped on slaves. (Bug#4680)

  • DELETE or UPDATE for an indexed MyISAM table could fail. This was due to a change in end-space comparison behavior from 4.0 to 4.1. (Bug#12565)

  • The ARCHIVE storage engine does not support deletes, but it was possible to delete by using DELETE or TRUNCATE TABLE with a FEDERATED table that points to an ARCHIVE table. (Bug#12836)

  • Queries that created implicit temporary tables could return incorrect data types for some columns. (Bug#11718)

  • An optimizer estimate of zero rows for a non-empty InnoDB table used in a left or right join could cause incomplete rollback for the table. (Bug#12779)

  • A SELECT DISTINCT query with a constant value for one of the columns would return only a single row. (Bug#12625)

  • Users created using an IP address or other alias rather than a hostname listed in /etc/hosts could not set their own passwords. (Bug#12302)

  • NDB Cluster: An ALTER TABLE command caused loss of data stored prior to the issuing of the command. (Bug#12118)

  • MEMORY tables using B-Tree index on 64-bit platforms could produce false table is full errors. (Bug#12460)

  • MySQL failed to compile when --with-ndb-ccflags was specified. (Bug#11538)

  • On Windows when the --innodb_buffer_pool_awe_mem_mb option has been given, the server detects whether AWE support is available and has been compiled into the server, and displays an appropriate error message if not. (Bug#6581)

B.1.10.聽Changes in release 4.1.14 (17 August 2005)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • SHOW CHARACTER SET and INFORMATION_SCHEMA now properly report the Latin1 character set as cp1252. (Bug#11216)

  • MySQL Cluster: A new -P option is available for use with the ndb_mgmd client. When called with this option, ndb_mgmd prints all configuration data to stdout, then exits.

  • The output of perror --help now displays the --ndb option. (Bug#11999)

  • NDB: Improved handling of the configuration variables NoOfPagesToDiskDuringRestartACC, NoOfPagesToDiskAfterRestartACC, NoOfPagesToDiskDuringRestartTUP, and NoOfPagesToDiskAfterRestartTUP should result in noticeably faster startup times for MySQL Cluster. (Bug#12149)

  • Added support of where clause for queries with FROM DUAL. (Bug#11745)

  • Added an optimization that avoids key access with NULL keys for the ref method when used in outer joins. (Bug#12144)

  • Added new query cache test for the embedded server to the test suite, there are now specific tests for the embedded and non-embedded servers. (Bug#9508)

Bugs fixed:

  • If a thread (connection) has tables locked, the query cache is switched off for that thread. This prevents invalid results where the locking thread inserts values between a second thread connecting and selecting from the table. (Bug#12385)

  • Prepared statement parameters could cause errors in the binary log if the character set was cp932. (Bug#11338)

  • Queries with subqueries that contain outer joins could return wrong results. (Bug#11479)

  • Slave I/O threads were considered to be in the running state when launched (rather than after successfully connecting to the master server), resulting in incorrect SHOW SLAVE STATUS output. (Bug#10780)

  • On Windows, the server could crash during shutdown if both replication threads and normal client connection threads were active. (Bug#11796)

  • Some subqueries of the form SELECT ... WHERE ROW(...) IN (subquery) were being handled incorrectly. (Bug#11867)

  • The mysql_info() C API function could return incorrect data when executed as part of a multi-statement that included a mix of statements that do and do not return information. (Bug#11688)

  • Renamed the rest() macro in my_list.h to list_rest() to avoid name clashes with user code. (Bug#12327)

  • myisampack failed to delete .TMD temporary files when run with -T option. (Bug#12235)

  • Concatenating USER()/DATEBASE() with a column produces invalid results. (Bug#12351)

  • For PKG installs on Mac OS X, the preinstallation and postinstallation scripts were being run only for new installations and not for upgrade installations, resulting in an incomplete installation process. (Bug#11380)

  • User variables were not automatically cast for comparisons, causing queries to fail if the column and connection character sets differed. Now when mixing strings with different character sets but the same coercibility, allow conversion if one character set is a superset of the other. (Bug#10892)

  • Pathame values for options such as ---basedir or --datadir didn't work on Japanese Windows machines for directory names containing multi-byte characters having a second byte of 0x5C (鈥\鈥). (Bug#5439)

  • Mishandling of comparison for rows containing NULL values against rows produced by an IN subquery could cause a server crash. (Bug#12392)

  • INSERT ... SELECT ... ON DUPLICATE KEY UPDATE could fail with an erroneous 鈥Column 'col_name' specified twice鈥 error. (Bug#10109)

  • myisam.test failed when server compiled using --without-geometry option. (Bug#11083)

  • Creation of the mysql group account failed during the RPM installation. (Bug#12348)

  • FLUSH TABLES WITH READ LOCK combined with LOCK TABLE .. WRITE caused deadlock. (Bug#9459)

  • GROUP_CONCAT ignores the DISTINCT modifier when used in a query joining multiple tables where one of the tables has a single row. (Bug#12095)

  • UNION query with FULLTEXT could cause server crash. (Bug#11869)

  • Performing DATE(LEFT(column,8)) on a DATE column produces incorrect results. (Bug#12266)

  • max_connections_per_hour setting was being capped by unrelated max_user_connections setting. (Bug#9947)

  • big5 strings were not being stored in FULLTEXT index. (Bug#12075)

  • Updated dependency list for RPM builds to include missing dependencies such as useradd and groupadd. (Bug#12233)

  • Multiplying ABS() output by a negative number would return incorrect results. (Bug#11402)

  • SELECT @@local... returned @@session... in the column header. (Bug#10724)

  • Character data truncated when GBK characters 0xA3A0 and 0xA1 are present. (Bug#11987)

  • Comparisons like SELECT "A\\" LIKE "A\\"; fail when using SET NAMES utf8;. (Bug#11754)

  • Attempting to repair a table having a fulltext index on a column containing words whose length exceeded 21 characters and where myisam_repair_threads was greater than 1 would crash the server. (Bug#11684)

  • Two threads could potentially initialize different characters sets and overwrite each other. (Bug#12109)

  • NDB: Attempting to create or drop tables during a backup would cause the cluster to shut down. (Bug#11942)

  • NDB_MGMD was leaking file descriptors. (Bug#11898)

  • NDB ignored the Hostname option in the NDBD DEFAULT section of the NDB configuration file. (Bug#12028)

  • The temporary tables created by an ALTER TABLE on a cluster table were visible to all MySQL servers. (Bug#12055)

  • For prepared statements, the SQL parser did not disallow 鈥?鈥 parameter markers immediately adjacent to other tokens, which could result in malformed statements in the binary log. (For example, SELECT * FROM t WHERE? = 1 could become SELECT * FROM t WHERE0 = 1.) (Bug#11299)

  • GROUP_CONCAT() sometimes returned a result with a different collation from that of its arguments. (Bug#10201)

  • When two threads compete for the same table, a deadlock could occur if one thread has also a lock on another table through LOCK TABLES and the thread is attempting to remove the table in some manner and the other thread want locks on both tables. (Bug#10600)

  • Incorrect error message displayed if user attempted to create a table in a non-existing database using CREATE database_name.table_name syntax. (Bug#10407)

  • The LPAD() and RPAD() functions returned the wrong length to mysql_fetch_fields(). (Bug#11311)

  • The C API function mysql_statement_reset() did not clear error information. (Bug#11183)

  • Multiple-table UPDATE queries using CONVERT_TZ() would fail with an error. (Bug#9979)

  • mysql_fetch_fields() returned incorrect length information for MEDIUM and LONG TEXT and BLOB columns. (Bug#9735)

  • LIKE pattern matching using prefix index didn't return correct result. (Bug#11650)

  • The MySQL server had issues with certain combinations of basedir and datadir. (Bug#7249)

  • mysql_next_result() returns incorrect value if final query in a batch fails. (Bug#12001)

  • SHOW BINARY LOGS displayed a file size of 0 for all log files but the current one if the files were not located in the data directory. (Bug#12004)

  • Server-side prepared statements failed for columns with a character set of ucs2. (Bug#9442)

  • References to system variables in an SQL statement prepared with PREPARE were evaluated during EXECUTE to their values at prepare time, not to their values at execution time. (Bug#9359)

  • For server shutdown on Windows, error messages of the form Forcing close of thread n user: 'name' were being written to the error log. Now connections are closed more gracefully without generating error messages. (Bug#7403)

  • Corrected a problem with the optimizer incorrectly adding NOT NULL constraints, producing in incorrect results for complex queries. (Bug#11482)

  • Corrected an optimizer problem with NOT NULL constraints within a subquery in an UPDATE statement that resulted in a server crash. (Bug#11868)

  • Creating a table with a SET or ENUM column with the DEFAULT 0 clause caused a server crash if the table's character set was utf8. (Bug#11819)

  • In SQL prepared statements, comparisons could fail for values not equally space-padded. For example, SELECT 'a' = 'a聽'; returns 1, but PREPARE s FROM 'SELECT ?=?'; SET @a = 'a', @b = 'a聽'; PREPARE s FROM 'SELECT ?=?'; EXECUTE s USING @a, @b; incorrectly returned 0. (Bug#9379)

  • InnoDB: Do not flush after each write, not even before setting up the doublewrite buffer. Flushing can be extremely slow on some systems. (Bug#12125)

  • ISO-8601 formatted dates were not being parsed correctly. (Bug#7308)

B.1.11.聽Changes in release 4.1.13 (15 July 2005)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • Security improvement: Applied a patch that addresses a zlib data vulnerability that could result in a buffer overflow and code execution. (CVE-2005-2096) (Bug#11844). Shortly after MySQL 4.1.13 was released, a second potential zlib security flaw was discovered and fixed - the issue is tracked by the Mitre CVE ID (CVE-2005-1849). A patch for this flaw was applied on top of the 4.1.13 sources and published as 4.1.13a. The affected binaries have been rebuilt.

  • Security improvement: Applied a patch to fix a UDF library-loading vulnerability that could result in a buffer overflow and code execution. (http://www.appsecinc.com/resources/alerts/mysql/2005-002.html)

  • Warning: Incompatible change: Previously, conversion of DATETIME values to numeric form by adding zero produced a result in YYYYMMDDHHMMSS format. The result of DATETIME+0 is now in YYYYMMDDHHMMSS.000000 format. (Bug#12268)

  • Added the --add-drop-database option to mysqldump. (Bug#3716)

  • Added mysql_set_character_set() C API function for setting the default character set of the current connection. This allows clients to affect the character set used by mysql_real_escape_string(). (Bug#8317)

  • MEMORY tables now support indexes of up to 500 bytes. See Section聽14.4, 鈥淭he MEMORY (HEAP) Storage Engine鈥. (Bug#10566)

  • System variables are now treated as having SYSVAR (system constant) coercibility. For example, @@version is now treated like VERSION() and @@character_set_client is now treated like CHARSET( USER() ). See Section聽10.5.4, 鈥淪ome Special Cases Where the Collation Determination Is Tricky鈥. (Bug#10904)

  • The statements CREATE TABLE, TRUNCATE TABLE, DROP DATABASE, and CREATE DATABASE cause an implicit commit. (Bug#6883)

  • Added the --log-slow-admin-statements server option to request logging of slow administrative statements such as OPTIMIZE TABLE, ANALYZE TABLE, and ALTER TABLE to the slow query log. These statements were logged in MySQL 4.0, but not in 4.1. (Bug#9141)

  • SHOW BINARY LOGS now displays a File_size column that indicates the size of each file.

  • You can again refer to other tables in the ON DUPLICATE KEY UPDATE part of an INSERT ... SELECT statement as long as there is no GROUP BY in the SELECT part. One side effect of this is that you may have to qualify non-unique column names in the values part of ON DUPLICATE KEY UPDATE. (Bug#9728, Bug#8147)

  • The table, type, and rows columns of EXPLAIN output can now be NULL. This is required for using EXPLAIN on SELECT queries that use no tables, such as EXPLAIN SELECT 1). (Bug#9899)

  • Expanded on information provided in general log and slow query log for prepared statements. (Bug#8367, Bug#9334)

  • InnoDB: When creating or extending an InnoDB data file, allocate at most one megabyte at a time for initializing the file. Previously, InnoDB used to allocate and initialize 1 or 8 megabytes of memory, even if a few 16-kilobyte pages were to be written. This fix improves the performance of CREATE TABLE in innodb_file_per_table mode.

Bugs fixed:

  • Security fix: On Windows systems, a user with any of the following privileges

    • REFERENCES

    • CREATE TEMPORARY TABLES

    • GRANT OPTION

    • CREATE

    • SELECT

    on *.* could crash mysqld by issuing a USE LPT1; or USE PRN; command. In addition, any of the commands USE NUL;, USE CON;, USE COM1;, or USE AUX; would report success even though the database was not in fact changed. (Bug#9148, CVE-2005-0799

  • When applying the group_concat_max_len limit, GROUP_CONCAT() could truncate multi-byte characters in the middle. (Bug#23451)

  • A CREATE TABLE db_name.tbl_name LIKE ... statement would crash the server when no database was selected. (Bug#11028)

  • IP addresses not shown in ndb_mgm SHOW command on second ndb_mgmd (or on ndb_mgmd restart). (Bug#11596)

  • SHOW FIELDS truncated the TYPE column to 40 characters. (Bug#7142, Bug#12817) (Note: This fix was reverted in MySQL 4.1.15 because it broke existing applications.)

  • Prepared statement with subqueries returned corrupt data. (Bug#11458)

  • A ROLLUP query could return a wrong result set when its GROUP BY clause contained references to the same column. (Bug#11543)

  • Queries with subqueries in the FROM clause were not being added to the query cache. (Bug#11522)

  • Possible crash on Windows when performing GROUP BY on a calculated field. (Bug#11414)

  • The mysql_config script did not handle symbolic linking properly. (Bug#10986)

  • When used within a subquery, SUBSTRING() returned an empty string. (Bug#10269)

  • On Mac OS X, libmysqlclient_r.a now is built with --fno-common to make it possible to link a shared two-level namespace library against libmysqlclient_r.a. (Bug#10638)

  • The handling by the HEX() function of numbers larger than 264 was improved. (Bug#9854)

  • Added a missing mutex when rotating the relay logs. Also, the server now logs an error message if the size of a relay log cannot be read. (Bug#6987)

  • Added a missing mutex when rotating the relay logs. Also, the server now logs an error message if the size of a relay log cannot be read. (Bug#6987)

  • mysqldump could crash for illegal or non-existent table names. (Bug#9358)

  • The --no-data option for mysqldump was being ignored if table names were given after the database name. (Bug#9558)

  • mysqldump now exports HASH index definitions using USING rather than TYPE when the index name is optional. This corrects a problem when reloading the output for PRIMARY KEY definition, because TYPE must be preceded an index name, which is not given for a PRIMARY KEY. (Bug#11635)

  • The --master-data option for mysqldump resulted in no error if the binary log was not enabled. Now an error occurs unless the --force option is given. (Bug#11678)

  • Corrected an optimization failure where a query returned an incorrect result for use of a newly populated table until the table was flushed. (Bug#11700)

  • Modifying a CHAR column with the utf8 character set to a shorter length did not properly truncate values due to not computing their length in utf8 character units. (Bug#11591)

  • DES_ENCRYPT() and DES_DECRYPT() require SSL support to be enabled, but were not checking for it. Checking for incorrect arguments or resource exhaustion was also improved for these functions. (Bug#10589)

  • Invoking the DES_ENCRYPT() function could cause a server crash if the server was started without the --des-key-file option. (Bug#11643)

  • Selecting the result of an aggregate function for an ENUM or SET column within a subquery could result in a server crash. (Bug#11821)

  • When used in joins, SUBSTRING() failed to truncate to zero those string values that could not be converted to numbers. (Bug#10124)

  • Error when performing GROUP BY on calculated values of a single row table. (Bug#11414)

  • mysqldump --xml did not format NULL column values correctly. (Bug#9657)

  • SHOW WARNINGS did not properly display warnings generated by executing a cached query. (Bug#9414)

  • Temporary tables were created in the data directory instead of tmpdir. (Bug#11440)

  • LOAD DATA ... REPLACE INTO ... on a replication slave failed for an InnoDB table having a unique index in addition to the primary key. (Bug#11401)

  • MySQL would not compile correctly on QNX due to missing rint() function. (Bug#11544)

  • Incorrect results when searching using IN() where search items included NULL and 0. (Bug#9393)

  • NDB Cluster: When trying to open a table that could not be discovered or unpacked, cluster would return error codes which the MySQL server falsely interpreted as operating system errors. (Bug#103651)

  • Manually inserting a row with host='' into mysql.tables_priv and performing a FLUSH PRIVILEGES would cause the server to crash. (Bug#11330)

  • MySQL sometimes reported erroneously that certain character values had crashed a table when trying to convert other character sets to UTF-8. (Bug#9557)

  • Using CONCAT_WS() on a column set NOT NULL caused incorrect results when used in a LEFT JOIN. (Bug#11469)

  • mysqld_safe would sometimes fail to remove the pid file for the old mysql process after a crash. As a result, the server would fail to start due to a false A mysqld process already exists... error. (Bug#11122)

  • For MEMORY tables, it was possible for updates to be performed using outdated key statistics when the updates involved only very small changes in a very few rows. This resulted in the random failures of queries such as UPDATE t SET col = col + 1 WHERE col_key = 2; where the same query with no WHERE clause would succeed. (Bug#10178)

  • The NULLIF() function could produce incorrect results if the first argument was NULL. (Bug#11142)

  • Optimizer performed range check when comparing unsigned integers to negative constants, could cause errors. (Bug#11185)

  • Cluster failed to build with gcc 4.0. (Bug#11377)

  • The LAST_DAY() failed to return NULL when supplied with an invalid argument. See Section聽12.6, 鈥淒ate and Time Functions鈥. (Bug#10568)

  • Setting @@SQL_MODE = NULL caused an erroneous error message. (Bug#10732)

  • Server crashed when using GROUP BY on the result of a DIV operation on a DATETIME value. (Bug#11385)

  • Possible NULL values in BLOB columns could crash server when BLOB used in GROUP BY. (Bug#11295)

  • Fixed 64 bit compiler warning for packet length in replication. (Bug#11064)

  • CASE function returns incorrect result when its arguments are not constants and its return value is put into a regular or temporary table (temporary == created by SQL engine for UNION/non-indexed GROUP BY and such operations). (Bug#10151)

  • A problem with the my_global.h file caused compilation of MySQL to fail on single-processor Linux systems running 2.6 kernels. (Bug#10364)

  • Queries against a table using a compound index based on the length of a UTF-8 text column produced incorrect results. For example, given a table with an index defined as shown:

    CREATE TABLE t (
      id INT NOT NULL,
      city VARCHAR(20) NOT NULL,
      KEY (city(7),id)
    ) TYPE=MYISAM CHARACTER SET=utf8;
    

    Assuming that suitable data has been inserted into the table, then a query such as SELECT * FROM t WHERE city = 'Durban'; would fail. (Bug#10253)

  • The mysqlhotcopy script was not parsing the output of SHOW SLAVE STATUS correctly when called with the --record_log_pos option. (Bug#7967)

  • An UPDATE query containing a subquery caused replication to fail. (Bug#9361)

  • Last insert expected from a query of the form INSERT ... SELECT ... ON DUPLICATE KEY UPDATE would fail. (Bug#9728)

  • INSERT ... SELECT ... ON DUPLICATE KEY UPDATE produced inaccurate results. (Bug#10886)

  • SELECT DISTINCT ... GROUP BY constant returned multiple rows (it should return a single row). (Bug#8614)

  • Queries of the form UPDATE ... (SELECT ... ) SET ... run on a replication master would crash all the slaves. (CVE-2004-4380, Bug#10442)

  • OPTIMIZE of InnoDB table did not return 'Table is full' if out of tablespace. (Bug#8135)

  • Queries with ROLLUP returned wrong results for expressions containingGROUP BY columns. (Bug#7894)

  • Fixed hang/crash with Boolean full-text search where a query contained more query terms that one-third of the query length (it could be achieved with truncation operator: 'a*b*c*d*'). (Bug#7858)

  • The mysql client would output a prompt twice following input of very long strings, because it incorrectly assumed that a call to the _cgets() function would clear the input buffer. (Bug#10840)

  • A bug in FIELD() function caused the value list to contain NULL. (Bug#10944)

  • A three byte buffer overflow in the client functions could cause improper exiting of the client when reading a command from the user. (Bug#10841)

  • Fixed a problem with the cp1250_czech_cs collation that caused some LIKE comparisons to fail. (Bug#9759)

  • Fixed a problem resolving table names with lower_case_table_names=2 when the table name lettercase differed in the FROM and WHERE clauses. (Bug#9500)

  • Fixed server crash due to some internal functions not taking into account that for multi-byte character sets, CHAR and VARCHAR columns could exceed 255 bytes. (Bug#11167)

  • Fixed a portability problem testing for crypt() support that caused compilation problems when using OpenSSL/yaSSL on HP-UX and Mac OS X. (Bug#10675, Bug#11150)

  • The hostname cache was not working. (Bug#10931)

  • For a MERGE table with MyISAM tables in other, symlinked, databases, SHOW CREATE TABLE reported the MyISAM tables using the name of the symlinked directory rather than the database name. (Bug#8183)

  • Fixed a server crash resulting from an attempt to allocate too much memory when GROUP BY blob_col and COUNT(DISTINCT) were used. (Bug#11088)

  • The incorrect sequence of statements HANDLER tbl_name READ index_name NEXT without a preceding HANDLER tbl_name READ index_name = (value_list) for an InnoDB table resulted in a server crash rather than an error. (Bug#5373)

  • SHOW WARNINGS with a LIMIT 0 clause returned all messages rather than an empty result set. (Bug#11095)

  • On Windows, with lower_case_table_names set to 2, using ALTER TABLE to alter a MEMORY or InnoDB table that had a mixed-case name also improperly changed the name to lowercase. (Bug#9660)

  • The server timed out SSL connections too quickly on Windows. (Bug#8572)

  • Inserting a DOUBLE value into a utf8 string column crashed the server on Windows. (Bug#10714)

  • Executing LOAD INDEX INTO CACHE for a table while other threads where selecting from the table caused a deadlock. (Bug#10602)

  • Fixed a server crash resulting from CREATE TABLE ... SELECT that selected from a table being altered by ALTER TABLE. (Bug#10224)

  • Fixed a server crash resulting from invalid string pointer when inserting into the mysql.host table. (Bug#10181)

  • GROUP_CONCAT() with DISTINCT and WITH ROLLUP ignored DISTINCT for some rows. (Bug#7405)

  • Fixed a problem creating the result set for a UNION that involved long string values. Values were not being converted correctly to TEXT values. (Bug#10025)

  • Locking for CREATE TABLE ... SELECT for InnoDB tables was too weak. It allowed INSERT statements issued for the created table while the CREATE TABLE statement was still running to appear in the binary log before the CREATE TABLE statement. (Bug#6678)

  • InnoDB: In DROP DATABASE, check for all referencing tables from other databases before dropping any tables. (Bug#10335)

  • InnoDB: Fix bug: InnoDB wrongly complained in the .err log that MySQL is trying to drop a non-existent table, if tablespace ran out. (Bug#10607)

  • Fixed an overly strict debugging assertion that caused debug server builds to fail for some col_name = const_expr, where const_expr was a constant expression such as a subquery. (Bug#10020)

  • SUBSTR() did not work properly for input in the ucs2 character set. (Bug#10344)

  • Fixed a problem causing an incorrect result for columns that include an aggregate function as part of an expression when WITH ROLLUP is added to GROUP BY. (Bug#7914)

  • Fixed a server crash for INSERT ... ON DUPLICATE KEY UPDATE with MERGE tables, which do not have unique indexes. (Bug#10400)

  • CREATE TABLE t AS SELECT UUID() created a VARCHAR(12) column, which is too small to hold the 36-character result from UUID(). (Bug#9535)

  • Portability fix for Cygwin: Don't use #pragma interface or #pragma implementation in source files. (Bug#10241)

  • Fixed a mysqldump crash that occurred with the --complete-insert option when dumping tables with a large number of long column names. (Bug#10286)

  • ALTER TABLE ... ENABLE INDEXES treated NULL values as equal when collecting index statistics for MyISAM tables, resulting in different statistics from those generated by ANALYZE TABLE and causing the optimizer to make poor index choices later. The same problem occurred for bulk insert statistics collection. Now NULL values are treated as unequal, just as for ANALYZE TABLE. (Bug#9622)

B.1.12.聽Changes in release 4.1.12 (13 May 2005)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Note: The fix for interpretation of MERGE table .MRG files (Bug#10687) was made for Windows builds after MySQL 4.1.12 was released and is present in MySQL 4.1.12a.

Functionality added or changed:

  • Incompatible change: The behavior of LOAD DATA INFILE and SELECT ... INTO OUTFILE has changed when the FIELDS TERMINATED BY and FIELDS ENCLOSED BY values both are empty. Formerly, a column was read or written the display width of the column. For example, INT(4) was read or written using a field with a width of 4. Now columns are read and written using a field width wide enough to hold all values in the field. However, data files written before this change was made might not be reloaded correctly with LOAD DATA INFILE for MySQL 4.1.12 and up. This change also affects data files read by mysqlimport and written by mysqldump --tab, which use LOAD DATA INFILE and SELECT ... INTO OUTFILE. For more information, see Section聽13.2.5, 鈥LOAD DATA INFILE Syntax鈥. (Bug#12564)

  • Added --debug option to my_print_defaults.

  • When the server cannot read a table because it cannot read the .frm file, print a message that the table was created with a different version of MySQL. (This can happen if you create tables that use new features and then downgrade to an older version of MySQL.) (Bug#10435)

  • New /*> prompt for mysql. This prompt indicates that a /* ... */ comment was begun on an earlier line and the closing */ sequence has not yet been seen. (Bug#9186)

  • Added cp1250_croatian_ci collation. (Bug#6505)

  • Updated version of libedit to 2.9. (Bug#2596)

  • InnoDB: When the maximum length of SHOW INNODB STATUS output would be exceeded, truncate the beginning of the list of active transactions, instead of truncating the end of the output. (Bug#5436)

  • InnoDB: When FOREIGN_KEY_CHECKS=0, ALTER TABLE and RENAME TABLE will ignore any type incompatibilities between referencing and referenced columns. Thus, it will be possible to convert the character sets of columns that participate in a foreign key. Be sure to convert all tables before modifying any data! (Bug#9802)

  • InnoDB: Setting the initial AUTO_INCREMENT value for an InnoDB table using CREATE TABLE ... AUTO_INCREMENT = n now works, and ALTER TABLE ... AUTO_INCREMENT = n resets the current value. (Bug#7061)

  • InnoDB: If innodb_locks_unsafe_for_binlog option set and isolation level of the transaction is not set to serializable then InnoDB uses a consistent read for select in clauses like INSERT INTO ... SELECT and UPDATE ... (SELECT) that do not specify FOR UPDATE or IN SHARE MODE. Thus no locks are set to rows read from selected table.

  • Previously in MySQL 4.1, an Illegal mix of collations error occurred when mixing strings from same character set when one had a non-binary collation and the other a binary collation. Now the binary collation takes precedence, so that both strings are treated as having the binary collation. This restores compatibility with MySQL 4.0 behavior.

  • Added the cp932 Japanese character set.

Bugs fixed:

  • Security fix: If mysqld was started with --user=non_existent_user, it would run using the privileges of the account it was invoked from, even if that was root. (Bug#9833)

  • Fixed handling of floats and doubles when using prepared statement API in the embedded server. (Bug#10443)

  • An error in the implementation of the MyISAM compression algorithm caused myisampack to fail with very large sets of data (total size of all the records in a single column needed to be >= 3 GB in order to trigger this issue). (Bug#8321)

  • When SELECT constant was the final SELECT in a UNION, a trailing LIMIT ... worked, but a trailing ORDER BY ... or ORDER BY ... LIMIT ... did not. (Bug#10032)

  • MERGE tables could fail on Windows due to incorrect interpretation of pathname separator characters for filenames in the .MRG file. (Bug#10687)

  • CHAR and VARCHAR columns that used the sjis character set were not being saved correctly, causing the following columns to be corrupted. (Bug#10493)

  • For a user-defined function invoked from within a prepared statement, the UDF's initialization routine was invoked for each execution of the statement, but the deinitialization routine was not. (It was invoked only when the statement was closed.) For UDFs that have an expensive deinit function (such as myperl), this bugfix will have negative performance consequences. (Bug#9913)

  • Fix CREATE TABLE ... LIKE to work when lower_case_table_names is set on a case-sensitive filesystem and the source table name is not given in lowercase. (Bug#9761)

  • my_print_defaults was ignoring the --defaults-extra-file option or crashing when the option was given. (Bug#9136, Bug#9851)

  • For MERGE tables, avoid writing absolute pathnames in the .MRG file for the names of the constituent MyISAM tables so that if the data directory is moved, MERGE tables will not break. For mysqld, write just the MyISAM table name if it is in the same database as the MERGE table, and a path relative to the data directory otherwise. For the embedded servers, absolute pathnames may still be used. (Bug#5964)

  • Corrected the error message for exceeding the MAX_CONNECTIONS_PER_HOUR limit to say max_connections_per_hour instead of max_connections. (Bug#9947)

  • Fixed incorrect memory block allocation for the query cache in the embedded server. (Bug#9549)

  • Fixed a configure problem in checking for capability of performing atomic operations. (Bug#7970)

  • net_read_timeout and net_write_timeout were not being respected on Windows. (Bug#9721)

  • An error occurred if you specified a default value of TRUE or FALSE for a BOOL column. (Bug#9666)

  • Corrected some failures of prepared statements for SQL (PREPARE plus EXECUTE) to return all rows for some SELECT statements. (Bug#9096, Bug#9777)

  • Remove extra slashes in --tmpdir value (for example, convert /var//tmp to /var/tmp, because they caused various errors. (Bug#8497)

  • Fixed a sort order problem with the latin2_croatian_ci collation. All tables that have indexes that use this collation will be treated as crashed. After upgrading, for each such table, you must use CHECK TABLE and possibly repair the table. (Bug#6505)

  • mysqld was not checking whether the PID file was successfully created. (Bug#5843)

  • With DISTINCT CONCAT(col,...) returned incorrect results when the arguments to CONCAT() were columns with an integer data type declared with a display width narrower than the values in the column. (For example, if an INT(1) column contain 1111.) (Bug#4082)

  • Fixed configure to properly recognize whether NPTL is available on Linux. (Bug#2173)

  • Fixed a portability problem in compiling mysql.cc with VC++ on Windows. (Bug#10245)

  • CAST(string_argument AS UNSIGNED) didn't work for big integers above the signed range. Now this function and CAST(string_argument AS SIGNED) also produces warnings for wrong string arguments. (Bug#7036)

  • Fixed compile problem with MinGW. Thanks to Nils Durner for patch! (Bug#8872)

  • MySQL no longer automatically blocks IP numbers for which gethostbyname_r() fails when the reason is that the DNS server is down. Thanks to Jeremy Cole for patch. (Bug#8467)

  • Fixed a bug in the key cache that caused a core dump. (Bug#10167)

  • The --delimiter option for the nds_select program was non-functional. (Bug#10287)

  • MAX() for an INT UNSIGNED (unsigned 4-byte integer) column could return negative values if the column contained values larger than 231. (Bug#9298)

  • Fixed a deadlock resulting from use of FLUSH TABLES WITH READ LOCK while an INSERT DELAYED statement is in progress. (Bug#7823)

  • Multiple-table updates could produce spurious data-truncation warnings if they used a join across columns that are indexed using a column prefix. (Bug#9103)

  • Use of a subquery that used WITH ROLLUP in the FROM clause of the main query sometimes resulted in a Column cannot be null error. (Bug#9681)

  • RENAME TABLE for an ARCHIVE table failed if the .arn file was not present. (Bug#9911)

  • Fixed an optimizer problem where extraneous comparisons between NULL values in indexed columns were being done for operators such as = that are never true for NULL. (Bug#8877)

  • SELECT ROUND(expr) produced a different result from CREATE TABLE ... SELECT ROUND(expr). (Bug#9837)

  • Fixed some awk script portability problems in cmd-line-utils/libedit/makelist.sh. (Bug#9954)

  • Changed metadata for result of SHOW KEYS: Data type for Sub_part column now is SMALLINT rather than TINYINT because key part length can be longer than 255. (Bug#9439)

  • Fixed some problems with myisampack on 64-bit systems that resulted in segmentation violations. (Bug#9487)

  • Fixed an optimizer bug in computing the union of two ranges for the OR operator. (Bug#9348)

  • Fixed an index corruption problem for MyISAM tables that resulted from the 4.1 behavior of padding values with blanks for comparison: Dumping a table with mysqldump, reloading it, and then re-running the binary log against it crashed the index and necessitated a repair. (Bug#9188)

  • Fixed a segmentation fault in mysqlcheck that occurred when the last table checked in --auto-repair mode returned an error (such as the table being a MERGE table). (Bug#9492)

  • Fixed the client/server protocol for prepared statements so that reconnection works properly when the connection is killed while reconnect is enabled. (Bug#8866)

  • INSERT ... ON DUPLICATE KEY UPDATE incorrectly updated a TIMESTAMP column to the current timestamp, even if the update list included col_name = col_name for that column to prevent the update. (Bug#7806)

  • Starting mysqld with the --skip-innodb and --default-storage-engine=innodb (or --default-table-type=innodb caused a server crash. (Bug#9815)

  • Queries containing CURRENT_USER() incorrectly were registered in the query cache. (Bug#9796)

  • A server installed as a Windows service and started with --shared-memory could not be stopped. (Bug#9665)

  • mysqldump dumped core when invoked with --tmp and --single-transaction options and a non-existent table name. (Bug#9175)

  • Additional fix for mysql_server_init() and mysql_server_end() C API functions so that stopping and restarting the embedded server will not cause a crash. (Bug#7344)

  • mysql.server no longer uses non-portable alias command or LSB functions. (Bug#9852)

  • Fixed a readline-related crash in mysql when the user pressed Control-R. (Bug#9568)

  • TIMEDIFF() with a negative time first argument and positive time second argument produced incorrect results. (Bug#8068)

  • Fixed a bug that caused concurrent inserts to be allowed into the tables in the SELECT ... UNION ... part of INSERT ... SELECT ... UNION .... This could result in the incorrect order of queries in the binary log. (Bug#9922)

  • The warning message from GROUP_CONCAT() did not always indicate the correct number of lines. (Bug#8681)

  • InnoDB: ENUM and SET columns were treated incorrectly as character strings. This bug did not manifest itself with latin1 collations, but it caused malfunction with utf8. Old tables will continue to work. In new tables, ENUM and SET will be internally stored as unsigned integers. (Bug#9526)

  • InnoDB: Avoid test suite failures caused by a locking conflict between two server instances at server shutdown/startup. This conflict on advisory locks appears to be the result of a bug in the operating system; these locks should be released when the files are closed, but somehow that does not always happen immediately in Linux. (Bug#9381)

  • InnoDB: Prevent ALTER TABLE from changing the storage engine if there are foreign key constraints on the table. (Bug#5574, Bug#5670)

  • InnoDB: Fixed a deadlock without any locking, simple select and update. (Bug#7975) InnoDB now takes an exclusive lock when INSERT ON DUPLICATE KEY UPDATE is checking duplicate keys.

  • InnoDB: Fix a problem in crash recovery of .ibd files on Windows if the user used lower_case_table_names=0 or 2; the directory scan in crash recovery forgot to put all paths to lower case, so that the tablespace name would be consistent with the internal data dictionary of InnoDB.

  • InnoDB: Add fault tolerance in the scan of .ibd files at a crash recovery; formerly a single failure of readdir_get_next caused the rest of the directory to be skipped.

  • InnoDB: Fix assertion failures of type ut_a(cursor->old_stored == BTR_PCUR_OLD_STORED) and prebuilt->template_type == 0. This bug was introduced in 4.1.10 and 4.0.24. (Bug#9670)

  • InnoDB: Fix a performance bug: At the shutdown, write the latest lsn only to the first pages of the ibdata files of the system tablespace, NOT to the .ibd files; writing to tens of thousands .ibd files can take minutes.

  • Fix for auto-increment not working with INSERT..SELECT and NDB storage engine. (Bug#9675)

B.1.13.聽Changes in release 4.1.11 (01 April 2005)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • ONLY_FULL_GROUP_BY no longer is included in the ANSI composite SQL mode. (Bug#8510)

  • mysqld_safe will create the directory where the UNIX socket file is to be located if the directory does not exist. This applies only to the last component of the directory pathname. (Bug#8513)

  • The coercibility for the return value of functions such as USER() or VERSION() now is 鈥system constant鈥 rather than 鈥implicit.鈥 This makes these functions more coercible than column values so that comparisons of the two do not result in Illegal mix of collations errors. COERCIBILITY() was modified to accommodate this new coercibility value. See Section聽12.10.3, 鈥淚nformation Functions鈥.

  • User variable coercibility has been changed from 鈥coercible鈥 to 鈥implicit.鈥 That is, user variables have the same coercibility as column values.

  • NULL now is considered more coercible than string constants. This resolves some Illegal mix of collations conflicts.

  • Modified the parser to allow SELECT statements following the UNION keyword to be subqueries in parentheses. (Bug#2435)

  • For slave replication servers started with --replicate-* options, statements that should not be replicated according those options no longer are written to the slave's general query log. (Bug#8297)

  • Added SQL_NOTES session variable to cause Note-level warnings not to be recorded. (Bug#6662)

  • InnoDB: Commit after every 10,000 copied rows when executing CREATE INDEX, DROP INDEX or OPTIMIZE TABLE, which are internally implemented as ALTER TABLE. This makes it much faster to recover from an aborted operation.

  • Added a new global system variable slave_transaction_retries: If the replication slave SQL thread fails to execute a transaction because of an InnoDB deadlock or exceeded InnoDB's innodb_lock_wait_timeout or NDBCluster's TransactionDeadlockDetectionTimeout or TransactionInactiveTimeout, it automatically retries slave_transaction_retries times before stopping with an error. The default in MySQL 4.1 is 0. You must explicitly set the value greater than 0 to enable the 鈥retry鈥 behavior. (In MySQL 5.0.3 or newer, the default is 10.) (Bug#8325)

  • Added --with-big-tables compilation option to configure. (Previously it was necessary to pass -DBIG_TABLES to the compiler manually in order to enable large table support.) See Section聽2.9.2, 鈥淭ypical configure Options鈥, for details.

  • Added configuration directives !include and !includedir for including option files and searching directories for option files. See Section聽4.3.2, 鈥淯sing Option Files鈥, for usage.

Bugs fixed:

  • Disallow use of SESSION or GLOBAL for user variables. (Bug#9286)

  • The use of XOR together with NOT ISNULL() erroneously resulted in some outer joins being converted to inner joins by the optimizer. (Bug#9017)

  • Fixed utf8_spanish2_ci and ucs2_spanish2_ci collations to not consider 鈥r鈥 equal to 鈥rr鈥. If you upgrade to this version from an earlier version, you should rebuild the indexes of affected tables. (Bug#9269)

  • Allow extra HKSCS and cp950 characters (big5 extension characters) to be accepted in big5 columns. (Bug#9357)

  • BLOB(M) and TEXT(M) columns, with M less than 256, were being created as BLOB and TEXT columns rather than TINYBLOB or TINYTEXT columns. (Bug#9303)

  • Fixed a problem with INSERT ... SELECT ... ON DUPLICATE KEY UPDATE where a column named in the insert list and in the ON DUPLICATE KEY UPDATE clause was erroneously declared to be ambiguous. (Bug#8147)

  • In prepared statements, subqueries containing parameters were erroneously treated as const tables during preparation, resulting in a server crash. (Bug#8807)

  • Fixed a problem with OPTIMIZE TABLE for InnoDB tables being written twice to the binary log. (Bug#9149)

  • Provide more informative error messages in clustered setting when a query is issued against a table that has been modified by another mysqld server. (Bug#6762)

  • For MyISAM tables, REPAIR TABLE no longer discard rows that have incorrect checksum. (Bug#9824)

  • Depending on index statistics, GROUP BY col1, col2, ... could return incorrect results if the first table processed for a join had several indexes that cover the grouped columns. (Bug#9213)

  • Fixed incorrect evaluation of ALL/ANY subqueries that contain a HAVING clause. (Bug#9350)

  • Fixed server crash when left expression of IN/ALL/ANY comparison was a subquery. (Bug#8888)

  • Fixed option-parsing code for the embedded server to understand K, M, and G suffixes for the net_buffer_length and max_allowed_packet options. (Bug#9472)

  • Fixed a crash when using TIMESTAMP columns with no minute or second parts in GROUP BY with the new system variable set to 1. (Bug#9401)

  • If a MyISAM table on Windows had INDEX DIRECTORY or DATA DIRECTORY table options, mysqldump dumped the directory pathnames with single-backslash pathname separators. This would cause syntax errors when importing the dump file. mysqldump now changes 鈥\鈥 to 鈥/鈥 in the pathnames on Windows. (Bug#6660)

  • Fixed a server crash caused by use of NOW() is a subquery. (Bug#8824)

  • Fixed problems with static variables to allow building on Fedora Core 3. (Bug#6554)

  • Some user variables were not being handled with 鈥implicit鈥 coercibility. (Bug#9425)

  • Setting the max_error_count system variable to 0 resulted in a setting of 1. (Bug#9072)

  • Fixed a collation coercibility problem that caused a union between binary and non-binary columns to fail. (Bug#6519)

  • Fixed a problem with the tee command in mysql that resulted in mysql crashing. (Bug#8499)

  • On Windows, create shared memory objects with the proper access rights to make them usable when the client and server are running under different accounts. (Bug#8226)

  • Bundled zlib in the source distribution was upgraded to 1.2.2. (Bug#9118)

  • Fixed server crash resulting from queries that combined SELECT DISTINCT, SUM(), and ROLLUP. (Bug#8615)

  • Incorrect results were returned from queries that combined SELECT DISTINCT, GROUP BY , and ROLLUP. (Bug#8616)

  • Fixed a bug that under certain circumstances could allow a privilege escalation via database wildcards in GRANT. (CVE-2004-0957)

  • Too many rows were returned from queries that combined ROLLUP and LIMIT if SQL_CALC_FOUND_ROWS was given. (Bug#8617)

  • mysqldump misinterpreted 鈥_鈥 and 鈥%鈥 characters in the names of tables to be dumped as wildcard characters. (Bug#9123)

  • Made the relay_log_space_limit system variable show up in the output of SHOW VARIABLES. (Bug#7100)

  • Use of GROUP_CONCAT(x) in a subquery, where x was an alias to a column in the outer query, resulted in a server crash. (Bug#8656)

  • The CHARSET(), COLLATION(), and COERCIBILITY() functions sometimes returned NULL. CHARSET() and COLLATION() returned NULL when given any of these arguments that evaluated to NULL: A system function such as DATABASE(); a column value; and a user variable. Now CHARSET() and COLLATION() return the system character set and collation; the column character set and collation; and binary. COERCIBILITY(NULL) now returns 鈥ignorable鈥 coercibility rather than NULL. (Bug#9129)

  • Expressions involving nested CONCAT() calls and character set conversion of string constants could return an incorrect result. (Bug#8785)

  • The MEMORY storage engine did not properly increment an AUTO_INCREMENT column if there was a second composite index that included the column. (Bug#8489)

  • Fixed a bug in the filesort routine such that killing a filesort could cause an assertion failure. (Bug#8799)

  • REPAIR TABLE did not invalidate query results in the query cache that were generated from the table. (Bug#8480)

  • If max_join_size was set, a query containing a subquery that exceeded the examined-rows limit could hang. (Bug#8726)

  • Mixed-case database and table names in the grant tables were ignored for authentication if the lower_case_table_names system variable was set. GRANT will not create such privileges when lower_case_table_names is set, but it is possible to create them by direct manipulation of the grant tables, or that old grant records were present before setting the variable. (Bug#7989)

  • AES_DECRYPT(col_name,key) could fail to return NULL for invalid values in col_name, if col_name was declared as NOT NULL. (Bug#8669)

  • Ordering by unsigned expression (more complex than a column reference) was treating the value as signed, producing incorrectly sorted results. (Bug#7425)

  • HAVING was treating unsigned columns as signed. (Bug#7425)

  • Fixed a problem with boolean full-text searches on utf8 columns where a double quote in the search string caused a server crash. (Bug#8351)

  • MIN(col_name) and MAX(col_name) could fail to produce the correct result if col_name was contained in multiple indexes and the optimizer did not choose the first index that contained the column. (Bug#8893)

  • Table creation for a MyISAM table failed if DATA DIRECTORY or INDEX DIRECTORY options were given that specified the pathname to the database directory where the table files would be created by default. (Bug#8707)

  • Fixed a problem with LIKE pattern-matching for strings with the cp1251_bin binary collation. (Bug#8560)

  • A join on two tables failed when each contained a BIGINT UNSIGNED column that were compared when their values exceeded 263 鈥 1. The match failed and the join returned no rows. (Bug#8562)

  • For a query with both GROUP BY and COUNT(DISTINCT) clauses and a FROM clause with a subquery, NULL was returned for any VARCHAR column selected by the subquery. (Bug#8218)

  • Fixed an optimizer bug that caused incorrectly ordered result from a query that used a FULLTEXT index to retrieve rows and there was another index that was usable for ORDER BY. For such a query, EXPLAIN showed fulltext join type, but regular (not FULLTEXT) index in the Key column. (Bug#6635)

  • For a statement string that contained multiple slow queries, only the last one would be written to the slow query log. (Bug#8475)

  • When the server was started with --skip-name-resolve, specifying hostname values that included netmasks in GRANT statements did not work. (Bug#8471)

  • The --set-character-set option for myisamchk was changed to --set-collation. The value needed for specifying how to sort indexes is a collation name, not a character set name. (Bug#8349)

  • Hostname matching didn't work if a netmask was specified for table-specific privileges. (Bug#3309)

  • Binary data stored in BLOB or BINARY columns would be erroneously dumped if mysqldump was invoked with --hex-blob and --skip-extended-insert arguments. This happened if data contained characters larger then 0x7F (Bug#8830).

  • Corruption of MyISAM table indexes could occur with TRUNCATE TABLE if the table had already been opened. For example, this was possible if the table had been opened implicitly by selecting from a MERGE table that mapped to the MyISAM table. The server now issues an error message for TRUNCATE TABLE under these conditions. (Bug#8306)

  • Fixed handling of table-name matching in mysqlhotcopy to accommodate DBD::mysql 2.9003 and up (which implement identifier quoting). (Bug#8136)

  • In the mysql_real_escape_string() C API function, when a multi-byte character is encountered that is illegal in the current character set, escape only the first byte, not each byte. This avoids creating a valid character from an invalid one. (Bug#8378)

  • Fixed a problem with the cp1250_czech_cs collation that caused empty literal strings not to compare equal to empty character columns. (Bug#8840)

  • Fixed a problem in index cost calculation that caused a USE INDEX or FORCE INDEX hint not to be used properly for a LEFT JOIN across indexed BLOB columns. (Bug#7520)

  • The data type for MAX(datetime_col) was returned as VARCHAR rather than DATETIME if the query included a GROUP BY clause. (Bug#5615)

  • FOUND_ROWS() returned an incorrect value for preceding SELECT statements that used no table or view. (Bug#6089)

  • In string literals with an escape character (鈥\鈥) followed by a multi-byte character that has a second byte of 鈥\鈥, the literal was not interpreted correctly. The next character now is escaped, not just the next byte. (Bug#8303)

  • InnoDB: Work around a problem in AIX 5.1 patched with ML7 security patch: InnoDB would refuse to open its ibdata files, complaining about an operating system error 0.

  • InnoDB: Fixed a memory corruption bug if one created a table with a primary key that contained at least two column prefixes. An example: CREATE TABLE t(a char(100), b tinyblob, PRIMARY KEY(a(5), b(10))).

  • InnoDB: Do not try to space-pad BLOB columns containing ucs2 characters. This avoids an assertion failure that was introduced when fixing Bug#7350. (Bug#8771)

  • InnoDB: Fixed a bug: MySQL 4.1.8 to 4.1.10 could complain that an InnoDB table created with MySQL 3.23.49 or earlier was in the new compact InnoDB table format of 5.0.3 or later, and InnoDB would refuse to use that table. There is nothing wrong with the table, it is mysqld that is in error. Workaround: wait that 4.1.11 is released before doing an upgrade, or dump the table and re-create it with any MySQL version >= 3.23.50 before upgrading.

  • InnoDB: Honor the --tmpdir startup option when creating temporary files. Previously, InnoDB temporary files were always created in the temporary directory of the operating system. On Netware, InnoDB will continue to ignore --tmpdir. (Bug#5822)

  • InnoDB: If MySQL wrote to its binlog, but for some reason trx->update_undo and trx->insert_undo were NULL in InnoDB, then trx->commit_lsn was garbage, and InnoDB could assert in the log flush of trx_commit_complete_for_mysql(). (Bug#9277)

  • InnoDB: If InnoDB cannot allocate memory, keep retrying for 60 seconds before we intentionally crash mysqld; maybe the memory shortage is just temporary.

  • InnoDB: If one used LOCK TABLES, created an InnoDB temp table, and did a multiple-table update where a MyISAM table was the update table and the temp table was a read table, then InnoDB asserted in row0sel.c because n_mysql_tables_in_use was 0. Also, we remove the assertion altogether and just print an error to the .err log if this important consistency check fails. (Bug#8677)

  • mysqldump now avoids writing SET NAMES to the dump output if the server is older than version 4.1 and would not understand that statement. (Bug#7997)

  • Fixed a bug in my_print_defaults that made it ignore the --defaults-extra-file and --defaults-file options.

  • Retrieving from a view defined as a SELECT that mixed UNION ALL and UNION DISTINCT resulted in a different result than retrieving from the original SELECT. (Bug#6565)

  • Worked around a bug in support for NSS support in glibc when static linking is used and LDAP is one of the NSS sources. The workaround is to detect when the bug causes a segmentation fault and issue a diagnostic message with information about the problem. (Bug#3037, Bug#4872)

  • If the mysql prompt was configured to display the default database name, and that database was dropped, mysql did not update the prompt. (Bug#4802)

  • perror was printing a spurious extra line of output ("Error code ###: Unknown error ###" printed directly before the correct line with the error message). (Bug#8517)

  • The CHAR() function was not ignoring NULL arguments, contrary to the documentation. (Bug#6317)

  • Neither SHOW ERRORS nor SHOW WARNINGS were displaying Error-level messages. (Bug#6572)

  • Creating a table using a name containing a character that is illegal in character_set_client resulted in the character being stripped from the name and no error. The character now is considered an error. (Bug#8041)

  • Fixed a problem with the Cyrillic letters I and SHORT I being treated the same by the utf8_general_ci collation. (Bug#8385)

  • The MAX_CONNECTIONS_PER_HOUR resource limit was not being reset hourly and thus imposed an absolute limit on number of connections per account until the server is restarted or the limits flushed. (Bug#8350)

  • With a database was dropped with lower_case_table_names=2, tables in the database also were dropped but not being flushed properly from the table cache. If the database was re-created, the tables also would appear to have been re-created. (Bug#8355)

  • Changed mysql_server_end() C API function to restore more variables to their initial state so that a subsequent call to mysql_server_init() would not cause a client program crash. (Bug#7344)

  • Fixed a problem with accented letters improperly being treated as distinct with the utf_general_ci collation. (Bug#7878)

  • ENUM and SET columns in privilege tables incorrectly had a case-sensitive collation, resulting in failure of assignments of values that did not have the same lettercase as given in the column definitions. The collation was changed to be case insensitive. (Bug#7617)

  • An expression that tested a case-insensitive character column against string constants that differed in lettercase could fail because the constants were treated as having a binary collation. (For example, WHERE city='London' AND city='london' could fail.) (Bug#7098, Bug#8690)

  • The output of the STATUS (\s) command in mysql had the values for the server and client character sets reversed. (Bug#7571)

  • If the slave was running with --replicate-*-table options which excluded one temporary table and included another, and the two tables were used in a single DROP TEMPORARY TABLE IF EXISTS statement, as the ones the master automatically writes to its binary log upon client's disconnection when client has not explicitly dropped these, the slave could forget to delete the included replicated temporary table. Only the slave needs to be upgraded. (Bug#8055)

  • Treat user variables as having IMPLICIT derivation (coercibility) to avoid 鈥Illegal mix of collations鈥 errors when replicating user variables. (Bug#6676)

  • When setting integer system variables to a negative value with SET VARIABLES, the value was treated as a positive value modulo 232. (Bug#6958)

  • Fixed a bug in bundled readline library that caused segmentation fault in mysql when user entered Shift+Enter. (Bug#5672)

  • Fix conversion of strings -> double to get higher accuracy for floating point values that are integers, like: 123.45E+02 (Bug#7840).

  • Fixed a bug in MATCH ... AGAINST in natural language mode that could cause a server crash if the FULLTEXT index was not used in a join (EXPLAIN did not show fulltext join mode) and the search query matched no rows in the table (Bug#8522).

  • Platform and architecture information in version information produced for --version option on Windows was always Win95/Win98 (i32). More accurately determine platform as Win32 or Win64 for 32-bit or 64-bit Windows, and architecture as ia32 for x86, ia64 for Itanium, and axp for Alpha. (Bug#4445)

  • Fixed a rare race condition which could lead to FLUSH TABLES WITH READ LOCK hanging. (Bug#8682)

  • Fixed a bug in replication that caused the master to stamp generated statements (such as SET commands) with an error_code intended only for another statement. This could happen, for example, when a statements generates a duplicate key error on the master but must be replicated. (Bug#8412)

  • If multiple semicolon-separated statements were received in a single packet, they were written to the binary log as a single event rather than as separate per-statement events. For a server serving as a replication master, this caused replication to fail when the event was sent to slave servers. (Bug#8436)

B.1.14.聽Changes in release 4.1.10 (12 February 2005)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Note: The security improvements related to creation of table files and to user-defined functions were made after MySQL 4.1.10 was released and are present in MySQL 4.1.10a. We would like to thank Stefano Di Paola for making us aware of these.

Functionality added or changed:

  • Added back faster subquery execution from 4.1.8. This adds also back a bug from 4.1.8 in comparing NULL to the value of a subquery. See Section聽A.1.8.4, 鈥淥pen Issues in MySQL鈥.

  • Security improvement: The server creates .frm, .MYD, .MYI, .MRG, .ISD, and .ISM table files only if a file with the same name does not already exist. Thanks to Stefano Di Paola for finding and informing us about this issue. (CVE-2005-0711)

  • Security improvement: User-defined functions should have at least one symbol defined in addition to the xxx symbol that corresponds to the main xxx() function. These auxiliary symbols correspond to the xxx_init(), xxx_deinit(), xxx_reset(), xxx_clear(), and xxx_add() functions. mysqld by default no longer loads UDFs unless they have at least one auxiliary symbol defined in addition to the main symbol. The --allow-suspicious-udfs option controls whether UDFs that have only an xxx symbol can be loaded. By default, the option is off. mysqld also checks UDF filenames when it reads them from the mysql.func table and rejects those that contain directory pathname separator characters. (It already checked names as given in CREATE FUNCTION statements.) See Section聽19.2.4.1, 鈥淯DF Calling Sequences for Simple Functions鈥, Section聽19.2.4.2, 鈥淯DF Calling Sequences for Aggregate Functions鈥, and Section聽19.2.4.6, 鈥淯ser-Defined Function Security Precautions鈥. Thanks to Stefano Di Paola for finding and informing us about this issue. (CVE-2005-0709, CVE-2005-0710)

  • Setting the connection collation to a value different from the server collation followed by a CREATE TABLE statement that included a quoted default value resulted in a server crash. (Bug#8235)

  • Thread stack size was increased from 192KB to 256KB on Linux/IA-64 (too small stack size was causing server crashes on some queries). (Bug#8391)

  • From the Windows distribution, predefined accounts without passwords for remote users ("root@%", "@%") were removed (other distributions never had them).

  • Added mysql_library_init() and mysql_library_end() as synonyms for the mysql_server_init() and mysql_server_end() C API functions. mysql_library_init() and mysql_library_end() are #define symbols, but the names more clearly indicate that they should be called when beginning and ending use of a MySQL C API library no matter whether the application uses libmysqlclient or libmysqld. (Bug#6149)

  • The server now issues a warning when lower_case_table_names=2 and the data directory is on a case-sensitive filesystem, just as when lower_case_table_names=0 on a case-insensitive filesystem. (Bug#7887)

  • The server now issues a warning to the error log when it encounters older tables that contain character columns that might be interpreted by newer servers to have a different column length. (Bug#6913) See Section聽2.11.1, 鈥淯pgrading from MySQL 4.0 to 4.1鈥, for a discussion of this problem and what to do about it.

  • InnoDB: When MySQL/InnoDB is compiled on Mac OS X 10.2 or earlier, detect the operating system version at run time and use the fcntl() file flush method on Mac OS X versions 10.3 and later. In Mac OS X, fsync() does not flush the write cache in the disk drive, but the special fcntl() does; however, the flush request is ignored by some external devices. Failure to flush the buffers may cause severe database corruption at power outages.

  • InnoDB: A shared record lock (LOCK_REC_NOT_GAP) is now taken for a matching record in the foreign key check because inserts can be allowed into gaps.

  • InnoDB: Relaxed locking in INSERT鈥ELECT, single table UPDATE鈥ELECT and single table DELETE鈥ELECT clauses when innodb_locks_unsafe_for_binlog is used and isolation level of the transaction is not serializable. InnoDB uses consistent read in these cases for a selected table.

Bugs fixed:

  • FOUND_ROWS() returned an incorrect value after a SELECT SQL_CALC_FOUND_ROWS DISTINCT statement that selected constants and included GROUP BY and LIMIT clauses. (Bug#7945)

  • Fixed a bug in cardinality estimations for HASH indexes of TEMPORARY tables created using MEMORY storage engine. As a result queries that were using this index (as shown by EXPLAIN) could have returned incorrect results. (Bug#8371)

  • Corrected a problem with references to DUAL where statements such as SELECT 1 AS a FROM DUAL would succeed but statements such as SELECT 1 AS a FROM DUAL LIMIT 1 would fail. (Bug#8023)

  • Fixed a server crash caused by DELETE FROM tbl_name ... WHERE ... ORDER BY tbl_name.col_name when the ORDER BY column was qualified with the table name. (Bug#8392)

  • mysqld had problems finding its language files if the basedir value was specified as a very long pathname. (Bug#8015)

  • Updates were being written to the binary log when there were binlog-do-db or binlog-ignore-db options even when there was no current database, contrary to Section聽5.11.4, 鈥淭he Binary Log鈥. (Bug#6749)

  • Fixed conversion of floating-point values to character fields when the absolute value of the float was less than 1, and also fixed calculation of length for negative values. (Bug#7774)

  • Column headers in query results retrieved from the query cache could be corrupted when a non-4.1 client was served a result originally generated for a 4.1 client. The query cache was not keeping track of which client/server protocol was being used. (Bug#6511)

  • Fixed LOAD INDEX statement to actually load index in memory. (Bug#8452)

  • If multiple prepared statements were executed without retrieving their results, executing one of them again would cause the client program to crash. (Bug#8330)

  • Non-numeric values inserted into a YEAR column were being stored as 2000 rather than as 0000. (Bug#6067)

  • Fixed a failure of multiple-table updates to replicate properly on slave servers when --replicate-*-table options had been specified. (Bug#7011)

  • mysql_stmt_close() C API function was not clearing an error indicator when a previous prepare call failed, causing subsequent invocations of error-retrieving calls to indicate spurious error values. (Bug#7990)

  • Fixed failure of CREATE TABLE ... LIKE Windows when the source or destination table was located in a symlinked database directory. (Bug#6607)

  • With lower_case_table_names set to 1, mysqldump on Windows could write the same table name in different lettercase for different SQL statements. Fixed so that consistent lettercase is used. (Bug#5185) HAVING that referred to RAND() or a user-defined function in the SELECT part through an alias could cause a crash or wrong value. (Bug#8216)

  • If one used CONVERT_TZ() function in SELECT, which in its turn was used in CREATE TABLE statements, then system time zone tables were added to list of tables joined in SELECT and thus erroneous result was produced. (Bug#7899)

  • Fixed a bug in CONV() function returning unsigned BIGINT number (third argument is positive, and return value does not fit in 32 bits). (Bug#7751)

  • Fixed a failure of the IN() operator to return correct result if all values in the list were constants and some of them were using substring functions, for example, LEFT(), RIGHT(), or MID().

  • Fixed problem with SHOW INDEX reporting Sub_part values in bytes rather than characters for columns with a multi-byte character set. (Bug#7943)

  • Fixed a crash in CONVERT_TZ() function when its second or third argument was from a const table (see Section聽7.2.1, 鈥淥ptimizing Queries with EXPLAIN). (Bug#7705)

  • Correct a problem with mysql_config, which was failing to produce proper zlib option for linking under some circumstances. (Bug#6273)

  • Fixed a problem with calculation of number of columns in row comparison against a subquery. (Bug#8020)

  • Fixed erroneous output resulting from SELECT DISTINCT combined with a subquery and GROUP BY. (Bug#7946)

  • Fixed server crash in comparing a nested row expression (for example row(1,(2,3))) with a subquery. (Bug#8022)

  • Fixed server crash resulting from certain correlated subqueries with forward references (referring to an alias defined later in the outer query). (Bug#8025)

  • Fixed server crash resulting from re-execution of prepared statements containing subqueries. (Bug#8125)

  • Removed a dependence of boolean full-text search on --default-character-set option. (Bug#8159)

  • Fixed a crash in a boolean full-text search in certain joins. (Bug#8234)

  • Fixed erroneous comparison where strings that began with CHAR(31) were considered equal to the empty string. (Bug#8134)

  • Add description of debug command to mysqladmin help output. (Bug#8207)

  • perror.exe was always returning 鈥Unknown error鈥 on Windows. See Section聽8.26, 鈥perror 鈥 Explain Error Codes鈥. (Bug#7390)

  • Modify SET statements produced by mysqldump to write quoted strings using single quotes rather than double quotes. This avoids problems if the dump file is reloaded while the ANSI_QUOTES SQL mode is in effect. (Bug#8148)

  • Fixed a bug where ALTER TABLE improperly would accept an index on a TIMESTAMP column that CREATE TABLE would reject. (Bug#7884)

  • Fixed a bug in multiple-table UPDATE statements that could cause spurious Table '#sql_....' is full errors if the number of rows to update is big enough. (Bug#7788)

  • Fixed a problem where SHOW INDEX on a MERGE table could crash a debugging version of the server. (Bug#7377)

  • Fixed a problem where adding an ORDER BY clause for an indexed column would cause a SELECT to return an empty result. (Bug#7331)

  • Fixed a problem where ALTER TABLE on a TEMPORARY table with a mixed-lettercase name could cause the table to disappear when lower_case_table_names was set to 2. (Bug#7261)

  • Fixed a problem with key cache statistics being reported incorrectly by the server after receipt of a SIGHUP signal. (Bug#4285)

  • Fixed a problem that caused mysql_stmt_prepare() to be very slow when used in client programs on Windows. (Bug#5787)

  • For indexes, SHOW CREATE TABLE now displays the index type even if it is the default, for storage engines that support multiple index types. (Bug#7235)

  • Fixed a bug where the use of GROUP_CONCAT() with HAVING caused a server crash. (Bug#7769)

  • Fixed a bug where comparing the result of a subquery to a non-existent column caused a server crash on Windows. (Bug#7885)

  • Fixed a bug which caused TIMEDIFF() function to return wrong results if one of its arguments had non-zero microsecond part (Bug#7586).

  • Fixed a bug which caused TIMESTAMP columns with display width specified to be not identical to DATETIME columns when server was run in MAXDB mode (Bug#7418).

  • Fixed a bug in UNION statements that resulted in the wrong number of the examined rows reported in the slow query log.

  • Fixed a bug in a combination of -not and trunc* operators of full-text search. Using more than one truncated negative search term, was causing empty result set.

  • InnoDB: Fixed a bug introduced in 4.1.9 to the Windows version if you used innodb_file_per_table. mysqld would stop and complain about Windows error number 87 in a file operation. (See the Bugs database or the 4.1.9 change notes about a workaround for that bug in 4.1.9). (Bug#8021)

  • InnoDB: Corrected the handling of trailing spaces in the ucs2 character set. (Bug#7350)

  • InnoDB: Use native tmpfile() function on Netware. All InnoDB temporary files are created under sys:\tmp. Previously, InnoDB temporary files were never deleted on Netware.

  • InnoDB: Fix a race condition that could cause the assertion space->n_pending_flushes == 0 to fail in fil0fil.c, in fil_space_free(), in DROP TABLE or in ALTER TABLE.

  • InnoDB: ALTER TABLE ... ADD CONSTRAINT PRIMARY KEY ... complained about bad foreign key definition. (Bug#7831)

  • InnoDB: Fix a theoretical hang over the adaptive hash latch in InnoDB if one runs INSERT ... SELECT ... (binlog not enabled), or a multiple-table UPDATE or DELETE, and only the read tables are InnoDB type, the rest are MyISAM. (Bug#7879)

  • Fixed a bug in max_heap_table_size handling, that resulted in Table is full error when the table was still smaller than the limit. (Bug#7791).

  • Fixed a symlink vulnerability in the mysqlaccess script. Reported by Javier Fernandez-Sanguino Pena and Debian Security Audit Team. (CVE-2005-0004)

  • mysqlbinlog forgot to add backquotes around the collation of user variables (causing later parsing problems as BINARY is a reserved word). (Bug#7793)

  • Ensured that mysqldump --single-transaction sets its transaction isolation level to REPEATABLE READ before proceeding (otherwise if the MySQL server was configured to run with a default isolation level lower than REPEATABLE READ it could give an inconsistent dump). (Bug#7850)

  • Changed mysql client so that including \p as part of a prompt command uses the name of the shared memory connection when the connection is using shared memory. (Bug#7922)

  • Fixed a problem in the server where executing a multi-statement query more than once with the query cache active could yield incorrect result sets. (Bug#7966)

  • Fixed that a 4.1.10 slave can connect to a master < 3.23.50 without hanging (the reason for the hang is a bug in these quite old masters -- SELECT @@unknown_var hangs them -- which was fixed in MySQL 3.23.50). (Bug#7965)

  • Fixed a bug where MySQL was allowing concurrent updates (inserts, deletes) to a table if binary logging is enabled. Changed to ensure that all updates are executed in a serialized fashion, because they are executed serialized when binlog is replayed. (Bug#7879)

B.1.15.聽Changes in release 4.1.9 (11 January 2005)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • mysqld_safe no longer tests for the presence of the data directory when using a relatively located server binary. It just assumes the directory is there, and fails to start up if it is not. This allows the data directory location to be specified on the command line, and avoids running a server binary that was not intended. (Bug#7249)

  • The naming scheme of the Windows installation packages has changed slightly:

    • The platform suffix was changed from -win to -win32

    • The product descriptions -noinstall and -essential have been moved in front of the version number

    Examples: mysql-essential-4.1.9-win32.msi, mysql-noinstall-4.1.9-win32.zip See Section聽2.3, 鈥淚nstalling MySQL on Windows鈥.

  • The Mac OS X 10.3 installation disk images now include a MySQL Preference Pane for the Mac OS X Control Panel that enables the user to start and stop the MySQL server via the GUI and activate and deactivate the automatic MySQL server startup on bootup.

  • The MySQL-shared-compat Linux RPM now includes the 3.23 as well as the 4.0 libysqlclient.so shared libraries. (Bug#6342)

  • Seconds_Behind_Master is NULL (which means 鈥unknown鈥) if the slave SQL thread is not running, or if the slave I/O thread is not running or not connected to master. It is zero if the SQL thread has caught up with the I/O thread. It no longer grows indefinitely if the master is idle.

  • InnoDB: Do not acquire an internal InnoDB table lock in LOCK TABLES if AUTOCOMMIT=1. This helps in porting old MyISAM applications to InnoDB. InnoDB table locks in that case caused deadlocks very easily.

  • InnoDB: Print a more descriptive error and refuse to start InnoDB if the size of ibdata files is smaller than what is stored in the tablespace header; innodb_force_recovery overrides this.

  • The MySQL server aborts immediately instead of simply issuing a warning if it is started with the --log-bin option but cannot initialize the binary log at startup (that is, an error occurs when writing to the binary log file or binary log index file).

  • The binary log file and binary log index file now behave like MyISAM when there is a "disk full" or "quota exceeded" error. See Section聽A.1.4.3, 鈥淗ow MySQL Handles a Full Disk鈥.

Bugs fixed:

  • Fixed problem where running mysql_fix_privilege_tables could result in grant table columns with too-short lengths if the server character set had been set to a multi-byte character set first. (Bug#7539)

  • InnoDB: Fixed the critical bug if you enabled innodb_file_per_table in my.cnf. If you shut down mysqld, records could disappear from the secondary indexes of a table. Unfortunately, on Windows a new Bug#8021 was introduced. Windows users of innodb_file_per_table should put a line innodb_flush_method=unbuffered to their my.cnf or my.ini to work around 8021. (Bug#7496)

  • InnoDB: Fixed a bug: 32-bit mysqld binaries built on HP-UX-11 did not work with InnoDB files greater than 2 GB in size. (Bug#6189)

  • InnoDB: Return a sensible error code from DISCARD TABLESPACE if it fails because the table is referenced by a FOREIGN KEY.

  • InnoDB: Fixed a bug: InnoDB failed to drop a table in the background drop queue if the table was referenced by a FOREIGN KEY constraint.

  • InnoDB: Fixed a bug: if we dropped a table where an INSERT was waiting for a lock to check a FOREIGN KEY constraint, then an assertion would fail in lock_reset_all_on_table().

  • InnoDB: Fix a little bug: we looked at the physical size of a stored SQL NULL value from a wrong field in the index; this has probably caused no bugs visible to the user. It caused only some extra space to be used in some rare cases.

  • InnoDB: Use the fcntl(F_FULLFSYNC) flush method on Mac OS X versions 10.3 and up instead of fsync() that could cause corruption at power outages.

  • mysqladmin password now checks whether the server has --old-passwords turned on or predates 4.1 and uses the old-format password if so. (Bug#7451)

  • Added a --default-character-set option to mysqladmin to avoid problems when the default character set is not latin1. (Bug#7524)

  • Fix a problem with truncation of FLOAT values. (Bug#7361)

  • Fixed a bug in PROCEDURE ANALYSE(), which did not quote some ENUM values properly. (Bug#2813)

  • Fixed a bug that caused incorrect results for complex datetime expressions containing casts of datetime values to TIME or DATE values. (Bug#6914)

  • Include compression library flags in the output from mysql_config --lib_r. (Bug#7021)

  • Corrected a problem with mysql_config not producing all relevant flags from CFLAGS. (Bug#6964)

  • Corrected a problem with mysqld_safe not properly capturing output from ps. (Bug#5878)

  • Fixed a bug that caused a linking failure when linking both the MySQL client library and IMAP library. (Bug#7428)

  • Fixed table corruption bug when using INSERT DELAYED with prepared statements.

  • Fixed a bug that caused microseconds to be gobbled from the string result of the STR_TO_DATE function, if there is some other specifier in the format string following %f. (Bug#7458)

  • Made the MySQL server accept executing SHOW CREATE DATABASE even if the connection has an open transaction or locked tables. Refusing it made mysqldump --single-transaction sometimes fail to print a complete CREATE DATABASE statement for some dumped databases. (Bug#7358)

  • Fixed that, when encountering a 鈥disk full鈥 or 鈥quota exceeded鈥 write error, MyISAM sometimes didn't sleep and retry the write, thus resulting in a corrupted table. (Bug#7714)

  • Fixed that --expire-log-days was not honored if using only transactions. (Bug#7236)

  • Fixed that a slave could crash after replicating many ANALYZE TABLE, OPTIMIZE TABLE, or REPAIR TABLE statements from the master. (Bug#6461, Bug#7658)

B.1.16.聽Changes in release 4.1.8 (14 December 2004)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Note: Due to a libtool-related bug in the source distribution, the creation of shared libmysqlclient libraries was not possible (the resulting files were missing the .so file name extension). The file ltmain.sh was updated to fix this problem and the resulting source distribution was released as mysql-4.1.8a.tar.gz. This modification did not affect the binary packages. (Bug#7401)

Functionality added or changed:

  • Automatic character set conversion formerly was done for operations that mix a column and a string such as assigning a string to a column, when this was possible without loss of information. Automatic conversion for operations that mix columns and strings has been expanded to cover many functions (such as CONCAT()) and assignment operators. This reduces the frequency of Illegal mix of collations errors.

  • For ALTER DATABASE, the database name now can be omitted to apply the change to the default database.

  • Added WITH CONSISTENT SNAPSHOT clause to START TRANSACTION to begin a transaction with a consistent read.

  • Added --order-by-primary to mysqldump, to sort each table's data in a dump file. This may be useful when dumping a MyISAM table which will be loaded into an InnoDB table. Dumping a MyISAM table with this option is considerably slower than without.

  • InnoDB: Do not periodically write SHOW INNODB STATUS information to a temporary file unless the configuration option innodb_status_file=1 is set.

  • InnoDB: Commit after every 10,000 copied rows when executing ALTER TABLE. This makes it much faster to recover from an aborted ALTER TABLE or OPTIMIZE TABLE.

  • FULLTEXT index block size is changed to be 1024 instead of 2048.

  • Added --disable-log-bin option to mysqlbinlog. Using this option you can disable binary logging for the statements produced by mysqlbinlog. That is, mysqlbinlog --disable-log-bin <file_name> | mysql won't write any statements to the MySQL server binary log.

  • The --master-data option for mysqldump now takes an optional argument of 1 or 2 to produce a non-commented or commented CHANGE MASTER TO statement. The default is 1 for backward compatibility.

  • mysqldump --single-transaction --master-data now is able to take an online (non-blocking) dump of InnoDB and report the corresponding binary log coordinates. This makes a backup suitable for point-in-time recovery, roll-forward or replication slave creation. See Section聽8.12, 鈥mysqldump 鈥 A Database Backup Program鈥.

  • Added --lock-all-tables to mysqldump to lock all tables by acquiring a global read lock.

  • Added --hex-blob option to mysqldump for dumping binary string columns using hexadecimal notation.

  • Added mysql_hex_string() C API function that hex-encodes a string.

  • In the normal log MySQL now prints the log position for Binlog Dump requests.

  • Added [mysql_cluster] section to my.cnf file for configuration settings specific to MySQL Cluster. ndb-connectstring variable moved here.

  • A connection doing a rollback now displays "Rolling back" in the State column of SHOW PROCESSLIST.

  • mysqlbinlog now prints an informative commented line (thread id, timestamp, server id, and so forth) before each LOAD DATA INFILE, like it does for other queries; unless --short-form is used.

  • The statements CREATE TABLE, TRUNCATE TABLE, DROP DATABASE, and CREATE DATABASE cause an implicit commit.

Bugs fixed:

  • A multiple-table DELETE could cause MySQL to crash when using InnoDB tables. (Bug#5837, Bug#6378)

  • Some data definition statements (CREATE TABLE where the table was not a temporary table, TRUNCATE TABLE, DROP DATABASE, and CREATE DATABASE) were not being written to the binary log after a ROLLBACK. This also caused problems with replication. (Bug#6883)

  • Fixed incorrect referencing to column by name from subquery to outer query in case of using temporary table by outer query and placing subquery in the WHERE clause. (Bug#7079)

  • Fixed a bug in authentication code that allowed a malicious user to crash the server with specially crafted packets (using a modified client library). (Bug#7187)

  • Fixed a crashing bug in a string function LEFT, when this function is part of the expression which is used as GROUP BY field. (Bug#7101)

  • Fixed bug which caused MySQL to require privileges on system time zone description tables for implicit access to them (that is, if one set time_zone variable or used CONVERT_TZ() function) in case when some table-level or column-level privileges existed. (Bug#6765)

  • mysql_stmt_data_seek(stmt,0) now rewinds a counter and enables buffered rows to be re-fetched on the client side. (Bug#6996)

  • Fixed an insufficient privilege check in SHOW CREATE TABLE command. (Bug#7043)

  • Fixed a rare memory corruption (that resulted in a crash) in MATCH ... AGAINST on columns that use multi-byte character sets. (Bug#6269)

  • Fixed NULL processing in ALL/SOME subqueries. (Bug#6247)

  • Fixed execution of complex queries with subqueries. (Bug#6406, Bug#6841)

  • Fixed initialization of some internal structures for first execution. (Bug#6517)

  • Backported a fix for the full-text interface from MySQL 5.0. (Bug#6523)

  • Fixed NULL value handling in case of empty results in subqueries. (Bug#6806)

  • Prevent adding CREATE TABLE .. SELECT query to the binary log when the insertion of new records partially failed. (Bug#6682)

  • INSERT ... SELECT no longer reports spurious "column truncated" warnings (Bug#6284)

  • Fixed a bug that could cause "Record has changed since last read in table" error message in some queries on HEAP tables that contain only one row. (Bug#6748)

  • mysqld_safe was in many cases ignoring any --no-defaults, --defaults-file, or --defaults-extra-file arguments. Those arguments are now honored, and this may change what options are passed to mysqld in some installations.

  • The server was interpreting CHAR BINARY and VARCHAR BINARY columns from 4.0 tables as having the BINARY and VARBINARY data types. Now they are interpreted as CHAR and VARCHAR columns that have the binary collation of the column's character set. (This is the same way that CHAR BINARY and VARCHAR BINARY are handled for new tables created in 4.1.)

  • Fixed spurious "duplicate key" error from REPLACE or INSERT ... ON DUPLICATE KEY UPDATE statements performing multiple-row insert in the table that had unique and full-text indexes. (Bug#6784)

  • Fixed a bug in execution of subqueries in SET and DO statements which caused wrong results to be returned from subsequent queries. (Bug#6462)

  • Fixed a bug that allowed server to accept datetime values with wrong year part. The server now also performs same checks for datetime values passed through MYSQL_TIME structures as for datetime values passed as strings. (Bug#6266)

  • Fixed a bug with INSERT for a table with FULLTEXT indexes. Under rare circumstances, this could result in a corrupted table if words of different lengths may be considered equal. This is possible in some collations, for example, in utf8_general_ci or latin1_german2_ci. (Bug#6265)

  • InnoDB: Do not intentionally crash mysqld if the buffer pool is exhausted by the lock table; return error 1206 instead. Do not intentionally crash mysqld if we cannot allocate the memory for the InnoDB buffer pool. (Bug#6817) (Bug#6827)

  • InnoDB: Let InnoDB's FOREIGN KEY parser to remove the latin1 character 0xA0 from the end of an unquoted identifier. The EMS MySQL Manager in ALTER TABLE adds that character after a table name, which caused error 121 when we tried to add a new constraint.

  • InnoDB: Refuse to open new-style tables created with MySQL 5.0.3 or later. (Bug#7089)

  • InnoDB: Do not call rewind() when displaying SHOW INNODB STATUS information on stderr.

  • InnoDB: Made the foreign key parser better aware of quotes. (Bug#6340)

  • InnoDB: If one used INSERT IGNORE to insert several rows at a time, and the first inserts were ignored because of a duplicate key collision, then InnoDB in a replication slave assigned AUTO_INCREMENT values 1 bigger than in the master. This broke the MySQL replication. (Bug#6287)

  • InnoDB: Fixed a bug: InnoDB ignored in innodb_data_file_path the max specification in :autoextend:max:2000M. This bug was introduced in 4.1.1.

  • InnoDB: Fixed a bug: innodb_locks_unsafe_for_binlog still uses next-key locking (Bug#6747). InnoDB used next-key locking when record matched completely to search tuple. This unnecessary next-key locking is now removed when innodb_locks_unsafe_for_binlog option is used.

  • InnoDB: Fix two hangs: FOREIGN KEY constraints treated table and database names as case-insensitive. RENAME TABLE t TO T would hang in an endless loop if t had a foreign key constraint defined on it. Fix also a hang over the dictionary mutex that would occur if one tried in ALTER TABLE or RENAME TABLE to create a foreign key constraint name that collided with another existing name. (Bug#3478)

  • If STMT_ATTR_UPDATE_MAX_LENGTH is set for a prepared statement, mysql_stmt_store_result() updates field->max_length for numeric columns as well. (Bug#6096)

  • Prepared statements now handle ZEROFILL when converting integer to string.

  • Fixed crash when a call to mysql_stmt_store_result() occurred without a preceding call to mysql_stmt_bind_result().

  • Fixed crash in prepared statements when using SELECT * FROM t1 NATURAL JOIN t2....

  • Fixed crash in prepared statements when using SELECT ... PROCEDURE.

  • Fixed crash in prepared statements when using subqueries.

  • GROUP_CONCAT(...ORDER BY) when used with prepared statements gave wrong sorting order.

  • CREATE TABLE created_table didn't signal when table was created. This could cause a DROP TABLE created_table in another thread to wait "forever".

  • Server warnings now are reset when you execute a prepared statement.

  • Improved performance of identifier comparisons (if many tables or columns are specified).

  • OPTIMIZE TABLE, REPAIR TABLE, and ANALYZE TABLE are now replicated without any error code in the binary log. (Bug#5551)

  • LOAD DATA INFILE now works with option replicate-rewrite-db. (Bug#6353)

  • Fixed a bug which caused a crash when only the slave I/O thread was stopped and started. (Bug#6148)

  • Changed semantics of CREATE/ALTER/DROP DATABASE statements so that replication of CREATE DATABASE is possible when using --binlog-do-db and --binlog-ignore-db. (Bug#6391)

  • If a connection had an open transaction but had done no updates to transactional tables (for example if had just done a SELECT FOR UPDATE then executed a non-transactional update, that update automatically committed the transaction (thus releasing InnoDB's row-level locks etc). (Bug#5714)

  • If a connection was interrupted by a network error and did a rollback, the network error code got stored into the BEGIN and ROLLBACK binary log events; that caused superfluous slave stops. (Bug#6522)

  • A sequence of BEGIN (or SET AUTOCOMMIT=0), FLUSH TABLES WITH READ LOCK, transactional update, COMMIT, FLUSH TABLES WITH READ LOCK could hang the connection forever and possibly the MySQL server itself. This happened for example when running the innobackup script several times. (Bug#6732)

  • mysqlbinlog did not print SET PSEUDO_THREAD_ID statements in front of LOAD DATA INFILE statements inserting into temporary tables, thus causing potential problems when rolling forward these statements after restoring a backup. (Bug#6671)

B.1.17.聽Changes in release 4.1.7 (23 October 2004: Production)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • MOD() no longer rounds arguments with a fractional part to integers. Now it returns exact remainder after division. (Bug#6138)

  • InnoDB: Added a startup option and settable system variable innodb_table_locks for making LOCK TABLE acquire also InnoDB locks. The default value is 1, which means that LOCK TABLES causes also InnoDB internally to take a table lock. In applications using AUTOCOMMIT=1 and LOCK TABLES, InnoDB's internal table locks that were added in 4.0.20 and 4.1.2 can cause deadlocks. You can set innodb_table_locks=0 in my.cnf to remove that problem. (Bug#3299, Bug#5998)

  • See Section聽14.2.17, 鈥淩estrictions on InnoDB Tables鈥. (Bug#3299, Bug#5998) InnoDB: SHOW TABLE STATUS now shows the creation time of the table for InnoDB. Note that this timestamp might not be the correct time because, for example, ALTER TABLE changes this timestamp.

  • InnoDB: If innodb_thread_concurrency would be exceeded, let a thread sleep 10 ms before entering the FIFO queue; previously, the value was 50 ms.

Bugs fixed:

  • Fixed a bug with FOUND_ROWS() used together with LIMIT clause in prepared statements. (Bug#6088)

  • Fixed a bug with NATURAL JOIN in prepared statements. (Bug#6046).

  • Fixed a bug in join of tables from different databases having columns with identical names (prepared statements). (Bug#6050)

  • Now implicit access to system time zone description tables (which happens when you set the time_zone variable or use CONVERT_TZ() function) does not require any privileges. (Bug#6116)

  • Fixed a bug which caused the server to crash when the deprecated libmysqlclient function mysql_create_db() was called. (Bug#6081)

  • Fixed REVOKE ALL PRIVILEGES, GRANT OPTION FROM user so that all privileges are revoked correctly. (Bug#5831). This corrects a case that the fix in 4.1.6 could miss.

  • Fixed crash when selecting from a HEAP table with key_column IS NOT NULL. This could also cause a crash if not all index parts where used. (Bug#6082)

  • Fixed a bug that could cause MyISAM index corruption when key values start with character codes below BLANK. This was caused by the new key sort order in 4.1. (Bug#6151)

  • InnoDB: Fixed a bug in LOAD DATA INFILE鈥EPLACE printing duplicate key error when executing the same load query several times. (Bug#5835)

  • Fixed a bug in the prepared statements protocol when wrong metadata was sent for SELECT statements not returning a result set (such as SELECT ... INTO OUTFILE). (Bug#6059)

  • Fixed bug which allowed one to circumvent missing UPDATE privilege if one had INSERT and SELECT privileges for table with primary key. (Bug#6173)

  • Fixed a bug in libmysqlclient with wrong conversion of negative time values to strings. (Bug#6049).

  • Fixed a bug in libmysqlclient with wrong conversion of zero date values (0000-00-00) to strings. (Bug#6058)

  • Fixed a bug that caused the server to crash on attempt to prepare a statement with RAND(?). (Bug#5985)

  • Fixed a bug with handling of DATE, TIME, and DATETIME columns in the binary protocol. The problem is compiler-specific and could have been observed on HP-UX, AIX, Solaris9, when compiling with native compiler. (Bug#6025)

  • Fixed a bug with handling of TINYINT columns in the binary protocol. The problem is specific to platforms where the C compiler has the char data type unsigned by default. (Bug#6024)

  • InnoDB: Fixed problem introduced in MySQL 4.0.21 where a connection starting a transaction, doing updates, then FLUSH TABLES WITH READ LOCK, then COMMIT, would cause replication slaves to stop (complaining about error 1223). Bug surfaced when using the InnoDB innobackup script. (Bug#5949)

  • InnoDB: Release the dictionary latch during a long cascaded FOREIGN KEY operation, so that we do not starve other users doing CREATE TABLE or other DDL operation. This caused a notorious 'Long semaphore wait' message to be printed to the .err log. (Bug#5961)

B.1.18.聽Changes in release 4.1.6 (10 October 2004)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • Added option --sigint-ignore to the mysql command line client to make it ignore SIGINT signals (typically the result of the user pressing Control-C).

  • InnoDB: Added the startup option and settable global variable innodb_max_purge_lag for delaying INSERT, UPDATE and DELETE operations when the purge operations are lagging. The default value of this parameter is zero, meaning that there are no delays. See Section聽14.2.13, 鈥淚mplementation of Multi-Versioning鈥.

  • InnoDB: The innodb_autoextend_increment startup option that was introduced in release 4.1.5 was made a settable global variable. (Bug#5736)

  • InnoDB: If DROP TABLE is invoked on an InnoDB table for which the .ibd file is missing, print to error log that the table was removed from the InnoDB data dictionary, and allow MySQL to delete the .frm file. Maybe DROP TABLE should issue a warning in this case.

  • TIMESTAMP columns now can store NULL values. To create such a column, you must explicitly specify the NULL attribute in the column specification. (Unlike all other data types, TIMESTAMP columns are NOT NULL by default.)

  • Now if ALTER TABLE converts one AUTO_INCREMENT column to another AUTO_INCREMENT column it preserves zero values (this includes the case that we don't change such column at all).

  • Now if ALTER TABLE converts some column to TIMESTAMP NOT NULL column it converts NULL values to current timestamp value (One can still get old behavior by setting system TIMESTAMP variable to zero).

  • On Windows, the MySQL configuration files included in the package now use .ini instead of .cnf as the file name suffix.

Bugs fixed:

  • Fixed a bug that caused the server to crash on attempt to execute a prepared statement with a subquery inside a boolean expression. (Bug#5987)

  • Fixed a bug that caused the server to sometimes choose non-optimal execution plan for a prepared statement executed with changed placeholder values. (Bug#6042)

  • InnoDB: Make the check for excessive semaphore waits tolerate glitches in the system clock (do not crash the server if the system time is adjusted while InnoDB is under load.). (Bug#5898)

  • InnoDB: Fixed a bug in the InnoDB FOREIGN KEY parser that prevented ALTER TABLE of tables containing 鈥#鈥 in their names. (Bug#5856)

  • InnoDB: Fixed a bug that prevented ALTER TABLE t DISCARD TABLESPACE from working. (Bug#5851)

  • InnoDB: SHOW CREATE TABLE now obeys the SET SQL_MODE=ANSI and SET SQL_QUOTE_SHOW_CREATE=0 settings. (Bug#5292)

  • InnoDB: Fixed a bug that caused CREATE TEMPORARY TABLE ... ENGINE=InnoDB to terminate mysqld when running in innodb_file_per_table mode. Per-table tablespaces for temporary tables from now on are created in the temporary directory of mysqld. (Bug#5137)

  • InnoDB: Fixed some (not all) UTF-8 bugs in column prefix indexes. (Bug#5975)

  • InnoDB: If one updated a column so that its size changed, or updated it to an externally stored (TEXT or BLOB) value, then ANOTHER externally stored column would show up as 512 bytes of good data + 20 bytes of garbage in a consistent read that fetched the old version of the row. (Bug#5960)

  • InnoDB: Change error code to HA_ERR_ROW_IS_REFERENCED if we cannot DROP a parent table referenced by a FOREIGN KEY constraint; this error number is less misleading than the previous number HA_ERR_CANNOT_ADD_FOREIGN, but misleading still. (Bug#6202)

  • Fixed REVOKE ALL PRIVILEGES, GRANT OPTION FROM user so that all privileges are revoked correctly. (Bug#5831)

  • Fixed a bug that caused the server to crash when character set conversion was implicitly used in prepared mode; for example, as in 'abc' LIKE CONVERT('abc' as utf8). (Bug#5688)

  • The mysql_change_user() C API function now frees all prepared statements associated with the connection. (Bug#5315)

  • Fixed a bug when inserting NULL into an AUTO_INCREMENT column failed, when using prepared statements. (Bug#5510)

  • Fixed slave SQL thread so that the SET COLLATION_SERVER... statements it replicates don't advance its position (so that if it gets interrupted before the actual update query, it later redoes the SET). (Bug#5705)

  • Fixed that if the slave SQL thread found a syntax error in a query (which should be rare, as the master parsed it successfully), it stops. (Bug#5711)

  • Fixed that if a write to a MyISAM table fails because of a full disk or an exceeded disk quota, it prints a message to the error log every 10 minutes, and waits until disk space becomes available. (Bug#3248)

  • Now MySQL does not prefer columns, which are mentioned in select list but are renamed, over columns from other tables participating in FROM clause when it resolves GROUP BY clause (for example, SELECT t1.a AS c FROM t1, t2 ORDER BY a produces an error if both t1 and t2 tables contain a column). (Bug#4302)

  • Behavior of ALTER TABLE converting column containing NULL values to AUTO_INCREMENT column is no longer affected by NO_AUTO_VALUE_ON_ZERO mode. (Bug#5915).

B.1.19.聽Changes in release 4.1.5 (16 September 2004)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • InnoDB: Added configuration option innodb_autoextend_increment for setting the size in megabytes by which InnoDB tablespaces are extended when they become full. The default value is 8, corresponding to the fixed increment of 8MB in previous versions of MySQL.

  • InnoDB: The new Windows installation wizard of MySQL makes InnoDB as the MySQL default table type on Windows, unless explicitly specified otherwise. Note that it places the my.ini file in the installation directory of the MySQL server. See Section聽2.3.4.14, 鈥淭he Location of the my.ini File鈥.

Bugs fixed:

  • Fixed a bug which caused the server to crash on attempt to execute a prepared statement with BETWEEN ? AND ? and a datetime column. (Bug#5748)

  • Fixed name resolving of external fields of subqueries if subquery placed in select list of query with grouping. (Bug#5326)

  • Fixed detection of using same table for updating and selecting in multi-update queries. (Bug#5455)

  • The values of the max_sort_length, sql_mode, and group_concat_max_len system variables now are stored in the query cache with other query information to avoid returning an incorrect result from the query cache. (Bug#5394) (Bug#5515)

  • Fixed syntax analyzer with sql_mode=IGNORE_SPACE. It happened to take phrases like default .07 as identifier.identifier. (Bug#5318)

  • Fixed illegal internal field length of user variables of integer type. This showed up when creating a table as SELECT @var_name. (Bug#4788)

  • Fixed a buffer overflow in prepared statements API (libmysqlclient) when a statement containing thousands of placeholders was executed. (Bug#5194)

  • Fixed a bug in the server when after reaching a certain limit of prepared statements per connection (97), statement ids began to overlap, so occasionally wrong statements were chosen for execution. (Bug#5399)

  • Fixed a bug in prepared statements when LIKE used with arguments in different character sets crashed server on first execute. (Bug#4368)

  • Fixed a bug in prepared statements when providing '0000-00-00' date to a parameter lead to server crash. (Bug#4231, Bug#4562)

  • Fixed a bug in OPTIMIZE TABLE that could cause table corruption on FULLTEXT indexes. (Bug#5327)

  • InnoDB: Fixed a bug that InnoDB only allowed a maximum of 1000 connections inside InnoDB at the same time. A higher number could cause an assertion failure in sync0arr.c, line 384. Now we allow 1000, 10000, or 50000, depending on the buffer pool size. (Bug#5414)

B.1.20.聽Changes in release 4.1.4 (26 August 2004: Gamma)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Note: To fix a compile problem on systems that do not have automake 1.7 installed, an updated 4.1.4a source tarball has been published. In addition to resolving this automake dependency (Bug#5319), it also fixes some reported libedit compile errors when using a non-gcc compiler (Bug#5353).

Functionality added or changed:

  • Added the CSV storage engine.

  • Made internal representation of TIMESTAMP values in InnoDB in 4.1 to be the same as in 4.0. This difference resulted in incorrect datetime values in TIMESTAMP columns in InnoDB tables after an upgrade from 4.0 to 4.1. (Bug#4492) Warning: extra steps during upgrade required! Unfortunately this means that if you are upgrading from 4.1.x, where x <= 3, to 4.1.4 you should use mysqldump for saving and then restoring your InnoDB tables with TIMESTAMP columns.

  • The mysqld-opt Windows server was renamed to mysqld. This completes the Windows server renaming begun in MySQL 4.1.2. See Section聽2.3.8, 鈥淪electing a MySQL Server Type鈥.

  • Added Latin language collations for the ucs2 and utf8 Unicode character sets. These are called ucs2_roman_ci and utf8_roman_ci.

  • Corrected the name of the Mac OS X StartupItem script (it must match the name of the subdirectory, which was renamed to MySQLCOM in MySQL 4.1.2). Thanks to Bryan McCormack for reporting this.

  • Added --start-datetime, --stop-datetime, --start-position, and --stop-position options to mysqlbinlog. These make point-in-time recovery easier.

  • Killing a CHECK TABLE statement does not result in the table being marked as 鈥corrupted鈥 any more; the table remains as if CHECK TABLE had not even started. See Section聽13.5.5.3, 鈥KILL Syntax鈥.

  • Made the MySQL server ignore SIGHUP and SIGQUIT on Mac OS X 10.3. This is needed because under this OS, the MySQL server receives lots of these signals (reported as Bug#2030).

  • Support of usage of column aliases qualified by table name or alias in ORDER BY and GROUP BY was dropped. For example the following query SELECT a AS b FROM t1 ORDER BY t1.b is not allowed. One should use SELECT a AS b FROM t1 ORDER BY t1.a or SELECT a AS b FROM t1 ORDER BY b instead. This was non-standard (since aliases are defined on query level not on table level) and caused problems with some queries.

Bugs fixed:

  • Fixed a bug that caused libmysql to crash when attempting to fetch a value of MEDIUMINT column. (Bug#5126)

  • Fixed a bug that caused the MySQL server to crash when attempting to execute a prepared statement with SELECT ... INTO @var for a second time. (Bug#5034)

  • Fixed execution of optimized IN subqueries that use compound indexes. (Bug#4435)

  • Prohibited resolving of table fields in inner queries if fields do not take part in grouping for queries with grouping (inside aggregate function arguments, all table fields are still allowed). (Bug#4814)

  • Fixed a crash after SLAVE STOP if the IO thread was in a special state. (Bug#4629)

  • Fixed an old bug in concurrent accesses to MERGE tables (even one MERGE table and MyISAM tables), that could have resulted in a crash or hang of the server. (Bug#2408, CVE-2004-0837)

  • Fixed a bug that caused server crash on attempt to execute for a second time a prepared statement with NOT in WHERE or ON clauses. (Bug#4912)

  • MATCH ... AGAINST now works in a subquery. (Bug#4769)

  • Fixed a bug that omitted the .err extension of the error log file (--log-error) when the hostname contained a domain name. The domain name is now replaced by the extension. (Bug#4997)

  • Fixed a crash in myisamchk. (Bug#4901)

  • Fixed a bug which caused server crash if one used the CONVERT_TZ() function with time zone described in database as parameter and this time zone was not used before. (Bug#4508)

  • Support for %T, %r, %V, %v and %X, %x format specifiers was added to STR_TO_DATE() function. (Bug#4756)

  • Fixed a bug (hang) in NATURAL JOIN where joined table had no common column. (Bug#4807)

  • Fixed a crash caused by UNHEX(NULL). (Bug#4441)

  • mysql_fix_privilege_tables didn't correctly handle the argument of its --password=password_val option. (Bug#4240, Bug#4543)

  • Fixed that mysqlbinlog --read-from-remote-server sometimes couldn't accept 2 binary logs on command line. (Bug#4507)

  • Fixed that mysqlbinlog --position --read-from-remote-server had wrong # at lines. (Bug#4506)

  • If CREATE TEMPORARY TABLE t SELECT failed while loading the data, the temporary table was not dropped. (Bug#4551)

  • Fixed that when a multiple-table DROP TABLE failed to drop a table on the master server, the error code was not written to the binary log. (Bug#4553)

  • When the slave SQL thread was replicating a LOAD DATA INFILE statement, it didn't show the statement in the output of SHOW PROCESSLIST. (Bug#4326)

  • Fixed an assertion failure when reading the grant tables (Bug#4407)

  • Fixed that CREATE TABLE ... TYPE=HEAP ... AS SELECT... caused replication slave to stop. (Bug#4971)

  • Fixed that mysql_options(...,MYSQL_OPT_LOCAL_INFILE,...) failed to disable LOAD DATA LOCAL INFILE. (Bug#5038)

  • Fixed that disable-local-infile option had no effect if client read it from a configuration file using mysql_options(...,MYSQL_READ_DEFAULT,...). (Bug#5073)

  • Fixed that SET GLOBAL SYNC_BINLOG did not work on some platforms (Mac OS X). (Bug#5064)

  • Fixed that mysql-test-run failed on the rpl_trunc_binlog test if running test from the installed (the target of 'make install') directory. (Bug#5050)

  • Fixed that mysql-test-run failed on the grant_cache test when run as Unix user 'root'. (Bug#4678)

  • Fixed an unlikely deadlock which could happen when using KILL. (Bug#4810)

  • Fixed a crash when one connection got KILLed while it was doing START SLAVE. (Bug#4827)

  • Made FLUSH TABLES WITH READ LOCK block COMMIT if server is running with binary logging; this ensures that the binary log position is trustable when doing a full backup of tables and the binary log. (Bug#4953)

  • Fixed that the counter of an auto_increment column was not reset by TRUNCATE TABLE if the table was a temporary table. (Bug#5033)

  • Fixed bug which caused error to be reported when column from ORDER BY clause was present in two tables participating in SELECT even if the second instance of column in select list was renamed. (Bug#4302)

B.1.21.聽Changes in release 4.1.3 (28 June 2004: Beta)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Note: The initial release of MySQL 4.1.3 for Windows accidentally was not compiled with support for the Spatial Extensions (OpenGIS). This was fixed by rebuilding from the same 4.1 code snapshot with the missing option and releasing those packages as version 4.1.3a.

To enable compiling the newly released PHP 5 against MySQL 4.1.3 on Windows, the Windows packages had to be rebuilt once more to add a few missing symbols to the MySQL client library. These packages were released as MySQL 4.1.3b.

Functionality added or changed:

  • Warning: Incompatible change: C API change: mysql_shutdown() now requires a second argument. This is a source-level incompatibility that affects how you compile client programs; it does not affect the ability of compiled clients to communicate with older servers. See Section聽17.2.3.63, 鈥mysql_shutdown().

  • Warning: Incompatible change: The timezone system variable has been removed and replaced by system_time_zone. See Section聽5.2.3, 鈥淪ystem Variables鈥.

  • Support for per-connection time zones was added. Now you can set the current time zone for a connection by setting the @@time_zone system variable to a value such as '+10:00' or 'Europe/Moscow' (where 'Europe/Moscow' is the name of one of the time zones described in the system tables). Functions like CURRENT_TIMESTAMP, UNIX_TIMESTAMP, and so forth honor this time zone. Values of TIMESTAMP type are also interpreted as values in this time zone. So now our TIMESTAMP type behaves similar to Oracle's TIMESTAMP WITH LOCAL TIME ZONE. That is, values stored in such a column are normalized toward UTC and converted back to the current connection time zone when they are retrieved from such a column. To set up the tables that store time zone information, see Section聽2.10, 鈥淧ost-Installation Setup and Testing鈥.

  • Basic time zone conversion function CONVERT_TZ() was added. It assumes that its first argument is a datetime value in the time zone specified by its second argument and returns the equivalent datetime value in the time zone specified by its third argument.

  • Added the ARCHIVE storage engine.

  • Added SQL syntax for prepared statements. See Section聽13.7, 鈥淪QL Syntax for Prepared Statements鈥.

  • Language-specific collations were added for the ucs2 and utf8 Unicode character sets: Icelandic, Latvian, Romanian, Slovenian, Polish, Estonian, Swedish, Turkish, Czech, Danish, Lithuanian, Slovak, Spanish, Traditional Spanish.

  • CHECK TABLE now can be killed. It then marks the table as corrupted. See Section聽13.5.5.3, 鈥KILL Syntax鈥.

  • OPTIMIZE TABLE for InnoDB tables is now mapped to ALTER TABLE instead of ANALYZE TABLE.

  • sync_frm is now a settable global variable (not only a startup option).

  • Added the sync_binlog=N global variable and startup option, which makes the MySQL server synchronize its binary log to disk (fdatasync()) after every Nth write to the binary log.

  • Changed the slave SQL thread to print fewer useless error messages (no more message duplication; no more messages when an error is skipped (because of slave-skip-errors).

  • DROP DATABASE IF EXISTS, DROP TABLE IF EXISTS, single-table DELETE and single-table UPDATE are now written to the binary log even if they changed nothing on the master (for example, even if the DELETE matched no row). The old behavior sometimes caused bad surprises in replication setups.

  • Replication and mysqlbinlog now have better support for the case that the session character set and collation variables are changed within a given session. See Section聽6.7, 鈥淩eplication Features and Known Problems鈥.

  • Added --innodb-safe-binlog server option, which adds consistency guarantees between the content of InnoDB tables and the binary log. See Section聽5.11.4, 鈥淭he Binary Log鈥.

  • LIKE now supports the use of a prepared statement parameter or delimited constant expression as the argument to ESCAPE (Bug#4200).

Bugs fixed:

  • Fixed CREATE DATABASE IF NOT EXISTS for Win32 which caused an error if database existed. (Bug#4378)

  • Added missing root account to Windows version of mysqld. (Bug#4242)

  • Fixed bug in prepared EXPLAIN statement which led to server crash. (Bug#4271)

  • Fixed a bug of using parameters in some prepared statements via SQL syntax. (Bug#4280)

  • Fixed a bug in MERGE tables created with INSERT_METHOD=LAST, that were not able to report a key number that caused 鈥Duplicate entry鈥 error for UNIQUE key in INSERT. As a result, error message was not precise enough (error 1022 instead of error 1062) and INSERT ... ON DUPLICATE KEY UPDATE did not work. (Bug#4008)

  • Fixed a bug in DELETE from a table with FULLTEXT indexes which under rare circumstances could result in a corrupted table, if words of different lengths may be considered equal (which is possible in some collations, for example, in utf8_general_ci or latin1_german2_ci.) (Bug#3808)

  • Fixed too-early unlocking of tables if we have subquery in HAVING clause. (Bug#3984)

  • Fixed a bug in mysqldump when it didn't return an error if the output device was filled (Bug#1851)

  • Fixed a bug in client-side conversion of string column to MYSQL_TIME application buffer (prepared statements API). (Bug#4030)

  • Fixed a bug with server crash on attempt to execute a non-prepared statement. (Bug#4236)

  • Fixed a bug with server crash on attempt to prepare a statement with character set introducer. (Bug#4105)

  • Fixed bug which caused different number of warnings to be generated when bad datetime as string or as number was inserted into DATETIME or TIMESTAMP column. (Bug#2336)

  • Fixed some byte order bugs with prepared statements on machines with high-byte-first. (Bug#4173)

  • Fixed unlikely bug in the range optimizer when using many IN() queries on different key parts. (Bug#4157)

  • Fixed problem with NULL and derived tables. (Bug#4097)

  • Fixed wrong UNION results if display length of fields for numeric types was set less then real length of values in them. (Bug#4067)

  • Fixed a bug in mysql_stmt_close(), which hung up when attempting to close statement after failed mysql_stmt_fetch(). (Bug#4079)

  • Fixed bug of re-execution optimized COUNT(*), MAX() and MIN() functions in prepared statements. (Bug#2687)

  • Fixed a bug with COUNT(DISTINCT) performance degradation in cases like COUNT(DISTINCT a TEXT, b CHAR(1)) (no index used). (Bug#3904)

  • Fixed a bug in MATCH ... AGAINST(... IN BOOLEAN MODE) that under rare circumstances could cause wrong results if in the data's collation one byte could match many (like in utf8_general_ci or latin1_german2_ci.) (Bug#3964)

  • Fixed a bug in prepared statements protocol, when microseconds part of MYSQL_TYPE_TIME/MYSQL_TYPE_DATETIME columns was not sent to the client. (Bug#4026)

  • Fixed a bug that using --with-charset with configure didn't affect the MySQL client library. (Bug#3990)

  • Fixed a bug in authentication code that allowed a malicious user to bypass password verification with specially crafted packets, using a modified client library. (CVE-2004-0627, CVE-2004-0628)

  • Fixed bug with wrong result of CONCAT(?, col_name) in prepared statements. (Bug#3796)

  • Fixed potential memory overrun in mysql_real_connect() (which required a compromised DNS server and certain operating systems). (Bug#4017, CVE-2004-0836)

  • During the installation process of the server RPM on Linux, mysqld was run as the root system user, and if you had --log-bin=file_name, where the file was located somewhere outside of the data directory, it created binary log files owned by root in this directory that remained owned by root after the installation. This is now fixed by starting mysqld as the mysql system user instead. (Bug#4038)

  • Made DROP DATABASE honor the value of lower_case_table_names. (Bug#4066)

  • The slave SQL thread refused to replicate INSERT ... SELECT if it examined more than 4 billion rows. (Bug#3871)

  • mysqlbinlog didn't escape the string content of user variables, and did not deal well when these variables were in non-ASCII character sets; this is now fixed by always printing the string content of user variables in hexadecimal. The character set and collation of the string is now also printed. (Bug#3875)

  • Fixed incorrect destruction of expression which led to crash of server on complex AND/OR expressions if query was ignored (either by a replication server because of --replicate-*-table rules, or by any MySQL server because of a syntax error). (Bug#3969, Bug#4494)

B.1.22.聽Changes in release 4.1.2 (28 May 2004)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • CHAR BYTE is an alias for the BINARY data type. (Previously, it was an alias for CHAR BINARY.)

  • Warning: Incompatible change: Handling of the FLOAT and DOUBLE floating-point data types is more strict to follow standard SQL. For example, a data type of FLOAT(3,1) stores a maximum value of 99.9. Previously, the server allowed larger numbers to be stored. That is, it stored a value such as 100.0 as 100.0. Now the server clips 100.0 to the maximum allowable value of 99.9. If you have tables that were created before MySQL 4.1.2 and that contain floating-point data not strictly legal for the column type, you should alter the data types of those columns. For example:

    ALTER TABLE tbl_name MODIFY col_name FLOAT(4,1);
    
  • Warning: Incompatible change: String comparison now works according to the SQL standard. Because we have that 'a' = 'a ' then from it must follow that 'a' > 'a\t'. (The latter was not the case before MySQL 4.1.2.) To implement it, we had to change how storage engines compare strings internally. As a side effect, if you have a table where a CHAR or VARCHAR column in some row has a value with the last character less than ASCII(32), you have to repair this table. CHECK TABLES tells you if this problem exists. (Bug#3152)

  • Added support for DEFAULT CURRENT_TIMESTAMP and for ON UPDATE CURRENT_TIMESTAMP specifications for TIMESTAMP columns. Now you can explicitly say that a TIMESTAMP column should be set automatically to the current timestamp for INSERT and/or UPDATE statements, or even prevent the column from updating automatically. Only one column with such an auto-set feature per table is supported. TIMESTAMP columns created with earlier versions of MySQL behave as before. Behavior of TIMESTAMP columns that were created without explicit specification of default/on as earlier depends on its position in table: If it is the first TIMESTAMP column, it be treated as having been specified as TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP. In other cases, it would be treated as a TIMESTAMP DEFAULT 0 column. NOW is supported as an alias for CURRENT_TIMESTAMP. Warning: Incompatible change: Unlike in previous versions, explicit specification of default values for TIMESTAMP column is never ignored and turns off the auto-set feature (unless you have CURRENT_TIMESTAMP as the default).

  • Warning: Incompatible change: Renamed prepared statements C API functions:

    Old NameNew Name
    mysql_bind_param()mysql_stmt_bind_param()
    mysql_bind_result()mysql_stmt_bind_result()
    mysql_prepare()mysql_stmt_prepare()
    mysql_execute()mysql_stmt_execute()
    mysql_fetch()mysql_stmt_fetch()
    mysql_fetch_column()mysql_stmt_fetch_column()
    mysql_param_count()mysql_stmt_param_count()
    mysql_param_result()mysql_stmt_param_metadata()
    mysql_get_metadata()mysql_stmt_result_metadata()
    mysql_send_long_data()mysql_stmt_send_long_data()

    Now all functions that operate with a MYSQL_STMT structure begin with the prefix mysql_stmt_.

  • Warning: Incompatible change: The signature of the mysql_stmt_prepare() function was changed to int mysql_stmt_prepare(MYSQL_STMT *stmt, const char *query, unsigned long length). To create a MYSQL_STMT handle, you should use the mysql_stmt_init() function, not mysql_stmt_prepare().

  • Warning: Incompatible change: The Type output column for SHOW TABLE STATUS now is labeled Engine.

  • Added the EXAMPLE storage engine.

  • The mysqld Windows server was renamed to mysqld-debug. See Section聽2.3.8, 鈥淪electing a MySQL Server Type鈥.

  • Added Handler_discover status variable.

  • Added support for character set conversion and MYSQL_TYPE_BLOB type code in prepared statement protocol.

  • Added explanation of hidden SELECT of UNION in output of EXPLAIN SELECT statement.

  • mysql command-line client now supports multiple -e options. (Bug#591)

  • New myisam_data_pointer_size system variable. See Section聽5.2.3, 鈥淪ystem Variables鈥.

  • The --log-warnings server option now is enabled by default. Disable with --skip-log-warnings.

  • The --defaults-file=file_name option now requires that the filename must exist (safety fix). (Bug#3413)

  • mysqld_multi now creates the log in the directory named by datadir (from the [mysqld] section in my.cnf or compiled in), not in /tmp. Thanks to Christian Hammers from Debian Security Team for reporting this. (CVE-2004-0388)

  • SHOW GRANTS with no FOR clause or with FOR CURRENT_USER() shows the privileges for the current session.

  • The improved character set support introduced in MySQL 4.1.0 for the MyISAM and HEAP storage engines is now available for InnoDB as well.

  • A name of 鈥Primary鈥 no longer can be specified as an index name. (That name is reserved for the PRIMARY KEY if the table has one.) (Bug#856)

  • MySQL now issues a warning when a SET or ENUM column with duplicate values in the list is created. (Bug#1427)

  • Now SQL_SELECT_LIMIT variable has no influence on subqueries. (Bug#2600)

  • UNHEX() function implemented. See Section聽12.4, 鈥淪tring Functions鈥.

  • The mysql command-line client no longer stores in the history file multiple copies of identical queries that are run consecutively.

  • Multi-line statements in the mysql command-line client now are stored in the history file as a single line.

  • UUID() function implemented. Note that it does not work with replication yet. See Section聽12.10.4, 鈥淢iscellaneous Functions鈥.

  • Prepared statements with all types of subqueries fixed.

  • MySQL now supports up to 64 indexes per table.

  • MyISAM tables now support keys up to 1000 bytes long.

  • MyISAM and InnoDB tables now support index prefix lengths up to 1000 bytes long.

  • If you try to create a key with a key part that is too long, and it is safe to auto-truncate it to a smaller length, MySQL now does so. A warning is generated, rather than an error.

  • The ft_boolean_syntax variable now can be changed while the server is running. See Section聽5.2.3, 鈥淪ystem Variables鈥.

  • REVOKE ALL PRIVILEGES, GRANT FROM user_list is changed to a more consistent REVOKE ALL PRIVILEGES, GRANT OPTION FROM user_list. (Bug#2642)

  • Internal string-to-number conversion now supports only SQL:2003 compatible syntax for numbers. In particular, '0x10'+0 does not work anymore. (Actually, it worked only on some systems before, such as Linux. It did not work on others, such as FreeBSD or Solaris. Making these queries OS-independent was the goal of this change.) Use CONV() to convert hexadecimal numbers to decimal. Example: CONV(MID('0x10',3),16,10)+0.

  • mysqlhotcopy now works on NetWare.

  • ALTER TABLE DROP PRIMARY KEY no longer drops the first UNIQUE index if there is no primary index. (Bug#2361)

  • Added latin1_spanish_ci (Modern Spanish) collation for the latin1 character set.

  • Added the ENGINE table option as a synonym for the TYPE option for CREATE TABLE and ALTER TABLE.

  • Added the --default-storage-engine server option as a synonym for --default-table-type.

  • Added the storage_engine system variable as a synonym for table_type.

  • Added init_connect and init_slave system variables. The values should be SQL statements to be executed when each client connects or each time a slave's SQL thread starts, respectively.

  • C API enhancement: SERVER_QUERY_NO_INDEX_USED and SERVER_QUERY_NO_GOOD_INDEX_USED flags are now set in the server_status field of the MYSQL structure. It is these flags that make the query to be logged as slow if mysqld was started with --log-slow-queries --log-queries-not-using-indexes.

  • For replication of MEMORY (HEAP) tables: Made the master automatically write a DELETE FROM statement to its binary log when a MEMORY table is opened for the first time since master's startup. This is for the case where the slave has replicated a non-empty MEMORY table, then the master is shut down and restarted: the table is now empty on master; the DELETE FROM empties it on slave too. Note that even with this fix, between the master's restart and the first use of the table on master, the slave still has out-of-date data in the table. But if you use the init-file option to populate the MEMORY table on the master at startup, it ensures that the failing time interval is zero. (Bug#2477)

  • When a session having open temporary tables terminates, the statement automatically written to the binary log is now DROP TEMPORARY TABLE IF EXISTS instead of DROP TEMPORARY TABLE, for more robustness.

  • The MySQL server now returns an error if SET SQL_LOG_BIN or SET SQL_LOG_UPDATE is issued by a user without the SUPER privilege (in previous versions it just silently ignored the statement in this case).

  • Changed that when the MySQL server has binary logging disabled (that is, no --log-bin option was used), then no transaction binary log cache is allocated for connections. This should save binlog_cache_size bytes of memory (32KB by default) for every connection.

  • Added Binlog_cache_use and Binlog_cache_disk_use status variables that count the number of transactions that used transaction binary log and that had to flush this temporary binary log to disk instead of using only the in-memory buffer. They can be used for tuning the binlog_cache_size system variable.

  • Added option --replicate-same-server-id.

  • The Mac OS X Startup Item has been moved from the directory /Library/StartupItems/MySQL to /Library/StartupItems/MySQLCOM to avoid a file name collision with the MySQL Startup Item installed with Mac OS X Server. See Section聽2.13.2, 鈥淢ac OS X Notes鈥.

  • Added option --to-last-log to mysqlbinlog, for use in conjunction with --read-from-remote-server.

  • The FLOAT and DECIMAL types now obey (precision,scale) settings. (Bug#10897)

  • Added the mysql_set_local_infile_handler() and mysql_set_local_infile_default() C API functions.

Bugs fixed:

  • Fixed check of EXPLAIN of UNION. (Bug#3639)

  • Fixed a bug in a query that used DISTINCT and ORDER BY by column's real name, while the column had an alias, specified in SELECT clause. (Bug#3681)

  • mysqld could crash when a table was altered and used at the same time. This was a 4.1.2-specific bug. (Bug#3643).

  • Fixed bug when using impossible WHERE with PROCEDURE ANALYSE(). (Bug#2238).

  • Fixed security problem in new authentication where password was not checked for changed GRANT accounts until FLUSH PRIVILEGES was executed. (Bug#3404)

  • Fixed crash of GROUP_CONCAT() on expression with ORDER BY and external ORDER BY in a query. (Bug#3752)

  • Fixed a bug in ALL/SOME subqueries in case of optimization (key field present in subquery). (Bug#3646)

  • Fixed a bug in SHOW GRANTS and EXPLAIN SELECT character set conversion. (Bug#3403)

  • Prepare statements parameter do not cause error message as fields used in select list but not included in ORDER BY list.

  • UNION statements did not consult SQL_SELECT_LIMIT value when set. This is now fixed properly, which means that this limit is applied to the top level query, unless LIMIT for entire UNION is used.

  • Fixed a bug in multiple-table UPDATE statements that resulted in an error when one of the tables was not updated but was used in the nested query, contained therein.

  • Fixed mysql_stmt_send_long_data() behavior on second execution of prepared statement and in case when long data had zero length. (Bug#1664)

  • Fixed crash on second execution of prepared statement with UNION. (Bug#3577)

  • Fixed incorrect results of aggregate functions in subquery with empty result set. (Bug#3505)

  • You can now call mysql_stmt_attr_set(..., STMT_ATTR_UPDATE_MAX_LENGTH) to tell the client library to update MYSQL_FIELD->max_length when doing mysql_stmt_store_result(). (Bug#1647).

  • Added support for unsigned integer types to prepared statement API (Bug#3035).

  • Fixed crash in prepared statements when subquery in the FROM clause with parameter used. (Bug#3020)

  • Fixed unknown error when negative value bind to unsigned. (Bug#3223)

  • Fixed aggregate function in prepared statements. (Bug#3360)

  • Incorrect error message when wrong table used in multiple-table DELETE statement in prepared statements. (Bug#3411)

  • Requiring UPDATE privilege for tables which are not updated in multiple-table UPDATE statement in prepared statements.

  • Fixed prepared statement support for INSERT, REPLACE, CREATE, DELETE, SELECT, DO, SET and SHOW. All other commands are prohibited via prepared statement interface. (Bug#3398, Bug#3406, Bug#2811)

  • Fixed a lot of bugs in GROUP_CONCAT(). (Bug#2695, Bug#3381, Bug#3319)

  • Added optimization that allows for prepared statements using a large number of tables or tables with a large number of columns to be re-executed significantly faster. (Bug#2050)

  • Fixed bug that caused execution of prepared statements to fail then table that this statement were using left table cache. This bug showed up as if this prepared statement used random garbage as column names or as server crashes. (Bug#3307)

  • Fixed a problem resulting from setting the character_set_results variable to NULL. (Bug#3296)

  • Fixed query cache statistics.

  • Fixed bug in ANALYZE TABLE on a BDB table inside a transaction that hangs server thread. (Bug#2342)

  • Fixed a symlink vulnerability in the mysqlbug script. (Bug#3284, CVE-2004-0381)

  • Fixed a bug in parallel repair (myisamchk -p, myisam_repair_threads); sometimes the repair process failed to repair a table. (Bug#1334)

  • A query that uses both UNION [DISTINCT] and UNION ALL now works correctly. (Bug#1428)

  • Table default character set affects LONGBLOB columns. (Bug#2821)

  • CONCAT_WS() makes the server die in case of illegal mix of collations. (Bug#3087)

  • UTF8 charset breaks joins with mixed column/string constant. (Bug#2959)

  • Fixed DROP DATABASE to report number of tables deleted.

  • Fixed bug in privilege checking of ALTER TABLE RENAME. (Bug#3270, CVE-2004-0835)

  • Fixed memory leak in the client library when statement handle was freed on closed connection (call to mysql_stmt_close after mysql_close). (Bug#3073)

  • Fixed server segmentation faults when processing malformed prepared statements. (Bug#2795, Bug#2274)

  • Fixed using subqueries with OR and AND functions. (Bug#2838)

  • Fixed comparison of tables/database names with --lower_case_table_names option. (Bug#2880)

  • Removed try to check NULL if index built on column where NULL is impossible in IN subquery optimization. (Bug#2393)

  • Fixed incorrect parsing of subqueries in the FROM clause. (Bug#2421)

  • Fixed processing of RAND() in subqueries with static tables. (Bug#2645)

  • Fixed bug with quoting of table names in mysqldump for various values of sql_mode of server. (Bug#2591)

  • Fixed bug with storing values that are out of range for DOUBLE and FLOAT columns. (Bug#2082)

  • Fixed bug with compiling --with-pstack with binutils 2.13.90. (Bug#1661)

  • Fixed a bug in the GRANT system. When a password was assigned to an account at the global level and then privileges were granted at the database level (without specifying any password), the existing password was replaced temporarily in memory until the next FLUSH PRIVILEGES operation or the server was restarted. (Bug#2953)

  • Fixed a bug in full-text search on multi-byte character set (such as UTF8) that appeared when a search word was shorter than a matching word from the index (for example, searching for 鈥Uppsala鈥 when table data contain 鈥Uppsa*la鈥). (Bug#3011)

  • Fixed a bug that made Max_used_connections to be less than the actual maximum number of connections in use simultaneously.

  • Fixed calculation of Index_length in HEAP table status for BTREE indexes. (Bug#2719)

  • Fixed mysql_stmt_affected_rows() call to always return number of rows affected by given statement. (Bug#2247)

  • Fixed crash in MATCH ... AGAINST() on a phrase search operator with a missing closing double quote. (Bug#2708)

  • Fixed output of mysqldump --tab. (Bug#2705)

  • Fix for a bug in UNION operations that prevented proper handling of NULL columns. This happened only if a column in the first SELECT node was NOT NULL. (Bug#2508)

  • Fix for a bug in UNION operations with InnoDB storage engine, when some columns from one table were used in one SELECT statement and some were used in another SELECT statement. (Bug#2552)

  • Fixed a few years old bug in the range optimizer that caused a segmentation fault on some very rare queries. (Bug#2698)

  • Fixed bug with SHOW CREATE TABLE ... which didn't properly double quotes. (Bug#2593)

  • Queries with subqueries in FROM clause locks all tables at once for now. This also fixed bugs in EXPLAIN of subqueries in FROM output. (Bug#2120)

  • Fixed bug with mysqldump not quoting 鈥tricky鈥 names correctly. (Bug#2592)

  • Fix for a bug that prevented table / column privileges from being loaded on startup. (Bug#2546)

  • Fixed bug in replication with CREATE TABLE ... LIKE ... that resulted in a statement not being written to the binary log. (Bug#2557)

  • Fixed memory leak in INSERT ... ON DUPLICATE KEY UPDATE .... (Bug#2438)

  • Fixed bug in the parser, making the syntax CONVERT(expr,type) legal again.

  • Fixed parsing of short-form IP addresses in INET_ATON(). (Bug#2310)

  • Fixed a bug in CREATE ... SELECT that sometimes caused a string column with a multi-byte character set (such as utf8) to have insufficient length to hold the data.

  • Fixed a rare table corruption on adding data (INSERT, REPLACE, UPDATE, etc. but not DELETE) to a FULLTEXT index. (Bug#2417)

  • Compile the MySQL-client RPM package against libreadline instead of libedit. (Bug#2289)

  • Fix for a crashing bug that was caused by not setting vio_timeout() virtual function for all protocols. This bug occurred on Windows. (Bug#2025)

  • Fix for a bug that caused mysql client program to erroneously cache the value of the current database. (Bug#2025)

  • Fix for a bug that caused client/server communication to be broken when mysql_set_server_option() or mysql_get_server_option() were invoked. (Bug#2207)

  • Fix for a bug that caused wrong results when CAST() was applied on NULL to signed or unsigned integer column. (Bug#2219)

  • Fix for a crashing bug that occurred in the mysql client program when database name was longer then expected. (Bug#2221)

  • Fixed a bug in CHECK TABLE that sometimes resulted in a spurious error Found key at page ... that points to record outside datafile for a table with a FULLTEXT index. (Bug#2190)

  • Fixed bug in GRANT with table-level privilege handling. (Bug#2178)

  • Fixed bug in ORDER BY on a small column. (Bug#2147)

  • Fixed a bug with the INTERVAL() function when 8 or more comparison arguments are provided. (Bug#1561)

  • Packaging: Fixed a bug in the Mac OS PKG postinstall script (mysql_install_db was called with an obsolete argument).

  • Packaging: Added missing file mysql_create_system_tables to the server RPM package. This bug was fixed for the 4.1.1 RPMs by updating the MySQL-server RPM from MySQL-server-4.1.1-0 to MySQL-server-4.1.1-1. The other RPMs were not affected by this change.

  • Fixed a bug in myisamchk and CHECK TABLE that sometimes resulted in a spurious error Found key at page ... that points to record outside datafile for a table with a FULLTEXT index. (Bug#1977)

  • Fixed a hang in full-text indexing of strings in multi-byte (all besides utf8) charsets. (Bug#2065)

  • Fixed a crash in full-text indexing of UTF8 data. (Bug#2033)

  • Replication: a rare race condition in the slave SQL thread that could lead to an incorrect complaint that the relay log is corrupted. (Bug#2011)

  • Replication: If a client connects to a slave server and issues an administrative statement for a table (for example, OPTIMIZE TABLE or REPAIR TABLE), this could sometimes stop the slave SQL thread. This does not lead to any corruption, but you must use START SLAVE to get replication going again. (Bug#1858)

  • Replication: in the slave SQL thread, a multiple-table UPDATE could produce an incorrect complaint that some record was not found in one table, if the UPDATE was preceded by a INSERT ... SELECT. (Bug#1701)

  • Replication: sometimes the master gets a non-fatal error during the execution of a statement but finally the statements succeeds (for example, a write to a MyISAM table first receives "no space left on device" but is able to finally complete, see Section聽A.1.4.3, 鈥淗ow MySQL Handles a Full Disk鈥); the bug was that the master forgot to reset the error code to 0 after success, so the error code got into its binary log, thus making the slave giving false alarms like "did not get the same error as on master". (Bug#2083)

  • Removed a misleading "check permissions on master.info" from a replication error message, because the cause of the problem could be different from permissions. (Bug#2121)

  • Fixed a crash when the replication slave was unable to create the first relay log. (Bug#2145)

  • ALTER DATABASE caused the client to hang if the database did not exist. (Bug#2333)

  • Multiple-table DELETE statements were never replicated by the slave if there were any --replicate-*-table options. (Bug#2527)

  • Fixed bug in ALTER TABLE RENAME, when rename to the table with the same name in another database silently dropped destination table if it existed. (Bug#2628)

  • The MySQL server did not report any error if a statement (submitted through mysql_real_query() or mysql_stmt_prepare()) was terminated by garbage characters. This can happen if you pass a wrong length parameter to these functions. The result was that the garbage characters were written into the binary log. (Bug#2703)

  • Fixed bug in client library that caused mysql_stmt_fetch and mysql_stmt_store_result() to hang if they were called without prior call of mysql_stmt_execute(). Now they give an error instead. (Bug#2248)

  • Made clearer the error message that one gets when an update is refused because of the --read-only option. (Bug#2757)

  • Fixed that --replicate-wild-*-table rules apply to ALTER DATABASE when the table pattern is %, as is the case for CREATE DATABASE and DROP DATABASE. (Bug#3000)

  • Fixed that when a Rotate event is found by the slave SQL thread in the middle of a transaction, the value of Relay_Log_Pos in SHOW SLAVE STATUS remains correct. (Bug#3017)

  • Corrected the master's binary log position that InnoDB reports when it is doing a crash recovery on a slave server. (Bug#3015)

  • Changed the column Seconds_Behind_Master in SHOW SLAVE STATUS to never show a value of -1. (Bug#2826)

  • Changed that when a DROP TEMPORARY TABLE statement is automatically written to the binary log when a session ends, the statement is recorded with an error code of value zero (this ensures that killing a SELECT on the master does not result in a superfluous error on the slave). (Bug#3063)

  • Changed that when a thread handling INSERT DELAYED (also known as a delayed_insert thread) is killed, its statements are recorded with an error code of value zero (killing such a thread does not endanger replication, so we thus avoid a superfluous error on the slave). (Bug#3081)

  • Fixed deadlock when two START SLAVE commands were run at the same time. (Bug#2921)

  • Fixed that a statement never triggers a superfluous error on the slave, if it must be excluded given the --replicate-* options. The bug was that if the statement had been killed on the master, the slave would stop. (Bug#2983)

  • The --local-load option of mysqlbinlog now requires an argument.

  • Fixed a segmentation fault when running LOAD DATA FROM MASTER after RESET SLAVE. (Bug#2922)

  • mysqlbinlog --read-from-remote-server read all binary logs following the one that was requested. It now stops at the end of the requested file, the same as it does when reading a local binary log. There is an option --to-last-log to get the old behavior. (Bug#3204)

  • Fixed mysqlbinlog --read-from-remote-server to print the exact positions of events in the "at #" lines. (Bug#3214)

  • Fixed a rare error condition that caused the slave SQL thread spuriously to print the message Binlog has bad magic number and stop when it was not necessary to do so. (Bug#3401)

  • Fixed the Exec_master_log_pos column and its disk image in the relay-log.info file to be correct if the master had version 3.23. (The value was too big by six bytes.) This bug does not exist in MySQL 5.0. (Bug#3400)

  • Fixed mysqlbinlog not to forget to print a USE statement under rare circumstances where the binary log contained a LOAD DATA INFILE statement. (Bug#3415)

  • Fixed a memory corruption when replicating a LOAD DATA INFILE when the master had version 3.23. Some smaller problems remain in this setup, See Section聽6.7, 鈥淩eplication Features and Known Problems鈥. (Bug#3422)

  • Multiple-table DELETE statements were always replicated by the slave if there were some --replicate-*-ignore-table options and no --replicate-*-do-table options. (Bug#3461)

  • Fixed a crash of the MySQL slave server when it was built with --with-debug and replicating itself. (Bug#3568)

  • Fixed that in some replication error messages, a very long query caused the rest of the message to be invisible (truncated), by putting the query last in the message. (Bug#3357)

  • Fixed a bug in REPAIR TABLE that resulted sometimes in a corrupted table, if the table contained FULLTEXT indexes and many words of different lengths that are considered equal (which is possible in certain collations, such as latin1_german2_ci or utf8_general_ci). (Bug#3835)

  • Fixed a crash of mysqld that was started with binary logging disabled, but with a non-zero value for the expire_logs_days system variable. (Bug#3807)

  • If server-id was not set using startup options but with SET GLOBAL, the replication slave still complained that it was not set. (Bug#3829)

B.1.23.聽Changes in release 4.1.1 (01 December 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

This release includes all fixes in MySQL 4.0.16 and most of the fixes in MySQL 4.0.17.

Functionality added or changed:

  • Warning: Incompatible change: Renamed the C API mysql_prepare_result() function to mysql_get_metadata() because the old name was confusing.

  • Warning: Incompatible change: Client authentication now is based on 41-byte passwords in the user table, not 45-byte passwords as in 4.1.0. Any 45-byte passwords created for 4.1.0 must be reset after running the mysql_fix_privilege_tables script.

  • Important note: If you upgrade to InnoDB-4.1.1 or higher, you cannot downgrade to a version lower than 4.1.1 any more! That is because earlier versions of InnoDB are not aware of multiple tablespaces.

  • Added secure_auth global server system variable and --secure-auth server option that disallow authentication for accounts that have old (pre-4.1.1) passwords.

  • Added --secure-auth option to mysql command-line client. If this option is set, the client refuses to send passwords in old (pre-4.1.1) format.

  • EXPLAIN now supports an EXTENDED option. When given, EXPLAIN generates extra information that may be viewed with the SHOW WARNINGS statement.

  • Table aliases are not case sensitive if lower_case_table_names is non-zero.

  • The --old-protocol option for mysqld is no longer supported and has been removed.

  • Renamed bdb_version system variable to version_bdb.

  • MyISAM tables now use a better checksum algorithm (if checksum is enabled with CREATE TABLE ... CHECKSUM=1). Old tables will appear to have incorrect checksum, and should be repaired.

  • New CHECKSUM TABLE statement for reporting table checksum values.

  • Added character_set_client, character_set_connection, character_set_database, character_set_results, character_set_server, character_set_system, collation_connection, collation_database, and collation_server system variables to provide information about character sets and collations.

  • It is now possible to create multiple key caches, assign table indexes to particular caches, and to preload indexes into caches. See Section聽13.5.5.1, 鈥CACHE INDEX Syntax鈥. See Section聽13.5.5.4, 鈥LOAD INDEX INTO CACHE Syntax鈥. Structured system variables are introduced as a means of grouping related key cache parameters. See Section聽5.2.4.1, 鈥淪tructured System Variables鈥.

  • Added preload_buffer_size system variable.

  • New COERCIBILITY() function to return the collation coercibility of a string.

  • The --quote-names option for mysqldump now is enabled by default.

  • mysqldump now includes a statement in the dump output to set FOREIGN_KEY_CHECKS to 0 to avoid problems with tables having to be reloaded in a particular order when the dump is reloaded. The existing FOREIGN_KEY_CHECKS value is saved and restored.

  • You can revoke all privileges from a user with REVOKE ALL PRIVILEGES, GRANT FROM user_list.

  • Added IGNORE option for DELETE statement.

  • MySQL source distributions now also include the MySQL Internals Manual internals.texi.

  • Added mysql_set_server_option() C API client function to allow multiple statement handling in the server to be enabled or disabled.

  • The mysql_next_result() C API function now returns -1 if there are no more result sets.

  • Renamed CLIENT_MULTI_QUERIES connect option flag to CLIENT_MULTI_STATEMENTS. To allow for a transition period, the old option continues to be recognized for a while.

  • Require DEFAULT before table and database default character set. This enables us to use ALTER TABLE tbl_name ... CHARACTER SET=... to change the character set for all CHAR, VARCHAR, and TEXT columns in a table.

  • Added MATCH ... AGAINST( ... WITH QUERY EXPANSION) and the ft_query_expansion_limit system variable.

  • Removed unused ft_max_word_len_for_sort system variable.

  • Removed unused ft_max_word_len_for_sort variable from myisamchk.

  • Full-text search now supports multi-byte character sets and the Unicode utf8 character set. (The Unicode ucs2 character set is not yet supported.)

  • Phrase search in MATCH ... AGAINST ( ... IN BOOLEAN MODE) no longer matches partial words.

  • Added aggregate function BIT_XOR() for bitwise XOR operations.

  • Replication over SSL now works.

  • The START SLAVE statement now supports an UNTIL clause for specifying that the slave SQL thread should be started but run only until it reaches a given position in the master's binary logs or in the slave's relay logs.

  • Produce warnings even for single-row INSERT statements, not just for multiple-row INSERT statements. Previously, it was necessary to set SQL_WARNINGS=1 to generate warnings for single-row statements.

  • Added delimiter (\d) command to the mysql command-line client for changing the statement delimiter (terminator). The default delimiter is semicolon.

  • CHAR, VARCHAR, and TEXT columns now have lengths measured in characters rather than in bytes. The character size depends on the column's character set. This means, for example, that a CHAR(n) column for a multi-byte character set takes more storage than before. Similarly, index values on such columns are measured in characters, not bytes.

  • LIMIT no longer accepts negative arguments (they used to be treated as very big positive numbers before).

  • The DATABASE() function now returns NULL rather than the empty string if there is no database selected.

  • Added --sql-mode=NO_AUTO_VALUE_ON_ZERO option to suppress the usual behavior of generating the next sequence number when zero is stored in an AUTO_INCREMENT column. With this mode enabled, zero is stored as zero; only storing NULL generates a sequence number.

  • Added DROP USER 'user_name'@'host_name' statement to drop an account that has no privileges.

  • The interface to aggregate user-defined functions has changed a bit. You must now declare a xxx_clear() function for each aggregate function XXX(). xxx_clear() is used instead of xxx_reset().

  • Added new ADDTIME(), DATE(), DATEDIFF(), LAST_DAY(), MAKEDATE(), MAKETIME(), MICROSECOND(), SUBTIME(), TIME(), TIMEDIFF(), TIMESTAMP(), UTC_DATE(), UTC_TIME(), UTC_TIMESTAMP(), and WEEKOFYEAR() functions.

  • Added new syntax for ADDDATE() and SUBDATE(). The second argument now may be a number representing the number of days to be added to or subtracted from the first date argument.

  • Added new type values DAY_MICROSECOND, HOUR_MICROSECOND, MINUTE_MICROSECOND, SECOND_MICROSECOND, and MICROSECOND for DATE_ADD(), DATE_SUB(), and EXTRACT().

  • Added new %f microseconds format specifier for DATE_FORMAT() and TIME_FORMAT().

  • All queries in which at least one SELECT does not use indexes properly now are written to the slow query log when long log format is used.

  • It is now possible to create a MERGE table from MyISAM tables in different databases. Formerly, all the MyISAM tables had to be in the same database, and the MERGE table had to be created in that database as well.

  • Added new COMPRESS(), UNCOMPRESS(), and UNCOMPRESSED_LENGTH() functions.

  • When using SET sql_mode='mode' for a complex mode (such as ANSI), we now update the sql_mode variable to include all the individual options implied by the complex mode.

  • Added the OLAP (On-Line Analytical Processing) function ROLLUP, which provides summary rows for each GROUP BY level.

  • Added SQLSTATE codes for all server errors.

  • Added mysql_sqlstate() and mysql_stmt_sqlstate() C API client functions that return the SQLSTATE error code for the last error.

  • TIME columns with hour values greater than 24 were returned incorrectly to the client.

  • ANALYZE TABLE, OPTIMIZE TABLE, REPAIR TABLE, and FLUSH statements are now stored in the binary log and thus replicated to slaves. This logging does not occur if the optional NO_WRITE_TO_BINLOG keyword (or its alias LOCAL) is given. Exceptions are that FLUSH LOGS, FLUSH MASTER, FLUSH SLAVE, and FLUSH TABLES WITH READ LOCK are not logged in any case. For a syntax example, see Section聽13.5.5.2, 鈥FLUSH Syntax鈥.

  • New global system variable relay_log_purge to enable or disable automatic relay log purging.

  • LOAD DATA now produces warnings that can be fetched with SHOW WARNINGS.

  • Added support for syntax CREATE TABLE table2 (LIKE table1) that creates an empty table table2 with a definition that is exactly the same as table1, including any indexes.

  • CREATE TABLE tbl_name (...) TYPE=storage_engine now generates a warning if the named storage engine is not available. The table is still created as a MyISAM table, as before.

  • Most subqueries are now much faster than before.

  • Added PURGE BINARY LOGS as an alias for PURGE MASTER LOGS.

  • Disabled the PURGE LOGS statement that was added in version 4.1.0. The statement now should be issued as PURGE MASTER LOGS or PURGE BINARY LOGS.

  • Added SHOW BDB LOGS as an alias for SHOW LOGS.

  • Added SHOW MASTER LOGS as an alias for SHOW BINARY LOGS. (In 4.1.0, SHOW MASTER LOGS was renamed to SHOW BINARY LOGS. Now you can use either one.)

  • Added Slave_IO_State and Seconds_Behind_Master columns to the output of SHOW SLAVE STATUS. Slave_IO_State indicates the state of the slave I/O thread, and Seconds_Behind_Master indicates the number of seconds by which the slave is late compared to the master.

  • The --lower-case-table-names=1 server option now also makes aliases case insensitive. (Bug#534)

  • Changed that the relay log is flushed to disk by the slave I/O thread every time it reads a relay log event. This reduces the risk of losing some part of the relay log in case of brutal crash.

Bugs fixed:

  • Fixed mysql parser not to erroneously interpret 鈥;鈥 character within /* ... */ comment as statement terminator.

  • Fixed merging types and length of result set columns for UNION operations. The types and lengths now are determined taking into account values for all SELECT statements in the UNION, not just the first SELECT.

  • Fixed a bug in privilege handling that caused connections from certain IP addresses to be assigned incorrect database-level privileges. A connection could be assigned the database privileges of the previous successful authentication from one of those IP addresses, even if the IP address username and database name were different. (Bug#1636)

  • Error-handling functions were not called properly when an error resulted from [CREATE | REPLACE| INSERT] ... SELECT statements.

  • HASH, BTREE, RTREE, ERRORS, and WARNINGS no longer are reserved words. (Bug#724)

  • Fix for bug in ROLLUP when all tables were const tables. (Bug#714)

  • Fixed a bug in UNION that prohibited NULL values from being inserted into result set columns where the first SELECT of the UNION retrieved NOT NULL columns. The type and max_length of the result column is now defined based on all UNION parts.

  • Fixed name resolution of columns of reduced subqueries in unions. (Bug#745)

  • Fixed memory overrun in subqueries in select list with WHERE clause bigger than outer query WHERE clause. (Bug#726)

  • Fixed a bug that caused MyISAM tables with FULLTEXT indexes created in 4.0.x to be unreadable in 4.1.x.

  • Fixed a data loss bug in REPAIR TABLE ... USE_FRM when used with tables that contained TIMESTAMP columns and were created in 4.0.x.

  • Fixed reduced subquery processing in ORDER BY/GROUP BY clauses. (Bug#442)

  • Fixed name resolution of outer columns of subquery in INSERT/REPLACE statements. (Bug#446)

  • Fixed bug in marking columns of reduced subqueries. (Bug#679)

  • Fixed a bug that made CREATE FULLTEXT INDEX syntax illegal.

  • Fixed a crash when a SELECT that required a temporary table (marked by Using temporary in EXPLAIN output) was used as a derived table in EXPLAIN command. (Bug#251)

  • Fixed a rare table corruption bug in DELETE from a big table with a new (created by MySQL-4.1) full-text index.

  • LAST_INSERT_ID() now returns 0 if the last INSERT statement didn't insert any rows.

  • Fixed missing last character in function output. (Bug#447)

  • Fixed a rare replication bug when a transaction spanned two or more relay logs, and the slave was stopped while executing the part of the transaction that was in the second or later relay log. Then replication would resume at the beginning of the second or later relay log, which was incorrect. (It should resume at BEGIN, in the first relay log.) (Bug#53)

  • CONNECTION_ID() now is properly replicated. (Bug#177)

  • The new PASSWORD() function in 4.1 is now properly replicated. (Bug#344)

  • Fixed a bug with double freed memory.

  • Fixed a crashing bug in UNION operations that involved temporary tables.

  • Fixed a bug that under certain circumstances could allow a privilege escalation via database wildcards in GRANT. (Bug#3924, CVE-2004-0957)

  • Fixed a crashing bug in DERIVED TABLES when EXPLAIN is used on a DERIVED TABLES with a join.

  • Fixed a crashing bug in DELETE with ORDER BY and LIMIT caused by an uninitialized array of reference pointers.

  • Fixed a bug in the USER() function caused by an error in the size of the allocated string.

  • Fixed a crashing bug when attempting to create a table containing a spatial (GIS) column with a storage engine that does not support spatial types.

  • Fixed a crashing bug in UNION caused by the empty select list and a non-existent column being used in some of the individual SELECT statements.

  • Fixed a replication bug with a 3.23 master and a 4.0 slave: The slave lost the replicated temporary tables if FLUSH LOGS was issued on the master. (Bug#254)

  • Fixed a security bug: A server compiled without SSL support still allowed connections by users who had the REQUIRE SSL option specified for their accounts.

  • When an undefined user variable was used in a updating query on the master (such as INSERT INTO t VALUES(@a), where @a had never been set by this connection before), the slave could replicate the query incorrectly if a previous transaction on the master used a user variable of the same name. (Bug#1331)

  • Fixed bug with prepared statements: Using the ? prepared statement parameter as the argument to certain functions or statement clauses caused a server crash when mysql_prepare() was invoked. (Bug#1500)

  • Fixed bug with prepared statements: after call to mysql_prepare placeholders became allowed in all consequent statements, even if they are not prepared (Bug#1946)

  • SLAVE START (which is a deprecated syntax, START SLAVE should be used instead) could crash the slave. (Bug#2516)

  • Fixed bug in ALTER TABLE RENAME, when rename to the table with the same name in another database silently dropped destination table if it existed. (Bug#2628)

  • When not specify hostname in SET PASSWORD FOR user it's now defaulted to % instead of the current host.

B.1.24.聽Changes in release 4.1.0 (03 April 2003: Alpha)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • Warning: Incompatible change: TIMESTAMP is now returned as a string of type 'YYYY-MM-DD HH:MM:SS' and different timestamp lengths are not supported.

    This change was necessary for SQL standards compliance. In a future version, a further change will be made (backward compatible with this change), allowing the timestamp length to indicate the desired number of digits of fractions of a second.

  • Renamed SHOW MASTER LOGS statement to SHOW BINARY LOGS.

  • Allow DEFAULT(col_name) in expressions; it produces the column's default value.

  • Added --compatible option to mysqldump for producing output that is compatible with other database systems or with older MySQL servers.

  • The --opt option for mysqldump now is enabled by default, as are all the options implied by --opt.

  • New CHARSET() and COLLATION() functions to return the character set and collation of a string.

  • Allow index type to be specified explicitly for some storage engines via USING type_name syntax in index definition.

  • New function IS_USED_LOCK() for determining the connection identifier of the client that holds a given advisory lock.

  • New more secure client authentication based on 45-byte passwords in the user table. (CVE-2000-0981)

  • Added old-password command to mysqladmin for changing password but storing it using the old password-hashing format.

  • New CRC32() function to compute cyclic redundancy check value.

  • On Windows, we are now using shared memory to communicate between server and client when they are running on the same machine and you are connecting to localhost.

  • REPAIR TABLE of MyISAM tables now uses less temporary disk space when sorting char columns.

  • DATE/DATETIME checking is now a bit stricter to support the ability to automatically distinguish between date, datetime, and time with microseconds. For example, dates of type YYYYMMDD HHMMDD are no longer supported; you must either have separators between each DATE/TIME part or not at all.

  • Server side help for all MySQL functions. One can now type help week in the mysql client and get help for the week() function.

  • Added new mysql_get_server_version() C API client function.

  • Fixed bug in libmysqlclient that fetched column defaults.

  • Fixed bug in mysql command-line client in interpreting quotes within comments. (Bug#539)

  • Added record_in_range() method to MERGE tables to be able to choose the right index when there are many to choose from.

  • Replication now works with RAND() and user variables @var.

  • Allow one to change mode for ANSI_QUOTES on the fly.

  • EXPLAIN SELECT now can be killed. See Section聽13.5.5.3, 鈥KILL Syntax鈥.

  • REPAIR TABLE and OPTIMIZE TABLE now can be killed. See Section聽13.5.5.3, 鈥KILL Syntax鈥.

  • Allow empty index lists to be specified for USE INDEX, IGNORE INDEX, and FORCE INDEX.

  • DROP TEMPORARY TABLE now drops only temporary tables and doesn't end transactions.

  • Added support for UNION in derived tables.

  • New faster client/server protocol that supports prepared statements, bound parameters, and bound result columns, binary transfer of data, warnings.

  • Added database and real table name (in case of alias) to the MYSQL_FIELD structure.

  • Multi-line queries: You can now issue several queries at once and then read the results in one go.

  • In CREATE TABLE foo (a INT not null primary key) the PRIMARY word is now optional.

  • In CREATE TABLE the attribute SERIAL is now an alias for BIGINT UNSIGNED NOT NULL AUTO_INCREMENT UNIQUE.

  • SELECT ... FROM DUAL is an alias for SELECT .... (To be compatible with some other database systems).

  • If one creates a too long CHAR/VARCHAR it's now automatically changed to TEXT or BLOB; One get a warning in this case.

  • One can specify the different BLOB/TEXT types with the syntax BLOB(length) and TEXT(length). MySQL automatically changes it to one of the internal BLOB/TEXT types.

  • CHAR BYTE is an alias for the CHAR BINARY data type.

  • VARCHARACTER is an alias for VARCHAR.

  • New operators integer MOD integer and integer DIV integer. DIV is now a reserved word.

  • SERIAL DEFAULT VALUE added as an alias for AUTO_INCREMENT.

  • TRUE and FALSE added as alias for 1 and 0, respectively.

  • Aliases are now forced in derived tables, as per standard SQL.

  • Fixed SELECT .. LIMIT 0 to return proper row count for SQL_CALC_FOUND_ROWS.

  • One can specify many temporary directories to be used in a round-robin fashion with: --tmpdir=dirname1:dirname2:dirname3.

  • Subqueries: SELECT * from t1 where t1.a=(SELECT t2.b FROM t2).

  • Derived tables:

    SELECT a.col1, b.col2
           FROM (SELECT MAX(col1) AS col1 FROM root_table) a,
           other_table b
           WHERE a.col1=b.col1;
    
  • Character sets to be defined per column, table and database.

  • Unicode (UTF8) support.

  • New CONVERT(... USING ...) syntax for converting string values between character sets.

  • BTREE index on MEMORY (HEAP) tables.

  • Faster embedded server (new internal communication protocol).

  • One can add a comment per column in CREATE TABLE.

  • SHOW FULL COLUMNS FROM tbl_name shows column comments.

  • ALTER DATABASE.

  • Support for GIS (Geometrical data). See Chapter聽16, Spatial Extensions.

  • SHOW [COUNT(*)] WARNINGS shows warnings from the last command.

  • One can specify a data type for a column in CREATE TABLE ... SELECT by defining the column in the CREATE part.

    CREATE TABLE foo (a TINYINT NOT NULL) SELECT b+1 AS a FROM bar;
    
  • expr SOUNDS LIKE expr same as SOUNDEX(expr)=SOUNDEX(expr).

  • Added new VARIANCE(expr) function returns the variance of expr

  • One can create a table from the existing table using CREATE [TEMPORARY] TABLE [IF NOT EXISTS] table (LIKE table). The table can be either normal or temporary.

  • New options --reconnect and --skip-reconnect for the mysql client, to reconnect automatically or not if the connection is lost.

  • START SLAVE (STOP SLAVE) no longer returns an error if the slave is started (stopped); it returns a warning instead.

  • SLAVE START and SLAVE STOP are no longer accepted by the query parser; use START SLAVE and STOP SLAVE instead.

B.2.聽Changes in release 4.0.x

B.2.1. Changes in release 4.0.30 (12 February 2007)
B.2.2. Changes in release 4.0.29 (Not released)
B.2.3. Changes in release 4.0.28 (Not released)
B.2.4. Changes in release 4.0.27 (06 May 2006)
B.2.5. Changes in release 4.0.26 (08 September 2005)
B.2.6. Changes in release 4.0.25 (05 July 2005)
B.2.7. Changes in release 4.0.24 (04 March 2005)
B.2.8. Changes in release 4.0.23 (18 December 2004)
B.2.9. Changes in release 4.0.22 (27 October 2004)
B.2.10. Changes in release 4.0.21 (06 September 2004)
B.2.11. Changes in release 4.0.20 (17 May 2004)
B.2.12. Changes in release 4.0.19 (04 May 2004)
B.2.13. Changes in release 4.0.18 (12 February 2004)
B.2.14. Changes in release 4.0.17 (14 December 2003)
B.2.15. Changes in release 4.0.16 (17 October 2003)
B.2.16. Changes in release 4.0.15 (03 September 2003)
B.2.17. Changes in release 4.0.14 (18 July 2003)
B.2.18. Changes in release 4.0.13 (16 May 2003)
B.2.19. Changes in release 4.0.12 (15 March 2003: Production)
B.2.20. Changes in release 4.0.11 (20 February 2003)
B.2.21. Changes in release 4.0.10 (29 January 2003)
B.2.22. Changes in release 4.0.9 (09 January 2003)
B.2.23. Changes in release 4.0.8 (07 January 2003)
B.2.24. Changes in release 4.0.7 (20 December 2002)
B.2.25. Changes in release 4.0.6 (14 December 2002: Gamma)
B.2.26. Changes in release 4.0.5 (13 November 2002)
B.2.27. Changes in release 4.0.4 (29 September 2002)
B.2.28. Changes in release 4.0.3 (26 August 2002: Beta)
B.2.29. Changes in release 4.0.2 (01 July 2002)
B.2.30. Changes in release 4.0.1 (23 December 2001)
B.2.31. Changes in release 4.0.0 (October 2001: Alpha)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Version 4.0 of the MySQL server includes many enhancements and new features:

For a full list of changes, please refer to the changelog sections for each individual 4.0.x release.

B.2.1.聽Changes in release 4.0.30 (12 February 2007)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

This is a bugfix release for the MySQL 4.0 release family.

This section documents all changes and bug fixes that have been applied since the last official MySQL release. If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise.

Bugs fixed:

  • Idle connections were not killed during timeout when using the Native POSIX Thread Library (NPTL) and mysqld. In the course of this fix, code to detect and handle the NPTL has been backported from 4.1 to 4.0. (Bug#16995)

B.2.2.聽Changes in release 4.0.29 (Not released)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

This is a bugfix release for the MySQL 4.0 release family.

This section documents all changes and bug fixes that have been applied since the last official MySQL release. If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise.

Bugs fixed:

  • InnoDB exhibited thread thrashing with more than 50 concurrent connections under an update-intensive workload. (Bug#22868)

  • InnoDB showed substandard performance with multiple queries running concurrently. (Bug#15815)

  • User-defined variables could consume excess memory, leading to a crash caused by the exhaustion of resources available to the MEMORY storage engine, due to the fact that this engine is used by MySQL for variable storage and intermediate results of GROUP BY queries. Where SET had been used, such a condition could instead give rise to the misleading error message You may only use constant expressions with SET, rather than Out of memory (Needed NNNNNN bytes). (Bug#23443)

B.2.3.聽Changes in release 4.0.28 (Not released)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

This is a bugfix release for the MySQL 4.0 release family.

This section documents all changes and bug fixes that have been applied since the last official MySQL release. If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise.

Functionality added or changed:

  • The mysqldumpslow script has been moved from client RPM packages to server RPM packages. This corrects a problem where mysqldumpslow could not be used with a client-only RPM install, because it depends on my_print_defaults which is in the server RPM. (Bug#20216)

Bugs fixed:

  • Deleting entries from a large MyISAM index could cause index corruption when it needed to shrink. Deletes from an index can happen when a record is deleted, when a key changes and must be moved, and when a key must be un-inserted because of a duplicate key. This can also happen in REPAIR TABLE when a duplicate key is found and in myisamchk when sorting the records by an index. (Bug#22384)

  • Transient errors in replication from master to slave may trigger multiple Got fatal error 1236: 'binlog truncated in the middle of event' errors on the slave. (Bug#4053)

  • A server or network failure with an open client connection would cause the client to hang even though the server was no longer available. (Bug#9678)

  • mysqlhotcopy did not copy RAID directories with names that contained non-decimal hex digits. (It copied only directories containing the characters 0 through 9 and ignored those containing a through f.) (Bug#18777)

  • Using SELECT and a table join while running a concurrent INSERT operation would join incorrect rows. (Bug#14400)

  • A query with a WHERE clause containing column = ELT(int_value_1, value_list) OR column = ELT(int_value_2, value_list) could return unexpected results. (Bug#12728)

B.2.4.聽Changes in release 4.0.27 (06 May 2006)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

This is a security fix release and bugfix release for the MySQL 4.0 release family.

This release includes the patches for recently reported security vulnerabilites in the MySQL client-server protocol. We would like to thank Stefano Di Paola for finding and reporting these to us.

Functionality added or changed:

  • The MySQL-server RPM now explicitly assigns the mysql system user to the mysql user group during the postinstallation process. This corrects an issue with upgrading the server on some Linux distributions whereby a previously existing mysql user was not changed to the mysql group, resulting in wrong groups for files created following the installation. (Bug#12823)

  • Better detection of connection timeout for replication servers on Windows allows elimination of extraneous Lost connection errors in the error log. (Bug#5588)

Bugs fixed:

  • Security fix: A malicious client, using specially crafted invalid login or COM_TABLE_DUMP packets was able to read uninitialized memory, which potentially, though unlikely in MySQL, could have led to an information disclosure. (CVE-2006-1516, CVE-2006-1517) Thanks to Stefano Di Paola for finding and reporting this bug.

  • MySQL-shared-compat-4.0.26-0.i386.rpm incorrectly depend on glibc 2.3 and cannot not be installed on a glibc 2.2 system. For MySQL 4.0, we recommend using the older MySQL-shared-compat-4.0.25-0.i386.rpm package. (Bug#16539)

  • Running myisampack followed by myisamchk with the --unpack option would corrupt the auto_increment key. (Bug#12633)

  • When myisamchk needed to rebuild a table, AUTO_INCREMENT information was lost. (Bug#10405)

  • Avoid trying to include <asm/atomic.h> when it doesn't work in C++ code. (Bug#13621)

  • BIT_COUNT() could return an incorrect value for right table columns in a LEFT JOIN. (Bug#13044)

  • MySQL would not compile on Linux distributions that use the tinfo library. (Bug#18912)

  • An UPDATE statement which tried to update a column with a name beginning with an asterisk would cause the server to crash. This was because the server would wrongly expand the * character to the list of all table columns, causing the list of columns to become longer than the list of values. Now the server performs this expansion only if the * character is followed by a space. (Bug#16510)

  • An INSERT ... SELECT statement between tables in a MERGE set can return errors when statement involves insert into child table from merge table or vice-versa. (Bug#5390)

  • Fixed problems with static variables to allow building on Fedora Core 3. (Bug#6554)

  • A LIMIT-related optimization failed to take into account that MyISAM table indexes can be disabled, causing Error 124 when it tried to use such an index. (Bug#14616)

  • For a table that had been opened with HANDLER OPEN, issuing OPTIMIZE TABLE, ALTER TABLE, or REPAIR TABLE caused a server crash. (Bug#14397)

  • Queries of the form (SELECT ...) ORDER BY ... were being treated as a UNION. This improperly resulted in only distinct values being returned (because UNION by default eliminates duplicate results). Also, references to column aliases in ORDER BY clauses following parenthesized SELECT statements were not resolved properly. (Bug#7672)

  • SELECT DISTINCT with a GROUP BY clause caused a server crash. (Bug#13855)

  • SHOW CREATE TABLE did not display any FOREIGN KEY clauses if a temporary file could not be created. Now SHOW CREATE TABLE displays an error message in an SQL comment if this occurs. (Bug#13002)

  • MySQL programs in binary distributions for Solaris 8/9/10 x86 systems would not run on Pentium III machines. (Bug#6772)

  • Queries against a MERGE table that has a composite index could produce incorrect results. (Bug#9112)

  • The counters for the Key_read_requests, Key_reads, Key_write_requests, and Key_writes status variables were changed from unsigned long to unsigned longlong to accommodate larger values before the variables roll over and restart from 0. (Bug#12920)

  • A concurrency problem for CREATE ... SELECT could cause a server crash. (Bug#12845)

  • On HP-UX 11.x (PA-RISC), the -L option caused mysqlimport to crash. (Bug#12958)

  • The server crashed when one thread resized the query cache while another thread was using it. (Bug#12848)

B.2.5.聽Changes in release 4.0.26 (08 September 2005)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • Added the mysql_get_client_version C API function to the embedded server library. (It was present in the regular client library but inadvertently omitted from the embedded library.) (Bug#10266)

Bugs fixed:

  • An optimizer estimate of zero rows for a non-empty InnoDB table used in a left or right join could cause incomplete rollback for the table. (Bug#12779)

  • Query cache is switched off if a thread (connection) has tables locked. This prevents invalid results where the locking thread inserts values between a second thread connecting and selecting from the table. (Bug#12385)

  • For PKG installs on Mac OS X, the preinstallation and postinstallation scripts were being run only for new installations and not for upgrade installations, resulting in an incomplete installation process. (Bug#11380)

  • On Windows, applications that used the embedded server made it not possible to remove certain files in the data directory, even after the embedded server had been shut down. This occurred because a file descriptor was being held open. (Bug#12177)

  • Creation of the mysql group account failed during the RPM installation. (Bug#12348)

  • Attempting to repair a table having a fulltext index on a column containing words whose length exceeded 21 characters and where myisam_repair_threads was greater than 1 would crash the server. (Bug#11684)

  • When two threads compete for the same table, a deadlock could occur if one thread has also a lock on another table through LOCK TABLES and the thread is attempting to remove the table in some manner and the other thread want locks on both tables. (Bug#10600)

B.2.6.聽Changes in release 4.0.25 (05 July 2005)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

Bugs fixed:

  • On Mac OS X, libmysqlclient_r.a now is built with --fno-common to make it possible to link a shared two-level namespace library against libmysqlclient_r.a. (Bug#10638)

  • An error in the implementation of the MyISAM compression algorithm caused myisampack to fail with very large sets of data (total size of all the records in a single column needed to be >= 3 GB in order to trigger this issue). (Bug#8321)

  • A problem with the my_global.h file caused compilation of MySQL to fail on single-processor Linux systems running 2.6 kernels. (Bug#10364)

  • Fixed a portability problem testing for crypt() support that caused compilation problems when using OpenSSL/yaSSL on HP-UX and Mac OS X. (Bug#10675, Bug#11150)

  • MyISAM table corruption could occur with ANALYZE TABLE if a write lock was acquired with LOCK TABLES and then an INSERT or DELETE was done prior to analyzing the table. (Bug#10901)

  • Fixed a server crash resulting from CREATE TABLE ... SELECT that selected from a table being altered by ALTER TABLE. (Bug#10224)

  • InnoDB: In DROP DATABASE, check for all referencing tables from other databases before dropping any tables. (Bug#10335)

  • Fixed a problem with incorrect constant propagation resulting in incorrect evaluation of AND/OR queries. (Bug#10095)

  • Fixed wrong buffer usage for auto-increment key with blob part that caused CHECK TABLE to report that the table was wrong. (Bug#10045)

  • No error was raised for BOOLEAN full-text searches for storage engines that do not support full-text. (Bug#7709)

  • The test in configure to see whether CXX specified gcc failed if gcc was specified as a full pathname. (Bug#9690)

  • In the mysql_real_escape_string() C API function, when a multi-byte character is encountered that is illegal in the current character set, escape only the first byte, not each byte. This avoids creating a valid character from an invalid one. (Bug#9864; this is a backport of Bug#8378 from MySQL 4.1.11 to 4.0.25)

  • Fixed a deadlock resulting from use of FLUSH TABLES WITH READ LOCK while an INSERT DELAYED statement is in progress. (Bug#7823)

  • Fixed a segmentation fault in mysqlcheck that occurred when the last table checked in --auto-repair mode returned an error (such as the table being a MERGE table). (Bug#9492)

  • Fixed faulty display of TIMESTAMP columns retrieved as col_name+0 while the new system variable is set to 1. (Bug#8894)

  • Queries containing CURRENT_USER() incorrectly were registered in the query cache. (Bug#9796)

  • An UPDATE that updated only some of the columns in a multiple-column index could result in a loop. (Bug#8942)

  • REPAIR TABLE did not invalidate query results in the query cache that were generated from the table. (Bug#8480)

  • Fixed a bug that caused concurrent inserts to be allowed into the tables in the SELECT ... UNION ... part of INSERT ... SELECT ... UNION .... This could result in the incorrect order of queries in the binary log. (Bug#9922)

  • Fixed a bug that under certain circumstances could allow a privilege escalation via database wildcards in GRANT. (Bug#3924, CVE-2004-0957)

  • <=> was not properly comparing NULL values in the WHERE clause of outer joins. (Bug#8711)

  • InnoDB: Fixed a bug: MySQL-4.0.23 and 4.0.24 could complain that an InnoDB table created with MySQL-3.23.49 or earlier was in the new compact InnoDB table format of 5.0.3 or later, and InnoDB would refuse to use that table. (The same bug exists in 4.1.8 - 4.1.10.) There is nothing wrong with the table, it is mysqld that is in error. Workaround: wait that 4.0.25 or 4.1.11 is released before doing an upgrade, or dump the table and re-create it with any MySQL version >= 3.23.50 before upgrading to 4.0.23 or 4.0.24.

B.2.7.聽Changes in release 4.0.24 (04 March 2005)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • Security improvement: The server creates .frm, .MYD, .MYI, .MRG, .ISD, and .ISM table files only if a file with the same name does not already exist. Thanks to Stefano Di Paola for finding and informing us about this issue. (CVE-2005-0711)

  • Security improvement: User-defined functions should have at least one symbol defined in addition to the xxx symbol that corresponds to the main xxx() function. These auxiliary symbols correspond to the xxx_init(), xxx_deinit(), xxx_reset(), xxx_clear(), and xxx_add() functions. mysqld by default no longer loads UDFs unless they have at least one auxiliary symbol defined in addition to the main symbol. The --allow-suspicious-udfs option controls whether UDFs that have only an xxx symbol can be loaded. By default, the option is off. mysqld also checks UDF filenames when it reads them from the mysql.func table and rejects those that contain directory pathname separator characters. (It already checked names as given in CREATE FUNCTION statements.) See Section聽19.2.4.1, 鈥淯DF Calling Sequences for Simple Functions鈥, Section聽19.2.4.2, 鈥淯DF Calling Sequences for Aggregate Functions鈥, and Section聽19.2.4.6, 鈥淯ser-Defined Function Security Precautions鈥. Thanks to Stefano Di Paola for finding and informing us about this issue. (CVE-2005-0709, CVE-2005-0710)

  • InnoDB: Added configuration option and settable global variable innodb_autoextend_increment for setting the size in megabytes by which InnoDB tablespaces are extended when they become full. The default value is 8, corresponding to the fixed increment of 8MB in previous versions of MySQL.

  • InnoDB: Do not acquire an internal InnoDB table lock in LOCK TABLES if AUTOCOMMIT=1. This helps in porting old MyISAM applications to InnoDB. InnoDB table locks in that case caused deadlocks very easily.

Bugs fixed:

  • AES_DECRYPT(col_name,key) could fail to return NULL for invalid values in col_name, if col_name was declared as NOT NULL. (Bug#8669)

  • FOUND_ROWS() returned an incorrect value after a SELECT SQL_CALC_FOUND_ROWS DISTINCT statement that selected constants and included GROUP BY and LIMIT clauses. (Bug#7945)

  • Index cardinality was not being updated properly for TEMPORARY tables under some circumstances, such as CREATE TABLE ... SELECT followed by ANALYZE TABLE. (Bug#7519)

  • Fixed a server crash caused by DELETE FROM tbl_name ... WHERE ... ORDER BY tbl_name.col_name when the ORDER BY column was qualified with the table name. (Bug#8392)

  • Fixed a bug in MATCH ... AGAINST in natural language mode that could cause a server crash if the FULLTEXT index was not used in a join (EXPLAIN did not show fulltext join mode) and the search query matched no rows in the table (Bug#8522).

  • Platform and architecture information in version information produced for --version option on Windows was always Win95/Win98 (i32). More accurately determine platform as Win32 or Win64 for 32-bit or 64-bit Windows, and architecture as ia32 for x86, ia64 for Itanium, and axp for Alpha. (Bug#4445)

  • Fixed an optimization problem that allowed a negative number to be stored in a DOUBLE UNSIGNED column when it was assigned a value from a signed DOUBLE column. (Bug#7700)

  • Fixed a failure of multiple-table updates to replicate properly on slave servers when --replicate-*-table options had been specified. (Bug#7011)

  • Renamed set_bit() and clear_bit() functions in source code to avoid a conflict with functions of the same names in Linux kernel header files. (Bug#7971)

  • Part of the information being used to cache access-permission lookups was not always reinitialized properly, particularly for connections from localhost on Windows. The result was connection failures that appeared to occur randomly. (Bug#5569)

  • Corrected a problem with the QUOTE() function returning bad results. (Bug#8248)

  • Fixed a problem where INSERT INTO ...SELECT failed when the source and target table were the same. (Bug#6034)

  • Fixed a problem where RPM installation on Linux as a non-privileged user would result in incomplete installation. (Bug#7347)

  • Change thread stack size used for building Linux RPM distributions to avoid warnings about stack size during server startup. (Bug#6226)

  • Fixed a symlink vulnerability in the mysqlaccess script. Reported by Javier Fernandez-Sanguino Pena and Debian Security Audit Team. (CVE-2005-0004)

  • Fixed support for C API function mysql_list_fields(), which was accidentally broken in 4.0.22 (Bug#6761)

  • Make query_cache_wlock_invalidate system variable visible in SHOW VARIABLES output. (Bug#7594)

  • Fixed a bug which caused FROM_UNIXTIME() function to return NULL for zero argument instead of the Epoch. (Bug#7515)

  • Now in datetime values two digit year is interpreted as year in 20th or 21st century even with zero month and day. (Bug#7297)

  • Fixed a bug in QUOTE function when used in conjunction with some other string functions. This lead to severe buffer overflow and server crashing. (Bug#7495)

  • InnoDB: Work around a problem in AIX 5.1 patched with ML7 security patch: InnoDB would refuse to open its ibdata files, complaining about an operating system error 0.

  • InnoDB: Fixed a memory corruption bug if one created a table with a primary key that contained at least two column prefixes. An example: CREATE TABLE t(a char(100), b tinyblob, PRIMARY KEY(a(5), b(10))).

  • InnoDB: Use native tmpfile() function on Netware. All InnoDB temporary files are created under sys:\tmp. Previously, InnoDB temporary files were never deleted on Netware.

  • InnoDB: Honor the --tmpdir startup option when creating temporary files. Previously, InnoDB temporary files were always created in the temporary directory of the operating system. On Netware, InnoDB will continue to ignore --tmpdir. (Bug#5822)

  • InnoDB: Fix a theoretical hang over the adaptive hash latch in InnoDB if one runs INSERT ... SELECT ... (binlog not enabled), or a multiple-table UPDATE or DELETE, and only the read tables are InnoDB type, the rest are MyISAM; this also fixes Bug#7879 for InnoDB type tables. (Bug#7879)

  • InnoDB: Fixed a bug: 32-bit mysqld binaries built on HP-UX-11 did not work with InnoDB files greater than 2 GB in size. (Bug#6189)

  • InnoDB: Fixed a bug: InnoDB failed to drop a table in the background drop queue if the table was referenced by a foreign key constraint.

  • InnoDB: Fixed a bug: if we dropped a table where an INSERT was waiting for a lock to check a FOREIGN KEY constraint, then an assertion would fail in lock_reset_all_on_table(), since that operation assumes no waiting locks on the table or its records.

  • Fixed that, when encountering a 鈥disk full鈥 or 鈥quota exceeded鈥 write error, MyISAM sometimes didn't sleep and retry the write, thus resulting in a corrupted table. (Bug#7714)

  • Fixed that a slave could crash after replicating many ANALYZE TABLE, OPTIMIZE TABLE, or REPAIR TABLE statements from the master. (Bug#6461, Bug#7658)

  • Fixed a bug where MySQL was allowing concurrent updates (inserts, deletes) to a table if binary logging is enabled. Changed to ensure that all updates are executed in a serialized fashion, because they are executed serialized when binlog is replayed. (Bug#7879)

  • Fixed a bug in replication that caused the master to stamp generated statements (such as SET commands) with an error_code intended only for another statement. This could happen, for example, when a statements generates a duplicate key error on the master but must be replicated. (Bug#8412)

  • Documented problem with using mysqldump in 4.0.x to dump TIMESTAMP(2) and TIMESTAMP(4) data types. (Bug#6530)

B.2.8.聽Changes in release 4.0.23 (18 December 2004)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Note: Due to a libtool-related bug in the source distribution, the creation of shared libmysqlclient libraries was not possible (the resulting files were missing the .so file name extension). The file ltmain.sh was updated to fix this problem and the resulting source distribution was released as mysql-4.0.23a.tar.gz. This modification did not affect the binary packages. (Bug#7401)

Functionality added or changed:

  • Added --hex-blob option to mysqldump for dumping binary string columns using hexadecimal notation.

  • Added mysql_hex_string() C API function that hex-encodes a string.

  • InnoDB: Do not periodically write SHOW INNODB STATUS information to a temporary file unless the configuration option innodb_status_file=1 is set.

  • InnoDB: Made the foreign key parser better aware of quotes. (Bug#6340)

  • mysqlbinlog now prints an informative commented line (thread id, timestamp, server id, and so forth) before each LOAD DATA INFILE, like it does for other queries; unless --short-form is used.

Bugs fixed:

  • A multiple-table DELETE could cause MySQL to crash when using InnoDB tables. (Bug#5837, Bug#6378)

  • Corrected accounts in the mysql.user table in Windows distributions that had been created with a Host value of build rather than %. (Bug#6000)

  • Prevent adding CREATE TABLE .. SELECT query to the binary log when the insertion of new records partially failed. (Bug#6682)

  • Fixed bug which caused FROM_UNIXTIME() function to return wrong result if the argument was too big. (Bug#6439)

  • Fixed bug which caused MySQL server to store wrong values in TIMESTAMP columns and give wrong results for UNIX_TIMESTAMP() function if it was run in time zone with leap seconds. (Bug#6387)

  • InnoDB: Fixed a bug in LOAD DATA INFILE鈥EPLACE printing duplicate key error when executing the same load query several times. (Bug#5835)

  • InnoDB: Refuse to open new-style tables created with MySQL 5.0.3 or later. (Bug#7089)

  • InnoDB: Do not call rewind() when displaying SHOW INNODB STATUS information on stderr.

  • InnoDB: If one used INSERT IGNORE to insert several rows at a time, and the first inserts were ignored because of a duplicate key collision, then InnoDB in a replication slave assigned AUTO_INCREMENT values 1 bigger than in the master. This broke the MySQL replication. (Bug#6287)

  • InnoDB: Fix two hangs: FOREIGN KEY constraints treated table and database names as case-insensitive. RENAME TABLE t TO T would hang in an endless loop if t had a foreign key constraint defined on it. Fix also a hang over the dictionary mutex that would occur if one tried in ALTER TABLE or RENAME TABLE to create a foreign key constraint name that collided with another existing name. (Bug#3478)

  • InnoDB: Treat character 0xA0 as space in InnoDB's FOREIGN KEY parser if MySQL treats it as space in the default charset. EMS MySQL Manager inserts character 0xA0 after the table name in an ALTER, which confused InnoDB's parser.

  • Fixed a bug which caused a crash when only the slave I/O thread was stopped and restarted. (Bug#6148)

  • If a connection had an open transaction but had done no updates to transactional tables (for example if had just done a SELECT FOR UPDATE then executed a non-transactional update, that update automatically committed the transaction (thus releasing InnoDB's row-level locks etc). (Bug#5714)

  • If a connection was interrupted by a network error and did a rollback, the network error code got stored into the BEGIN and ROLLBACK binary log events; that caused superfluous slave stops. (Bug#6522)

  • A sequence of BEGIN (or SET AUTOCOMMIT=0), FLUSH TABLES WITH READ LOCK, transactional update, COMMIT, FLUSH TABLES WITH READ LOCK could hang the connection forever and possibly the MySQL server itself. This happened for example when running the innobackup script several times. (Bug#6732)

B.2.9.聽Changes in release 4.0.22 (27 October 2004)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • The --with-openssl option for configure now accepts a path prefix as an argument. --with-openssl-includes and --with-openssl-libs are still supported, but are needed only to override the default values. (Bug#5494)

  • Added new --without-man option to configure to suppress building/installing the manual pages. (Bug#5379)

  • InnoDB: New mysqld option --innodb-table-locks and session variable innodb_table_locks (on by default). In applications using AUTOCOMMIT=1 and MySQL's LOCK TABLES command, InnoDB's internal table locks that were added in 4.0.20 can cause deadlocks. You can set innodb_table_locks=0 in my.cnf to remove that problem. See Section聽14.2.17, 鈥淩estrictions on InnoDB Tables鈥. (Bug#3299, Bug#5998)

  • InnoDB: Added the startup option and settable global variable innodb_max_purge_lag for delaying INSERT, UPDATE and DELETE operations when the purge operations are lagging. The default value of this parameter is zero, meaning that there are no delays. See Section聽14.2.13, 鈥淚mplementation of Multi-Versioning鈥.

  • InnoDB: Change error code to HA_ERR_ROW_IS_REFERENCED if we cannot DROP a parent table because it is referenced by a FOREIGN KEY constraint.

Bugs fixed:

  • Fixed bug in server which caused connection stall when one of deprecated libmysqlclient functions mysql_create_db(), mysql_rm_db() were called and were going to return error. (Bug#6081)

  • Fixed returning wrong query result from query cache if a temporary table was hiding a real table after putting results to query cache. (Bug#6084)

  • Fixed ENABLE KEYS, which failed if tmpdir ran out of space. Now, a full repair is done in this case. (Bug#5625)

  • Fixed an improper error message when trying to drop a table which is referenced by a FOREIGN KEY constraint. (Bug#5784)

  • Fixed a bug that allowed FLUSH TABLE(S) to close HANDLER tables. HANDLER tables are now reopened after a FLUSH TABLE(S) the next time they are used. However, they lose their file position if this happens. (Bug#4286)

  • Fixed a bug that allowed HANDLER tables with the same alias to be opened multiple times. HANDLER aliases must now be unique, even though it is syntactically correct in versions below 4.1 to qualify them with their base table's database name (for example, test_db.handler_tbl now conflicts with another_db.handler_tbl). (Bug#4335)

  • Fixed crash when using MySQL 4.0 with privilege tables from MySQL 5.0.

  • mysqlimport now reads input files locally from the client host only if the --local option is given. Previously, it assumed incorrectly in some cases that files were local even without --local. (Bug#5829)

  • InnoDB: Make the check for excessive semaphore waits to tolerate glitches in the system clock (do not crash the server if the system time is adjusted while InnoDB is under load.). (Bug#5898)

  • InnoDB: Fixed a bug in the InnoDB FOREIGN KEY parser that prevented ALTER TABLE of tables containing 鈥#鈥 in their names. (Bug#5856)

  • InnoDB: Fixed problem introduced in 4.0.21 where a connection starting a transaction, doing updates, then FLUSH TABLES WITH READ LOCK, then COMMIT, would cause replication slaves to stop (complaining about error 1223). Bug surfaced when using the InnoDB innobackup script. (Bug#5949)

  • InnoDB: If one updated a column so that its size changed, or updated it to an externally stored (TEXT or BLOB) value, then ANOTHER externally stored column would show up as 512 bytes of good data + 20 bytes of garbage in a consistent read that fetched the old version of the row. (Bug#5960)

  • InnoDB: Release the dictionary latch during a long cascaded FOREIGN KEY operation, so that we do not starve other users doing CREATE TABLE or other DDL operations. This caused a notorious 'Long semaphore wait' message to be printed to the .err log. (Bug#5961)

  • InnoDB: Let InnoDB remember row locking type (X or S) inside LOCK TABLES, also over plain consistent read SELECTs.

  • InnoDB: Fixed a bug introduced in 4.0.21. An assertion failed if one used mysqldump with the option -l or --opt, or if one used LOCK TABLES ... LOCAL. (Workaround in 4.0.21: use --quick and --single-transaction. (Bug#5538)

  • InnoDB: Having a column prefix index in the primary key, and the same column fully in a secondary key could cause an assertion failure in row_build_row_ref(). (Bug#5180)

  • Fixed a bug which resulted in an erroneously calculated number of examined rows in UNIONs. This value is printed in the slow query log. (Bug#5879)

  • Fixed bug with crash of server on some values of read_rnd_buffer_size (Bug#5492)

  • Fixed bug which caused truncation of values read from or into TIMESTAMP fields if --new mode was enabled. (Bug#4131)

  • mysqladmin now returns a status of 0 even when the server denies access; such an error means the server is running. (Bug#3120)

  • Fixed that if the slave SQL thread found a syntax error in a query (which should be rare, as the master parsed it successfully), it stops. (Bug#5711)

  • Fixed that if a write to a MyISAM table fails because of a full disk or an exceeded disk quota, it prints a message to the error log every 10 minutes, and waits until disk becomes free. (Bug#3248)

  • Fixed problem with symlinked databases on Windows being shown with SHOW DATABASES even if the database name doesn't match the given wildcard (Bug#5539)

B.2.10.聽Changes in release 4.0.21 (06 September 2004)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • Print version_comment (from ./configure --comment during compilation) when starting the server. Example: Version: '4.0.21-debug' socket: '/tmp/mysql.sock' port: 0 Official MySQL Binary

  • Made the MySQL server not react to signals SIGHUP and SIGQUIT on Mac OS X 10.3. This is needed because under this OS, the MySQL server receives lots of these signals (reported as Bug#2030).

  • On Windows, the mysqld-nt and mysqld-max-nt servers now write error messages to the Windows event log in addition to the MySQL error log.

Bugs fixed:

  • Fixed an old bug in concurrent accesses to MERGE tables (even one MERGE table and MyISAM tables), that could've resulted in a crash or hang of the server. (Bug#2408, CVE-2004-0837)

  • Fixed a bug that caused incorrect results from GROUP BY queries with expression in HAVING clause that refers to a columns such as BLOB, TEXT, or TINYBLOB. (Bug#4358)

  • Fixed a bug when memory was not released when HEAP table is dropped. It could only happen on Windows when a symlink file (.sym) is used and if that symlink file contained double backslashes (\\). (Bug#4973)

  • Fixed a bug which prevented TIMESTAMP(19) fields from being created. (Bug#4491)

  • Fixed a bug that caused wrong results in queries that were using index to search for NULL values in BLOB (TINYBLOB, TEXT, TINYTEXT, etc) columns of MyISAM tables. (Bug#4816)

  • Fixed a bug in the function ROUND() reporting incorrect metadata (number of digits after the decimal point). It can be seen, for example, in CREATE TABLE t1 SELECT ROUND(1, 34). (Bug#4393)

  • Fixed precision loss bug in some mathematical functions such as SQRT() and LOG(). (Bug#4356)

  • Fixed a long-standing problem with LOAD DATA with the LOCAL option. The problem occurs when an error happens during the LOAD DATA operation. Previously, the connection was broken. Now the error message is returned and connection stays open.

  • Optimizer now treats col IN (val) the same way it does for col = val.

  • Fixed a problem with net_buffer_length when building the DBD::mysql Perl module. (Bug#4206)

  • lower_case_table_names=2 (keep case for table names) was not honored with ALTER TABLE and CREATE/DROP INDEX. (Bug#3109)

  • Fixed a crash on declaration of DECIMAL(0,...) column. (Bug#4046)

  • Fixed a bug in IF() function incorrectly determining the result type if aggregate functions were involved. (Bug#3987)

  • Fixed bug in privilege checking where, under some conditions, one was able to grant privileges on the database, he has no privileges on. (Bug#3933)

  • Fixed crash in MATCH ... AGAINST() on a phrase search operator with a missing closing double quote. (Bug#3870, CVE-2004-0956)

  • Fixed a bug with truncation of big values (> 4294967295) of 64-bit system variables. (Bug#3754)

  • If server-id was not set using startup options but with SET GLOBAL, the replication slave still complained that it was not set. (Bug#3829)

  • Fixed potential memory overrun in mysql_real_connect() (which required a compromised DNS server and certain operating systems). (Bug#4017, CVE-2004-0836)

  • During the installation process of the server RPM on Linux, mysqld was run as the root system user, and if you had --log-bin=somewhere_out_of_var_lib_mysql it created binary log files owned by root in this directory, which remained owned by root after the installation. This is now fixed by starting mysqld as the mysql system user instead. (Bug#4038)

  • Made DROP DATABASE honor the value of lower_case_table_names. (Bug#4066)

  • The slave SQL thread refused to replicate INSERT ... SELECT if it examined more than 4 billion rows. (Bug#3871)

  • Fixed incorrect destruction of expression which led to crash of server on complex AND/OR expressions if query was ignored (either by a replication server because of --replicate-*-table rules, or by any MySQL server because of a syntax error). (Bug#3969, Bug#4494)

  • Fixed that mysqlbinlog --position --read-from-remote-server had wrong # at lines. (Bug#4506)

  • If CREATE TEMPORARY TABLE t SELECT failed while loading the data, the temporary table was not dropped. (Bug#4551)

  • Fixed that when a multiple-table DROP TABLE failed to drop a table on the master server, the error code was not written to the binary log. (Bug#4553)

  • When the slave SQL thread was replicating a LOAD DATA INFILE statement, it didn't show the statement in the output of SHOW PROCESSLIST. (Bug#4326)

  • Fixed that CREATE TABLE ... TYPE=HEAP ... AS SELECT... caused replication slave to stop. (Bug#4971)

  • Fixed that disable-local-infile option had no effect if client read it from a configuration file using mysql_options(...,MYSQL_READ_DEFAULT,...). (Bug#5073)

  • Fixed that mysql-test-run failed on the rpl_trunc_binlog test if running test from the installed (the target of 'make install') directory. (Bug#5050)

  • Fixed an unlikely deadlock which could happen when using KILL. (Bug#4810)

  • Fixed a crash when one connection got KILLed while it was doing START SLAVE. (Bug#4827)

  • Made FLUSH TABLES WITH READ LOCK block COMMIT if server is running with binary logging; this ensures that the binary log position is trustable when doing a full backup of tables and the binary log. (Bug#4953)

  • Fixed that the counter of an auto_increment column was not reset by TRUNCATE TABLE is the table was a temporary one. (Bug#5033)

  • Made database names to compare case-insensitively in fully qualified column names (database.table.column) when lower_case_table_names=1. (Bug#4792)

  • Fixed that SET CHARACTER SET was not replicated correctly. MySQL 4.1 does not have that bug. (Bug#4500)

B.2.11.聽Changes in release 4.0.20 (17 May 2004)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Note: The windows packages had to be repackaged and re-released several times to resolve packaging issues (such as missing files). This did not affect the binaries included (they have not been recompiled), therefore the installation packages are of version 4.0.20d, while the binaries included still identify themselves as version 4.0.20b.

Functionality added or changed:

  • From the Windows distribution, predefined accounts without passwords for remote users ("root@%", "@%") were removed (other distributions never had them).

  • Phrase search in MATCH ... AGAINST ( ... IN BOOLEAN MODE) no longer matches partial words.

Bugs fixed:

  • A crashing bug (race condition) was fixed in InnoDB diagnostic logging. It was introduced in 4.0.19. (Bug#3596)

  • Fixed a bug in division / reporting incorrect metadata (number of digits after the decimal point). It can be seen, for example, in CREATE TABLE t1 SELECT "0.01"/"3". (Bug#3612)

  • Fixed a problem with non-working DROP DATABASE on some configurations (in particular, Linux 2.6.5 with ext3 are known to expose this bug). (Bug#3594)

  • Fixed a symlink vulnerability in the mysqlhotcopy script. (CVE-2004-0457)

  • Fixed that in some replication error messages, a very long query caused the rest of the message to be invisible (truncated), by putting the query last in the message. (Bug#3357)

B.2.12.聽Changes in release 4.0.19 (04 May 2004)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Note: The MySQL 4.0.19 binaries were uploaded to the download mirrors on May, 10th. However, a potential crashing bug was found just before the 4.0.19 release was publicly announced and published from the 4.0 download pages at http://dev.mysql.com/.

A fix for the bug was pushed into the MySQL source tree shortly after it could be reproduced and is included in MySQL 4.0.20. Users upgrading from MySQL 4.0.18 should upgrade directly to MySQL 4.0.20 or later.

See (Bug#3596) for details (it was reported against MySQL-4.1, but was confirmed to affect 4.0.19 as well).

Functionality added or changed:

  • If length of a timestamp field is defined as 19, the timestamp is displayed as "YYYY-MM-DD HH:MM:SS. This is done to make it easier to use tables created in MySQL 4.1 to be used in MySQL 4.0.

  • If you use RAID_CHUNKS with a value > 255 it is set to 255. This was made to ensure that all raid directories are always 2 hex bytes. (Bug#3182)

  • Changed that the optimizer now considers the index specified in FORCE INDEX clause as a candidate to resolve ORDER BY as well.

  • The --log-warnings server option now is enabled by default. Disable with --skip-log-warnings.

  • Until now, in SELECT ... UNION SELECT ... ORDER BY ..., it was possible to qualify a column name in the ORDER BY clause with a table name. This is no longer possible. Column names in ORDER BY should refer to names established in the first SELECT of the UNION. (Bug#3064)

  • Added max_insert_delayed_threads system variable as a synonym for max_delayed_threads.

  • Added query_cache_wlock_invalidate system variable. It allows emulation of MyISAM table write-locking behavior, even for queries in the query cache. (Bug#2693)

  • The keyword MASTER_SERVER_ID is not reserved anymore.

  • The following is relevant mainly for Mac OS X users who use a case-insensitive filesystem. This is not relevant for Windows users as InnoDB in this case always stores filenames in lower case:

    You can now force lower_case_table_names to 0 from the command line or a configuration file. This is useful with case-insensitive filesystems when you have previously not used lower_case_table_names=1 or lower_case_table_names=2 and you have created InnoDB tables. With lower_case_table_names=0, InnoDB tables were stored in mixed case while setting lower_case_table_names to a non-zero value now forces it to lower case (to make the table names case insensitive).

    Because it's possible to crash MyISAM tables by referring to them with different case on a case-insensitive filesystem, we recommend that you use lower_case_table_names or lower_case_table_names=2 on such filesystems.

    The easiest way to convert to use lower_case_table_names=2 is to dump all your InnoDB tables with mysqldump, drop them and then restore them.

  • Changed that the relay log is flushed to disk by the slave I/O thread every time it reads a relay log event. This reduces the risk of losing some part of the relay log in case of brutal crash.

  • When a session having open temporary tables terminates, the statement automatically written to the binary log is now DROP TEMPORARY TABLE IF EXISTS instead of DROP TEMPORARY TABLE, for more robustness.

  • Added option --replicate-same-server-id.

Bugs fixed:

  • Added missing full-text variable ft_stopword_file to myisamchk.

  • Don't allow stray ',' at the end of field specifications. (Bug#3481)

  • INTERVAL now can handle big values for seconds, minutes and hours. (Bug#3498)

  • Blank hostname did not work as documented for table and column privileges. Now it's works the same way as '%'. (Bug#3473)

  • Fixed a harmless buffer overflow in replace utility. (Bug#3541)

  • Fixed SOUNDEX() to ignore non-alphabetic characters also in the beginning of the string. (Bug#3556)

  • Fixed a bug in MATCH ... AGAINST() searches when another thread was doing concurrent inserts into the MyISAM table in question. The first --- full-text search --- query could return incorrect results in this case (for example, 鈥phantom鈥 rows or not all matching rows, even an empty result set). The easiest way to check whether you are affected is to start mysqld with --skip-concurrent-insert switch and see whether it helps.

  • Fixed bug when doing DROP DATABASE on a directory containing non- MySQL files. Now a proper error message is returned.

  • Fixed bug in ANALYZE TABLE on a BDB table inside a transaction that hangs server thread. (Bug#2342)

  • Fixed a symlink vulnerability in the mysqlbug script. (Bug#3284, CVE-2004-0381)

  • Fixed core dump bug in SELECT DISTINCT where all selected parts where constants and there were hidden columns in the created temporary table. (Bug#3203)

  • Fixed core dump bug in COUNT(DISTINCT) when there was a lot of values and one had a big value for max_heap_table_size.

  • Fixed problem with multiple-table-update and BDB tables. (Bug: #3098)

  • Fixed memory leak when dropping database with RAID tables. (Bug#2882)

  • Fixed core dump crash in replication during relay-log switch when the relay log went over max_relay_log_size and the slave thread did a flush_io_cache() at the same time.

  • Fixed hangup bug when issuing multiple SLAVE START from different threads at the same time. (Bug#2921)

  • Fixed bug when using DROP DATABASE with lower_case_table_names=2.

  • Fixed wrong result in UNION when using lower_case_table_names=2. (Bug#2858)

  • One can now kill threads that is 'stuck' in the join optimizer (can happen when there is MANY tables in the join in which case the optimizer can take really long time). (Bug#2825)

  • Rollback DELETE and UPDATE statements if thread is killed. (Bug#2422)

  • Ensure that all rows in an INSERT DELAYED statement is written at once if binary logging is enabled. (Bug#2491).

  • Fixed bug in query cache statistic, more accurate formula linked statistic variables mentioned in the manual.

  • Fixed a bug in parallel repair (myisamchk -p, myisam_repair_threads) - sometimes repair process failed to repair a table. (Bug#1334)

  • Fixed bugs with names of tables, databases, and columns that end to space (Bug#2985)

  • Fixed a bug in multiple-table UPDATE statements involving at least one constant table. Bug was exhibited in allowing non matching row to be updated. (Bug#2996).

  • Fixed all bugs in scripts for creating/upgrading system database (Bug#2874) Added tests which guarantee against such bugs in the future.

  • Fixed bug in mysql command-line client in interpreting quotes within comments. (Bug#539)

  • --set-character-set and --character-sets-dir options in myisamchk now work.

  • Fixed a bug in mysqlbinlog that caused one pointer to be free'd twice in some cases.

  • Fixed a bug in boolean full-text search, that sometimes could lead to false matches in queries with several levels of subexpressions using + operator (for example, MATCH ... AGAINST('+(+(word1 word2)) +word3*' IN BOOLEAN MODE).

  • Fixed Windows-specific portability bugs in myisam_ftdump.

  • Fixed a bug in multiple-table DELETE that was caused by foreign key constraints. If the order of the tables established by MySQL optimizer did not match parent-child order, no rows were deleted and no error message was provided. (Bug#2799)

  • Fixed a few years old bug in the range optimizer that caused a segmentation fault on some very rare queries. (Bug#2698)

  • Replication: If a client connects to a slave server and issues an administrative statement for a table (for example, OPTIMIZE TABLE or REPAIR TABLE), this could sometimes stop the slave SQL thread. This does not lead to any corruption, but you must use START SLAVE to get replication going again. (Bug#1858) The bug was accidentally not fixed in 4.0.17 as it was unfortunately earlier said.

  • Fixed that when a Rotate event is found by the slave SQL thread in the middle of a transaction, the value of Relay_Log_Pos in SHOW SLAVE STATUS remains correct. (Bug#3017)

  • Corrected the master's binary log position that InnoDB reports when it is doing a crash recovery on a slave server. (Bug#3015)

  • Changed that when a DROP TEMPORARY TABLE statement is automatically written to the binary log when a session ends, the statement is recorded with an error code of value zero (this ensures that killing a SELECT on the master does not result in a superfluous error on the slave). (Bug#3063)

  • Changed that when a thread handling INSERT DELAYED (also known as a delayed_insert thread) is killed, its statements are recorded with an error code of value zero (killing such a thread does not endanger replication, so we thus avoid a superfluous error on the slave). (Bug#3081)

  • Fixed deadlock when two START SLAVE commands were run at the same time. (Bug#2921)

  • Fixed that a statement never triggers a superfluous error on the slave, if it must be excluded given the --replicate-* options. The bug was that if the statement had been killed on the master, the slave would stop. (Bug#2983)

  • The --local-load option of mysqlbinlog now requires an argument.

  • Fixed a segmentation fault when running LOAD DATA FROM MASTER after RESET SLAVE. (Bug#2922)

  • Fixed a rare error condition that caused the slave SQL thread spuriously to print the message Binlog has bad magic number and stop when it was not necessary to do so. (Bug#3401)

  • Fixed bug in privilege checking of ALTER TABLE RENAME. (Bug#3270, CVE-2004-0835)

  • Fixed the column Exec_master_log_pos (and its disk image in the relay-log.info file) to be correct if the master had version 3.23 (it was too big by 6 bytes). This bug does not exist in the 5.0 version. (Bug#3400)

  • Fixed that mysqlbinlog does not forget to print a USE command under rare circumstances where the binary log contained a LOAD DATA INFILE command. (Bug#3415)

  • Fixed a memory corruption when replicating a LOAD DATA INFILE when the master had version 3.23. Some smaller problems remain in this setup, See Section聽6.7, 鈥淩eplication Features and Known Problems鈥. (Bug#3422)

  • Multiple-table DELETE statements were always replicated by the slave if there were some --replicate-*-ignore-table options and no --replicate-*-do-table options. (Bug#3461)

  • Fixed a crash of the MySQL slave server when it was built with --with-debug and replicating itself. (Bug#3568)

B.2.13.聽Changes in release 4.0.18 (12 February 2004)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • Fixed processing of LOAD DATA by mysqlbinlog in remote mode. (Bug#1378)

  • The ft_dump utility program was renamed to myisam_ftdump, and is included in binary distributions.

  • ENGINE is now a synonym for the TYPE option for CREATE TABLE and ALTER TABLE.

  • lower_case_table_names system variable now can take a value of 2, to store table names in mixed case on case-insensitive filesystems. It's forced to 2 if the database directory is located on a case-insensitive filesystem.

  • For replication of MEMORY (HEAP) tables: Made the master automatically write a DELETE FROM statement to its binary log when a MEMORY table is opened for the first time since master's startup. This is for the case where the slave has replicated a non-empty MEMORY table, then the master is shut down and restarted: the table is now empty on master; the DELETE FROM empties it on slave too. Note that even with this fix, between the master's restart and the first use of the table on master, the slave still has out-of-date data in the table. But if you use the init-file option to populate the MEMORY table on the master at startup, it ensures that the failing time interval is zero. (Bug#2477)

  • Optimizer is now better tuned for the case where the first used key part (of many) is a constant. (Bug#1679)

  • Removed old non-working --old-rpl-compat server option, which was a holdover from the very first 4.0.x versions. (Bug#2428)

  • Added option --sync-frm. It's on by default, to instruct MySQL to sync to disk each time .frm file is created. Use --disable-sync-frm to disable.

Bugs fixed:

  • mysqlhotcopy now works on NetWare.

  • DROP DATABASE could not drop databases with RAID tables that had more than nine RAID_CHUNKS. (Bug#2627)

  • Fixed bug in range optimizer when using overlapping ranges. (Bug#2448)

  • Limit wait_timeout to 2147483 on Windows (OS limit). (Bug#2400)

  • Fixed bug when --init-file crashes MySQL if it contains a large SELECT. (Bug#2526)

  • SHOW KEYS now shows NULL in the Sub_part column for FULLTEXT indexes.

  • The signal thread's stack size was increased to enable mysqld to run on Debian/IA-64 with a TLS-enabled glibc. (Bug#2599)

  • Now only the SELECT privilege is needed for tables that are only read in multiple-table UPDATE statements. (Bug#2377)

  • Give proper error message if one uses LOCK TABLES ... ; INSERT ... SELECT and one used the same table in the INSERT and SELECT part. (Bug#2296)

  • SELECT INTO ... DUMPFILE now deletes the generated file on error.

  • Fixed foreign key reference handling to allow references to column names that contain spaces. (Bug#1725)

  • Fixed problem with index reads on character columns with BDB tables. The symptom was that data could be returned in the wrong lettercase. (Bug#2509)

  • Fixed a spurious table corruption problem that could sometimes appear on tables with indexed TEXT columns if these columns happened to contain values having trailing spaces. This bug was introduced in 4.0.17.

  • Fixed a problem where some queries could hang if a condition like indexed_TEXT_column = expr was present and the column contained values having trailing spaces. This bug was introduced in 4.0.17.

  • Fixed a bug that could cause incorrect results from a query that involved range conditions on indexed TEXT columns that happened to contain values having trailing spaces. This bug was introduced in 4.0.17. (Bug#2295)

  • Fixed incorrect path names in some of the manual pages. (Bug#2270)

  • Fixed spurious 鈥table corrupted鈥 errors in parallel repair operations. See Section聽5.2.3, 鈥淪ystem Variables鈥.

  • Fixed a crashing bug in parallel repair operations. See Section聽5.2.3, 鈥淪ystem Variables鈥.

  • Fixed bug in updating MyISAM tables for BLOB values longer than 16MB. (Bug#2159)

  • Fixed bug in mysqld_safe when running multiple instances of MySQL. (Bug#2114)

  • Fixed a bug in using HANDLER statement with tables not from a current database. (Bug#2304)

  • Fixed a crashing bug that occurred due to the fact that multiple-table UPDATE statements did not check that there was only one table to be updated. (Bug#2103)

  • Fixed a crashing bug that occurred due to BLOB data type index size being calculated incorrectly in MIN() and MAX() optimizations. (Bug#2189)

  • Fixed a bug with incorrect syntax for LOCK TABLES in mysqldump. (Bug#2242)

  • Fixed a bug in mysqld_safe that caused mysqld to generate a warning about duplicate user=xxx options if this option was specified in the [mysqld] or [server] sections of my.cnf. (Bug#2163)

  • INSERT DELAYED ... SELECT ... could cause table corruption because tables were not locked properly. This is now fixed by ignoring DELAYED in this context. (Bug#1983)

  • Replication: Sometimes the master gets a non-fatal error during the execution of a statement that does not immediately succeed. (For example, a write to a MyISAM table may first receive 鈥no space left on device,鈥 but later complete when disk space becomes available. See Section聽A.1.4.3, 鈥淗ow MySQL Handles a Full Disk鈥.) The bug was that the master forgot to reset the error code to 0 after success, so the error code got into its binary log, thus causing the slave to issue false alarms such as 鈥did not get the same error as on master.鈥 (Bug#2083)

  • Removed a misleading 鈥check permissions on master.info鈥 from a replication error message, because the cause of the problem could be something other than permissions. (Bug#2121)

  • Fixed a crash when the replication slave was unable to create the first relay log. (Bug#2145)

  • Replication of LOAD DATA INFILE for an empty file from a 3.23 master to a 4.0 slave caused the slave to print an error. (Bug#2452)

  • When automatically forcing lower_case_table_names to 1 if the file system was case insensitive, mysqld could crash. This bug existed only in MySQL 4.0.17. (Bug#2481)

  • Restored ability to specify default values for TIMESTAMP columns that was erroneously disabled in previous release. (Bug#2539) Fixed SHOW CREATE TABLE to reflect these values. (Bug#1885) Note that because of the auto-update feature for the first TIMESTAMP column in a table, it makes no sense to specify a default value for the column. Any such default is silently ignored (unless another TIMESTAMP column is added before this one). Also fixed the meaning of the DEFAULT keyword when it is used to specify the value to be inserted into a TIMESTAMP column other than the first. (Bug#2464)

  • Fixed bug for out-of-range arguments on QNX platform that caused UNIX_TIMESTAMP() to produce incorrect results or that caused non-zero values to be inserted into TIMESTAMP columns. (Bug#2523) Also, current time zone now is taken into account when checking if datetime values satisfy both range boundaries for TIMESTAMP columns. The range allowed for a TIMESTAMP column is time zone-dependent and equivalent to a range of 1970-01-01 00:00:01 UTC to 2037-12-31 23:59:59 UTC.

  • Multiple-table DELETE statements were never replicated by the slave if there were any --replicate-*-table options. (Bug#2527)

  • Changes to session counterparts of variables query_prealloc_size, query_alloc_block_size, trans_prealloc_size, trans_alloc_block_size now have an effect. (Bug#1948)

  • Fixed bug in ALTER TABLE RENAME, when rename to the table with the same name in another database silently dropped destination table if it existed. (Bug#2628)

B.2.14.聽Changes in release 4.0.17 (14 December 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • mysqldump no longer dumps data for MERGE tables. (Bug#1846)

  • lower_case_table_names is now forced to 1 if the database directory is located on a case-insensitive filesystem. (Bug#1812)

  • Symlink creation is now disabled on systems where realpath() doesn't work. (Before one could use CREATE TABLE .. DATA DIRECTORY=.. even if HAVE_BROKEN_REALPATH was defined. This is now disabled to avoid problems when running ALTER TABLE).

  • Inserting a negative AUTO_INCREMENT value in a MyISAM table no longer updates the AUTO_INCREMENT counter to a big unsigned value. (Bug#1366)

  • Added four new modes to WEEK(..., mode) function. See WEEK(date: (mode)). (Bug#1178)

  • Allow UNION DISTINCT syntax.

  • MySQL now syncs to disk each time .frm file is created.

  • mysql_server_init() now returns 1 if it can't initialize the environment. (Previously mysql_server_init() called exit(1) if it could not create a key with pthread_key_create(). (Bug#2062)

  • Allow spaces in Windows service names.

  • Changed the default Windows service name for mysqld from MySql to MySQL. This should not affect usage, because service names are not case sensitive.

  • When you install mysqld as a service on Windows systems, mysqld reads startup options in option files from the option group with the same name as the service name. (Except when the service name is MySQL).

Bugs fixed:

  • Sending SIGHUP to mysqld crashed the server if it was running with --log-bin. (Bug#2045)

  • One can now configure MySQL as a Windows service as a normal user. (Bug#1802). Thanks to Richard Hansen for fixing this.

  • Database names are now compared in lowercase in ON clauses when lower_case_table_names is set. (Bug#1736)

  • IGNORE ... LINES option to LOAD DATA INFILE didn't work when used with fixed length rows. (Bug#1704)

  • Fixed problem with UNIX_TIMESTAMP() for timestamps close to 0. (Bug#1998)

  • Fixed problem with character values greater than 128 in the QUOTE() function. (Bug#1868)

  • Fixed searching of TEXT with endspace. (Bug#1651)

  • Fixed caching bug in multiple-table updates where same table was used twice. (Bug#1711)

  • Fixed directory permissions for the MySQL-server RPM documentation directory. (Bug#1672)

  • Fixed server crash when updating an ENUM column that is set to the empty string (for example, with REPLACE()). (Bug#2023)

  • mysql client program now correctly prints connection identifier returned by mysql_thread_id() as unsigned integer rather than as signed integer. (Bug#1951)

  • FOUND_ROWS() could return incorrect number of rows after a query with an impossible WHERE condition. (Bug#1468)

  • SHOW DATABASES no longer shows .sym files (on Windows) that do not point to a valid directory. (Bug#1385)

  • Fixed a possible memory leak on Mac OS X when using the shared libmysql.so library. (from pthread_key_create()). (Bug#2061)

  • Fixed bug in UNION statement with alias *. (Bug#1249)

  • Fixed a bug in DELETE ... ORDER BY ... LIMIT where the rows were not deleted in the proper order. (Bug#1024, Bug#1697).

  • Fixed serious problem with multi-threaded programs on Windows that used the embedded MySQL libraries. (Locks of tables were not handled correctly between different threads).

  • Code cleanup: Fixed a few code defects (potential memory leaks, null pointer dereferences, uninitialized variables). Thanks to Reasoning Inc. for informing us about these findings.

  • Fixed a buffer overflow error that occurred with prepended 鈥0鈥 characters in some columns of type DECIMAL. (Bug#2128)

  • Filesort was never shown in EXPLAIN if query contained an ORDER BY NULL clause. (Bug#1335)

  • Fixed invalidation of whole query cache on DROP DATABASE. (Bug#1898)

  • Fixed bug in range optimizer that caused wrong results for some unlikely AND/OR queries. (Bug#1828)

  • Fixed a crash in ORDER BY when ordering by expression and identifier. (Bug#1945)

  • Fixed a crash in an open HANDLER when an ALTER TABLE was executed in a different connection. (Bug#1826)

  • Fixed a bug in trunc* operator of full-text search which sometimes caused MySQL not to find all matched rows.

  • Fixed bug in prepending 鈥0鈥 characters to DECIMAL column values.

  • Fixed optimizer bug, introduced in 4.0.16, when REF access plan was preferred to more efficient RANGE on another column.

  • Fixed problem when installing a MySQL server as a Windows service using a command of the form mysqld --install mysql --defaults-file=path-to-file. (Bug#1643)

  • Fixed an incorrect result from a query that uses only const tables (such as one-row tables) and non-constant expression (such as RAND()). (Bug#1271)

  • Fixed bug when the optimizer did not take SQL_CALC_FOUND_ROWS into account if LIMIT clause was present. (Bug#1274)

  • mysqlbinlog now asks for a password at the console when the -p or --password option is used with no argument. This is consistent with the way that other clients such mysqladmin and mysqldump behave. Note: A consequence of this change is that it is no longer possible to invoke mysqlbinlog as mysqlbinlog -p pass_val (with a space between the -p option and the following password value). (Bug#1595)

  • Fixed bug accidentally introduced in 4.0.16 where the slave SQL thread deleted its replicated temporary tables when STOP SLAVE was issued.

  • In a 鈥chain鈥 replication setup A->B->C, if 2 sessions on A updated temporary tables of the same name at the same time, the binary log of B became incorrect, resulting in C becoming confused. (Bug#1686)

  • In a 鈥chain鈥 replication setup A->B->C, if STOP SLAVE was issued on B while it was replicating a temporary table from A, then when START SLAVE was issued on B, the binary log of B became incorrect, resulting in C becoming confused. (Bug#1240)

  • When MASTER_LOG_FILE and MASTER_LOG_POS were not specified, CHANGE MASTER used the coordinates of the slave I/O thread to set up replication, which broke replication if the slave SQL thread lagged behind the slave I/O thread. This caused the slave SQL thread to lose some events. The new behavior is to use the coordinates of the slave SQL thread instead. See Section聽13.6.2.1, 鈥CHANGE MASTER TO Syntax鈥. (Bug#1870)

  • Now if integer is stored or converted to TIMESTAMP or DATETIME value checks of year, month, day, hour, minute and second ranges are performed and numbers representing illegal timestamps are converted to 0 value. This behavior is consistent with manual and with behavior of string to TIMESTAMP/DATETIME conversion. (Bug#1448)

  • Fixed bug when BIT_AND() and BIT_OR() group functions returned incorrect value if SELECT used a temporary table and no rows were found. (Bug#1790).

  • BIT_AND() is now unsigned in all contexts. This means that it now returns 18446744073709551615 (= 0xffffffffffffffff) instead of -1 if there were no rows in the result.

  • Fixed bug with BIT_AND() still returning signed value for an empty set in some cases. (Bug#1972)

  • Fixed bug with ^ (XOR) and >> (bit shift) still returning signed value in some cases. (Bug#1993)

  • Replication: a rare race condition in the slave SQL thread, which could lead to a wrong complain that the relay log is corrupted. (Bug#2011)

  • Replication: in the slave SQL thread, a multiple-table UPDATE could produce a wrong complain that some record was not found in one table, if the UPDATE was preceded by a INSERT ... SELECT. (Bug#1701)

  • Fixed deficiency in MySQL code which is responsible for scanning directories. This deficiency caused SHOW TABLE STATUS to be very slow when a database contained a large number of tables, even if a single particular table were specified. (Bug#1952)

B.2.15.聽Changes in release 4.0.16 (17 October 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • Option values in option files now may be quoted. This is useful for values that contain whitespace or comment characters.

  • Write memory allocation information to error log when doing mysqladmin debug. This works only on systems that support the mallinfo() call (like newer Linux systems).

  • Added the following new system variables to allow more precise memory allocation: range_alloc_block_size, query_alloc_block_size, query_prealloc_size, transaction_alloc_block_size, and transaction_prealloc_size.

  • mysqlbinlog now reads option files. To make this work, you must now specify --read-from-remote-server when reading binary logs from a MySQL server. (Note that using a remote server is deprecated and may disappear in future mysqlbinlog versions).

  • Block SIGPIPE signals also for non-threaded programs. The blocking is moved from mysql_init() to mysql_server_init(), which is automatically called on the first call to mysql_init().

  • Added --libs_r and --include options to mysql_config.

  • New `> prompt for mysql. This prompt is similar to the '> and "> prompts, but indicates that an identifier quoted with backticks was begun on an earlier line and the closing backtick has not yet been seen.

  • Updated mysql_install_db to be able to use the local machine's IP address instead of the hostname when building the initial grant tables if skip-name-resolve has been specified. This option can be helpful on FreeBSD to avoid thread-safety problems with the FreeBSD resolver libraries. (Thanks to Jeremy Zawodny for the patch.)

  • A documentation change: Added a note that when backing up a slave, it is necessary also to back up the master.info and relay-log.info files, as well as any SQL_LOAD-* files located in the directory specified by the --slave-load-tmpdir option. All these files are needed when the slave resumes replication after you restore the slave's data.

Bugs fixed:

  • Fixed a spurious error ERROR 14: Can't change size of file (Errcode: 2) on Windows in DELETE FROM tbl_name without a WHERE clause or TRUNCATE TABLE tbl_name, when tbl_name is a MyISAM table. (Bug#1397)

  • Fixed a bug that resulted in thr_alarm queue is full warnings after increasing the max_connections variable with SET GLOBAL. (Bug#1435)

  • Made LOCK TABLES to work when Lock_tables_priv is granted on the database level and Select_priv is granted on the table level.

  • Fixed crash of FLUSH QUERY CACHE on queries that use same table several times (Bug#988).

  • Fixed core dump bug when setting an enum system variable (such as SQL_WARNINGS) to NULL.

  • Extended the default timeout value for Windows clients from 30 seconds to 1 year. (The timeout that was added in MySQL 4.0.15 was way too short). This fixes a bug that caused ERROR 2013: Lost connection to MySQL server during query for queries that lasted longer than 30 seconds, if the client didn't specify a limit with mysql_options(). Users of 4.0.15 on Windows should upgrade to avoid this problem.

  • More 鈥out of memory鈥 checking in range optimizer.

  • Fixed and documented a problem when setting and using a user variable within the same SELECT statement. (Bug#1194).

  • Fixed bug in overrun check for BLOB values with compressed tables. This was a bug introduced in 4.0.14. It caused MySQL to regard some correct tables containing BLOB values as corrupted. (Bug#770, Bug#1304, and maybe Bug#1295)

  • SHOW GRANTS showed USAGE instead of the real column-level privileges when no table-level privileges were given.

  • When copying a database from the master, LOAD DATA FROM MASTER dropped the corresponding database on the slave, thus erroneously dropping tables that had no counterpart on the master and tables that may have been excluded from replication using --replicate-*-table rules. Now LOAD DATA FROM MASTER no longer drops the database. Instead, it drops only the tables that have a counterpart on the master and that match the --replicate-*-table rules. --replicate-*-db rules can still be used to include or exclude a database as a whole from LOAD DATA FROM MASTER. A database also is included or excluded as a whole if there are some rules like --replicate-wild-do-table=db1.% or --replicate-wild-ignore-table=db1.%, as is the case for CREATE DATABASE and DROP DATABASE in replication. (Bug#1248)

  • Fixed a bug where mysqlbinlog crashed with a segmentation fault when used with the -h or --host option. (Bug#1258)

  • Fixed a bug where mysqlbinlog crashed with a segmentation fault when used on a binary log containing only final events for LOAD DATA. (Bug#1340)

  • mysqlbinlog does not reuse temporary filenames from previous runs. Previously mysqlbinlog failed if was used several times on the same binary log file that contained a LOAD DATA command.

  • Fixed compilation problem when compiling with OpenSSL 0.9.7 with disabled old DES support (If OPENSSL_DISABLE_OLD_DES_SUPPORT option was enabled).

  • Fixed a bug when two (or more) MySQL servers were running on the same machine, and they were both slaves, and at least one of them was replicating some LOAD DATA INFILE command from its master. The bug was that one slave MySQL server sometimes deleted the SQL_LOAD-* files (used for replication of LOAD DATA INFILE and located in the slave-load-tmpdir directory, which defaults to tmpdir) belonging to the other slave MySQL server of this machine, if these slaves had the same slave-load-tmpdir directory. When that happened, the other slave could not replicate LOAD DATA INFILE and complained about not being able to open some SQL_LOAD-* file. (Bug#1357)

  • If LOAD DATA INFILE failed for a small file, the master forgot to write a marker (a Delete_file event) in its binary log, so the slave could not delete 2 files (SQL_LOAD-*.info and SQL_LOAD-*.data from its tmpdir. (Bug#1391)

  • On Windows, the slave forgot to delete a SQL_LOAD-*.info file from tmpdir after successfully replicating a LOAD DATA INFILE command. (Bug#1392)

  • When a connection terminates, MySQL writes DROP TEMPORARY TABLE statements to the binary log for all temporary tables which the connection had not explicitly dropped. MySQL forgot to use backticks to quote the database and table names in the statement. (Bug#1345)

  • On some 64-bit machines (some HP-UX and Solaris machines), a slave installed with the 64-bit MySQL binary could not connect to its master (it connected to itself instead). (Bug#1256, Bug#1381)

  • Code was introduced in MySQL 4.0.15 for the slave to detect that the master had died while writing a transaction to its binary log. This code reported an error in a legal situation: When the slave I/O thread was stopped while copying a transaction to the relay log, the slave SQL thread would later pretend that it found an unfinished transaction. (Bug#1475)

B.2.16.聽Changes in release 4.0.15 (03 September 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

IMPORTANT:

If you are using this release on Windows, you should upgrade at least your clients (any program that uses libmysql.lib) to 4.0.16 or above. This is because the 4.0.15 release had a bug in the Windows client library that causes Windows clients using the library to die with a Lost connection to MySQL server during query error for queries that take more than 30 seconds. This problem is specific to Windows; clients on other platforms are unaffected.

Functionality added or changed:

  • mysqldump now correctly quotes all identifiers when communicating with the server. This assures that during the dump process, mysqldump never sends queries to the server that result in a syntax error. This problem is not related to the mysqldump program's output, which was not changed. (Bug#1148)

  • Change result set metadata information so that MIN() and MAX() report that they can return NULL (this is true because an empty set returns NULL). (Bug#324)

  • Produce an error message on Windows if a second mysqld server is started on the same TCP/IP port as a running mysqld server.

  • The mysqld system variables wait_timeout, net_read_timeout, and net_write_timeout now work on Windows. One can now also set timeouts for read and writes in Windows clients with mysql_options().

  • Added option --sql-mode=NO_DIR_IN_CREATE to make it possible for slaves to ignore INDEX DIRECTORY and DATA DIRECTORY options given to CREATE TABLE. When this is mode is on, SHOW CREATE TABLE does not show the given directories.

  • SHOW CREATE TABLE now shows the INDEX DIRECTORY and DATA DIRECTORY options, if they were specified when the table was created.

  • The open_files_limit system variable now shows the real open files limit.

  • MATCH ... AGAINST() in natural language mode now treats words that are present in more than 2,000,000 rows as stopwords.

  • The Mac OS X installation disk images now include an additional MySQLStartupItem.pkg package that enables the automatic startup of MySQL on system startup. See Section聽2.5, 鈥淚nstalling MySQL on Mac OS X鈥.

  • Most of the documentation included in the binary tarball distributions (.tar.gz) has been moved into a subdirectory docs. See Section聽2.1.5, 鈥淚nstallation Layouts鈥.

  • The manual is now included as an additional info file in the binary distributions. (Bug#1019)

  • The binary distributions now include the embedded server library (libmysqld.a) by default. Due to a linking problem with non-gcc compilers, it was not included in all packages of the initial 4.0.15 release. The affected packages were rebuilt and released as 4.0.15a. See Section聽1.6.1, 鈥淢ySQL 4.0 in a Nutshell鈥.

  • MySQL can now use range optimization for BETWEEN with non-constant limits. (Bug#991)

  • Replication error messages now include the default database, so that users can check which database the failing query was run for.

  • A documentation change: Added a paragraph about how the binlog-do-db and binlog-ignore-db options are tested against the database on the master (see Section聽5.11.4, 鈥淭he Binary Log鈥), and a paragraph about how --replicate-do-db, --replicate-do-table and analogous options are tested against the database and tables on the slave (see Section聽6.8, 鈥淩eplication Startup Options鈥).

  • Now the slave does not replicate SET PASSWORD if it is configured to exclude the mysql database from replication (using for example --replicate-wild-ignore-table=mysql.%). This was the case for GRANT and REVOKE since version 4.0.13 (although there was Bug#980 in 4.0.13 & 4.0.14, which has been fixed in 4.0.15).

  • Rewrote the information shown in the State column of SHOW PROCESSLIST for replication threads and for MASTER_POS_WAIT() and added the most common states for these threads to the documentation, see Section聽6.3, 鈥淩eplication Implementation Details鈥.

  • Added a test in replication to detect the case where the master died in the middle of writing a transaction to the binary log; such unfinished transactions now trigger an error message on the slave.

  • A GRANT command that creates an anonymous user (that is, an account with an empty username) no longer requires FLUSH PRIVILEGES for the account to be recognized by the server. (Bug#473)

  • CHANGE MASTER now flushes relay-log.info. Previously this was deferred to the next run of START SLAVE, so if mysqld was shutdown on the slave after CHANGE MASTER without having run START SLAVE, the relay log's name and position were lost. At restart they were reloaded from relay-log.info, thus reverting to their old (incorrect) values from before CHANGE MASTER and leading to error messages (as the old relay log did not exist any more) and the slave threads refusing to start. (Bug#858)

Bugs fixed:

  • Fixed buffer overflow in password handling which could potentially be exploited by MySQL users with ALTER privilege on the mysql.user table to execute random code or to gain shell access with the UID of the mysqld process (thanks to Jedi/Sector One for spotting and reporting this bug).

  • Fixed server crash on FORCE INDEX in a query that contained "Range checked for each record" in the EXPLAIN output. (Bug#1172)

  • Fixed table/column grant handling: The proper sort order (from most specific to less specific, see Section聽5.7.6, 鈥淎ccess Control, Stage 2: Request Verification鈥) was not honored. (Bug#928)

  • Fixed rare bug in MYISAM introduced in 4.0.3 where the index file header was not updated directly after an UPDATE of split dynamic rows. The symptom was that the table had a corrupted delete-link if mysqld was shut down or the table was checked directly after the update.

  • Fixed Can't unlock file error when running myisamchk --sort-index on Windows. (Bug#1119)

  • Fixed possible deadlock when changing key_buffer_size while the key cache was actively used. (Bug#1088)

  • Fixed overflow bug in MyISAM and ISAM when a row is updated in a table with a large number of columns and at least one BLOB/TEXT column.

  • Fixed incorrect result when doing UNION and LIMIT #,# when braces were not used around the SELECT parts.

  • Fixed incorrect result when doing UNION and ORDER BY .. LIMIT # when one didn't use braces around the SELECT parts.

  • Fixed problem with SELECT SQL_CALC_FOUND_ROWS ... UNION ALL ... LIMIT # where FOUND_ROWS() returned incorrect number of rows.

  • Fixed unlikely stack bug when having a BIG expression of type 1+1-1+1-1... in certain combinations. (Bug#871)

  • Fixed the bug that sometimes prevented a table with a FULLTEXT index from being marked as "analyzed".

  • Fixed MySQL so that the column length (in C API) for the second column in SHOW CREATE TABLE is always larger than the data length. The only known application that was affected by the old behavior was Borland dbExpress, which truncated the output from the command. (Bug#1064)

  • Fixed crash in comparisons of strings using the tis620 character set. (Bug#1116)

  • Fixed ISAM bug in MAX() optimization.

  • myisamchk --sort-records=N no longer marks table as crashed if sorting failed because of an inappropriate key. (Bug#892)

  • Fixed a minor bug in MyISAM compressed table handling that sometimes made it impossible to repair compressed table in "Repair by sort" mode. "Repair with keycache" (myisamchk --safe-recover) worked, though. (Bug#1015)

  • Fixed bug in propagating the version number to the manual included in the distribution files. (Bug#1020)

  • Fixed key sorting problem (a PRIMARY key declared for a column that is not explicitly marked NOT NULL was sorted after a UNIQUE key for a NOT NULL column).

  • Fixed the result of INTERVAL when applied to a DATE value. (Bug#792)

  • Fixed compiling of the embedded server library in the RPM spec file. (Bug#959)

  • Added some missing files to the RPM spec file and fixed some RPM building errors that occurred on Red Hat Linux 9. (Bug#998)

  • Fixed incorrect XOR evaluation in WHERE clause. (Bug#992)

  • Fixed bug with processing in query cache merged tables constructed from more then 255 tables. (Bug#930)

  • Fixed incorrect results from outer join query (for example, LEFT JOIN) when ON condition is always false, and range search in used. (Bug#926)

  • Fixed a bug causing incorrect results from MATCH ... AGAINST() in some joins. (Bug#942)

  • MERGE tables do not ignore Using index (from EXPLAIN output) anymore.

  • Fixed a bug that prevented an empty table from being marked as "analyzed". (Bug#937)

  • Fixed myisamchk --sort-records crash when used on compressed table.

  • Fixed slow (as compared to 3.23) ALTER TABLE and related commands such as CREATE INDEX. (Bug#712)

  • Fixed segmentation fault resulting from LOAD DATA FROM MASTER when the master was running without the --log-bin option. (Bug#934)

  • Fixed a security bug: A server compiled without SSL support still allowed connections by users who had the REQUIRE SSL option specified for their accounts.

  • Fixed a random bug: Sometimes the slave would replicate GRANT or REVOKE queries even if it was configured to exclude the mysql database from replication (for example, using --replicate-wild-ignore-table=mysql.%). (Bug#980)

  • The Last_Errno and Last_Error fields in the output of SHOW SLAVE STATUS are now cleared by CHANGE MASTER and when the slave SQL thread starts. (Bug#986)

  • A documentation mistake: It said that RESET SLAVE does not change connection information (master host, port, user, and password), whereas it does. The statement resets these to the startup options (master-host etc) if there were some. (Bug#985)

  • SHOW SLAVE STATUS now shows correct information (master host, port, user, and password) after RESET SLAVE (that is, it shows the new values, which are copied from the startup options if there were some). (Bug#985)

  • Disabled propagation of the original master's log position for events because this caused unexpected values for Exec_Master_Log_Pos and problems with MASTER_POS_WAIT() in A->B->C replication setup. (Bug#1086)

  • Fixed a segmentation fault in mysqlbinlog when --position=x was used with x being between a Create_file event and its fellow Append_block, Exec_load or Delete_file events. (Bug#1091)

  • mysqlbinlog printed superfluous warnings when using --database, which caused syntax errors when piped to mysql. (Bug#1092)

  • Made mysqlbinlog --database filter LOAD DATA INFILE too (previously, it filtered all queries except LOAD DATA INFILE). (Bug#1093)

  • mysqlbinlog in some cases forgot to put a leading '#' in front of the original LOAD DATA INFILE (this command is displayed only for information, not to be run; it is later reworked to LOAD DATA LOCAL with a different filename, for execution by mysql). (Bug#1096)

  • binlog-do-db and binlog-ignore-db incorrectly filtered LOAD DATA INFILE (it was half-written to the binary log). This resulted in a corrupted binary log, which could cause the slave to stop with an error. (Bug#1100)

  • When, in a transaction, a transactional table (such as an InnoDB table) was updated, and later in the same transaction a non-transactional table (such as a MyISAM table) was updated using the updated content of the transactional table (with INSERT ... SELECT for example), the queries were written to the binary log in an incorrect order. (Bug#873)

  • When, in a transaction, INSERT ... SELECT updated a non-transactional table, and ROLLBACK was issued, no error was returned to the client. Now the client is warned that some changes could not be rolled back, as this was the case for normal INSERT. (Bug#1113)

  • Fixed a potential bug: When STOP SLAVE was run while the slave SQL thread was in the middle of a transaction, and then CHANGE MASTER was used to point the slave to some non-transactional statement, the slave SQL thread could get confused (because it would still think, from the past, that it was in a transaction).

B.2.17.聽Changes in release 4.0.14 (18 July 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • Added default_week_format system variable. The value is used as the default mode for the WEEK() function.

  • mysqld now reads an additional option file group having a name corresponding to the server's release series: [mysqld-4.0] for 4.0.x servers, [mysqld-4.1] for 4.1.x servers, and so forth. This allows options to be specified on a series-specific basis.

  • The CONCAT_WS() function no longer skips empty strings. (Bug#586).

  • InnoDB now supports indexing a prefix of a column. This means, in particular, that BLOB and TEXT columns can be indexed in InnoDB tables, which was not possible before.

  • A documentation change: Function INTERVAL(NULL, ...) returns -1.

  • Enabled INSERT from SELECT when the table into which the records are inserted is also a table listed in the SELECT.

  • Allow CREATE TABLE and INSERT from any UNION.

  • The SQL_CALC_FOUND_ROWS option now always returns the total number of rows for any UNION.

  • Removed --table option from mysqlbinlog to avoid repeating mysqldump functionality.

  • Comment lines in option files can now start from the middle of a line, too (like basedir=c:\mysql # installation directory).

  • Changed optimizer slightly to prefer index lookups over full table scans in some boundary cases.

  • Added thread-specific max_seeks_for_key variable that can be used to force the optimizer to use keys instead of table scans even if the cardinality of the index is low.

  • Added optimization that converts LEFT JOIN to normal join in some cases.

  • A documentation change: added a paragraph about failover in replication (how to use a surviving slave as the new master, how to resume to the original setup). See Section聽6.10, 鈥淩eplication FAQ鈥.

  • A documentation change: added warning notes about safe use of the CHANGE MASTER command. See Section聽13.6.2.1, 鈥CHANGE MASTER TO Syntax鈥.

  • MySQL now issues a warning (not an error, as in 4.0.13) when it opens a table that was created with MySQL 4.1.

  • Added --nice option to mysqld_safe to allow setting the niceness of the mysqld process. (Thanks to Christian Hammers for providing the initial patch.) (Bug#627)

  • Added --read-only option to cause mysqld to allow no updates except from slave threads or from users with the SUPER privilege. (Original patch from Markus Benning).

  • SHOW BINLOG EVENTS FROM x where x is less than 4 now silently converts x to 4 instead of printing an error. The same change was done for CHANGE MASTER TO MASTER_LOG_POS=x and CHANGE MASTER TO RELAY_LOG_POS=x.

  • mysqld now only adds an interrupt handler for the SIGINT signal if you start it with the new --gdb option. This is done because some MySQL users encountered strange problems when they accidentally sent SIGINT to mysqld threads.

  • RESET SLAVE now clears the Last_Errno and Last_Error fields in the output of SHOW SLAVE STATUS.

  • Added max_relay_log_size variable; the relay log is rotated automatically when its size exceeds max_relay_log_size. But if max_relay_log_size is 0 (the default), max_binlog_size is used (as in older versions). max_binlog_size still applies to binary logs in any case.

  • FLUSH LOGS now rotates relay logs in addition to the other types of logs it rotates.

Bugs fixed:

  • Comparison/sorting for latin1_de character set was rewritten. The old algorithm could not handle cases like "s盲" > "脽a". See Section聽5.10.1.1, 鈥淯sing the German Character Set鈥. In rare cases it resulted in table corruption.

  • Fixed a problem with the password prompt on Windows. (Bug#683)

  • ALTER TABLE ... UNION=(...) for MERGE table is now allowed even if some underlying MyISAM tables are read-only. (Bug#702)

  • Fixed a problem with CREATE TABLE t1 SELECT x'41'. (Bug#801)

  • Removed some incorrect lock warnings from the error log.

  • Fixed memory overrun when doing REPAIR TABLE on a table with a multiple-part auto_increment key where one part was a packed CHAR.

  • Fixed a probable race condition in the replication code that could potentially lead to INSERT statements not being replicated in the event of a FLUSH LOGS command or when the binary log exceeds max_binlog_size. (Bug#791)

  • Fixed a crashing bug in INTERVAL and GROUP BY or DISTINCT. (Bug#807)

  • Fixed bug in mysqlhotcopy so it actually aborts for unsuccessful table copying operations. Fixed another bug so that it succeeds when there are thousands of tables to copy. (Bug#812)

  • Fixed problem with mysqlhotcopy failing to read options from option files. (Bug#808)

  • Fixed bugs in optimizer that sometimes prevented MySQL from using FULLTEXT indexes even though it was possible (for example, in SELECT * FROM t1 WHERE MATCH a,b AGAINST("index") > 0).

  • Fixed a bug with 鈥table is full鈥 in UNION operations.

  • Fixed a security problem that enabled users with no privileges to obtain information on the list of existing databases by using SHOW TABLES and similar commands.

  • Fixed a stack problem on UnixWare/OpenUnix.

  • Fixed a configuration problem on UnixWare/OpenUNIX and OpenServer.

  • Fixed a stack overflow problem in password verification. (CVE-2003-0780)

  • Fixed a problem with max_user_connections.

  • HANDLER without an index now works properly when a table has deleted rows. (Bug#787)

  • Fixed a bug with LOAD DATA in mysqlbinlog. (Bug#670)

  • Fixed that SET CHARACTER SET DEFAULT works. (Bug#462)

  • Fixed MERGE table behavior in ORDER BY ... DESC queries. (Bug#515)

  • Fixed server crash on PURGE MASTER LOGS or SHOW MASTER LOGS when the binary log is off. (Bug#733)

  • Fixed password-checking problem on Windows. (Bug#464)

  • Fixed the bug in comparison of a DATETIME column and an integer constant. (Bug#504)

  • Fixed remote mode of mysqlbinlog. (Bug#672)

  • Fixed ERROR 1105: Unknown error that occurred for some SELECT queries, where a column that was declared as NOT NULL was compared with an expression that took NULL value.

  • Changed timeout in mysql_real_connect() to use poll() instead of select() to work around problem with many open files in the client.

  • Fixed incorrect results from MATCH ... AGAINST used with a LEFT JOIN query.

  • Fixed a bug that limited the maximum value for mysqld variables to 4294967295 when they are specified on the command line.

  • Fixed a bug that sometimes caused spurious 鈥Access denied鈥 errors in HANDLER ... READ statements, when a table is referenced via an alias.

  • Fixed portability problem with safe_malloc, which caused MySQL to give "Freeing wrong aligned pointer" errors on SCO 3.2.

  • ALTER TABLE ... ENABLE/DISABLE KEYS could cause a core dump when done after an INSERT DELAYED statement on the same table.

  • Fixed problem with conversion of localtime to GMT where some times resulted in different (but correct) timestamps. Now MySQL should use the smallest possible timestamp value in this case. (Bug#316)

  • Very small query cache sizes could crash mysqld. (Bug#549)

  • Fixed a bug (accidentally introduced by us but present only in version 4.0.13) that made INSERT ... SELECT into an AUTO_INCREMENT column not replicate well. This bug is in the master, not in the slave. (Bug#490)

  • Fixed a bug: When an INSERT ... SELECT statement inserted rows into a non-transactional table, but failed at some point (for example, due to a 鈥Duplicate key鈥 error), the query was not written to the binary log. Now it is written to the binary log, with its error code, as all other queries are. About the slave-skip-errors option for how to handle partially completed queries in the slave, see Section聽6.8, 鈥淩eplication Startup Options鈥. (Bug#491)

  • SET FOREIGN_KEY_CHECKS=0 was not replicated properly. The fix probably will not be backported to 3.23.

  • On a slave, LOAD DATA INFILE which had no IGNORE or REPLACE clause on the master, was replicated with IGNORE. Although this is not a problem if the master and slave data are identical (a LOAD that produces no duplicate conflicts on the master produces none on the slave anyway), which is true in normal operation, it is better for debugging not to silently add the IGNORE. That way, you can get an error message on the slave and discover that for some reason, the data on master and slave are different and investigate why. (Bug#571)

  • On a slave, LOAD DATA INFILE printed an incomplete 鈥Duplicate entry '%-.64s' for key %d'鈥 message (the key name and value were not mentioned) in case of duplicate conflict (which does not happen in normal operation). (Bug#573)

  • When using a slave compiled with --debug, CHANGE MASTER TO RELAY_LOG_POS could cause a debug assertion failure. (Bug#576)

  • When doing a LOCK TABLES WRITE on an InnoDB table, commit could not happen, if the query was not written to the binary log (for example, if --log-bin was not used, or binlog-ignore-db was used). (Bug#578)

  • If a 3.23 master had open temporary tables that had been replicated to a 4.0 slave, and the binary log got rotated, these temporary tables were immediately dropped by the slave (which caused problems if the master used them subsequently). This bug had been fixed in 4.0.13, but in a manner which caused an unlikely inconvenience: If the 3.23 master died brutally (power failure), without having enough time to automatically write DROP TABLE statements to its binary log, then the 4.0.13 slave would not notice the temporary tables have to be dropped, until the slave mysqld server is restarted. This minor inconvenience is fixed in 3.23.57 and 4.0.14 (meaning the master must be upgraded to 3.23.57 and the slave to 4.0.14 to remove the inconvenience). (Bug#254)

  • If MASTER_POS_WAIT() was waiting, and the slave was idle, and the slave SQL thread terminated, MASTER_POS_WAIT() would wait forever. Now when the slave SQL thread terminates, MASTER_POS_WAIT() immediately returns NULL (鈥slave stopped鈥). (Bug#651)

  • After RESET SLAVE; START SLAVE;, the Relay_Log_Space value displayed by SHOW SLAVE STATUS was too big by four bytes. (Bug#763)

  • If a query was ignored on the slave (because of --replicate-ignore-table and other similar rules), the slave still checked if the query got the same error code (0, no error) as on the master. So if the master had an error on the query (for example, 鈥Duplicate entry鈥 in a multiple-row insert), then the slave stopped and warned that the error codes didn't match. (Bug#797)

B.2.18.聽Changes in release 4.0.13 (16 May 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • PRIMARY KEY now implies NOT NULL. (Bug#390)

  • The Windows binary packages are now compiled with --enable-local-infile to match the Unix build configuration.

  • Removed timing of tests from mysql-test-run. time does not accept all required parameters on many platforms (for example, QNX) and timing the tests is not really required (it's not a benchmark anyway).

  • SHOW MASTER STATUS and SHOW SLAVE STATUS required the SUPER privilege; now they accept REPLICATION CLIENT as well. (Bug#343)

  • Added multi-threaded MyISAM repair optimization and myisam_repair_threads variable to enable it. See Section聽5.2.3, 鈥淪ystem Variables鈥.

  • Added innodb_max_dirty_pages_pct variable which controls amount of dirty pages allowed in InnoDB buffer pool.

  • CURRENT_USER() and Access denied error messages now report the hostname exactly as it was specified in the GRANT command.

  • Removed benchmark results from the source and binary distributions. They are still available in the BK source tree, though.

  • InnoDB tables now support ANALYZE TABLE.

  • MySQL now issues an error when it opens a table that was created with MySQL 4.1.

  • Option --new now changes binary items (0xFFDF) to be treated as binary strings instead of numbers by default. This fixes some problems with character sets where it's convenient to input the string as a binary item. After this change you have to convert the binary string to INTEGER with a CAST if you want to compare two binary items with each other and know which one is bigger than the other. SELECT CAST(0xfeff AS UNSIGNED) < CAST(0xff AS UNSIGNED). This is the default behavior in MySQL 4.1. (Bug#152)

  • Enabled delayed_insert_timeout on Linux (most modern glibc libraries have a fixed pthread_cond_timedwait()). (Bug#211)

  • Don't create more insert delayed threads than given by max_delayed_threads. (Bug#211)

  • Changed UPDATE ... LIMIT to apply the limit to rows that were matched, whether or not they actually were changed. Previously the limit was applied as a restriction on the number of rows changed.

  • Tuned optimizer to favor clustered index over table scan.

  • BIT_AND() and BIT_OR() now return an unsigned 64-bit value.

  • Added warnings to error log of why a secure connection failed (when running with --log-warnings).

  • Deprecated options --skip-symlink and --use-symbolic-links and replaced these with --symbolic-links.

  • The default option for innodb_flush_log_at_trx_commit was changed from 0 to 1 to make InnoDB tables ACID by default. See Section聽14.2.5, 鈥InnoDB Startup Options and System Variables鈥.

  • Added a feature to SHOW KEYS to display keys that are disabled by ALTER TABLE DISABLE KEYS command.

  • When using a non-existing table type with CREATE TABLE, first try if the default table type exists before falling back to MyISAM.

  • Added MEMORY as an alias for HEAP.

  • Renamed function rnd to my_rnd as the name was too generic and is an exported symbol in libmysqlclient (thanks to Dennis Haney for the initial patch).

  • Portability fix: renamed include/dbug.h to include/my_dbug.h.

  • mysqldump no longer silently deletes the binary logs when invoked with the --master-data or --first-slave option; while this behavior was convenient for some users, others may suffer from it. Now you must explicitly ask for binary logs to be deleted by using the new --delete-master-logs option.

  • If the slave is configured (using for example --replicate-wild-ignore-table=mysql.%) to exclude mysql.user, mysql.host, mysql.db, mysql.tables_priv and mysql.columns_priv from replication, then GRANT and REVOKE are not replicated.

Bugs fixed:

  • Logged Access denied error message had incorrect Using password value. (Bug#398)

  • Fixed bug with NATURAL LEFT JOIN, NATURAL RIGHT JOIN and RIGHT JOIN when using many joined tables. The problem was that the JOIN method was not always associated with the tables surrounding the JOIN method. If you have a query that uses many RIGHT JOIN or NATURAL ... JOINS you should verify that they work as you expected after upgrading MySQL to this version. (Bug#291)

  • Fixed mysql parser not to erroneously interpret 鈥'鈥 or 鈥"鈥 characters within /* ... */ comment as beginning a quoted string.

  • mysql command-line client no longer looks for \* commands inside backtick-quoted strings.

  • Fixed Unknown error when using UPDATE ... LIMIT. (Bug#373)

  • Fixed problem with ANSI mode and GROUP BY with constants. (Bug#387)

  • Fixed bug with UNION and OUTER JOIN. (Bug#386)

  • Fixed bug if one used a multiple-table UPDATE and the query required a temporary table bigger than tmp_table_size. (Bug#286)

  • Run mysql_install_db with the -IN-RPM option for the Mac OS X installation to not fail on systems with improperly configured hostname configurations.

  • LOAD DATA INFILE now reads 000000 as a zero date instead of "2000-00-00".

  • Fixed bug that caused DELETE FROM table WHERE const_expression always to delete the whole table (even if expression result was false). (Bug#355)

  • Fixed core dump bug when using FORMAT('nan',#). (Bug#284)

  • Fixed name resolution bug with HAVING ... COUNT(DISTINCT ...).

  • Fixed incorrect result from truncation operator (*) in MATCH ... AGAINST() in some complex joins.

  • Fixed a crash in REPAIR ... USE_FRM command, when used on read-only, non-existing table or a table with a crashed index file.

  • Fixed a crashing bug in mysql monitor program. It occurred if program was started with --no-defaults, with a prompt that contained the hostname and a connection to a non-existent database was requested.

  • Fixed problem when comparing a key for a multi-byte character set. (Bug#152)

  • Fixed bug in LEFT, RIGHT and MID when used with multi-byte character sets and some GROUP BY queries. (Bug#314)

  • Fix problem with ORDER BY being discarded for some DISTINCT queries. (Bug#275)

  • Fixed that SET SQL_BIG_SELECTS=1 works as documented (This corrects a new bug introduced in 4.0)

  • Fixed some serious bugs in UPDATE ... ORDER BY. (Bug#241)

  • Fixed unlikely problem in optimizing WHERE clause with constant expression like in WHERE 1 AND (a=1 AND b=1).

  • Fixed that SET SQL_BIG_SELECTS=1 works again.

  • Introduced proper backtick quoting for db.table in SHOW GRANTS.

  • FULLTEXT index stopped working after ALTER TABLE that converts TEXT column to CHAR. (Bug#283)

  • Fixed a security problem with SELECT and wildcarded select list, when user only had partial column SELECT privileges on the table.

  • Mark a MyISAM table as "analyzed" only when all the keys are indeed analyzed.

  • Only ignore world-writable my.cnf files that are regular files (and not, for example, named pipes or character devices).

  • Fixed few smaller issues with SET PASSWORD.

  • Fixed error message which contained deprecated text.

  • Fixed a bug with two NATURAL JOINs in the query.

  • SUM() didn't return NULL when there was no rows in result or when all values was NULL.

  • On Unix, symbolic link handling was not enabled by default and there was no way to turn this on.

  • Added missing dashes to parameter --open-files-limit in mysqld_safe. (Bug#264)

  • Fixed incorrect hostname for TCP/IP connections displayed in SHOW PROCESSLIST.

  • Fixed a bug with NAN in FORMAT(...) function ...

  • Fixed a bug with improperly cached database privileges.

  • Fixed a bug in ALTER TABLE ENABLE / DISABLE KEYS which failed to force a refresh of table data in the cache.

  • Fixed bugs in replication of LOAD DATA INFILE for custom parameters (ENCLOSED, TERMINATED and so on) and temporary tables. (Bug#183, Bug#222)

  • Fixed a replication bug when the master is 3.23 and the slave 4.0: the slave lost the replicated temporary tables if FLUSH LOGS was issued on the master. (Bug#254)

  • Fixed a bug when doing LOAD DATA INFILE IGNORE: When reading the binary log, mysqlbinlog and the replication code read REPLACE instead of IGNORE. This could make the slave's table become different from the master's table. (Bug#218)

  • Fixed a deadlock when relay_log_space_limit was set to a too small value. (Bug#79)

  • Fixed a bug in HAVING clause when an alias is used from the select list.

  • Fixed overflow bug in MyISAM when a row is inserted into a table with a large number of columns and at least one BLOB/TEXT column. Bug was caused by incorrect calculation of the needed buffer to pack data.

  • Fixed a bug when SELECT @non_existent_variable caused an error in the client/server protocol due to net_printf() output being sent to the client twice.

  • Fixed a bug in setting SQL_BIG_SELECTS option.

  • Fixed a bug in SHOW PROCESSLIST which only displayed a localhost in the "Host" column. This was caused by a glitch that used only current thread information instead of information from the linked list of threads.

  • Removed unnecessary Mac OS X helper files from server RPM. (Bug#144)

  • Allow optimization of multiple-table update for InnoDB tables as well.

  • Fixed a bug in multiple-table updates that caused some rows to be updated several times.

  • Fixed a bug in mysqldump when it was called with --master-data: the CHANGE MASTER TO commands appended to the SQL dump had incorrect coordinates. (Bug#159)

  • Fixed a bug when an updating query using USER() was replicated on the slave; this caused a segmentation fault on the slave. (Bug#178). USER() is still badly replicated on the slave (it is replicated to "").

B.2.19.聽Changes in release 4.0.12 (15 March 2003: Production)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • mysqld no longer reads options from world-writable config files. (CVE-2003-0150)

  • Integer values between 9223372036854775807 and 9999999999999999999 are now regarded as unsigned longlongs, not as floats. This makes these values work similar to values between 10000000000000000000 and 18446744073709551615.

  • SHOW PROCESSLIST now includes the client TCP port after the hostname to make it easier to know from which client the request originated.

  • The --new option can be used to make a 4.0 server return TIMESTAMP as a string in 'YYYY-MM-DD HH:MM:SS' format, the way that 4.1 servers do. This is also a new system variable that can be set for the same effect. See Section聽11.3.1.1, 鈥TIMESTAMP Properties Prior to MySQL 4.1鈥.

Bugs fixed:

  • Fixed mysqld crash on extremely small values of sort_buffer variable.

  • INSERT INTO u SELECT ... FROM t was written too late to the binary log if t was very frequently updated during the execution of this query. This could cause a problem with mysqlbinlog or replication. The master must be upgraded, not the slave. (Bug#136)

  • Fixed checking of random part of WHERE clause. (Bug#142)

  • Fixed a bug with multiple-table updates with InnoDB tables. This bug occurred as, in many cases, InnoDB tables cannot be updated 鈥on the fly,鈥 but offsets to the records have to be stored in a temporary table.

  • Added missing file mysql_secure_installation to the server RPM subpackage. (Bug#141)

  • Fixed MySQL (and myisamchk) crash on artificially corrupted .MYI files.

  • Don't allow BACKUP TABLE to overwrite existing files.

  • Fixed a bug with multiple-table UPDATE statements when user had all privileges on the database where tables are located and there were any entries in tables_priv table, that is, grant_option was true.

  • Fixed a bug that allowed a user with table or column grants on some table, TRUNCATE any table in the same database.

  • Fixed deadlock when doing LOCK TABLE followed by DROP TABLE in the same thread. In this case one could still kill the thread with KILL.

  • LOAD DATA LOCAL INFILE was not properly written to the binary log (hence not properly replicated). (Bug#82)

  • RAND() entries were not read correctly by mysqlbinlog from the binary log which caused problems when restoring a table that was inserted with RAND(). INSERT INTO t1 VALUES(RAND()). In replication this worked okay.

  • SET SQL_LOG_BIN=0 was ignored for INSERT DELAYED queries. (Bug#104)

  • SHOW SLAVE STATUS reported too old positions (columns Relay_Master_Log_File and Exec_Master_Log_Pos) for the last executed statement from the master, if this statement was the COMMIT of a transaction. The master must be upgraded for that, not the slave. (Bug#52)

  • LOAD DATA INFILE was not replicated by the slave if replicate_*_table was set on the slave. (Bug#86)

  • After RESET SLAVE, the coordinates displayed by SHOW SLAVE STATUS looked un-reset (although they were, but only internally). (Bug#70)

  • Fixed query cache invalidation on LOAD DATA.

  • Fixed memory leak on ANALYZE procedure with error.

  • Fixed a bug in handling CHAR(0) columns that could cause incorrect results from the query.

  • Fixed rare bug with incorrect initialization of AUTO_INCREMENT column, as a secondary column in a multi-column key (see Section聽3.6.9, 鈥淯sing AUTO_INCREMENT), when data was inserted with INSERT ... SELECT or LOAD DATA into an empty table.

  • On Windows, STOP SLAVE didn't stop the slave until the slave got one new command from the master (this bug has been fixed for MySQL 4.0.11 by releasing updated 4.0.11a Windows packages, which include this individual fix on top of the 4.0.11 sources). (Bug#69)

  • Fixed a crash when no database was selected and LOAD DATA command was issued with full table name specified, including database prefix.

  • Fixed a crash when shutting down replication on some platforms (for example, Mac OS X).

  • Fixed a portability bug with pthread_attr_getstacksize on HP-UX 10.20 (Patch was also included in 4.0.11a sources).

  • Fixed the bigint test to not fail on some platforms (for example, HP-UX and Tru64) due to different return values of the atof() function.

  • Fixed the rpl_rotate_logs test to not fail on certain platforms (such as Mac OS X) due to a too-long file name (changed slave-master-info.opt to .slave-mi).

B.2.20.聽Changes in release 4.0.11 (20 February 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • NULL is now sorted LAST if you use ORDER BY ... DESC (as it was before MySQL 4.0.2). This change was required to comply with the SQL standard. (The original change was made because we thought that standard SQL required NULL to be always sorted at the same position, but this was incorrect).

  • Added START TRANSACTION (standard SQL syntax) as alias for BEGIN. This is recommended to use instead of BEGIN to start a transaction.

  • Added OLD_PASSWORD() as a synonym for PASSWORD().

  • Allow keyword ALL in group functions.

  • Added support for some new INNER JOIN and JOIN syntaxes. For example, SELECT * FROM t1 INNER JOIN t2 didn't work before.

  • Novell NetWare 6.0 porting effort completed, Novell patches merged into the main source tree.

Bugs fixed:

  • Fixed problem with multiple-table delete and InnoDB tables.

  • Fixed a problem with BLOB NOT NULL columns used with IS NULL.

  • Re-added missing pre- and post(un)install scripts to the Linux RPM packages (they were missing after the renaming of the server subpackage).

  • Fixed that table locks are not released with multiple-table updates and deletes with InnoDB storage engine.

  • Fixed bug in updating BLOB columns with long strings.

  • Fixed integer-wraparound when giving big integer (>= 10 digits) to function that requires an unsigned argument, like CREATE TABLE (...) AUTO_INCREMENT=N.

  • MIN(key_column) could in some cases return NULL on a column with NULL and other values.

  • MIN(key_column) and MAX(key_column) could in some cases return incorrect values when used in OUTER JOIN.

  • MIN(key_column) and MAX(key_column) could return incorrect values if one of the tables was empty.

  • Fixed rare crash in compressed MyISAM tables with blobs.

  • Fixed bug in using aggregate functions as argument for INTERVAL, CASE, FIELD, CONCAT_WS, ELT and MAKE_SET functions.

  • When running with --lower-case-table-names (default on Windows) and you had tables or databases with mixed case on disk, then executing SHOW TABLE STATUS followed with DROP DATABASE or DROP TABLE could fail with Errcode 13.

B.2.21.聽Changes in release 4.0.10 (29 January 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • Added option --log-error[=file_name] to mysqld_safe and mysqld. This option forces all error messages to be put in a log file if the option --console is not given. On Windows --log-error is enabled as default, with a default name of host_name.err if the name is not specified.

  • Changed some things from Warning: to Note: in the log files.

  • The mysqld server should now compile on NetWare.

  • Added optimization that if one does GROUP BY ... ORDER BY NULL then result is not sorted.

  • New --ft-stopword-file command-line option for mysqld to replace/disable the built-in stopword list that is used in full-text searches. See Section聽5.2.3, 鈥淪ystem Variables鈥.

  • Changed default stack size from 64KB to 192KB; This fixes a core dump problem on Red Hat 8.0 and other systems with a glibc that requires a stack size larger than 128K for gethostbyaddr() to resolve a hostname. You can fix this for earlier MySQL versions by starting mysqld with --thread-stack=192K.

  • Added mysql_waitpid to the binary distribution and the MySQL-client RPM subpackage (required for mysql-test-run).

  • Renamed the main MySQL RPM package to MySQL-server. When updating from an older version, MySQL-server.rpm simply replaces MySQL.rpm.

  • If a slave is configured with replicate_wild_do_table=db.% or replicate_wild_ignore_table=db.%, these rules are applied to CREATE/DROP DATABASE, too.

  • Added timeout value for MASTER_POS_WAIT().

Bugs fixed:

  • Fixed initialization of the random seed for newly created threads to give a better rand() distribution from the first call.

  • Fixed a bug that caused mysqld to hang when a table was opened with the HANDLER command and then dropped without being closed.

  • Fixed bug in logging to binary log (which affects replication) a query that inserts a NULL in an AUTO_INCREMENT column and also uses LAST_INSERT_ID().

  • Fixed an unlikely bug that could cause a memory overrun when using ORDER BY constant_expression.

  • Fixed a table corruption in myisamchk parallel repair mode.

  • Fixed bug in query cache invalidation on simple table renaming.

  • Fixed bug in mysqladmin --relative.

  • On some 64-bit systems, show status reported a strange number for Open_files and Open_streams.

  • Fixed incorrect number of columns in EXPLAIN on empty table.

  • Fixed bug in LEFT JOIN that caused zero rows to be returned in the case the WHERE condition was evaluated as FALSE after reading const tables. (Unlikely condition).

  • FLUSH PRIVILEGES didn't correctly flush table/column privileges when mysql.tables_priv is empty.

  • Fixed bug in replication when using LOAD DATA INFILE one a file that updated an AUTO_INCREMENT column with NULL or 0. This bug only affected MySQL 4.0 masters (not slaves or MySQL 3.23 masters). Note: If you have a slave that has replicated a file with generated AUTO_INCREMENT columns then the slave data is corrupted and you should reinitialize the affected tables from the master.

  • Fixed possible memory overrun when sending a BLOB value larger than 16M to the client.

  • Fixed incorrect error message when setting a NOT NULL column to an expression that returned NULL.

  • Fixed core dump bug in str LIKE "%other_str%" where str or other_str contained characters >= 128.

  • Fixed bug: When executing on master LOAD DATA and InnoDB failed with table full error the binary log was corrupted.

B.2.22.聽Changes in release 4.0.9 (09 January 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • OPTIMIZE TABLE for MyISAM tables treats all NULL values as different when calculating cardinality. This helps in optimizing joins between tables where one of the tables has a lot of NULL values in a indexed column:

    SELECT * from t1, t2 where t1.a=t2.key_with_a_lot_of_null;
    
  • Added join operator FORCE INDEX (index_list). This acts likes USE INDEX (index_list) but with the addition that a table scan is assumed to be VERY expensive. One bad thing with this is that it makes FORCE a reserved word.

  • Reset internal row buffer in MyISAM after each query. This reduces memory in case you have a lot of big blobs in a table.

Bugs fixed:

  • A security patch in 4.0.8 causes the mysqld server to die if the remote hostname can't be resolved. This is now fixed.

  • Fixed crash when replication big LOAD DATA INFILE statement that caused log rotation.

B.2.23.聽Changes in release 4.0.8 (07 January 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • Default max_packet_length for libmysqld.c is now 1024*1024*1024.

  • You can now specify max_allowed_packet in a file read by mysql_options(MYSQL_READ_DEFAULT_FILE). for clients.

  • When sending a too big packet to the server with the not compressed protocol, the client now gets an error message instead of a lost connection.

  • We now send big queries/result rows in bigger hunks, which should give a small speed improvement.

  • Fixed some bugs with the compressed protocol for rows > 16MB.

  • InnoDB tables now also support ON UPDATE CASCADE in FOREIGN KEY constraints. See the InnoDB section in the manual for the InnoDB changelog.

Bugs fixed:

  • Fixed bug in ALTER TABLE with BDB tables.

  • Fixed core dump bug in QUOTE() function.

  • Fixed a bug in handling communication packets bigger than 16MB. Unfortunately this required a protocol change; If you upgrade the server to 4.0.8 and above and have clients that use packets >= 255*255*255 bytes (=16581375) you must also upgrade your clients to at least 4.0.8. If you don't upgrade, the clients hang when sending a big packet.

  • Fixed bug when sending blobs longer than 16MB to client.

  • Fixed bug in GROUP BY when used on BLOB column with NULL values.

  • Fixed a bug in handling NULL values in CASE ... WHEN ...

B.2.24.聽Changes in release 4.0.7 (20 December 2002)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • mysqlbug now also reports the compiler version used for building the binaries (if the compiler supports the option --version).

Bugs fixed:

  • Fixed compilation problems on OpenUnix and HPUX 10.20.

  • Fixed some optimization problems when compiling MySQL with -DBIG_TABLES on a 32-bit system.

  • mysql_drop_db() didn't check permissions properly so anyone could drop another users database. DROP DATABASE is checked properly.

B.2.25.聽Changes in release 4.0.6 (14 December 2002: Gamma)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • Added syntax support for CHARACTER SET xxx and CHARSET=xxx table options (to be able to read table dumps from 4.1).

  • Fixed replication bug that caused the slave to loose its position in some cases when the replication log was rotated.

  • Fixed that a slave restarts from the start of a transaction if it's killed in the middle of one.

  • Moved the manual pages from man to man/man1 in the binary distributions.

  • The default type returned by IFNULL(A,B) is now set to be the more 'general' of the types of A and B. (The order is STRING, REAL or INTEGER).

  • Moved the mysql.server startup script in the RPM packages from /etc/rc.d/init.d/mysql to /etc/init.d/mysql (which almost all current Linux distributions support for LSB compliance).

  • Added Qcache_lowmem_prunes status variable (number of queries that were deleted from the cache because of low memory).

  • Fixed mysqlcheck so it can deal with table names containing dashes.

  • Bulk insert optimization (see Section聽5.2.3, 鈥淪ystem Variables鈥) is no longer used when inserting small (less than 100) number of rows.

  • Optimization added for queries like SELECT ... FROM merge_table WHERE indexed_column=constant_expr.

  • Added functions LOCALTIME and LOCALTIMESTAMP as synonyms for NOW().

  • CEIL is now an alias for CEILING.

  • The CURRENT_USER() function can be used to get a user@host value as it was matched in the GRANT system. See Section聽12.10.3, 鈥淚nformation Functions鈥.

  • Fixed CHECK constraints to be compatible with standard SQL. This made CHECK a reserved word. (Checking of CHECK constraints is still not implemented).

  • Added CAST(... as CHAR).

  • Added PostgreSQL compatible LIMIT syntax: SELECT ... LIMIT row_count OFFSET offset

  • mysql_change_user() now resets the connection to the state of a fresh connect (Ie, ROLLBACK any active transaction, close all temporary tables, reset all user variables etc..)

  • CHANGE MASTER and RESET SLAVE now require that slave threads both be stopped; these commands return an error if at least one of these two threads is running.

Bugs fixed:

  • Fixed number of found rows returned in multi table updates

  • Make --lower-case-table-names default on Mac OS X as the default filesystem (HFS+) is case insensitive. See Section聽9.2.2, 鈥淚dentifier Case Sensitivity鈥.

  • Transactions in AUTOCOMMIT=0 mode didn't rotate binary log.

  • A fix for the bug in a SELECT with joined tables with ORDER BY and LIMIT clause when filesort had to be used. In that case LIMIT was applied to filesort of one of the tables, although it could not be. This fix also solved problems with LEFT JOIN.

  • mysql_server_init() now makes a copy of all arguments. This fixes a problem when using the embedded server in C# program.

  • Fixed buffer overrun in libmysqlclient library that allowed a malicious MySQL server to crash the client application. (CVE-2002-1376)

  • Fixed security-related bug in mysql_change_user() handling. All users are strongly recommended to upgrade to version 4.0.6. (CVE-2002-1374, CVE-2002-1375)

  • Fixed bug that prevented --chroot command-line option of mysqld from working.

  • Fixed bug in phrase operator "..." in boolean full-text search.

  • Fixed bug that caused OPTIMIZE TABLE to corrupt the table under some rare circumstances.

  • Part rewrite of multiple-table-update to optimize it, make it safer and more bug-free.

  • LOCK TABLES now works together with multiple-table-update and multiple-table-delete.

  • --replicate-do=xxx didn't work for UPDATE commands. (Bug introduced in 4.0.0)

  • Fixed shutdown problem on Mac OS X.

  • Major InnoDB bugs in REPLACE, AUTO_INCREMENT, INSERT INTO ... SELECT ... were fixed. See the InnoDB changelog in the InnoDB section of the manual.

  • RESET SLAVE caused a crash if the slave threads were running.

B.2.26.聽Changes in release 4.0.5 (13 November 2002)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

Functionality added or changed:

  • Port number was added to hostname (if it is known) in SHOW PROCESSLIST command

  • Changed handling of last argument in WEEK() so that you can get week number according to the ISO 8601 specification. (Old code should still work).

  • Fixed that INSERT DELAYED threads don't hang on Waiting for INSERT when one sends a SIGHUP to mysqld.

  • Change that AND works according to standard SQL when it comes to NULL handling. In practice, this affects only queries where you do something like WHERE ... NOT (NULL AND 0).

  • mysqld now resolves basedir to its full path (with realpath()). This enables one to use relative symlinks to the MySQL installation directory. This however causes show variables to report different directories on systems where there is a symbolic link in the path.

  • Fixed that MySQL does not use index scan on index disabled with IGNORE INDEX or USE INDEX. to be ignored.

  • Added --use-frm option to mysqlcheck. When used with REPAIR TABLE, it gets the table structure from the .frm file, so the table can be repaired even if the .MYI header is corrupted.

  • Fixed bug in MAX() optimization when used with JOIN and ON expressions.

  • Added support for reading of MySQL 4.1 table definition files.

  • BETWEEN behavior changed (see Section聽12.2.3, 鈥淐omparison Functions and Operators鈥). Now datetime_col BETWEEN timestamp AND timestamp should work as expected.

  • One can create TEMPORARY MERGE tables now.

  • DELETE FROM myisam_table now shrinks not only the .MYD file but also the .MYI file.

  • When one uses the --open-files-limit=val option to mysqld_safe it's now passed on to mysqld.

  • Changed output from EXPLAIN from 'where used' to 'Using where' to make it more in line with other output.

  • Removed variable safe_show_database as it was no longer used.

  • Updated source tree to be built using automake 1.5 and libtool 1.4.

  • Fixed an inadvertently changed option (--ignore-space) back to the original --ignore-spaces in mysqlclient. (Both syntaxes work).

  • Don't require UPDATE privilege when using REPLACE.

  • Added support for DROP TEMPORARY TABLE ..., to be used to make replication safer.

  • When transactions are enabled, all commands that update temporary tables inside a BEGIN/COMMIT are now stored in the binary log on COMMIT and not stored if one does ROLLBACK. This fixes some problems with non-transactional temporary tables used inside transactions.

  • Allow braces in joins in all positions. Formerly, things like SELECT * FROM (t2 LEFT JOIN t3 USING (a)), t1 worked, but not SELECT * FROM t1, (t2 LEFT JOIN t3 USING (a)). Note that braces are simply removed, they do not change the way the join is executed.

  • InnoDB now supports also isolation levels READ UNCOMMITTED and READ COMMITTED. For a detailed InnoDB changelog, see Section聽B.4, 鈥淐hanges in InnoDB.

Bugs fixed:

  • Fixed bug in MAX() optimization when used with JOIN and ON expressions.

  • Fixed that INSERT DELAY threads don't hang on Waiting for INSERT when one sends a SIGHUP to mysqld.

  • Fixed that MySQL does not use an index scan on an index that has been disabled with IGNORE INDEX or USE INDEX.

  • Corrected test for root user in mysqld_safe.

  • Fixed error message issued when storage engine cannot do CHECK TABLE or REPAIR TABLE.

  • Fixed rare core dump problem in complicated GROUP BY queries that didn't return any result.

  • Fixed mysqlshow to work properly with wildcarded database names and with database names that contain underscores.

  • Portability fixes to get MySQL to compile cleanly with Sun Forte 5.0.

  • Fixed MyISAM crash when using dynamic-row tables with huge numbers of packed columns.

  • Fixed query cache behavior with BDB transactions.

  • Fixed possible floating point exception in MATCH relevance calculations.

  • Fixed bug in full-text search IN BOOLEAN MODE that made MATCH to return incorrect relevance value in some complex joins.

  • Fixed a bug that limited MyISAM key length to a value slightly less that 500. It is exactly 500 now.

  • Fixed that GROUP BY on columns that may have a NULL value doesn't always use disk based temporary tables.

  • The filename argument for the --des-key-file argument to mysqld is interpreted relative to the data directory if given as a relative pathname.

  • Removed a condition that temp table with index on column that can be NULL has to be MyISAM. This was okay for 3.23, but not needed in 4.*. This resulted in slowdown in many queries since 4.0.2.

  • Small code improvement in multiple-table updates.

  • Fixed a newly introduced bug that caused ORDER BY ... LIMIT row_count to not return all rows.

  • Fixed a bug in multiple-table deletes when outer join is used on an empty table, which gets first to be deleted.

  • Fixed a bug in multiple-table updates when a single table is updated.

  • Fixed bug that caused REPAIR TABLE and myisamchk to corrupt FULLTEXT indexes.

  • Fixed bug with caching the mysql grant table database. Now queries in this database are not cached in the query cache.

  • Small fix in mysqld_safe for some shells.

  • Give error if a MyISAM MERGE table has more than 232 rows and MySQL was not compiled with -DBIG_TABLES.

  • Fixed some ORDER BY ... DESC problems with InnoDB tables.

B.2.27.聽Changes in release 4.0.4 (29 September 2002)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • Fixed bug where GRANT/REVOKE failed if hostname was given in non-matching case.

  • Don't give warning in LOAD DATA INFILE when setting a timestamp to a string value of '0'.

  • Fixed bug in myisamchk -R mode.

  • Fixed bug that caused mysqld to crash on REVOKE.

  • Fixed bug in ORDER BY when there is a constant in the SELECT statement.

  • One didn't get an error message if mysqld couldn't open the privilege tables.

  • SET PASSWORD FOR ... closed the connection in case of errors (bug from 4.0.3).

  • Increased maximum possible max_allowed_packet in mysqld to 1GB.

  • Fixed bug when doing a multiple-row INSERT on a table with an AUTO_INCREMENT key which was not in the first part of the key.

  • Changed LOAD DATA INFILE to not re-create index if the table had rows from before.

  • Fixed overrun bug when calling AES_DECRYPT() with incorrect arguments.

  • --skip-ssl can now be used to disable SSL in the MySQL clients, even if one is using other SSL options in an option file or previously on the command line.

  • Fixed bug in MATCH ... AGAINST( ... IN BOOLEAN MODE) used with ORDER BY.

  • Added LOCK TABLES and CREATE TEMPORARY TABLES privilege on the database level. You must run the mysql_fix_privilege_tables script on old installations to activate these.

  • In SHOW TABLE ... STATUS, compressed tables sometimes showed up as dynamic.

  • SELECT @@[global|session].var_name didn't report global | session in the result column name.

  • Fixed problem in replication that FLUSH LOGS in a circular replication setup created an infinite number of binary log files. Now a rotate-binary-log command in the binary log does not cause slaves to rotate logs.

  • Removed STOP EVENT from binary log when doing FLUSH LOGS.

  • Disable the use of SHOW NEW MASTER FOR SLAVE as this needs to be completely reworked in a future release.

  • Fixed a bug with constant expression (for example, column of a one-row table, or column from a table, referenced by a UNIQUE key) appeared in ORDER BY part of SELECT DISTINCT.

  • --log-binary=a.b.c now properly strips off .b.c.

  • FLUSH LOGS removed numerical extension for all future update logs.

  • GRANT ... REQUIRE didn't store the SSL information in the mysql.user table if SSL was not enabled in the server.

  • GRANT ... REQUIRE NONE can now be used to remove SSL information.

  • AND is now optional between REQUIRE options.

  • REQUIRE option was not properly saved, which could cause strange output in SHOW GRANTS.

  • Fixed that mysqld --help reports correct values for --datadir and --bind-address.

  • Fixed that one can drop UDFs that didn't exist when mysqld was started.

  • Fixed core dump problem with SHOW VARIABLES on some 64-bit systems (like Solaris SPARC).

  • Fixed a bug in my_getopt(); --set-variable syntax didn't work for those options that didn't have a valid variable in the my_option struct. This affected at least the default-table-type option.

  • Fixed a bug from 4.0.2 that caused REPAIR TABLE and myisamchk --recover to fail on tables with duplicates in a unique key.

  • Fixed a bug from 4.0.3 in calculating the default data type for some functions. This affected queries of type CREATE TABLE tbl_name SELECT expression(),...

  • Fixed bug in queries of type SELECT * FROM table-list GROUP BY ... and SELECT DISTINCT * FROM ....

  • Fixed bug with the --slow-log when logging an administrator command (like FLUSH TABLES).

  • Fixed a bug that OPTIMIZE TABLE of locked and modified table, reported table corruption.

  • Fixed a bug in my_getopt() in handling of special prefixes (--skip-, --enable-). --skip-external-locking didn't work and the bug may have affected other similar options.

  • Fixed bug in checking for output file name of the tee option.

  • Added some more optimization to use index for SELECT ... FROM many_tables .. ORDER BY key limit #

  • Fixed problem in SHOW OPEN TABLES when a user didn't have access permissions to one of the opened tables.

B.2.28.聽Changes in release 4.0.3 (26 August 2002: Beta)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • Fixed problem with types of user variables. (Bug#551)

  • Fixed problem with configure ... --localstatedir=....

  • Cleaned up mysql.server script.

  • Fixed a bug in mysqladmin shutdown when pid file was modified while mysqladmin was still waiting for the previous one to disappear. This could happen during a very quick restart and caused mysqladmin to hang until shutdown_timeout seconds had passed.

  • Don't increment warnings when setting AUTO_INCREMENT columns to NULL in LOAD DATA INFILE.

  • Fixed all boolean type variables/options to work with the old syntax, for example, all of these work: --lower-case-table-names, --lower-case-table-names=1, -O lower-case-table-names=1, --set-variable=lower-case-table-names=1

  • Fixed shutdown problem (SIGTERM signal handling) on Solaris. (Bug from 4.0.2).

  • SHOW MASTER STATUS now returns an empty set if binary log is not enabled.

  • SHOW SLAVE STATUS now returns an empty set if slave is not initialized.

  • Don't update MyISAM index file on update if not strictly necessary.

  • Fixed bug in SELECT DISTINCT ... FROM many_tables ORDER BY not-used-column.

  • Fixed a bug with BIGINT values and quoted strings.

  • Added QUOTE() function that performs SQL quoting to produce values that can be used as data values in queries.

  • Changed variable DELAY_KEY_WRITE to an enumeration to allow it to be set for all tables without taking down the server.

  • Changed behavior of IF(condition,column,NULL) so that it returns the value in the column's data type.

  • Made safe_mysqld a symlink to mysqld_safe in binary distribution.

  • Fixed security bug when having an empty database name in the user.db table.

  • Fixed some problems with CREATE TABLE ... SELECT function().

  • mysqld now has the option --temp-pool enabled by default as this gives better performance with some operating systems.

  • Fixed problem with too many allocated alarms on slave when connecting to master many times (normally not a very critical error).

  • Fixed hang in CHANGE MASTER TO if the slave thread died very quickly.

  • Big cleanup in replication code (less logging, better error messages, etc..)

  • If the --code-file option is specified, the server calls setrlimit() to set the maximum allowed core file size to unlimited, so core files can be generated.

  • Fixed bug in query cache after temporary table creation.

  • Added --count=N (-c) option to mysqladmin, to make the program do only N iterations. To be used with --sleep (-i). Useful in scripts.

  • Fixed bug in multiple-table UPDATE: when updating a table, do_select() became confused about reading records from a cache.

  • Fixed bug in multiple-table UPDATE when several columns were referenced from a single table

  • Fixed bug in truncating non-existing table.

  • Fixed bug in REVOKE that caused user resources to be randomly set.

  • Fixed bug in GRANT for the new CREATE TEMPORARY TABLE privilege.

  • Fixed bug in multiple-table DELETE when tables are re-ordered in the table initialization method and ref_lengths are of different sizes.

  • Fixed two bugs in SELECT DISTINCT with large tables.

  • Fixed bug in query cache initialization with very small query cache size.

  • Allow DEFAULT with INSERT statement.

  • The startup parameters myisam_max_sort_file_size and myisam_max_extra_sort_file_size are now given in bytes, not megabytes.

  • External system locking of MyISAM/ISAM files is now turned off by default. One can turn this on with --external-locking. (For most users this is never needed).

  • Fixed core dump bug with INSERT ... SET db_name.tbl_name.col_name=''.

  • Fixed client hangup bug when using some SQL commands with incorrect syntax.

  • Fixed a timing bug in DROP DATABASE

  • New SET [GLOBAL | SESSION] syntax to change thread-specific and global system variables at runtime.

  • Added variable slave_compressed_protocol.

  • Renamed variable query_cache_startup_type to query_cache_type, myisam_bulk_insert_tree_size to bulk_insert_buffer_size, record_buffer to read_buffer_size and record_rnd_buffer to read_rnd_buffer_size.

  • Renamed some SQL variables, but old names still work until 5.0. See Section聽2.11.2, 鈥淯pgrading from MySQL 3.23 to 4.0鈥.

  • Renamed --skip-locking to --skip-external-locking.

  • Removed unused variable query_buffer_size.

  • Fixed a bug that made the pager option in the mysql client non-functional.

  • Added full AUTO_INCREMENT support to MERGE tables.

  • Extended LOG() function to accept an optional arbitrary base parameter. See Section聽12.5.2, 鈥淢athematical Functions鈥.

  • Added LOG2() function (useful for finding out how many bits a number would require for storage).

  • Added LN() natural logarithm function for compatibility with other databases. It is synonymous with LOG(X).

B.2.29.聽Changes in release 4.0.2 (01 July 2002)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • Cleaned up NULL handling for default values in DESCRIBE tbl_name.

  • Fixed TRUNCATE() to round up negative values to the nearest integer.

  • Fixed buffer overflow problem if someone specified a too-long datadir parameter to mysqld. (CVE-2002-0969)

  • Changed --chroot=path option to execute chroot() immediately after all options have been parsed.

  • Don't allow database names that contain 鈥\鈥.

  • lower_case_table_names now also applies to database names.

  • Added XOR operator (logical and bitwise XOR) with ^ as a synonym for bitwise XOR.

  • Added function IS_FREE_LOCK("lock_name"). Based on code contributed by Hartmut Holzgraefe .

  • Removed mysql_ssl_clear() from C API, as it was not needed.

  • DECIMAL and NUMERIC types can now read exponential numbers.

  • Added SHA1() function to calculate 160 bit hash value as described in RFC 3174 (Secure Hash Algorithm). This function can be considered a cryptographically more secure equivalent of MD5(). See Section聽12.10.2, 鈥淓ncryption and Compression Functions鈥.

  • Added AES_ENCRYPT() and AES_DECRYPT() functions to perform encryption according to AES standard (Rijndael). See Section聽12.10.2, 鈥淓ncryption and Compression Functions鈥.

  • Added --single-transaction option to mysqldump, allowing a consistent dump of InnoDB tables. See Section聽8.12, 鈥mysqldump 鈥 A Database Backup Program鈥.

  • Fixed bug in innodb_log_group_home_dir in SHOW VARIABLES.

  • Fixed a bug in optimizer with merge tables when non-unique values are used in summing up (causing crashes).

  • Fixed a bug in optimizer when a range specified makes index grouping impossible (causing crashes).

  • Fixed a rare bug when FULLTEXT index is present and no tables are used.

  • Added privileges CREATE TEMPORARY TABLES, EXECUTE, LOCK TABLES, REPLICATION CLIENT, REPLICATION SLAVE, SHOW DATABASES and SUPER. To use these, you must have run the mysql_fix_privilege_tables script after upgrading.

  • Fixed query cache align data bug.

  • Fixed mutex bug in replication when reading from master fails.

  • Added missing mutex in TRUNCATE TABLE. This fixes some core dump/hangup problems when using TRUNCATE TABLE.

  • Fixed bug in multiple-table DELETE when optimizer uses only indexes.

  • Fixed that ALTER TABLE tbl_name RENAME new_tbl_name is as fast as RENAME TABLE.

  • Fixed bug in GROUP BY with two or more columns, where at least one column can contain NULL values.

  • Use Turbo Boyer-Moore algorithm to speed up LIKE "%keyword%" searches.

  • Fixed bug in DROP DATABASE with symlink.

  • Fixed crash in REPAIR ... USE_FRM.

  • Fixed bug in EXPLAIN with LIMIT offset != 0.

  • Fixed bug in phrase operator "..." in boolean full-text search.

  • Fixed bug that caused duplicated rows when using truncation operator * in boolean full-text search.

  • Fixed bug in truncation operator of boolean full-text search (incorrect results when there are only +word*s in the query).

  • Fixed bug in boolean full-text search that caused a crash when an identical MATCH expression that did not use an index appeared twice.

  • Query cache is now automatically disabled in mysqldump.

  • Fixed problem on Windows 98 that made sending of results very slow.

  • Boolean full-text search weighting scheme changed to something more reasonable.

  • Fixed bug in boolean full-text search that caused MySQL to ignore queries of ft_min_word_len characters.

  • Boolean full-text search now supports 鈥phrase searches.

  • New configure option --without-query-cache.

  • Memory allocation strategy for 鈥root memory鈥 changed. Block size now grows with number of allocated blocks.

  • INET_NTOA() now returns NULL if you give it an argument that is too large (greater than the value corresponding to 255.255.255.255).

  • Fix SQL_CALC_FOUND_ROWS to work with UNION. It works only if the first SELECT has this option and if there is global LIMIT for the entire statement. For the moment, this requires using parentheses for individual SELECT queries within the statement.

  • Fixed bug in SQL_CALC_FOUND_ROWS and LIMIT.

  • Don't give an error for CREATE TABLE ...(... VARCHAR(0)).

  • Fixed SIGINT and SIGQUIT problems in mysql.cc on Linux with some glibc versions.

  • Fixed bug in convert.cc, which is caused by having an incorrect net_store_length() linked in the CONVERT::store() method.

  • DOUBLE and FLOAT columns now honor the UNSIGNED flag on storage.

  • InnoDB now retains foreign key constraints through ALTER TABLE and CREATE/DROP INDEX.

  • InnoDB now allows foreign key constraints to be added through the ALTER TABLE syntax.

  • InnoDB tables can now be set to automatically grow in size (auto-extend).

  • Added --ignore-lines=n option to mysqlimport. This has the same effect as the IGNORE n LINES clause for LOAD DATA.

  • Fixed bug in UNION with last offset being transposed to total result set.

  • REPAIR ... USE_FRM added.

  • Fixed that DEFAULT_SELECT_LIMIT is always imposed on UNION result set.

  • Fixed that some SELECT options can appear only in the first SELECT.

  • Fixed bug with LIMIT with UNION, where last select is in the braces.

  • Fixed that full-text works fine with UNION operations.

  • Fixed bug with indexless boolean full-text search.

  • Fixed bug that sometimes appeared when full-text search was used with const tables.

  • Fixed incorrect error value when doing a SELECT with an empty HEAP table.

  • Use ORDER BY column DESC now sorts NULL values first. (In other words, NULL values sort first in all cases, whether or not DESC is specified.) This is changed back in 4.0.10.

  • Fixed bug in WHERE key_name='constant' ORDER BY key_name DESC.

  • Fixed bug in SELECT DISTINCT ... ORDER BY DESC optimization.

  • Fixed bug in ... HAVING 'GROUP_FUNCTION'(xxx) IS [NOT] NULL.

  • Fixed bug in truncation operator for boolean full-text search.

  • Allow value of --user option for mysqld to be specified as a numeric user ID (--user=user_id).

  • Fixed a bug where SQL_CALC_ROWS returned an incorrect value when used with one table and ORDER BY and with InnoDB tables.

  • Fixed that SELECT 0 LIMIT 0 doesn't hang thread.

  • Fixed some problems with USE/IGNORE INDEX when using many keys with the same start column.

  • Don't use table scan with BerkeleyDB and InnoDB tables when we can use an index that covers the whole row.

  • Optimized InnoDB sort-buffer handling to take less memory.

  • Fixed bug in multiple-table DELETE and InnoDB tables.

  • Fixed problem with TRUNCATE and InnoDB tables that produced the error Can't execute the given command because you have active locked tables or an active transaction.

  • Added NO_UNSIGNED_SUBTRACTION to the set of flags that may be specified with the --sql-mode option for mysqld. It disables unsigned arithmetic rules when it comes to subtraction. (This makes MySQL 4.0 behave more like 3.23 with UNSIGNED columns).

  • The result returned for all bit functions (|, <<, ...) is now of type unsigned integer.

  • Added detection of nan values in MyISAM to make it possible to repair tables with nan in float or double columns.

  • Fixed new bug in myisamchk where it didn't correctly update number of 鈥parts鈥 in the MyISAM index file.

  • Changed to use autoconf 2.52 (from autoconf 2.13).

  • Fixed optimization problem where the MySQL Server was in 鈥preparing鈥 state for a long time when selecting from an empty table which had contained a lot of rows.

  • Fixed bug in complicated join with const tables. This fix also improves performance a bit when referring to another table from a const table.

  • First pre-version of multiple-table UPDATE statement.

  • Fixed bug in multiple-table DELETE.

  • Fixed bug in SELECT CONCAT(argument_list) ... GROUP BY 1.

  • INSERT ... SELECT did a full rollback in case of an error. Fixed so that we only roll back the last statement in the current transaction.

  • Fixed bug with empty expression for boolean full-text search.

  • Fixed core dump bug in updating full-text key from/to NULL.

  • ODBC compatibility: Added BIT_LENGTH() function.

  • Fixed core dump bug in GROUP BY BINARY column.

  • Added support for NULL keys in HEAP tables.

  • Use index for ORDER BY in queries of type: SELECT * FROM t WHERE key_part1=1 ORDER BY key_part1 DESC, key_part2 DESC

  • Fixed bug in FLUSH QUERY CACHE.

  • Added CAST() and CONVERT() functions. The CAST and CONVERT functions are nearly identical and mainly useful when you want to create a column with a specific type in a CREATE ... SELECT statement. For more information, read Section聽12.9, 鈥淐ast Functions and Operators鈥.

  • CREATE ... SELECT on DATE and TIME functions now create columns of the expected type.

  • Changed order in which keys are created in tables.

  • Added new columns Null and Index_type to SHOW INDEX output.

  • Added --no-beep and --prompt options to mysql command-line client.

  • New feature: management of user resources.

    GRANT ... WITH MAX_QUERIES_PER_HOUR N1
                   MAX_UPDATES_PER_HOUR N2
                   MAX_CONNECTIONS_PER_HOUR N3;
    

    See Section聽5.8.4, 鈥淟imiting Account Resources鈥.

  • Added mysql_secure_installation to the scripts/ directory.

B.2.30.聽Changes in release 4.0.1 (23 December 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • Added system command to mysql.

  • Fixed bug when HANDLER was used with some unsupported table type.

  • mysqldump now puts ALTER TABLE tbl_name DISABLE KEYS and ALTER TABLE tbl_name ENABLE KEYS in the sql dump.

  • Added mysql_fix_extensions script.

  • Fixed stack overrun problem with LOAD DATA FROM MASTER on OSF/1.

  • Fixed shutdown problem on HP-UX.

  • Added DES_ENCRYPT() and DES_DECRYPT() functions.

  • Added FLUSH DES_KEY_FILE statement.

  • Added --des-key-file option to mysqld.

  • HEX(str) now returns the characters in str converted to hexadecimal.

  • Fixed problem with GRANT when using lower_case_table_names=1.

  • Changed SELECT ... IN SHARE MODE to SELECT ... LOCK IN SHARE MODE (as in MySQL 3.23).

  • A new query cache to cache results from identical SELECT queries.

  • Fixed core dump bug on 64-bit machines when it got an incorrect communication packet.

  • MATCH ... AGAINST(... IN BOOLEAN MODE) can now work without FULLTEXT index.

  • Fixed slave to replicate from 3.23 master.

  • Miscellaneous replication fixes/cleanup.

  • Got shutdown to work on Mac OS X.

  • Added myisam/ft_dump utility for low-level inspection of FULLTEXT indexes.

  • Fixed bug in DELETE ... WHERE ... MATCH ....

  • Added support for MATCH ... AGAINST(... IN BOOLEAN MODE). Note: You must rebuild your tables with ALTER TABLE tbl_name TYPE=MyISAM to be able to use boolean full-text search.

  • LOCATE() and INSTR() are now case sensitive if either argument is a binary string.

  • Changed RAND() initialization so that RAND(N) and RAND(N+1) are more distinct.

  • Fixed core dump bug in UPDATE ... ORDER BY.

  • In 3.23, INSERT INTO ... SELECT always had IGNORE enabled. Now MySQL stops (and possibly rolls back) by default in case of an error unless you specify IGNORE.

  • Ignore DATA DIRECTORY and INDEX DIRECTORY directives on Windows.

  • Added boolean full-text search code. It should be considered early alpha.

  • Extended MODIFY and CHANGE in ALTER TABLE to accept the FIRST and AFTER keywords.

  • Indexes are now used with ORDER BY on a whole InnoDB table.

B.2.31.聽Changes in release 4.0.0 (October 2001: Alpha)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • Added --xml option to mysql for producing XML output.

  • Added full-text variables ft_min_word_len, ft_max_word_len, and ft_max_word_len_for_sort system variables.

  • Added full-text variables ft_min_word_len, ft_max_word_len, and ft_max_word_len_for_sort variables to myisamchk.

  • Added documentation for libmysqld, the embedded MySQL server library. Also added example programs (a mysql client and mysqltest test program) which use libmysqld.

  • Removed all Gemini hooks from MySQL server.

  • Removed my_thread_init() and my_thread_end() from mysql_com.h, and added mysql_thread_init() and mysql_thread_end() to mysql.h.

  • Support for communication packets > 16MB. In 4.0.1 we extended MyISAM to be able to handle these.

  • Secure connections (with SSL).

  • Unsigned BIGINT constants now work. MIN() and MAX() now handle signed and unsigned BIGINT numbers correctly.

  • New character set latin1_de which provides correct German sorting.

  • STRCMP() now uses the current character set when doing comparisons, which means that the default comparison behavior now is case insensitive.

  • TRUNCATE TABLE and DELETE FROM tbl_name are now separate functions. One bonus is that DELETE FROM tbl_name now returns the number of deleted rows, rather than zero.

  • DROP DATABASE now executes a DROP TABLE on all tables in the database, which fixes a problem with InnoDB tables.

  • Added support for UNION.

  • Added support for multiple-table DELETE operations.

  • A new HANDLER interface to MyISAM tables.

  • Added support for INSERT on MERGE tables. Patch from Benjamin Pflugmann.

  • Changed WEEK(date,0) to match the calendar in the USA.

  • COUNT(DISTINCT) is about 30% faster.

  • Speed up all internal list handling.

  • Speed up IS NULL, ISNULL() and some other internal primitives.

  • Full-text index creation now is much faster.

  • Tree-like cache to speed up bulk inserts and myisam_bulk_insert_tree_size variable.

  • Searching on packed (CHAR/VARCHAR) keys is now much faster.

  • Optimized queries of type: SELECT DISTINCT * FROM tbl_name ORDER by key_part1 LIMIT row_count.

  • SHOW CREATE TABLE now shows all table attributes.

  • ORDER BY ... DESC can now use keys.

  • LOAD DATA FROM MASTERautomatically鈥 sets up a slave.

  • Renamed safe_mysqld to mysqld_safe to make this name more in line with other MySQL scripts/commands.

  • Added support for symbolic links to MyISAM tables. Symlink handling is now enabled by default for Windows.

  • Added SQL_CALC_FOUND_ROWS and FOUND_ROWS(). This makes it possible to know how many rows a query would have returned without a LIMIT clause.

  • Changed output format of SHOW OPEN TABLES.

  • Allow SELECT expression LIMIT ....

  • Added the IDENTITY variable as a synonym for the LAST_INSERT_ID variable (like Sybase).

  • Added ORDER BY syntax to UPDATE and DELETE.

  • SHOW INDEXES is now a synonym for SHOW INDEX.

  • Added ALTER TABLE tbl_name DISABLE KEYS and ALTER TABLE tbl_name ENABLE KEYS commands.

  • Allow use of IN as a synonym for FROM in SHOW commands.

  • Implemented 鈥repair by sort鈥 for FULLTEXT indexes. REPAIR TABLE, ALTER TABLE, and OPTIMIZE TABLE for tables with FULLTEXT indexes are now up to 100 times faster.

  • Allow standard SQL syntax X'hexadecimal-number'.

  • Cleaned up global lock handling for FLUSH TABLES WITH READ LOCK.

  • Fixed problem with DATETIME = constant in WHERE optimization.

  • Added --master-data and --no-autocommit options to mysqldump. (Thanks to Brian Aker for this.)

  • Added script mysql_explain_log.sh to distribution. (Thanks to mobile.de).

B.3.聽Changes in release 3.23.x

B.3.1. Changes in release 3.23.59 (Not yet released)
B.3.2. Changes in release 3.23.58 (11 September 2003)
B.3.3. Changes in release 3.23.57 (06 June 2003)
B.3.4. Changes in release 3.23.56 (13 March 2003)
B.3.5. Changes in release 3.23.55 (23 January 2003)
B.3.6. Changes in release 3.23.54 (05 December 2002)
B.3.7. Changes in release 3.23.53 (09 October 2002)
B.3.8. Changes in release 3.23.52 (14 August 2002)
B.3.9. Changes in release 3.23.51 (31 May 2002)
B.3.10. Changes in release 3.23.50 (21 April 2002)
B.3.11. Changes in release 3.23.49 (14 February 2002)
B.3.12. Changes in release 3.23.48 (07 February 2002)
B.3.13. Changes in release 3.23.47 (27 December 2001)
B.3.14. Changes in release 3.23.46 (29 November 2001)
B.3.15. Changes in release 3.23.45 (22 November 2001)
B.3.16. Changes in release 3.23.44 (31 October 2001)
B.3.17. Changes in release 3.23.43 (04 October 2001)
B.3.18. Changes in release 3.23.42 (08 September 2001)
B.3.19. Changes in release 3.23.41 (11 August 2001)
B.3.20. Changes in release 3.23.40 (18 July 2001)
B.3.21. Changes in release 3.23.39 (12 June 2001)
B.3.22. Changes in release 3.23.38 (09 May 2001)
B.3.23. Changes in release 3.23.37 (17 April 2001)
B.3.24. Changes in release 3.23.36 (27 March 2001)
B.3.25. Changes in release 3.23.35 (15 March 2001)
B.3.26. Changes in release 3.23.34a (11 March 2001)
B.3.27. Changes in release 3.23.34 (10 March 2001)
B.3.28. Changes in release 3.23.33 (09 February 2001)
B.3.29. Changes in release 3.23.32 (22 January 2001)
B.3.30. Changes in release 3.23.31 (17 January 2001: Production)
B.3.31. Changes in release 3.23.30 (04 January 2001)
B.3.32. Changes in release 3.23.29 (16 December 2000)
B.3.33. Changes in release 3.23.28 (22 November 2000: Gamma)
B.3.34. Changes in release 3.23.27 (24 October 2000)
B.3.35. Changes in release 3.23.26 (18 October 2000)
B.3.36. Changes in release 3.23.25 (29 September 2000)
B.3.37. Changes in release 3.23.24 (08 September 2000)
B.3.38. Changes in release 3.23.23 (01 September 2000)
B.3.39. Changes in release 3.23.22 (31 July 2000)
B.3.40. Changes in release 3.23.21 (04 July 2000)
B.3.41. Changes in release 3.23.20 (28 June 2000: Beta)
B.3.42. Changes in release 3.23.19
B.3.43. Changes in release 3.23.18 (11 June 2000)
B.3.44. Changes in release 3.23.17 (07 June 2000)
B.3.45. Changes in release 3.23.16 (16 May 2000)
B.3.46. Changes in release 3.23.15 (08 May 2000)
B.3.47. Changes in release 3.23.14 (09 April 2000)
B.3.48. Changes in release 3.23.13 (14 March 2000)
B.3.49. Changes in release 3.23.12 (07 March 2000)
B.3.50. Changes in release 3.23.11 (16 February 2000)
B.3.51. Changes in release 3.23.10 (30 January 2000)
B.3.52. Changes in release 3.23.9 (29 January 2000)
B.3.53. Changes in release 3.23.8 (02 January 2000)
B.3.54. Changes in release 3.23.7 (10 December 1999)
B.3.55. Changes in release 3.23.6 (15 December 1999)
B.3.56. Changes in release 3.23.5 (20 October 1999)
B.3.57. Changes in release 3.23.4 (28 September 1999)
B.3.58. Changes in release 3.23.3 (13 September 1999)
B.3.59. Changes in release 3.23.2 (09 August 1999)
B.3.60. Changes in release 3.23.1 (08 July 1999)
B.3.61. Changes in release 3.23.0 (05 July 1999: Alpha)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

The 3.23 release has several major features that are not present in previous versions. We have added three new table types:

  • MyISAM

    A new ISAM library which is tuned for SQL and supports large files.

  • InnoDB

    A transaction-safe storage engine that supports row level locking, and many Oracle-like features.

  • BerkeleyDB or BDB

    Uses the Berkeley DB library from Sleepycat Software to implement transaction-safe tables.

Note that only MyISAM is available in the standard binary distribution.

The 3.23 release also includes support for database replication between a master and many slaves, full-text indexing, and much more.

All new features are being developed in the 4.1.x and 5.0.x versions. Only serious bugfixes are added to 3.23.

B.3.1.聽Changes in release 3.23.59 (Not yet released)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • Fixed an old bug in concurrent accesses to MERGE tables (even one MERGE table and MyISAM tables), that could've resulted in a crash or hang of the server. (Bug#2408, CVE-2004-0837)

  • Fixed incorrect destruction of expression which led to crash of server on complex AND/OR expressions if query was ignored (either by a replication server because of --replicate-*-table rules, or by any MySQL server because of a syntax error). (Bug#3969, Bug#4494)

  • Fixed problem with parsing complex queries on 64-bit architectures. (Bug#4204)

  • Fixed a symlink vulnerability in the mysqlbug script. (Bug#3284, CVE-2004-0381)

  • Fixed bug in privilege checking of ALTER TABLE RENAME. (Bug#3270, CVE-2004-0835)

  • Fixed bugs in ACOS(), ASIN() (Bug#2338) and in FLOOR() (Bug#3051). The cause of the problem is an overly strong optimization done by gcc in this case.

  • Fixed bug in INSERT ... SELECT statements where, if a NOT NULL column is assigned a value of NULL, the following columns in the row might be assigned a value of zero. (Bug#2012)

  • If a query was ignored on the slave (because of --replicate-ignore-table and other similar rules), the slave still checked if the query got the same error code (0, no error) as on the master. So if the master had an error on the query (for example, 鈥Duplicate entry鈥 in a multiple-row insert), then the slave stopped and warned that the error codes didn't match. This is a backport of the fix for MySQL 4.0. (Bug#797)

  • mysqlbinlog now asks for a password at console when the -p/--password option is used with no argument. This is how the other clients (mysqladmin, mysqldump..) behave. Note that one now has to use mysqlbinlog -p<my_password>; mysqlbinlog -p <my_password> does not work anymore (in other words, put no space after -p). (Bug#1595)

  • On some 64-bit machines (some HP-UX and Solaris machines), a slave installed with the 64-bit MySQL binary could not connect to its master (it connected to itself instead). (Bug#1256, Bug#1381)

  • Fixed a Windows-specific bug present since MySQL 3.23.57 and 3.23.58 that caused Windows slaves to crash when they started replication if a master.info file existed. (Bug#1720)

  • Fixed bug in ALTER TABLE RENAME, when rename to the table with the same name in another database silently dropped destination table if it existed. (Bug#2628)

  • Fixed potential memory overrun in mysql_real_connect() (which required a compromised DNS server and certain operating systems). (Bug#4017, CVE-2004-0836)

B.3.2.聽Changes in release 3.23.58 (11 September 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • Fixed buffer overflow in password handling which could potentially be exploited by MySQL users with ALTER privilege on the mysql.user table to execute random code or to gain shell access with the UID of the mysqld process (thanks to Jedi/Sector One for spotting and reporting this bug).

  • mysqldump now correctly quotes all identifiers when communicating with the server. This assures that during the dump process, mysqldump never sends queries to the server that result in a syntax error. This problem is not related to the mysqldump program's output, which was not changed. (Bug#1148)

  • Fixed table/column grant handling: The proper sort order (from most specific to less specific, see Section聽5.7.6, 鈥淎ccess Control, Stage 2: Request Verification鈥) was not honored. (Bug#928)

  • Fixed overflow bug in MyISAM and ISAM when a row is updated in a table with a large number of columns and at least one BLOB/TEXT column.

  • Fixed MySQL so that field length (in C API) for the second column in SHOW CREATE TABLE is always larger than the data length. The only known application that was affected by the old behavior was Borland dbExpress, which truncated the output from the command. (Bug#1064)

  • Fixed ISAM bug in MAX() optimization.

  • Fixed Unknown error when doing ORDER BY on reference table which was used with NULL value on NOT NULL column. (Bug#479)

B.3.3.聽Changes in release 3.23.57 (06 June 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • Fixed problem in alarm handling that could cause problems when getting a packet that is too large.

  • Fixed problem when installing MySQL as a service on Windows when two arguments were specified to mysqld (option file group name and service name).

  • Fixed kill pid-of-mysqld to work on Mac OS X.

  • SHOW TABLE STATUS displayed incorrect Row_format value for tables that have been compressed with myisampack. (Bug#427)

  • SHOW VARIABLES LIKE 'innodb_data_file_path' displayed only the name of the first data file. (Bug#468)

  • Fixed security problem where mysqld didn't allow one to UPDATE rows in a table even if one had a global UPDATE privilege and a database SELECT privilege.

  • Fixed a security problem with SELECT and wildcarded select list, when user only had partial column SELECT privileges on the table.

  • Fixed unlikely problem in optimizing WHERE clause with a constant expression such as in WHERE 1 AND (a=1 AND b=1).

  • Fixed problem on IA-64 with timestamps that caused mysqlbinlog to fail.

  • The default option for innodb_flush_log_at_trx_commit was changed from 0 to 1 to make InnoDB tables ACID by default. See Section聽14.2.5, 鈥InnoDB Startup Options and System Variables鈥.

  • Fixed problem with too many allocated alarms on slave when connecting to master many times (normally not a very critical error).

  • Fixed a bug in replication of temporary tables. (Bug#183)

  • Fixed 64-bit bug that affected at least AMD hammer systems.

  • Fixed a bug when doing LOAD DATA INFILE IGNORE: When reading the binary log, mysqlbinlog and the replication code read REPLACE instead of IGNORE. This could make the slave's table become different from the master's table. (Bug#218)

  • Fixed overflow bug in MyISAM when a row is inserted into a table with a large number of columns and at least one BLOB/TEXT column. Bug was caused by incorrect calculation of the needed buffer to pack data.

  • The binary log was not locked during TRUNCATE tbl_name or DELETE FROM tbl_name statements, which could cause an INSERT to tbl_name to be written to the log before the TRUNCATE or DELETE statements.

  • Fixed rare bug in UPDATE of InnoDB tables where one row could be updated multiple times.

  • Produce an error for empty table and column names.

  • Changed PROCEDURE ANALYSE() to report DATE instead of NEWDATE.

  • Changed PROCEDURE ANALYSE(#) to restrict the number of values in an ENUM column to # also for string values.

  • mysqldump no longer silently deletes the binary logs when invoked with the --master-data or --first-slave option; while this behavior was convenient for some users, others may suffer from it. Now you must explicitly ask for binary logs to be deleted by using the new --delete-master-logs option.

  • Fixed a bug in mysqldump when it was invoked with the --master-data option: The CHANGE MASTER TO statements that were appended to the SQL dump had incorrect coordinates. (Bug#159)

B.3.4.聽Changes in release 3.23.56 (13 March 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • Fixed mysqld crash on extremely small values of sort_buffer variable.

  • Fixed a bug in privilege system for GRANT UPDATE on the column level.

  • Fixed a rare bug when using a date in HAVING with GROUP BY.

  • Fixed checking of random part of WHERE clause. (Bug#142)

  • Fixed MySQL (and myisamchk) crash on artificially corrupted .MYI files.

  • Security enhancement: mysqld no longer reads options from world-writable config files. (CVE-2003-0150)

  • Security enhancement: mysqld and safe_mysqld now use only the first --user option specified on the command line. Normally this comes from /etc/my.cnf. (CVE-2003-0150)

  • Security enhancement: Don't allow BACKUP TABLE to overwrite existing files.

  • Fixed unlikely deadlock bug when one thread did a LOCK TABLE and another thread did a DROP TABLE. In this case one could do a KILL on one of the threads to resolve the deadlock.

  • LOAD DATA INFILE was not replicated by slave if replicate_*_table was set on the slave.

  • Fixed a bug in handling CHAR(0) columns that could cause incorrect results from the query.

  • Fixed a bug in SHOW VARIABLES on 64-bit platforms. The bug was caused by incorrect declaration of variable server_id.

  • The Comment column in SHOW TABLE STATUS now reports that it can contain NULL values (which is the case for a crashed .frm file).

  • Fixed the rpl_rotate_logs test to not fail on certain platforms (such as Mac OS X) due to a too-long file name (changed slave-master-info.opt to .slave-mi).

  • Fixed a problem with BLOB NOT NULL columns used with IS NULL.

  • Fixed bug in MAX() optimization in MERGE tables.

  • Better RAND() initialization for new connections.

  • Fixed bug with connect timeout. This bug was manifested on OS's with poll() system call, which resulted in timeout the value specified as it was executed in both select() and poll().

  • Fixed bug in SELECT * FROM table WHERE datetime1 IS NULL OR datetime2 IS NULL.

  • Fixed bug in using aggregate functions as argument for INTERVAL, CASE, FIELD, CONCAT_WS, ELT and MAKE_SET functions.

  • When running with --lower-case-table-names=1 (default on Windows) and you had tables or databases with mixed case on disk, then executing SHOW TABLE STATUS followed with DROP DATABASE or DROP TABLE could fail with Errcode 13.

  • Fixed bug in logging to binary log (which affects replication) a query that inserts a NULL in an auto_increment field and also uses LAST_INSERT_ID().

  • Fixed bug in mysqladmin --relative.

  • On some 64-bit systems, show status reported a strange number for Open_files and Open_streams.

B.3.5.聽Changes in release 3.23.55 (23 January 2003)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • Fixed double free'd pointer bug in mysql_change_user() handling, that enabled a specially hacked version of MySQL client to crash mysqld. Note that you must log in to the server by using a valid user account to be able to exploit this bug. (CVE-2003-0073)

  • Fixed bug with the --slow-log when logging an administrator command (like FLUSH TABLES).

  • Fixed bug in GROUP BY when used on BLOB column with NULL values.

  • Fixed a bug in handling NULL values in CASE ... WHEN ....

  • Bugfix for --chroot (see Section聽B.3.6, 鈥淐hanges in release 3.23.54 (05 December 2002)鈥) is reverted. Unfortunately, there is no way to make it to work, without introducing backward-incompatible changes in my.cnf. Those who need --chroot functionality, should upgrade to MySQL 4.0. (The fix in the 4.0 branch did not break backward-compatibility).

  • Make --lower-case-table-names default on Mac OS X as the default filesystem (HFS+) is case insensitive.

  • Fixed a bug in scripts/mysqld_safe.sh in NOHUP_NICENESS testing.

  • Transactions in AUTOCOMMIT=0 mode didn't rotate binary log.

  • Fixed a bug in scripts/make_binary_distribution that resulted in a remaining @HOSTNAME@ variable instead of replacing it with the correct path to the hostname binary.

  • Fixed a very unlikely bug that could cause SHOW PROCESSLIST to core dump in pthread_mutex_unlock() if a new thread was connecting.

  • Forbid SLAVE STOP if the thread executing the query has locked tables. This removes a possible deadlock situation.

B.3.6.聽Changes in release 3.23.54 (05 December 2002)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • Fixed a bug, that allowed to crash mysqld with a specially crafted packet. (CVE-2002-1373)

  • Fixed a rare crash (double free'd pointer) when altering a temporary table.

  • Fixed buffer overrun in libmysqlclient library that allowed malicious MySQL server to crash the client application. (CVE-2002-1376)

  • Fixed security-related bug in mysql_change_user() handling. All users are strongly recommended to upgrade to the version 3.23.54. (CVE-2002-1374, CVE-2002-1375)

  • Fixed bug that prevented --chroot command-line option of mysqld from working.

  • Fixed bug that made OPTIMIZE TABLE to corrupt the table under some rare circumstances.

  • Fixed mysqlcheck so it can deal with table names containing dashes.

  • Fixed shutdown problem on Mac OS X.

  • Fixed bug with comparing an indexed NULL field with <=> NULL.

  • Fixed bug that caused IGNORE INDEX and USE INDEX sometimes to be ignored.

  • Fixed rare core dump problem in complicated GROUP BY queries that didn't return any result.

  • Fixed a bug where MATCH ... AGAINST () >=0 was treated as if it was >.

  • Fixed core dump in SHOW PROCESSLIST when running with an active slave (unlikely timing bug).

  • Make it possible to use multiple MySQL servers on Windows (code backported from 4.0.2).

  • One can create TEMPORARY MERGE tables now.

  • Fixed that --core-file works on Linux (at least on kernel 2.4.18).

  • Fixed a problem with BDB and ALTER TABLE.

  • Fixed reference to freed memory when doing complicated GROUP BY ... ORDER BY queries. Symptom was that mysqld died in function send_fields.

  • Allocate heap rows in smaller blocks to get better memory usage.

  • Fixed memory allocation bug when storing BLOB values in internal temporary tables used for some (unlikely) GROUP BY queries.

  • Fixed a bug in key optimizing handling where the expression WHERE col_name = key_col_name was calculated as true for NULL values.

  • Fixed core dump bug when doing LEFT JOIN ... WHERE key_column=NULL.

  • Fixed MyISAM crash when using dynamic-row tables with huge numbers of packed fields.

  • Updated source tree to be built using automake 1.5 and libtool 1.4.

B.3.7.聽Changes in release 3.23.53 (09 October 2002)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • Fixed crash when SHOW INNODB STATUS was used and skip-innodb was defined.

  • Fixed possible memory corruption bug in binary log file handling when slave rotated the logs (only affected 3.23, not 4.0).

  • Fixed problem in LOCK TABLES on Windows when one connects to a database that contains uppercase letters.

  • Fixed that --skip-show-database doesn't reset the --port option.

  • Small fix in safe_mysqld for some shells.

  • Fixed that FLUSH STATUS doesn't reset delayed_insert_threads.

  • Fixed core dump bug when using the BINARY cast on a NULL value.

  • Fixed race condition when someone did a GRANT at the same time a new user logged in or did a USE database.

  • Fixed bug in ALTER TABLE and RENAME TABLE when running with -O lower_case_table_names=1 (typically on Windows) when giving the table name in uppercase.

  • Fixed that -O lower_case_table_names=1 also converts database names to lowercase.

  • Fixed unlikely core dump with SELECT ... ORDER BY ... LIMIT.

  • Changed AND/OR to report that they can return NULL. This fixes a bug in GROUP BY on AND/OR expressions that return NULL.

  • Fixed a bug that OPTIMIZE TABLE of locked and modified MyISAM table, reported table corruption.

  • Fixed a BDB-related ALTER TABLE bug with dropping a column and shutting down immediately thereafter.

  • Fixed problem with configure ... --localstatedir=....

  • Fixed problem with UNSIGNED BIGINT on AIX (again).

  • Fixed bug in pthread_mutex_trylock() on HPUX 11.0.

  • Multi-threaded stress tests for InnoDB.

B.3.8.聽Changes in release 3.23.52 (14 August 2002)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • Wrap BEGIN/COMMIT around transaction in the binary log. This makes replication honor transactions.

  • Fixed security bug when having an empty database name in the user.db table.

  • Changed initialization of RAND() to make it less predicatable.

  • Fixed problem with GROUP BY on result with expression that created a BLOB field.

  • Fixed problem with GROUP BY on columns that have NULL values. To solve this we now create an MyISAM temporary table when doing a GROUP BY on a possible NULL item. From MySQL 4.0.5 we can use in memory HEAP tables for this case.

  • Fixed problem with privilege tables when downgrading from 4.0.2 to 3.23.

  • Fixed thread bug in SLAVE START, SLAVE STOP and automatic repair of MyISAM tables that could cause table cache to be corrupted.

  • Fixed possible thread related key-cache-corruption problem with OPTIMIZE TABLE and REPAIR TABLE.

  • Added name of 'administrator command' logs.

  • Fixed bug with creating an auto-increment value on second part of a UNIQUE() key where first part could contain NULL values.

  • Don't write slave-timeout reconnects to the error log.

  • Fixed bug with slave net read timeouting

  • Fixed a core-dump bug with MERGE tables and MAX() function.

  • Fixed bug in ALTER TABLE with BDB tables.

  • Fixed bug when logging LOAD DATA INFILE to binary log with no active database.

  • Fixed a bug in range optimizer (causing crashes).

  • Fixed possible problem in replication when doing DROP DATABASE on a database with InnoDB tables.

  • Fixed mysql_info() to return 0 for Duplicates value when using INSERT DELAYED IGNORE.

  • Added -DHAVE_BROKEN_REALPATH to the Mac OS X (darwin) compile options in configure.in to fix a failure under high load.

B.3.9.聽Changes in release 3.23.51 (31 May 2002)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • Fix bug with closing tags missing slash for mysqldump XML output.

  • Remove endspace from ENUM values. (This fixed a problem with SHOW CREATE TABLE.)

  • Fixed bug in CONCAT_WS() that cut the result.

  • Changed name of server variables Com_show_master_stat to Com_show_master_status and Com_show_slave_stat to Com_show_slave_status.

  • Changed handling of gethostbyname() to make the client library thread-safe even if gethostbyname_r doesn't exist.

  • Fixed core-dump problem when giving a wrong password string to GRANT.

  • Fixed bug in DROP DATABASE with symlinked directory.

  • Fixed optimization problem with DATETIME and value outside DATETIME range.

  • Removed Sleepycat's BDB doc files from the source tree, as they're not needed (MySQL covers BDB in its own documentation).

  • Fixed MIT-pthreads to compile with glibc 2.2 (needed for make dist).

  • Fixed the FLOAT(X+1,X) is not converted to FLOAT(X+2,X). (This also affected DECIMAL, DOUBLE and REAL types)

  • Fixed the result from IF() is case in-sensitive if the second and third arguments are case sensitive.

  • Fixed core dump problem on OSF/1 in gethostbyname_r.

  • Fixed that underflowed decimal fields are not zero filled.

  • If we get an overflow when inserting '+11111' for DECIMAL(5,0) UNSIGNED columns, we just drop the sign.

  • Fixed optimization bug with ISNULL(expression_which_cannot_be_null) and ISNULL(constant_expression).

  • Fixed host lookup bug in the glibc library that we used with the 3.23.50 Linux-x86 binaries.

B.3.10.聽Changes in release 3.23.50 (21 April 2002)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • Fixed buffer overflow problem if someone specified a too-long datadir parameter to mysqld. (CVE-2002-0969)

  • Add missing <row> tags for mysqldump XML output.

  • Fixed problem with crash-me and gcc 3.0.4.

  • Fixed that @@unknown_variable doesn't hang server.

  • Added @@VERSION as a synonym for VERSION().

  • SHOW VARIABLES LIKE 'xxx' is now case-insensitive.

  • Fixed timeout for GET_LOCK() on HP-UX with DCE threads.

  • Fixed memory allocation bug in the glibc library used to build Linux binaries, which caused mysqld to die in free().

  • Fixed SIGINT and SIGQUIT problems in mysql.

  • Fixed bug in character table converts when used with big (larger than 64KB) strings.

  • InnoDB now retains foreign key constraints through ALTER TABLE and CREATE/DROP INDEX.

  • InnoDB now allows foreign key constraints to be added through the ALTER TABLE syntax.

  • InnoDB tables can now be set to automatically grow in size (auto-extend).

  • Our Linux RPMS and binaries are now compiled with gcc 3.0.4, which should make them a bit faster.

  • Fixed some buffer overflow problems when reading startup parameters.

  • Because of problems on shutdown we have now disabled named pipes on Windows by default. One can enable named pipes by starting mysqld with --enable-named-pipe.

  • Fixed bug when using WHERE key_column = 'J' or key_column='j'.

  • Fixed core-dump bug when using --log-bin with LOAD DATA INFILE without an active database.

  • Fixed bug in RENAME TABLE when used with lower_case_table_names=1 (default on Windows).

  • Fixed unlikely core-dump bug when using DROP TABLE on a table that was in use by a thread that also used queries on only temporary tables.

  • Fixed problem with SHOW CREATE TABLE and PRIMARY KEY when using 32 indexes.

  • Fixed that one can use SET PASSWORD for the anonymous user.

  • Fixed core dump bug when reading client groups from option files using mysql_options().

  • Memory leak (16 bytes per every corrupted table) closed.

  • Fixed binary builds to use --enable-local-infile.

  • Update source to work with new version of bison.

  • Updated shell scripts to now agree with new POSIX standard.

  • Fixed bug where DATE_FORMAT() returned empty string when used with GROUP BY.

B.3.11.聽Changes in release 3.23.49 (14 February 2002)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • For a MERGE table, DELETE FROM merge_table used without a WHERE clause no longer clears the mapping for the table by emptying the .MRG file. Instead, it deletes records from the mapped tables.

  • Don't give warning for a statement that is only a comment; this is needed for mysqldump --disable-keys to work.

  • Fixed unlikely caching bug when doing a join without keys. In this case, the last used field for a table always returned NULL.

  • Added options to make LOAD DATA LOCAL INFILE more secure.

  • MySQL binary release 3.23.48 for Linux contained a new glibc library, which has serious problems under high load and Red Hat 7.2. The 3.23.49 binary release doesn't have this problem.

  • Fixed shutdown problem on NT.

B.3.12.聽Changes in release 3.23.48 (07 February 2002)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • Added --xml option to mysqldump for producing XML output.

  • Changed to use autoconf 2.52 (from autoconf 2.13)

  • Fixed bug in complicated join with const tables.

  • Added internal safety checks for InnoDB.

  • Some InnoDB variables were always shown in SHOW VARIABLES as OFF on high-byte-first systems (like SPARC).

  • Fixed problem with one thread using an InnoDB table and another thread doing an ALTER TABLE on the same table. Before that, mysqld could crash with an assertion failure in row0row.c, line 474.

  • Tuned the InnoDB SQL optimizer to favor index searches more often over table scans.

  • Fixed a performance problem with InnoDB tables when several large SELECT queries are run concurrently on a multiprocessor Linux computer. Large CPU-bound SELECT queries now also generally run faster on all platforms.

  • If MySQL binary logging is used, InnoDB now prints after crash recovery the latest MySQL binary log name and the offset InnoDB was able to recover to. This is useful, for example, when resynchronizing a master and a slave database in replication.

  • Added better error messages to help in installation problems of InnoDB tables.

  • It is now possible to recover MySQL temporary tables that have become orphaned inside the InnoDB tablespace.

  • InnoDB now prevents a FOREIGN KEY declaration where the signedness is not the same in the referencing and referenced integer columns.

  • Calling SHOW CREATE TABLE or SHOW TABLE STATUS could cause memory corruption and make mysqld crash. Especially at risk was mysqldump, because it frequently calls SHOW CREATE TABLE.

  • If inserts to several tables containing an AUTO_INCREMENT column were wrapped inside one LOCK TABLES, InnoDB asserted in lock0lock.c.

  • In 3.23.47 we allowed several NULL values in a UNIQUE secondary index for an InnoDB table. But CHECK TABLE was not relaxed: it reports the table as corrupt. CHECK TABLE no longer complains in this situation.

  • SHOW GRANTS now shows REFERENCES instead of REFERENCE.

B.3.13.聽Changes in release 3.23.47 (27 December 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • Fixed bug when using the following construct: SELECT ... WHERE key=@var_name OR key=@var_name2

  • Restrict InnoDB keys to 500 bytes.

  • InnoDB now supports NULL in keys.

  • Fixed shutdown problem on HP-UX. (Introduced in 3.23.46)

  • Fixed core dump bug in replication when using SELECT RELEASE_LOCK().

  • Added new statement: DO expr[,expr]...

  • Added slave-skip-errors option.

  • Added statistics variables for all MySQL commands. (SHOW STATUS is now much longer.)

  • Fixed default values for InnoDB tables.

  • Fixed that GROUP BY expr DESC works.

  • Fixed bug when using t1 LEFT JOIN t2 ON t2.key=constant.

  • mysql_config now also works with binary (relocated) distributions.

B.3.14.聽Changes in release 3.23.46 (29 November 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • Fixed problem with aliased temporary table replication.

  • InnoDB and BDB tables now use index when doing an ORDER BY on the whole table.

  • Fixed bug where one got an empty set instead of a DEADLOCK error when using BDB tables.

  • One can now kill ANALYZE TABLE, REPAIR TABLE, and OPTIMIZE TABLE when the thread is waiting to get a lock on the table.

  • Fixed race condition in ANALYZE TABLE.

  • Fixed bug when joining with caching (unlikely to happen).

  • Fixed race condition when using the binary log and INSERT DELAYED which could cause the binary log to have rows that were not yet written to MyISAM tables.

  • Changed caching of binary log to make replication slightly faster.

  • Fixed bug in replication on Mac OS X.

B.3.15.聽Changes in release 3.23.45 (22 November 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • (UPDATE|DELETE) ...WHERE MATCH bugfix.

  • shutdown should now work on Darwin (Mac OS X).

  • Fixed core dump when repairing corrupted packed MyISAM files.

  • --core-file now works on Solaris.

  • Fix a bug which could cause InnoDB to complain if it cannot find free blocks from the buffer cache during recovery.

  • Fixed bug in InnoDB insert buffer B-tree handling that could cause crashes.

  • Fixed bug in InnoDB lock timeout handling.

  • Fixed core dump bug in ALTER TABLE on a TEMPORARY InnoDB table.

  • Fixed bug in OPTIMIZE TABLE that reset index cardinality if it was up to date.

  • Fixed problem with t1 LEFT_JOIN t2 ... WHERE t2.date_column IS NULL when date_column was declared as NOT NULL.

  • Fixed bug with BDB tables and keys on BLOB columns.

  • Fixed bug in MERGE tables on OS with 32-bit file pointers.

  • Fixed bug in TIME_TO_SEC() when using negative values.

B.3.16.聽Changes in release 3.23.44 (31 October 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • Fixed Rows_examined count in slow query log.

  • Fixed bug when using a reference to an AVG() column in HAVING.

  • Fixed that date functions that require correct dates, like DAYOFYEAR(column), return NULL for 0000-00-00 dates.

  • Fixed bug in const-propagation when comparing columns of different types. (SELECT * FROM date_col="2001-01-01" and date_col=time_col)

  • Fixed bug that caused error message Can't write, because of unique constraint with some GROUP BY queries.

  • Fixed problem with sjis character strings used within quoted table names.

  • Fixed core dump when using CREATE ... FULLTEXT keys with other storage engines than MyISAM.

  • Don't use signal() on Windows because this appears to not be 100% reliable.

  • Fixed bug when doing WHERE col_name=NULL on an indexed column that had NULL values.

  • Fixed bug when doing LEFT JOIN ... ON (col_name = constant) WHERE col_name = constant.

  • When using replications, aborted queries that contained % could cause a core dump.

  • TCP_NODELAY was not used on some systems. (Speed problem.)

  • Applied portability fixes for OS/2. (Patch by Yuri Dario.)

The following changes are for InnoDB tables:

  • Add missing InnoDB variables to SHOW VARIABLES.

  • Foreign key checking is now done for InnoDB tables.

  • DROP DATABASE now works also for InnoDB tables.

  • InnoDB now supports data files and raw disk partitions bigger than 4GB on those operating systems that have big files.

  • InnoDB calculates better table cardinality estimates for the MySQL optimizer.

  • Accent characters in the default character set latin1 are ordered according to the MySQL ordering.

    Note: If you are using latin1 and have inserted characters whose code is greater than 127 into an indexed CHAR column, you should run CHECK TABLE on your table when you upgrade to 3.23.44, and drop and reimport the table if CHECK TABLE reports an error!

  • A new my.cnf parameter, innodb_thread_concurrency, helps in performance tuning in heavily concurrent environments.

  • A new my.cnf parameter, innodb_fast_shutdown, speeds up server shutdown.

  • A new my.cnf parameter, innodb_force_recovery, helps to save your data in case the disk image of the database becomes corrupt.

  • innodb_monitor has been improved and a new innodb_table_monitor added.

  • Increased maximum key length from 500 to 7000 bytes.

  • Fixed a bug in replication of AUTO_INCREMENT columns with multiple-line inserts.

  • Fixed a bug when the case of letters changes in an update of an indexed secondary column.

  • Fixed a hang when there are more than 24 data files.

  • Fixed a crash when MAX(col) is selected from an empty table, and col is not the first column in a multi-column index.

  • Fixed a bug in purge which could cause crashes.

B.3.17.聽Changes in release 3.23.43 (04 October 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • Fixed a bug in INSERT DELAYED and FLUSH TABLES introduced in 3.23.42.

  • Fixed unlikely bug, which returned non-matching rows, in SELECT with many tables and multi-column indexes and 'range' type.

  • Fixed an unlikely core dump bug when doing EXPLAIN SELECT when using many tables and ORDER BY.

  • Fixed bug in LOAD DATA FROM MASTER when using table with CHECKSUM=1.

  • Added unique error message when a DEADLOCK occurs during a transaction with BDB tables.

  • Fixed problem with BDB tables and UNIQUE columns defined as NULL.

  • Fixed problem with myisampack when using pre-space filled CHAR columns.

  • Applied patch from Yuri Dario for OS/2.

  • Fixed bug in --safe-user-create.

B.3.18.聽Changes in release 3.23.42 (08 September 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • Fixed problem when using LOCK TABLES and BDB tables.

  • Fixed problem with REPAIR TABLE on MyISAM tables with row lengths in the range from 65517 to 65520 bytes.

  • Fixed rare hang when doing mysqladmin shutdown when there was a lot of activity in other threads.

  • Fixed problem with INSERT DELAYED where delayed thread could be hanging on upgrading locks for no apparent reason.

  • Fixed problem with myisampack and BLOB.

  • Fixed problem when one edited .MRG tables by hand. (Patch from Benjamin Pflugmann).

  • Enforce that all tables in a MERGE table come from the same database.

  • Fixed bug with LOAD DATA INFILE and transactional tables.

  • Fix bug when using INSERT DELAYED with wrong column definition.

  • Fixed core dump during REPAIR TABLE of some particularly broken tables.

  • Fixed bug in InnoDB and AUTO_INCREMENT columns.

  • Fixed bug in InnoDB and RENAME TABLE columns.

  • Fixed critical bug in InnoDB and BLOB columns. If you have used BLOB columns larger than 8000 bytes in an InnoDB table, it is necessary to dump the table with mysqldump, drop it and restore it from the dump.

  • Applied large patch for OS/2 from Yuri Dario.

  • Fixed problem with InnoDB when one could get the error Can't execute the given command... even when no transaction was active.

  • Applied some minor fixes that concern Gemini.

  • Use real arithmetic operations even in integer context if not all arguments are integers. (Fixes uncommon bug in some integer contexts).

  • Don't force everything to lowercase on Windows. (To fix problem with Windows and ALTER TABLE.) Now --lower_case_table_names also works on Unix.

  • Fixed that automatic rollback is done when thread end doesn't lock other threads.

B.3.19.聽Changes in release 3.23.41 (11 August 2001)

End of Product LifecycleActive development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).

  • Added --sql-mode=value[,value[,value]] option to mysqld. See Section聽5.2.2, 鈥淐ommand Options鈥.

  • Fixed possible problem with shutdown on Solaris where the .pid file wasn't deleted.

  • InnoDB now supports < 4GB rows. The former limit was 8000 bytes.

  • The doublewrite file flush method is used in InnoDB. It reduces the need for Unix fsync() calls to a fraction and improves performance on most Unix flavors.

  • You can now use the InnoDB Monitor to print a lot of InnoDB state information, including locks, to the standard output. This is useful in performance tuning.

  • Several bugs which could cause hangs in InnoDB have been fixed.

  • Split record_buffer to record_buffer and record_rnd_buffer. To make things compatible to previous MySQL versions, if record_rnd_buffer is not set, then it takes the value of record_buffer.

  • Fixed optimizing bug in ORDER BY where some ORDER BY parts where wrongly removed.

  • Fixed overflow bug with ALTER TABLE and MERGE tables.

  • Added prototypes for my_thread_init() and my_thread_end() to mysql_com.h

  • Added --safe-user-create option to mysqld.

  • Fixed bug in SELECT DISTINCT ... HAVING that caused error message Can't find record in #...

B.3.20.聽Changes in release 3.23.40 (18 July 2001)

End of Product Lifec