Skip navigation links
MySQL 3.23, 4.0, 4.1 Reference Manual :: B MySQL Change History :: B.3 Changes in Release 3.23.x :: B.3.37 Changes in Release 3.23.24 (08 September 2000)
B.3.38 Changes in Release 3.23.23 (01 September 2000) »
Section Navigation      [Toggle]

B.3.37. Changes in Release 3.23.24 (08 September 2000)

End of Product Lifecycle. Active 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 Created_tmp_disk_tables variable to mysqld.

  • To make it possible to reliably dump and restore tables with TIMESTAMP(X) columns, MySQL now reports columns with X other than 14 or 8 to be strings.

  • Changed sort order for latin1 as it was before MySQL 3.23.23. Any table that was created or modified with 3.23.22 must be repaired if it has CHAR columns that may contain characters with ASCII values greater than 128!

  • Fixed small memory leak introduced from 3.23.22 when creating a temporary table.

  • Fixed problem with BDB tables and reading on a unique (not primary) key.

  • Restored the win1251 character set (it is now only marked deprecated).