Skip navigation links

Additional languages
MySQL 3.23, 4.0, 4.1 Reference Manual :: B MySQL Change History :: B.3 Changes in release 3.23.x :: B.3.43 Changes in release 3.23.18 (11 June 2000)
B.3.44 Changes in release 3.23.17 (07 June 2000) »
Section Navigation      [Toggle]

B.3.43. Changes in release 3.23.18 (11 June 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).

  • Fixed a problem from 3.23.17 when choosing character set on the client side.

  • Added FLUSH TABLES WITH READ LOCK to make a global lock suitable for making a copy of MySQL data files.

  • CREATE TABLE ... SELECT ... PROCEDURE now works.

  • Internal temporary tables now use compressed index when using GROUP BY on VARCHAR/CHAR columns.

  • Fixed a problem when locking the same table with both a READ and a WRITE lock.

  • Fixed problem with myisamchk and RAID tables.