持續蓬勃發展的資料庫軟體Mysql官方日前釋出了各平台的Mysql 5.0.20版本，繼一個月前的5.0.19只差了不到一個月就更新。
Mysql 5.0.20更新下載頁面
Mysql 5.0.20功能與bug更新列表
新增加的功能如下：
Functionality added or changed:
Added the –sysdate-is-now option to mysqld to enable SYSDATE() to be treated as an alias for NOW(). See Section 12.5, “Date and Time Functions”. (Bug #15101)
InnoDB: The InnoDB storage engine now provides a descriptive error message if ibdata file information is omitted from my.cnf. (Bug #16827)
The NDBCluster storage engine now supports INSERT IGNORE and REPLACE statements. Previously, these statements failed with an error. (Bug #17431)
Builds for Windows, Linux, and Unix (except AIX) platforms now have SSL support enabled, in the server as well as in the client libraries. Because part of the SSL code is written in C++, this does introduce dependencies on the system's C++ runtime libraries in several cases, depending on compiler specifics. (Bug #18195)
The syntax for CREATE PROCEDURE and CREATE FUNCTION statements now includes a DEFINER clause. The DEFINER value specifies the security context to be used when checking access privileges at routine invocation time if the routine has the SQL SECURITY DEFINER characteristic. See Section 17.2.1, “CREATE PROCEDURE and CREATE FUNCTION Syntax”, for more information.
When mysqldump is invoked with the –routines option, it now dumps the DEFINER value for stored routines.
Large file support added to build for QNX platform. (Bug #17336)
Large file support was re-enabled for the MySQL server binary for the AIX 5.2 platform. (Bug #13571)
Bugs fixed:
If the WHERE condition of a query contained an OR-ed FALSE term, the set of tables whose rows cannot serve for null-complements in outer joins was determined incorrectly. This resulted in blocking possible conversions of outer joins into joins by the optimizer for such queries. (Bug #17164)
mysql_config returned incorrect libraries on x86_64 systems. (Bug #13158)
Stored routine names longer than 64 characters were silently truncated. Now the limit is properly enforced and an error occurs. (Bug #17015)
During conversion from one character set to ucs2, multi-byte characters with no ucs2 equivalent were converted to multiple characters, rather than to 0x003F QUESTION MARK. (Bug #15375)
The mysql_close() C API function leaked handles for shared-memory connections on Windows. (Bug #15846)
Checks for permissions on database operations could be performed in a case-insensitive manner (a user with permissions on database MYDATABASE could by accident get permissions on database myDataBase), if the privilege data were still cached from a previous check. (Bug #17279)
If InnoDB ran out of buffer space for row locks and adaptive hashes, the server would crash. Now InnoDB rolls back the transaction. (Bug #18238)
InnoDB tables with an adaptive hash blocked other queries during CHECK TABLE statements while the entire hash was checked. This could be a long time for a large hash. (Bug #17126)
For InnoDB tables created in MySQL 4.1 or earlier, or created in 5.0 or later with compact format, updating a row so that a long column is updated or the length of some column changes, InnoDB later would fail to reclaim the BLOB storage space if the row was deleted. (Bug #18252)
InnoDB had a memory leak for duplicate-key errors with tables having 90 columns or more. (Bug #18384)
Checks for permissions on database operations could be performed in a case-insensitive manner (a user with permissions on database MYDATABASE could by accident get permissions on database myDataBase), if the privilege data were still cached from a previous check. (Bug #17279)
InnoDB: The LATEST FOREIGN KEY ERROR section in the output of SHOW INNODB STATUS was sometimes formatted incorrectly, causing problems with scripts that parsed the output of this statement. (Bug #16814)
When using ORDER BY with a non-string column inside GROUP_CONCAT() the result's character set was converted to binary. (Bug #18281)
See also Bug #14169.
SELECT … WHERE column LIKE 'A%' when column had a key and used the latin2_czech_cs collation. (Bug #17374)
Complex queries with nested joins could cause a server crash. (Bug #18279)
The server could deadlock under
