MySQL

3.23.21

Released on 4 Jul 2000
MySQL 3.23.21 Changelog

End of Product Lifecycle. Active development and support for MySQL Database Server versions 3.23, 4.0, and 4.1 has ended. For details, see http://www.mysql.com/about/legal/lifecycle/#calendar. Please consider upgrading to a recent version. Further updates to the content of this manual will be minimal. All formats of this manual will continue to be available until 31 Dec 2010.

  • Added mysql_character_set_name() function to the MySQL C API.

  • Made the update log ASCII 0 safe.

  • Added the mysql_config script.

  • Fixed problem when using < or > with a char column that was only partly indexed.

  • One would get a core dump if the log file was not readable by the MySQL user.

  • Changed mysqladmin to use CREATE DATABASE and DROP DATABASE statements instead of the old deprecated API calls.

  • Fixed chown warning in safe_mysqld.

  • Fixed a bug in ORDER BY that was introduced in 3.23.19.

  • Only optimize the DELETE FROM tbl_name to do a drop+create of the table if we are in autocommit mode (needed for BDB tables).

  • Added extra checks to avoid index corruption when the ISAM/MyISAM index files get full during an INSERT/UPDATE.

  • myisamchk didn't correctly update row checksum when used with -ro (this only gave a warning in subsequent runs).

  • Fixed bug in REPAIR TABLE so that it works with tables without indexes.

  • Fixed buffer overrun in DROP DATABASE.

  • LOAD TABLE FROM MASTER is sufficiently bug-free to announce it as a feature.

  • MATCH and AGAINST are now reserved words.