Released on 27 Jan 2006
MySQL 4.1.18 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 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.

Functionality Added or Changed

  • MySQL 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

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

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

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

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

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

  • 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 the server was not compiled with InnoDB support. (Bug #15429)

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

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

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