Skip navigation links
B.1.22 Changes in MySQL 4.1.4 (26 August 2004 Gamma) »
Section Navigation      [Toggle]

B.1.21. Changes in MySQL 4.1.5 (16 September 2004)

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.

Functionality added or changed:

  • InnoDB: The new Windows installation wizard of MySQL makes InnoDB as the MySQL default table type on Windows, unless explicitly specified otherwise. Note that it places the my.ini file in the installation directory of the MySQL server. See Section 2.3.4.14, “The Location of the my.ini File”.

  • InnoDB: Added the configuration option innodb_autoextend_increment for setting the size in megabytes by which InnoDB tablespaces are extended when they become full. The default value is 8, corresponding to the fixed increment of 8MB in previous versions of MySQL.

Bugs fixed:

  • Executing a prepared statement with BETWEEN ? AND ? and a datetime column caused the server to crash. (Bug#5748)

  • Detection of using the same table for updating and selecting in multi-update queries was not done correctly. (Bug#5455)

  • InnoDB: A maximum of 1000 connections could occur inside InnoDB at the same time, a higher number causing an assertion failure. Now the maximum can be much higher, and depends on the buffer pool size. (Bug#5414)

  • After reaching a certain limit of prepared statements per connection (97), statement IDs began to overlap, so occasionally wrong statements were chosen for execution. (Bug#5399)

  • The values of the max_sort_length, sql_mode, and group_concat_max_len system variables now are stored in the query cache with other query information to avoid returning an incorrect result from the query cache. (Bug#5394, Bug#5515)

  • OPTIMIZE TABLE could cause table corruption on FULLTEXT indexes. (Bug#5327)

  • Name resolution of external columns of subqueries was done correctly if the subquery was placed in the select list of the outer query and used grouping. (Bug#5326)

  • The syntax analyzer did not handle the IGNORE_SPACE server SQL mode correctly, using (for example) default.07 in place of default .07. (Bug#5318)

  • Executing a statement containing thousands of placeholders caused a buffer overflow in the prepared statements API (libmysqlclient). (Bug#5194)

  • The internal field length of integer user variables was incorrect. This showed up when creating a table as SELECT @var_name. (Bug#4788)

  • A prepared statement using LIKE and called with arguments in different character sets caused the server to crash. (Bug#4368)

  • Providing '0000-00-00' date as a prepared statement parameter value led to a server crash. (Bug#4231, Bug#4562)