Skip navigation links

Additional languages
MySQL 3.23, 4.0, 4.1 Reference Manual :: B MySQL Change History :: B.1 Changes in release 4.1.x (Production) :: B.1.19 Changes in MySQL 4.1.7 (23 October 2004: Production)
B.1.20 Changes in MySQL 4.1.6 (10 October 2004) »
Section Navigation      [Toggle]

B.1.19. Changes in MySQL 4.1.7 (23 October 2004: Production)

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:

  • MOD() no longer rounds arguments with a fractional part to integers. Now it returns exact remainder after division. (Bug#6138)

  • Added a startup option and settable system variable innodb_table_locks for making LOCK TABLE acquire locks on InnoDB tables. The default value is 1, which means that LOCK TABLES also causes InnoDB to take a table lock internally. In applications using AUTOCOMMIT=1 and LOCK TABLES, InnoDB's internal table locks (added in MySQL 4.0.20 and 4.1.2) can cause deadlocks. You can set innodb_table_locks=0 in my.cnf to remove that problem.

    In addition, SHOW TABLE STATUS now shows the creation time of InnoDB tables. That this timestamp might not always be correct because (for example) it was changed by ALTER TABLE. See Section 13.2.17, “Restrictions on InnoDB Tables”. (Bug#3299, Bug#5998)

  • InnoDB: If innodb_thread_concurrency would be exceeded, let a thread sleep 10 ms before entering the FIFO queue; previously, the value was 50 ms.

Bugs fixed:

  • Security Fix: A missing UPDATE privilege could be circumvented by a user having INSERT and SELECT privileges for table with a primary key. (Bug#6173)

  • Fixed a bug that could cause MyISAM index corruption when key values start with character codes below BLANK. This was caused by the new key sort order in 4.1. (Bug#6151)

  • Now implicit access to system time zone description tables (which happens when you set the time_zone variable or use CONVERT_TZ() function) does not require any privileges. (Bug#6116)

  • Fixed a bug with FOUND_ROWS() used together with LIMIT clause in prepared statements. (Bug#6088)

  • Fixed crash when selecting from a HEAP table with key_column IS NOT NULL. This could also cause a crash if not all index parts where used. (Bug#6082)

  • Fixed a bug which caused the server to crash when the deprecated libmysqlclient function mysql_create_db() was called. (Bug#6081)

  • Bad metadata was sent for SELECT statements not returning a result set (such as SELECT ... INTO OUTFILE) by the prepared statements protocol. (Bug#6059)

  • Fixed a bug in libmysqlclient with wrong conversion of zero date values (0000-00-00) to strings. (Bug#6058)

  • Join of tables from different databases having columns with identical names did not work correctly, returning the error Column 'xxx' in field list is ambiguous. (Bug#6050)

  • libmysqlclient did not convert negative time values to strings correctly. (Bug#6049)

  • NATURAL JOIN did not work correctly in prepared statements. . (Bug#6046)

  • Fixed a bug with handling of DATE, TIME, and DATETIME columns in the binary protocol. The problem is compiler-specific and could have been observed on HP-UX, AIX, Solaris9, when compiling with native compiler. (Bug#6025)

  • TINYINT columns were not handled correctly in the binary protocol. The problem was specific to platforms where the C compiler has the char data type unsigned by default. (Bug#6024)

  • Attempting to prepare a statement with RAND(?) caused the server to crash. (Bug#5985)

  • InnoDB: Release the dictionary latch during a long cascaded FOREIGN KEY operation, so that we do not starve other users doing CREATE TABLE or other DDL operation. This caused a notorious 'Long semaphore wait' message to be printed to the .err log. (Bug#5961)

  • Fixed problem introduced in MySQL 4.0.21 where a connection starting a transaction, doing updates, then FLUSH TABLES WITH READ LOCK, followed by COMMIT, would cause replication slaves to stop (error 1223). This issue occurred when using the InnoDB innobackup script. (Bug#5949)

  • InnoDB: LOAD DATA INFILE…REPLACE printed duplicate key errors when executing the same LOAD statement several times. (Bug#5835)

  • REVOKE ALL PRIVILEGES, GRANT OPTION FROM user did not remove all privileges correctly. (Bug#5831)