Skip navigation links

Additional languages
MySQL 3.23, 4.0, 4.1 Reference Manual :: B MySQL Change History :: B.2 Changes in release 4.0.x :: B.2.23 Changes in release 4.0.9 (09 January 2003)
B.2.24 Changes in release 4.0.8 (07 January 2003) »
Section Navigation      [Toggle]

B.2.23. Changes in release 4.0.9 (09 January 2003)

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).

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.