Skip navigation links

Additional languages
B.1.21 Changes in MySQL 4.1.4 (26 August 2004: Gamma) »
Section Navigation      [Toggle]

B.1.20. 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. 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:

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

  • Fixed a bug which caused the server to crash on attempt to execute a prepared statement with BETWEEN ? AND ? and a datetime column. (Bug#5748)

  • Fixed detection of using same table for updating and selecting in multi-update queries. (Bug#5455)

  • InnoDB: Fixed a bug that InnoDB only allowed a maximum of 1000 connections inside InnoDB at the same time. A higher number could cause an assertion failure in sync0arr.c, line 384. Now we allow 1000, 10000, or 50000, depending on the buffer pool size. (Bug#5414)

  • Fixed a bug in the server when 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)

  • Fixed a bug in OPTIMIZE TABLE that could cause table corruption on FULLTEXT indexes. (Bug#5327)

  • Fixed name resolving of external fields of subqueries if subquery placed in select list of query with grouping. (Bug#5326)

  • Fixed syntax analyzer with sql_mode=IGNORE_SPACE. It happened to take phrases like default .07 as identifier.identifier. (Bug#5318)

  • Fixed a buffer overflow in prepared statements API (libmysqlclient) when a statement containing thousands of placeholders was executed. (Bug#5194)

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

  • Fixed a bug in prepared statements when LIKE used with arguments in different character sets crashed server on first execute. (Bug#4368)

  • Fixed a bug in prepared statements when providing '0000-00-00' date to a parameter lead to server crash. (Bug#4231, Bug#4562)