先日 [4.1.7は正式版の模様] とお知らせしたばかりですが、早速、その MySQL 4.1.7 がリリースされました。
　これまで、αリリース → βリリース → γリリース とテスト版をたどってきた 4.1.x の、最初の製品バージョンリリースです。　
すでにメーリングリストにも情報が寄せられているとおり4.1.7 では 、いわゆる「半角かな」の扱いに不具合があるようですのでご注意ください。


　MySQL 4.1.x は 4.0.x からの 「事実上のメジャーバージョンアップ」です。バージョン移行の際には どうぞ念入りに検証を。


以下チェンジログ：
-------

■Functionality added or changed:

- InnoDB: SHOW TABLE STATUS now shows the creation time of the table for InnoDB. Note that this timestamp might not be the correct time because, e.g., ALTER TABLE changes this timestamp.

- 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.

- InnoDB: New mysqld option --innodb-table-locks and session variable innodb_table_locks (on by default). You can now disable InnoDB table locks if your application depends on the way MySQL did table locks before 4.1.2. See section 16.17 Restrictions on InnoDB Tables. (Bug #3299, Bug #5998)


■Bugs fixed:

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

- Fixed a bug with NATURAL JOIN in prepared statements. (Bug#6046).

- Fixed a bug in join of tables from different databases having columns with identical names (prepared statements). (Bug#6050)

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

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

- Fixed REVOKE ALL PRIVILEGES, GRANT OPTION FROM user so that all privileges are revoked correctly. (Bug #5831). This corrects a case that the fix in 4.1.6 could miss.

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

- Fixed a bug in the prepared statements protocol when wrong metadata was sent for SELECT statements not returning a result set (such as SELECT ... INTO OUTFILE). (Bug #6059)

- Fixed bug which allowed one to circumvent missing UPDATE privilege if one had INSERT and SELECT privileges for table with primary key. (Bug #6173)

- Fixed a bug in libmysqlclient with wrong conversion of negative time values to strings. (Bug #6049).

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

- Fixed a bug that caused the server to crash on attempt to prepare a statement with RAND(?). (Bug #5985)

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

- Fixed a bug with handling of TINYINT columns in the binary protocol. The problem is specific to platforms where the C compiler has the char data type unsigned by default. (Bug #6024)

- InnoDB: Fixed problem introduced in MySQL 4.0.21 where a connection starting a transaction, doing updates, then FLUSH TABLES WITH READ LOCK, then COMMIT, would cause replication slaves to stop complaining about error 1223. Bug surfaced when using the InnoDB innobackup script. (Bug #5949)

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