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.21 Changes in Release 3.23.39 (12 June 2001)
B.3.22 Changes in Release 3.23.38 (09 May 2001) »
Section Navigation      [Toggle]

B.3.21. Changes in Release 3.23.39 (12 June 2001)

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.

  • The AUTO_INCREMENT sequence wasn't reset when dropping and adding an AUTO_INCREMENT column.

  • CREATE ... SELECT now creates nonunique indexes delayed.

  • Fixed problem where LOCK TABLES tbl_name READ followed by FLUSH TABLES put an exclusive lock on the table.

  • REAL @variable values were represented with only 2 digits when converted to strings.

  • Fixed problem that client “hung” when LOAD TABLE FROM MASTER failed.

  • myisamchk --fast --force no longer repairs tables that only had the open count wrong.

  • Added functions to handle symbolic links to make life easier in 4.0.

  • We are now using the -lcma thread library on HP-UX 10.20 so that MySQL is more stable on HP-UX.

  • Fixed problem with IF() and number of decimals in the result.

  • Fixed date-part extraction functions to work with dates where day and/or month is 0.

  • Extended argument length in option files from 256 to 512 chars.

  • Fixed problem with shutdown when INSERT DELAYED was waiting for a LOCK TABLE.

  • Fixed core dump bug in InnoDB when tablespace was full.

  • Fixed problem with MERGE tables and big tables (larger than 4GB) when using ORDER BY.