MySQL (32-bit) 歷史版本列表 Page13

更新時間：2009-04-02
更新細節：

What's new in this version:

Functionality added or changed:

* mysql-test-run.pl now supports an --experimental=file_name option. It enables you to specify a file that contains a list of test cases that should be displayed with the [ exp-fail ] code rather than [ fail ] if they fail. (Bug#42888)

* The MD5 algorithm now uses the Xfree implementation. (Bug#42434)

* The query cache now checks whether a SELECT statement begins with SQL_NO_CACHE to determine whether it can skip checking for the query result in the query cache. This is not supported when SQL_NO_CACHE occurs within a comment. (Bug#37416)

Bugs fixed:

* Partitioning: A duplicate key error raised when inserting into a partitioned table used a different error code from that returned by such an error raised when inserting into a table that was not partitioned. (Bug#38719)
See also Bug#28842.

* Partitioning: Several error messages relating to partitioned tables were incorrect or missing. (Bug#36001)

* Replication: When --binlog_format was set to STATEMENT, a statement unsafe for statement-based logging caused an error or warning to be issued even if sql_log_bin was set to 0. (Bug#41980)

* Replication: When using MIXED replication format and temporary tables were created in statement-based mode, but a later operation in the same session caused a switch to row-based mode, the temporary tables were not dropped on the slave at the end of the session. (Bug#40013)
See also Bug#43046.
This regression was introduced by Bug#20499.

* Replication: When using the MIXED replication format, UPDATE and DELETE statements that searched for rows where part of the key had nullable BIT columns failed. This occurred because operations that inserted the data were replicated as statements, but UPDATE and DELETE statements affecting the same data were replicated using row-based format.

This issue did not occur when using statement-based replication (only) or row-based replication (only). (Bug#39753)
See also Bug#39648.

* Replication: The server SQL mode in effect when a stored procedure was created was not retained in the binary log. This could cause a CREATE PROCEDURE statement that succeeded on the master to fail on the slave.

This issue was first noticed when a stored procedure was created when ANSI_QUOTES was in effect on the master, but could possibly cause failed CREATE PROCEDURE statements and other problems on the slave when using other server SQL modes as well. (Bug#39526)

* Replication: If --secure-file-priv was set on the slave, it was unable to execute LOAD DATA INFILE statements sent from the master when using mixed-format or statement-based replication.

As a result of this fix, this security restriction is now ignored on the slave in such cases; instead the slave checks whether the files were created and should be read by the slave in its --slave-load-tmpdir. (Bug#38174)

* Replication: Server IDs greater than 2147483647 (232 – 1) were represented by negative numbers in the binary log. (Bug#37313)

* Replication: When its disk becomes full, a replication slave may wait while writing the binary log, relay log or MyISAM tables, continuing after space has been made available. The error message provided in such cases was not clear about the frequency with which checking for free space is done (once every 60 seconds), and how long the server waits after space has been freed before continuing (also 60 seconds); this caused users to think that the server had hung.

These issues have been addressed by making the error message clearer, and dividing it into two separate messages:
1. The error message Disk is full writing 'filename' (Errcode: error_code). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space) is printed only once.
2. The warning Retry in 60 secs, Message reprinted in 600 secs is printed once every for every 10 times that the check for free space is made; that is, the check is performed once each 60 seconds, but the reminder that space needs to be freed is printed only once every 10 minutes (600 seconds).

(Bug#22082)

* Replication: The statements DROP PROCEDURE IF EXISTS and DROP FUNCTION IF EXISTS were not written to the binary log if the procedure or function to be dropped did not exist. (Bug#13684)

See also Bug#25705.

* Use of USE INDEX hints could cause EXPLAIN EXTENDED to crash. (Bug#43354)

* For InnoDB tables, overflow in an AUTO_INCREMENT column could cause a server crash. (Bug#43203)

* On 32-bit Windows, mysqld could not use large buffers due to a 2GB user mode address limit. (Bug#43082)

* stderr should be unbuffered, but when the server redirected stderr to a file, it became buffered. (Bug#42790)

* The DATA_TYPE column of the INFORMATION_SCHEMA.COLUMNS table displayed the UNSIGNED attribute for floating-point data types. (The column should contain only the data type name.) (Bug#42758)

* For InnoDB tables, spurious duplicate-key errors could occur when inserting into an AUTO_INCREMENT column. (Bug#42714)

* mysqldump included views that were excluded with the --ignore-table option. (Bug#42635)

* An earlier bug fix resulted in the problem that the InnoDB plugin could not be used with a server that was compiled with the built-in InnoDB. To handle this two changes were made:
o The server now supports an --ignore-builtin-innodb option that causes the server to behave as if the built-in InnoDB is not present. This option causes other InnoDB options not to be recognized.
o For the INSTALL PLUGIN statement, the server reads option (my.cnf) files just as during server startup. This enables the plugin to pick up any relevant options from those files. Consequently, a plugin no longer is started with each option set to its default value.

Because of this change, it is possible to add plugin options to an option file even before loading a plugin (if the loose prefix is used). It is also possible to uninstall a plugin, edit my.cnf, and install the plugin again. Restarting the plugin this way enables it to the new option values without a server restart.
Note

To take advantage of this bug fix, InnoDB Plugin 1.0.4 or higher is required.

(Bug#42610)

This regression was introduced by Bug#29263.

* With the ONLY_FULL_GROUP_BY SQL mode enabled, some legal queries failed. (Bug#42567)

* Tables could enter open table cache for a thread without being properly cleaned up, leading to a server crash. (Bug#42419)

* For InnoDB tables, inserting into floating-point AUTO_INCREMENT columns failed. (Bug#42400)

* The InnoDB btr_search_drop_page_hash_when_freed() function had a race condition. (Bug#42279)

* Parsing of the optional microsecond component of DATETIME values did not fail gracefully when that component width was larger than the allowed six places. (Bug#42146)

* mysqldumpslow parsed the --debug and --verbose options incorrectly. (Bug#42027)

* Queries that used the loose index scan access method could return no rows. (Bug#41610)

* The error message for a too-long column comment was Unknown error rather than a more appropriate message. (Bug#41465)

* Use of SELECT * allowed users with rights to only some columns of a view to access all columns. (Bug#41354)

* The server did not robustly handle problems hang if a table opened with HANDLER needed to be re-opened because it had been altered to use a different storage engine that does not support HANDLER. The server also failed to set an error if the re-open attempt failed. These problems could cause the server to crash or hang. (Bug#41110, Bug#41112)

* SELECT statements executed concurrently with INSERT statements for a MyISAM table could cause incorrect results to be returned from the query cache. (Bug#41098)

* For prepared statements, multibyte character sets were not taking into account when calculating max_length for string values and mysql_stmt_fetch() could return truncated strings. (Bug#41078)

* Deprecation warnings that referred to MySQL 5.2 were changed to refer to MySQL 6.0. (Bug#41077)

* For user-defined variables in a query result, incorrect length values were returned in the result metadata. (Bug#41030)

* On Windows, starting the server with an invalid value for innodb_flush_method caused a crash. (Bug#40757)

* MySQL 5.1 crashed with index merge algorithm and merge tables.
A query in the MyISAM merge table caused a crash if the index merge algorithm was being used. (Bug#40675)

* With strict SQL mode enabled, setting a system variable to an out-of-bounds value caused an assertion failure. (Bug#40657)

* Table temporary scans were slower than necessary due to use of mmap rather than caching, even with the myisam_use_mmap system variable disabled. (Bug#40634)

* For a view that references a table in another database, mysqldump wrote the view name qualified with the current database name. This makes it impossible to reload the dump file into a different database. (Bug#40345)

* On platforms where long and pointer variables have different sizes, MyISAM could copy key statistics incorrectly, resulting in a server crash or incorrect cardinality values. (Bug#40321)

* DELETE tried to acquire write (not read) locks for tables accessed within a subquery of the WHERE clause. (Bug#39843)

* perror did not produce correct output for error codes 153 to 163. (Bug#39370)

* Several functions in libmysqld called exit() when an error occurred rather than returning an error to the caller. (Bug#39289)

* The innodb_log_arch_dir system variable is no longer available but was present in some of the sample option files included with MySQL distributions (such as my-huge.cnf). The line was present as a comment but uncommenting it would cause server startup failure so the line has been removed. (Bug#38249)

* --help output for myisamchk did not list the --HELP option. (Bug#38103)

* Comparisons between row constructors, such as (a, b) = (c, d) resulted in unnecessary Illegal mix of collations errors for string columns. (Bug#37601)

* If a user created a view that referenced tables for which the user had disjoint privileges, an assertion failure occurred. (Bug#37191)

* An argument to the MATCH() function that was an alias for an expression other than a column name caused a server crash. (Bug#36737)

* The event, general_log, and slow_log tables in the mysql database store server_id values, but did not use an UNSIGNED column and thus were not able to store the full range of ID values. (Bug#36540)

* On Windows, the _PC macro in my_global.h was causing problems for modern compilers. It has been removed because it is no longer used. (Bug#34309)

* For DROP FUNCTION with names that were qualified with a database name, the database name was handled in case-sensitive fashion even with lower_case_table_names set to 1. (Bug#33813)

* mysqldump --compatible=mysql40 emitted statements referring to the character_set_client system variable, which is unknown before MySQL 4.1. Now the statements are enclosed in version-specific comments. (Bug#33550)

* Use of MBR spatial functions such as MBRTouches() with columns of InnoDB tables caused a server crash rather than an error. (Bug#31435)

* The mysql client mishandled input parsing if a delimiter command was not first on the line. (Bug#31060)

* SHOW PRIVILEGES listed the CREATE ROUTINE privilege as having a context of Functions,Procedures, but it is a database-level privilege. (Bug#30305)

* mysqld --help did not work as root. (Bug#30261)

* CHECK TABLE, REPAIR TABLE, ANALYZE TABLE, and OPTIMIZE TABLE erroneously reported a table to be corrupt if the table did not exist or the statement was terminated with KILL. (Bug#29458)

* SHOW TABLE STATUS could fail to produce output for tables with non-ASCII characters in their name. (Bug#25830)

* Allocation of stack space for error messages could be too small on HP-UX, leading to stack overflow crashes. (Bug#21476)

* Floating-point numbers could be handled with different numbers of digits depending on whether the text or prepared-statement protocol was used. (Bug#21205)

* ROUND() sometimes returned different results on different platforms. (Bug#15936)

更新時間：2009-03-05
更新細節：

What's new in this version:

Functionality added or changed:

* Important Change: Replication: RESET MASTER and RESET SLAVE
now reset the values shown for Last_IO_Error, Last_IO_Errno,
Last_SQL_Error, and Last_SQL_Errno in the output of SHOW SLAVE
STATUS. (Bug#34654: http://bugs.mysql.com/34654)

* Incompatible Change: The fix for
Bug#33699: http://bugs.mysql.com/33699 introduced a change to
the UPDATE statement such that assigning NULL to a NOT NULL
column caused an error even when strict SQL mode was not
enabled. The original behavior before was that such
assignments caused an error only in strict SQL mode, and
otherwise set the column to the the implicit default value for
the column data type and generated a warning. (For information
about implicit default values, see Section 10.1.4, "Data Type
Default Values.")
The change caused compatibility problems for applications that
relied on the original behavior. It also caused replication
problems between servers that had the original behavior and
those that did not, for applications that assigned NULL to NOT
NULL columns in UPDATE statements without strict SQL mode
enabled. This change has been reverted so that UPDATE again
had the original behavior. Problems can still occur if you
replicate between servers that have the modified UPDATE
behavior and those that do not.
(Bug#39265: http://bugs.mysql.com/39265)

* The libedit library was upgraded to version 2.11.
(Bug#42433: http://bugs.mysql.com/42433)

Bugs fixed:

* Security Fix: Using an XPath expression employing a scalar
expression as a FilterExpr
(http://www.w3.org/TR/xpath#NT-FilterExpr) with ExtractValue()
or UpdateXML() caused the server to crash. Such expressions
now cause an error instead.
(Bug#42495: http://bugs.mysql.com/42495)

* Replication: START SLAVE UNTIL did not work correctly with
--replicate-same-server-id enabled; when started with this
option, the slave did not perform events recorded in the relay
log and that originated from a different master.
Log rotation events are automatically generated and written
when rotating the binary log or relay log. Such events for
relay logs are usually ignored by the slave SQL thread because
they have the same server ID as that of the slave. However,
when --replicate-same-server-id was enabled, the rotation
event for the relay log was treated as if it originated on the
master, because the log's name and position were incorrectly
updated. This caused the MASTER_POS_WAIT() function always to
return NULL and thus to fail.
(Bug#38734: http://bugs.mysql.com/38734,
Bug#38934: http://bugs.mysql.com/38934)

* Replication: TRUNCATE statements failed to replicate when
statement-based binary logging mode was not available. The
issue was observed when using InnoDB with the transaction
isolation level set to READ UNCOMMITTED (thus forcing InnoDB
not to allow statement-based logging). However, the same
behavior could be reproduced using any transactional storage
engine supporting only row-based logging, regardless of the
isolation level. This was due to two separate problems:

1. An error was printed by InnoDB for TRUNCATE when using
statement-based logging mode where the transaction
isolation level was set to READ COMMITTED or READ
UNCOMMITTED, because InnoDB permits statement-based
replication for DML statements. However, TRUNCATE is not
transactional; since it is the equivalent of DROP TABLE
followed by CREATE TABLE, it is actually DDL, and should
therefore be allowed to be replicated as a statement.

2. TRUNCATE was not logged in mixed mode because of the
error just described; however, this error was not
reported to the client.

As a result of this fix, TRUNCATE is now treated as DDL for
purposes of binary logging and replication; that is, it is
always logged as a statement and so no longer causes an error
when replicated using a transactional storage engine such as
InnoDB. (Bug#36763: http://bugs.mysql.com/36763)
See also Bug#42643: http://bugs.mysql.com/42643.

* Replication: mysqlbinlog replay of CREATE TEMPORARY TABLE ...
LIKE statements and of TRUNCATE statements used on temporary
tables failed with Error 1146 (Table ... doesn't exist).
(Bug#35583: http://bugs.mysql.com/35583)

* Replication: In statement mode, mysqlbinlog failed to issue a
SET @@autommit statement when the autocommit mode was changed.
(Bug#34541: http://bugs.mysql.com/34541)

* Replication: LOAD DATA INFILE statements did not replicate
correctly from a master running MySQL 4.1 to a slave running
MySQL 5.1 or later. (Bug#31240: http://bugs.mysql.com/31240)

* A '%' character in SQL statements could cause the server to
crash. (Bug#42634: http://bugs.mysql.com/42634)

* An optimization introduced for
Bug#37553: http://bugs.mysql.com/37553 required an explicit
cast to be added for some uses of TIMEDIFF() because automatic
casting could produce incorrect results. (It was necessary to
use TIME(TIMEDIFF(...)).)
(Bug#42525: http://bugs.mysql.com/42525)

* On the IBM i5 platform, the MySQL configuration process caused
the system version of pthread_setschedprio() to be used. This
function returns SIGILL on i5 because it is not supported,
causing the server to crash. Now the my_pthread_setprio()
function in the mysys library is used instead.
(Bug#42524: http://bugs.mysql.com/42524)

* The SSL certficates included with MySQL distributions were
regenerated because the previous ones had expired.
(Bug#42366: http://bugs.mysql.com/42366)

* User variables within triggers could cause a crash if the
mysql_change_user() C API function was invoked.
(Bug#42188: http://bugs.mysql.com/42188)

* Dependent subqueries such as the following caused a memory
leak proportional to the number of outer rows:
SELECT COUNT(*) FROM t1, t2 WHERE t2.b
IN (SELECT DISTINCT t2.b FROM t2 WHERE t2.b = t1.a);
(Bug#42037: http://bugs.mysql.com/42037)

* Some queries using NAME_CONST(.. COLLATE ...) led to a server
crash due to a failed type cast.
(Bug#42014: http://bugs.mysql.com/42014)

* On Mac OS X, some of the universal client libraries were not
actually universal and were missing code for one or more
architectures. (Bug#41940: http://bugs.mysql.com/41940)

* String reallocation could cause memory overruns.
(Bug#41868: http://bugs.mysql.com/41868)

* Setting innodb_locks_unsafe_for_binlog should be equivalent to
setting the transaction isolation level to READ COMMITTED.
However, if both of those things were done, non-matching
semi-consistently read rows were not unlocked when they should
have been. (Bug#41671: http://bugs.mysql.com/41671)

* REPAIR TABLE crashed for compressed MyISAM tables.
(Bug#41574: http://bugs.mysql.com/41574)

* For a TIMESTAMP NOT NULL DEFAULT ... column, storing NULL as
the return value from some functions caused a "cannot be NULL"
error. NULL returns now correctly cause the column default
value to be stored. (Bug#41370: http://bugs.mysql.com/41370)

* The server cannot execute INSERT DELAYED statements when
statement-based binary logging is enabled, but the error
message displayed only the table name, not the entire
statement. (Bug#41121: http://bugs.mysql.com/41121)

* FULLTEXT indexes did not work for Unicode columns that used a
custom UCA collation. (Bug#41084: http://bugs.mysql.com/41084)

* The Windows installer displayed incorrect product names in
some images. (Bug#40845: http://bugs.mysql.com/40845)

* SELECT statements could be blocked by INSERT DELAYED
statements that were waiting for a lock, even with
low_priority_updates enabled.
(Bug#40536: http://bugs.mysql.com/40536)

* The query cache stored only partial query results if a
statement failed while the results were being sent to the
client. This could cause other clients to hang when trying to
read the cached result. Now if a statement fails, the result
is not cached. (Bug#40264: http://bugs.mysql.com/40264)

* When a MEMORY table became full, the error generated was
returned to the client but was not written to the error log.
(Bug#39886: http://bugs.mysql.com/39886)

* The expression ROW(...) IN (SELECT ... FROM DUAL) always
returned TRUE. (Bug#39069: http://bugs.mysql.com/39069)

* The greedy optimizer could cause a server crash due to
improper handling of nested outer joins.
(Bug#38795: http://bugs.mysql.com/38795)

* Use of COUNT(DISTINCT) prevented NULL testing in the HAVING
clause. (Bug#38637: http://bugs.mysql.com/38637)

* Enabling the sync_frm system variable had no effect on the
handling of .frm files for views.
(Bug#38145: http://bugs.mysql.com/38145)

* Setting myisam_repair_threads greater than 1 caused a server
crash for table repair or alteration operations for MyISAM
tables with multiple FULLTEXT indexes.
(Bug#37756: http://bugs.mysql.com/37756)

* The mysql client sometimes improperly interpreted string
escape sequences in non-string contexts.
(Bug#36391: http://bugs.mysql.com/36391)

* The query cache stored packets containing the server status of
the time when the cached statement was run. This might lead to
an incorrect transaction status on the client side if a
statement was cached during a transaction and later served
outside a transaction context (or vice versa).
(Bug#36326: http://bugs.mysql.com/36326)

* If the system time was adjusted backward during query
execution, the apparent execution time could be negative. But
in some cases these queries would be written to the slow query
log, with the negative execution time written as a large
unsigned number. Now statements with apparent negative
execution time are not written to the slow query log.
(Bug#35396: http://bugs.mysql.com/35396)

* libmysqld was not built with all character sets.
(Bug#32831: http://bugs.mysql.com/32831)

* For mysqld_multi, using the --mysqld=mysqld_safe option caused
the --defaults-file and --defaults-extra-file options to
behave the same way. (Bug#32136: http://bugs.mysql.com/32136)

* For Solaris package installation using pkgadd, the postinstall
script failed, causing the system tables in the mysql database
not to be created. (Bug#31164: http://bugs.mysql.com/31164)

* If the default database was dropped, the value of
character_set_database was not reset to character_set_server
as it should have been.
(Bug#27208: http://bugs.mysql.com/27208)

更新時間：2009-02-05
更新細節：

What's new in this version:

Functionality added or changed:

*A new status variable, Queries, indicates the number of statements executed by the server. This includes statements executed within stored programs, unlike the Questions variable which includes only statements sent to the server by clients. (Bug#41131)
*Performance of SELECT * retrievals from INFORMATION_SCHEMA.COLUMNS was improved slightly. (Bug#38918)
*Previously, index hints did not work for FULLTEXT searches. Now they work as follows:

For natural language mode searches, index hints are silently ignored. For example, IGNORE INDEX(i) is ignored with no warning and the index is still used.

For boolean mode searches, index hints with FOR ORDER BY or FOR GROUP BY are silently ignored. Index hints with FOR JOIN or no FOR modifier are honored. In contrast to how hints apply for non-FULLTEXT searches, the hint is used for all phases of query execution (finding rows and retrieval, grouping, and ordering). This is true even if the hint is given for a non-FULLTEXT index. (Bug#38842)

更新時間：2008-12-31
更新細節：

What's new in this version:

# New! Partitioning to improve performance and management of very large database environments
# New! Row-based/Hybrid Replication for improved replication security
# New! Event Scheduler to create and schedule jobs that perform various database tasks
# New! XPath Support
# New! Dynamic General/Slow Query Log
# New! Performance/Load Testing Utility (mysqlslap)
# Improved! Full Text Search (faster, new dev templates)
# Improved! Archive engine (better compression, more features)
# Improved! User session and problem SQL identification
# Improved! MySQL embedded library (libmysqld)

更新時間：2008-10-18
更新細節：

What's new in this version:

This is a bugfix release for the current production release family. It replaces MySQL 5.0.67 (binary) and 5.0.75 (source-only).

Functionality added or changed:

*Security Enhancement: To enable stricter control over the location from which user-defined functions can be loaded, the plugin_dir system variable has been backported from MySQL 5.1. If the value is non-empty, user-defined function object files can be loaded only from the directory named by this variable. If the value is empty, the behavior that is used prior to the inclusion of plugin_dir applies: The UDF object files must be located in a directory that is searched by your system's dynamic linker. (Bug#37428)
*A new status variable, Queries, indicates the number of statements executed by the server. This includes statements executed within stored programs, unlike the Questions variable which includes only statements sent to the server by clients. (Bug#41131)
*Previously, index hints did not work for FULLTEXT searches. Now they work as follows:
For natural language mode searches, index hints are silently ignored. For example, IGNORE INDEX(i) is ignored with no warning and the index is still used.
For boolean mode searches, index hints are honored. (Bug#38842)

Bugs fixed:

*Important Change: Security Fix: Additional corrections were made for the symlink-related privilege problem originally addressed in MySQL 5.0.60. The original fix did not correctly handle the data directory path name if it contained symlinked directories in its path, and the check was made only at table-creation time, not at table-opening time later. (Bug#32167, CVE-2008-2079)

See also Bug#39277.
*Security Enhancement: The server consumed excess memory while parsing statements with hundreds or thousands of nested boolean conditions (such as OR (OR ... (OR ... ))). This could lead to a server crash or incorrect statement execution, or cause other client statements to fail due to lack of memory. The latter result constitutes a denial of service. (Bug#38296)
*Incompatible Change: There were some problems using DllMain() hook functions on Windows that automatically do global and per-thread initialization for libmysqld.dll:
oPer-thread initialization: MySQL internally counts the number of active threads, which causes a delay in my_end() if not all threads have exited. But there are threads that can be started either by Windows internally (often in TCP/IP scenarios) or by users. Those threads do not necessarily use libmysql.dll functionality but still contribute to the open-thread count. (One symptom is a five-second delay in times for PHP scripts to finish.)
oProcess-initialization: my_init() calls WSAStartup that itself loads DLLs and can lead to a deadlock in the Windows loader.

To correct these problems, DLL initialization code now is not invoked from libmysql.dll by default. To obtain the previous behavior (DLL initialization code will be called), set the LIBMYSQL_DLLINIT environment variable to any value. This variable exists only to prevent breakage of existing Windows-only applications that do not call mysql_thread_init() and work okay today. Use of LIBMYSQL_DLLINIT is discouraged and is removed in MySQL 6.0. (Bug#37226, Bug#33031)
*Incompatible Change: SHOW STATUS took a lot of CPU time for calculating the value of the Innodb_buffer_pool_pages_latched status variable. Now this variable is calculated and included in the output of SHOW STATUS only if the UNIV_DEBUG symbol is defined at MySQL build time. (Bug#36600)
*Incompatible Change: In connection with view creation, the server created arc directories inside database directories and maintained useless copies of .frm files there. Creation and renaming procedures of those copies as well as creation of arc directories has been discontinued.

This change does cause a problem when downgrading to older server versions which manifests itself under these circumstances:
1.Create a view v_orig in MySQL 5.0.72 or higher.
2.Rename the view to v_new and then back to v_orig.
3.Downgrade to an older 5.0.x server and run mysql_upgrade.
4.Try to rename v_orig to v_new again. This operation fails.

As a workaround to avoid this problem, use either of these approaches:
oDump your data using mysqldump before downgrading and reload the dump file after downgrading.
oInstead of renaming a view after the downgrade, drop it and recreate it.

The downgrade problem introduced by the fix for this bug has been addressed as Bug#40021. (Bug#17823)
*Replication: When rotating relay log files, the slave deletes relay log files and then edits the relay log index file. Formerly, if the slave shut down unexpectedly between these two events, the relay log index file could then reference relay logs that no longer existed. Depending on the circumstances, this could when restarting the slave cause either a race condition or the failure of replication. (Bug#38826, Bug#39325)
*In example option files provided in MySQL distributions, the thread_stack value was increased from 64K to 128K. (Bug#41577)
*SET PASSWORD caused a server crash if the account name was given as CURRENT_USER(). (Bug#41456)
*The INFORMATION_SCHEMA.SCHEMA_PRIVILEGES table was limited to 7680 rows. (Bug#41079)
*In debug builds, obsolete debug code could be used to crash the server. (Bug#41041)
*CHECK TABLE ... FOR UPGRADE did not check for incompatible collation changes made in MySQL 5.0.48 (Bug#27562, Bug#29461, Bug#29499). This also affects mysqlcheck and mysql_upgrade, which cause that statement to be executed. See Section 2.18.3, “Checking Whether Table Indexes Must Be Rebuilt”. (Bug#40984)

See also Bug#39585.
*Some queries that used a “range checked for each record” scan could return incorrect results. (Bug#40974)
*Certain SELECT queries could fail with a Duplicate entry error. (Bug#40953)
*The FEDERATED handler had a memory leak. (Bug#40875)
*IF(..., CAST(longtext_val AS UNSIGNED), signed_val) as an argument to an aggregate function could cause an assertion failure. (Bug#40761)
*Prepared statements allowed invalid dates to be inserted when the ALLOW_INVALID_DATES SQL mode was not enabled. (Bug#40365)
*mc.exe is no longer needed to compile MySQL on Windows. This makes it possible to build MySQL from source using Visual Studio Express 2008. (Bug#40280)
*Support for the revision field in .frm files has been removed. This addresses the downgrading problem introduced by the fix for Bug#17823. (Bug#40021)
*If the operating system is configured to return leap seconds from OS time calls or if the MySQL server uses a time zone definition that has leap seconds, functions such as NOW() could return a value having a time part that ends with :59:60 or :59:61. If such values are inserted into a table, they would be dumped as is by mysqldump but considered invalid when reloaded, leading to backup/restore problems.

Now leap second values are returned with a time part that ends with :59:59. This means that a function such as NOW() can return the same value for two or three consecutive seconds during the leap second. It remains true that literal temporal values having a time part that ends with :59:60 or :59:61 are considered invalid.

For additional details about leap-second handling, see Section 9.7.2, “Time Zone Leap Second Support”. (Bug#39920)
*The server could crash during a sort-order optimization of a dependent subquery. (Bug#39844)
*With the ONLY_FULL_GROUP_BY SQL mode enabled, the check for non-aggregated columns in queries with aggregate functions, but without a GROUP BY clause was treating all the parts of the query as if they were in the select list. This is fixed by ignoring the non-aggregated columns in the WHERE clause. (Bug#39656)
*The server crashed if an integer field in a CSV file did not have delimiting quotes. (Bug#39616)
*CHECK TABLE failed for MyISAM INFORMATION_SCHEMA tables. (Bug#39541)
*For a TIMESTAMP column in an InnoDB table, testing the column with multiple conditions in the WHERE clause caused a server crash. (Bug#39353)
*The server returned a column type of VARBINARY rather than DATE as the result from the COALESCE(), IFNULL(), IF(), GREATEST(), or LEAST() functions or CASE expression if the result was obtained using filesort in an anonymous temporary table during the query execution. (Bug#39283)
*References to local variables in stored procedures are replaced with NAME_CONST(name, value) when written to the binary log. However, an “illegal mix of collation” error might occur when executing the log contents if the value's collation differed from that of the variable. Now information about the variable collation is written as well. (Bug#39182)
*Some recent releases for Solaris 10 were built on Solaris 10 U5, which included a new version of libnsl.so that does not work on U4 or earlier. To correct this, Solaris 10 builds now are created on machines that do not have that upgraded libnsl.so, so that they will work on Solaris 10 installations both with and without the upgraded libnsl.so. (Bug#39074)
*With binary logging enabled CREATE VIEW was subject to possible buffer overwrite and a server crash. (Bug#39040)
*Queries of the form SELECT ... REGEXP BINARY NULL could lead to a hung or crashed server. (Bug#39021)
*Statements of the form INSERT ... SELECT .. ON DUPLICATE KEY UPDATE col_name = DEFAULT could result in a server crash. (Bug#39002)
*Column names constructed due to wild-card expansion done inside a stored procedure could point to freed memory if the expansion was performed after the first call to the stored procedure. (Bug#38823)
*Repeated CREATE TABLE ... SELECT statements, where the created table contained an AUTO_INCREMENT column, could lead to an assertion failure. (Bug#38821)
*If delayed insert failed to upgrade the lock, it did not free the temporary memory storage used to keep newly constructed BLOB values in memory, resulting in a memory leak. (Bug#38693)
*A server crash resulted from concurrent execution of a multiple-table UPDATE that used a NATURAL or USING join together with FLUSH TABLES WITH READ LOCK or ALTER TABLE for the table being updated. (Bug#38691)
*On ActiveState Perl, mysql-test-run.pl --start-and-exit started but did not exit. (Bug#38629)
*Server-side cursors were not initialized properly, which could cause a server crash. (Bug#38486)
*Stored procedures involving substrings could crash the server on certain platforms due to invalid memory reads. (Bug#38469)
*A server crash or Valgrind warnings could result when a stored procedure selected from a view that referenced a function. (Bug#38291)
*Incorrect handling of aggregate functions when loose index scan was used caused a server crash. (Bug#38195)
*Queries containing a subquery with DISTINCT and ORDER BY could cause a server crash. (Bug#38191)
*Queries with a HAVING clause could return a spurious row. (Bug#38072)
*Use of spatial data types in prepared statements could cause memory leaks or server crashes. (Bug#37956, Bug#37671)
*The server crashed if an argument to a stored procedure was a subquery that returned more than one row. (Bug#37949)
*When analyzing the possible index use cases, the server was incorrectly reusing an internal structure, leading to a server crash. (Bug#37943)
*A SELECT with a NULL NOT IN condition containing a complex subquery from the same table as in the outer select caused an assertion failure. (Bug#37894)
*For InnoDB tables, ORDER BY ... DESC sometimes returned results in ascending order. (Bug#37830)
*If a table has a BIT NOT NULL column c1 with a length shorter than 8 bits and some additional NOT NULL columns c2, ..., and a SELECT query has a WHERE clause of the form (c1 = constant) AND c2 ..., the query could return an unexpected result set. (Bug#37799)
*Nesting of IF() inside of SUM() could cause an extreme server slowdown. (Bug#37662)
*The MONTHNAME() and DAYNAME() functions returned a binary string, so that using LOWER() or UPPER() had no effect. Now MONTHNAME() and DAYNAME() return a value in character_set_connection character set. (Bug#37575)
*TIMEDIFF() was erroneously treated as always returning a positive result. Also, CAST() of TIME values to DECIMAL dropped the sign of negative values. (Bug#37553)
*mysqlcheck used SHOW FULL TABLES to get the list of tables in a database. For some problems, such as an empty .frm file for a table, this would fail and mysqlcheck then would neglect to check other tables in the database. (Bug#37527)
*The <=> operator could return incorrect results when comparing NULL to DATE, TIME, or DATETIME values. (Bug#37526)
*Updating a view with a subquery in the CHECK option could cause an assertion failure. (Bug#37460)
*Statements that displayed the value of system variables (for example, SHOW VARIABLES) expect variable values to be encoded in character_set_system. However, variables set from the command line such as basedir or datadir were encoded using character_set_filesystem and not converted correctly. (Bug#37339)
*For a MyISAM table with CHECKSUM = 1 and ROW_FORMAT = DYNAMIC table options, a data consistency check (maximum record length) could fail and cause the table to be marked as corrupted. (Bug#37310)
*The max_length result set metadata value was calculated incorrectly under some circumstances. (Bug#37301)
*CREATE INDEX could crash with InnoDB plugin 1.0.1. (Bug#37284)
*Certain boolean-mode FULLTEXT searches that used the truncation operator did not return matching records and calculated relevance incorrectly. (Bug#37245)
*The NO_BACKSLASH_ESCAPES SQL mode was ignored for LOAD DATA INFILE and SELECT INTO ... OUTFILE. The setting is taken into account now. (Bug#37114)
*On a 32-bit server built without big tables support, the offset argument in a LIMIT clause might be truncated due to a 64-bit to 32-bit cast. (Bug#37075)
*If the server failed to expire binary log files at startup, it could crash. (Bug#37027)
*The code for the ut_usectime() function in InnoDB did not handle errors from the gettimeofday() system call. Now it retries gettimeofday() several times and updates the value of the Innodb_row_lock_time_max status variable only if ut_usectime() was successful. (Bug#36819)
*Use of CONVERT() with GROUP BY to convert numeric values to CHAR could return truncated results. (Bug#36772)
*A query which had an ORDER BY DESC clause that is satisfied with a reverse range scan could cause a server crash for some specific CPU/compiler combinations. (Bug#36639)
*Dumping information about locks in use by sending a SIGHUP signal to the server or by invoking the mysqladmin debug command could lead to a server crash in debug builds or to undefined behavior in production builds. (Bug#36579)
*The mysql client, when built with Visual Studio 2005, did not display Japanese characters. (Bug#36279)
*When the fractional part in a multiplication of DECIMAL values overflowed, the server truncated the first operand rather than the longest. Now the server truncates so as to produce more precise multiplications. (Bug#36270)
*A read past the end of the string could occur while parsing the value of the --innodb-data-file-path option. (Bug#36149)
*Host name values in SQL statements were not being checked for '@', which is illegal according to RFC952. (Bug#35924)
*The UUID() function returned UUIDs with the wrong time; this was because the offset for the time part in UUIDs was miscalculated. (Bug#35848)
*SHOW CREATE TABLE did not display a printable value for the default value of BIT columns. (Bug#35796)
*mysql_install_db failed on machines that had the host name set to localhost. (Bug#35754)
*Dynamic plugins failed to load on i5/OS. (Bug#35743)
*Freeing of an internal parser stack during parsing of complex stored programs caused a server crash. (Bug#35577, Bug#37269, Bug#37228)
*The max_length metadata value was calculated incorrectly for the FORMAT() function, which could cause incorrect result set metadata to be sent to clients. (Bug#35558)
*Index scans performed with the sort_union() access method returned wrong results, caused memory to be leaked, and caused temporary files to be deleted when the limit set by sort_buffer_size was reached. (Bug#35477, Bug#35478)
*If the server crashed with an InnoDB error due to unavailability of undo slots, errors could persist during rollback when the server was restarted: There are two UNDO slot caches (for INSERT and UPDATE). If all slots end up in one of the slot caches, a request for a slot from the other slot cache would fail. This can happen if the request is for an UPDATE slot and all slots are in the INSERT slot cache, or vice versa. (Bug#35352)
*For InnoDB tables, ALTER TABLE DROP failed if the name of the column to be dropped began with “foreign”. (Bug#35220)
*perror on Windows did not know about Win32 system error codes. (Bug#34825)
*EXPLAIN EXTENDED evaluation of aggregate functions that required a temporary table caused a server crash. (Bug#34773)
*Queries of the form SELECT ... WHERE string = ANY(...) failed when the server used a single-byte character set and the client used a multi-byte character set. (Bug#34760)

See also Bug#20835.
*Using OPTIMIZE TABLE as the first statement on an InnoDB table with an AUTO_INCREMENT column could cause a server crash. (Bug#34286)
*mysql_install_db failed if the server was running with an SQL mode of TRADITIONAL. This program now resets the SQL mode internally to avoid this problem. (Bug#34159)
*The mysql client incorrectly parsed statements containing the word “delimiter” in mid-statement. This fix is different from the one applied for this bug in MySQL 5.0.66. (Bug#33812)

See also Bug#38158.
*For a stored procedure containing a SELECT * ... RIGHT JOIN query, execution failed for the second call. (Bug#33811)
*Previously, use of index hints with views (which do not have indexes) produced the error ERROR 1221 (HY000): Incorrect usage of USE/IGNORE INDEX and VIEW. Now this produces ERROR 1176 (HY000): Key '...' doesn't exist in table '...', the same error as for base tables without an appropriate index. (Bug#33461)
*Cached queries that used 256 or more tables were not properly cached, so that later query invalidation due to a TRUNCATE TABLE for one of the tables caused the server to hang. (Bug#33362)
*Some division operations produced a result with incorrect precision. (Bug#31616)
*mysql_upgrade attempted to use the /proc file system even on systems that do not have it. (Bug#31605)
*mysqldump could fail to dump views containing a large number of columns. (Bug#31434)
*Queries executed using join buffering of BIT columns could produce incorrect results. (Bug#31399)
*ALTER TABLE CONVERT TO CHARACTER SET did not convert TINYTEXT or MEDIUMTEXT columns to a longer text type if necessary when converting the column to a different character set. (Bug#31291)
*On NetWare, mysql_install_db could appear to execute normally even if it failed to create the initial databases. (Bug#30129)
*The Serbian translation for the ER_INCORRECT_GLOBAL_LOCAL_VAR error was corrected. (Bug#29738)
*XA transaction rollbacks could result in corrupted transaction states and a server crash. (Bug#28323)
*On Windows, Visual Studio does not take into account some x86 hardware limitations, which led to incorrect results converting large DOUBLE values to unsigned BIGINT values. (Bug#27483)
*SSL support was not included in some “generic” RPM packages. (Bug#26760)
*In some cases, the parser interpreted the ; character as the end of input and misinterpreted stored program definitions. (Bug#26030)
*The Questions status variable is intended as a count of statements sent by clients to the server, but was also counting statements executed within stored routines. (Bug#24289)
*For access to the INFORMATION_SCHEMA.VIEWS table, the server did not check the SHOW VIEW and SELECT privileges, leading to inconsistency between output from that table and the SHOW CREATE VIEW statement. (Bug#22763)
*The FLUSH PRIVILEGES statement did not produce an error when it failed. (Bug#21226)
*A race condition between the mysqld.exe server and the Windows service manager could lead to inability to stop the server from the service manager. (Bug#20430)
*mysqld_safe would sometimes fail to remove the pid file for the old mysql process after a crash. As a result, the server would fail to start due to a false A mysqld process already exists... error. (Bug#11122)

更新時間：2008-08-12
更新細節：

What's new in this version:

This is a bugfix release for the current production release family. It replaces MySQL 5.0.51b.

Functionality added or changed:

* Security Enhancement: To enable stricter control over the location from which user-defined functions can be loaded, the plugin_dir system variable has been backported from MySQL 5.1. If the value is non-empty, user-defined function object files can be loaded only from the directory named by this variable. If the value is empty, the behavior that is used before 5.0.67 applies: The UDF object files must be located in a directory that is searched by your system's dynamic linker. (Bug#37428)
* Important Change: Incompatible Change: The FEDERATED storage engine is now disabled by default in the .cnf files shipped with MySQL distributions (my-huge.cnf, my-medium.cnf, and so forth). This affects server behavior only if you install one of these files. (Bug#37069)
* Cluster API: Important Change: Because NDB_LE_MemoryUsage.page_size_kb shows memory page sizes in bytes rather than kilobytes, it has been renamed to page_size_bytes. The name page_size_kb is now deprecated and thus subject to removal in a future release, although it currently remains supported for reasons of backward compatibility. See The Ndb_logevent_type Type, for more information about NDB_LE_MemoryUsage. (Bug#30271)
* Important Change: Some changes were made to CHECK TABLE ... FOR UPGRADE and REPAIR TABLE with respect to detection and handling of tables with incompatible .frm files (files created with a different version of the MySQL server). These changes also affect mysqlcheck because that program uses CHECK TABLE and REPAIR table, and thus also mysql_upgrade because that program invokes mysqlcheck.
o If your table was created by a different version of the MySQL server than the one you are currently running, CHECK TABLE ... FOR UPGRADE indicates that the table has an .frm file with an incompatible version. In this case, the result set returned by CHECK TABLE contains a line with a Msg_type value of error and a Msg_text value of Table upgrade required. Please do "REPAIR TABLE `tbl_name`" to fix it!
o REPAIR TABLE without USE_FRM upgrades the .frm file to the current version.
o If you use REPAIR TABLE ...USE_FRM and your table was created by a different version of the MySQL server than the one you are currently running, REPAIR TABLE will not attempt to repair the table. In this case, the result set returned by REPAIR TABLE contains a line with a Msg_type value of error and a Msg_text value of Failed repairing incompatible .FRM file.

Previously, use of REPAIR TABLE ...USE_FRM with a table created by a different version of the MySQL server risked the loss of all rows in the table.

更新時間：2008-05-12
更新細節：

What's new in this version:

Bugs fixed:

* On Windows, the installer attempted to use JScript to determine whether the target data directory already existed. On Windows Vista x64, this resulted in an error because the installer was attempting to run the JScript in a 32-bit engine, which wasn't registered on Vista. The installer no longer uses JScript but instead relies on a native WiX command. (Bug#36103)
* The MySQL preferences pane did not work to start or stop MySQL on Mac OS X 10.5 (Leopard). (Bug#28854)
* On Mac OS X, the StartupItem for MySQL did not work. (Bug#25008)

更新時間：2008-02-01
更新細節：

What's new in this version:

Bugs fixed:

* Security Fix: Three vulnerabilities in yaSSL versions 1.7.5 and earlier were discovered that could lead to a server crash or execution of unauthorized code. The exploit requires a server with yaSSL enabled and TCP/IP connections enabled, but does not require valid MySQL account credentials. The exploit does not apply to OpenSSL.
Note The proof-of-concept exploit is freely available on the Internet. Everyone with a vulnerable MySQL configuration is advised to upgrade immediately.

(Bug#33814, CVE-2008-0226, CVE-2008-0227)
* Security Fix: ALTER VIEW retained the original DEFINER value, even when altered by another user, which could allow that user to gain the access rights of the view. Now ALTER VIEW is allowed only to the original definer or users with the SUPER privilege. (Bug#29908)
*Security Fix: When using a FEDERATED table, the local server could be forced to crash if the remote server returned a result with fewer columns than expected. (Bug#29801)

更新時間：2007-10-31
更新細節：

What's new in this version:

Functionality added or changed:

*MySQL Cluster: The server source tree now includes scripts to simplify building MySQL with SCI support. For more information about SCI interconnects and these build scripts, see Section 16.9.1, Configuring MySQL Cluster to use SCI Sockets. (Bug#25470)
*Binaries for the Linux x86 statically linked tar.gz Community package were linked dynamically, not statically. Static linking has been re-enabled. (Bug#29617)
*Prior to this release, when DATE values were compared with DATETIME values the time portion of the DATETIME value was ignored. Now a DATE value is coerced to the DATETIME type by adding the time portion as 00:00:00. To mimic the old behavior use the CAST() function in the following way: SELECT date_field = CAST(NOW() as DATE);. (Bug#28929)
*A new status variable, Com_call_procedure, indicates the number of calls to stored procedures. (Bug#27994)

Bugs fixed:

*Security Fix: A malformed password packet in the connection protocol could cause the server to crash. Thanks for Dormando for reporting this bug and providing details and a proof of concept. (Bug#28984)
*Security Fix: Use of a view could allow a user to gain update privileges for tables in other databases. (Bug#27878, CVE-2007-3782)
*Security Fix: The requirement of the DROP privilege for RENAME TABLE was not being enforced. (Bug#27515, CVE-2007-2691)
*Security Fix: If a stored routine was declared using SQL SECURITY INVOKER, a user who invoked the routine could gain privileges. (Bug#27337, CVE-2007-2692)
*Security Fix: CREATE TABLE LIKE did not require any privileges on the source table. Now it requires the SELECT privilege.

In addition, CREATE TABLE LIKE was not isolated from alteration by other connections, which resulted in various errors and incorrect binary log order when trying to execute concurrently a CREATE TABLE LIKE statement and either DDL statements on the source table or DML or DDL statements on the target table. (Bug#23667, Bug#25578, CVE-2007-3781)
*Incompatible Change: When mysqldump was run with the --delete-master-logs option, binary log files were deleted before it was known that the dump had succeeded, not after. (The method for removing log files used RESET MASTER prior to the dump. This also reset the binary log sequence numbering to .000001.) Now mysqldump flushes the logs (which creates a new binary log number with the next sequence number), performs the dump, and then uses PURGE MASTER LOGS to remove the log files older than the new one. This also preserves log numbering because the new log with the next number is generated and only the preceding logs are removed. However, this may affect applications if they rely on the log numbering sequence being reset. (Bug#24733)
*Incompatible Change: The use of an ORDER BY or DISTINCT clause with a query containing a call to the GROUP_CONCAT() function caused results from previous queries to be redisplayed in the current result. The fix for this includes replacing a BLOB value used internally for sorting with a VARCHAR. This means that for long results (more than 65,535 bytes), it is possible for truncation to occur; if so, an appropriate warning is issued. (Bug#23856, Bug#28273)
*MySQL Cluster: : A corrupt schema file could cause a File already open error. (Bug#28770)
*MySQL Cluster: A race condition could result when non-master nodes (in addition to the master node) tried to update active status due to a local checkpoint. Now only the master updates the active status. (Bug#28717)
*MySQL Cluster: A fast global checkpoint under high load with a high usage of the redo buffer caused data nodes to fail. (Bug#28653)
*MySQL Cluster: When an API node sent more than 1024 signals in a single batch, NDB would process only the first 1024 of these, and then hang. (Bug#28443)
*MySQL Cluster: A delay in obtaining AUTO_INCREMENT IDs could lead to excess temporary errors. (Bug#28410)
*MySQL Cluster: INSERT IGNORE wrongly ignored NULL values in unique indexes. (Bug#27980)
*MySQL Cluster: The name of the month March was given incorrectly in the cluster error log. (Bug#27926)
*MySQL Cluster: It was not possible to add a unique index to an NDB table while in single user mode. (Bug#27710)
*MySQL Cluster: Repeated insertion of data generated by mysqldump into NDB tables could eventually lead to failure of the cluster. (Bug#27437)
*MySQL Cluster: (APIs): For BLOB reads on operations with lock mode LM_CommittedRead, the lock mode was not upgraded to LM_Read before the state of the BLOB had already been calculated. The NDB API methods affected by this problem included the following:
o

NdbOperation::readTuple()
o

NdbScanOperation::readTuples()
o

NdbIndexScanOperation::readTuples()

(Bug#27320)
*MySQL Cluster: ndb_connectstring did not appear in the output of SHOW VARIABLES. (Bug#26675)
*MySQL Cluster: A failure to release internal resources following an error could lead to problems with single user mode. (Bug#25818)
*On the IBM i5 platform, the installation script in *SAVF binaries unconditionally executed the mysql_install_db script. This problem was fixed in a repackaged distribution numbered 5.0.45b. (Bug#30084)
*Long pathnames for internal temporary tables could cause stack overflows. (Bug#29015)
*Using an INTEGER column from a table to ROUND() a number produced different results than using a constant with the same value as the INTEGER column. (Bug#28980)
*If a program binds a given number of parameters to a prepared statement handle and then somehow changes stmt->param_count to a different number, mysql_stmt_execute() could crash the client or server. (Bug#28934)
*INSERT .. ON DUPLICATE KEY UPDATE could under some circumstances silently update rows when it should not have. (Bug#28904)
*Queries that used UUID() were incorrectly allowed into the query cache. (This should not happen because UUID() is non-deterministic.) (Bug#28897)
*Using a VIEW created with a non-existing DEFINER could lead to incorrect results under some circumstances. (Bug#28895)
*On Windows, USE_TLS was not defined for mysqlclient.lib. (Bug#28860)
*A subquery with ORDER BY and LIMIT 1 could cause a server crash. (Bug#28811)
*Using BETWEEN with non-indexed date columns and short formats of the date string could return incorrect results. (Bug#28778)
*Selecting GEOMETRY columns in a UNION caused a server crash. (Bug#28763)
*When constructing the path to the original .frm file, ALTER .. RENAME was unnecessarily (and incorrectly) lowercasing the entire path when not on a case-insensitive filesystem, causing the statement to fail. (Bug#28754)
*The actual value of MaxNoOfOpenFiles as used by the cluster was offset by 1 from the value set in config.ini. This meant that setting InitialNoOpenFilesto the same value always caused an error. (Bug#28749)
*Searches on indexed and non-indexed ENUM columns could return different results for empty strings. (Bug#28729)
*Executing EXPLAIN EXTENDED on a query using a derived table over a grouping subselect could lead to a server crash. This occurred only when materialization of the derived tables required creation of an auxiliary temporary table, an example being when a grouping operation was carried out with usage of a temporary table. (Bug#28728)
*UPDATE IGNORE statements involving the primary keys of multiple tables could result in data corruption. (Bug#28719)
*The result of evaluation for a view's CHECK OPTION option over an updated record and records of merged tables was arbitrary and dependant on the order of records in the merged tables during the execution of the SELECT statement. (Bug#28716)
*The manager thread of the LinuxThreads implementation was unintentionally started before mysqld had dropped privileges (to run as an unprivileged user). This caused signaling between threads in mysqld to fail when the privileges were finally dropped. (Bug#28690)
*For debug builds, ALTER TABLE could trigger an assertion failure due to occurrence of a deadlock when committing changes. (Bug#28652)
*After an upgrade, the names of stored routines referenced by views were no longer displayed by SHOW CREATE VIEW. (Bug#28605)

This regression was introduced by Bug#23491
*Killing from one connection a long-running EXPLAIN QUERY started from another connection caused mysqld to crash. (Bug#28598)
*Outer join queries with ON conditions over constant outer tables did not return NULL-complemented rows when conditions were evaluated to FALSE. (Bug#28571)
*An update on a multiple-table view with the CHECK OPTION clause and a subquery in the WHERE condition could cause an assertion failure. (Bug#28561)
*PURGE MASTER LOGS BEFORE (subquery) caused a server crash. Subqueries are forbidden in the BEFORE clause now. (Bug#28553)
*mysqldump calculated the required memory for a hex-blob string incorrectly causing a buffer overrun. This in turn caused mysqldump to crash silently and produce incomplete output. (Bug#28522)
*Passing a DECIMAL value as a parameter of a statement prepared with PREPARE resulted in an error. (Bug#28509)
*mysql_affected_rows() could return an incorrect result for INSERT ... ON DUPLICATE KEY UPDATE if the CLIENT_FOUND_ROWS flag was set. (Bug#28505)
*A query that grouped by the result of an expression returned a different result when the expression was assigned to a user variable. (Bug#28494)
*Subselects returning LONG values in MySQL versions later than 5.0.24a returned LONGLONG prior to this. The previous behavior was restored. (Bug#28492)

This regression was introduced by Bug#19714
*Forcing the use of an index on a SELECT query when the index had been disabled would raise an error without running the query. The query now executes, with a warning generated noting that the use of a disabled index has been ignored. (Bug#28476)
*The result of executing of a prepared statement created with PREPARE s FROM "SELECT 1 LIMIT ?" was not replicated correctly. (Bug#28464)
*The query SELECT '2007-01-01' + INTERVAL column_name DAY FROM table_name caused mysqld to fail. (Bug#28450)
*A server crash could happen under rare conditions such that a temporary table outgrew heap memory reserved for it and the remaining disk space was not big enough to store the table as a MyISAM table. (Bug#28449)
*mysql_upgrade failed if certain SQL modes were set. Now it sets the mode itself to avoid this problem. (Bug#28401)
*A query with a NOT IN subquery predicate could cause a crash when the left operand of the predicate evaluated to NULL. (Bug#28375)
*The test case for mysqldump failed with bin-log disabled. (Bug#28372)
*Attempting to LOAD_FILE from an empty floppy drive under Windows, caused the server to hang. For example, if you opened a connection to the server and then issued the command SELECT LOAD_FILE('a:test');, with no floppy in the drive, the server was inaccessible until the modal pop-up dialog box was dismissed. (Bug#28366)
*A buffer overflow could occur when using DECIMAL columns on Windows operating systems. (Bug#28361)
*libmysql.dll could not be dynamically loaded on Windows. (Bug#28358)
*Grouping queries with correlated subqueries in WHERE conditions could produce incorrect results. (Bug#28337)
*mysqltest used a too-large stack size on PPC/Debian Linux, causing thread-creation failure for tests that use many threads. (Bug#28333)
*EXPLAIN for a query on an empty table immediately after its creation could result in a server crash. (Bug#28272)
*The IS_UPDATABLE column in the INFORMATION_SCHEMA.VIEWS table was not always set correctly. (Bug#28266)
*Comparing a DATETIME column value with a user variable yielded incorrect results. (Bug#28261)
*For CAST() of a NULL value with type DECIMAL, the return value was incorrectly initialized, producing a runtime error for binaries built using Visual C++ 2005. (Bug#28250)
*Recreating a view that already exists on the master would cause a replicating slave to terminate replication with a 'different error message on slave and master' error. (Bug#28244)
*Portability problems caused by use of isinf() were corrected. (Bug#28240)
*When dumping procedures, mysqldump --compact generated output that restored the session variable SQL_MODE without first capturing it. When dumping routines, mysqldump --compact neither set nor retrieved the value of SQL_MODE. (Bug#28223)
*Comparison of the string value of a date showed as unequal to CURTIME(). Similar behavior was exhibited for DATETIME values. (Bug#28208)
*For InnoDB, in some rare cases the optimizer preferred a more expensive ref access to a less expensive range access. (Bug#28189)
*A performance degradation was observed for outer join queries to which a not-exists optimization was applied. (Bug#28188)
*SELECT * INTO OUTFILE ... FROM INFORMATION_SCHEMA.schemata failed with an Access denied error, even for a user who has the FILE privilege. (Bug#28181)
*The Bytes_received and Bytes_sent status variables could hold only 32-bit values (not 64-bit values) on some platforms. (Bug#28149)
*Comparisons of DATE or DATETIME values for the IN() function could yield incorrect results. (Bug#28133)
*Storing a large number into a FLOAT or DOUBLE column with a fixed length could result in incorrect truncation of the number if the column's length was greater than 31. (Bug#28121)
*The cluster waited 30 seconds instead of 30 milliseconds before reading table statistics. (Bug#28093)
*The server could hang for INSERT IGNORE ... ON DUPLICATE KEY UPDATE if an update failed. (Bug#28000)
*The BLACKHOLE storage engine does not support INSERT DELAYED statements, but they were not being rejected. (Bug#27998)
*DECIMAL values beginning with nine 9 digits could be incorrectly rounded. (Bug#27984)
*CAST() to DECIMAL did not check for overflow. (Bug#27957)
*For INSERT ... ON DUPLICATE KEY UPDATE statements that affected many rows, updates could be applied to the wrong rows. (Bug#27954)
*Early NULL-filtering optimization did not work for eq_ref table access. (Bug#27939)
*The second execution of a prepared statement from a UNION query with ORDER BY RAND() caused the server to crash. This problem could also occur when invoking a stored procedure containing such a query. (Bug#27937)
*Views ignored precision for CAST() operations. (Bug#27921)
*For attempts to open a non-existent table, the server should report ER_NO_SUCH_TABLE but sometimes reported ER_TABLE_NOT_LOCKED. (Bug#27907)
*A stored program that uses a variable name containing multibyte characters could fail to execute. (Bug#27876)
*Non-grouped columns were allowed by * in ONLY_FULL_GROUP_BY SQL mode. (Bug#27874)
*ON conditions from JOIN expressions were ignored when checking the CHECK OPTION clause while updating a multiple-table view that included such a clause. (Bug#27827)
*Debug builds on Windows generated false alarms about uninitialized variables with some Visual Studio runtime libraries. (Bug#27811)
*Certain queries that used uncorrelated scalar subqueries caused EXPLAIN to to crash. (Bug#27807)
*Changes to some system variables should invalidate statements in the query cache, but invalidation did not happen. (Bug#27792)
*Performing a UNION on two views that had had ORDER BY clauses resulted in an Unknown column error. (Bug#27786)
*mysql_install_db is supposed to detect existing system tables and create only those that do not exist. Instead, it was exiting with an error if tables already existed. (Bug#27783)
*On some systems, udf_example.c returned an incorrect result length. Also on some systems, mysql-test-run.pl could not find the shared object built from udf_example.c. (Bug#27741)
*mysqld did not check the length of option values and could crash with a buffer overflow for long values. (Bug#27715)
*Comparisons using row constructors could fail for rows containing NULL values. (Bug#27704)
*LOAD DATA did not use CURRENT_TIMESTAMP as the default value for a TIMESTAMP column for which no value was provided. (Bug#27670)
*mysqldump could not connect using SSL. (Bug#27669)
*On Linux, the server could not create temporary tables if lower_case_table_names was set to 1 and the value of tmpdir was a directory name containing any uppercase letters. (Bug#27653)
*For InnoDB tables, a multiple-row INSERT of the form INSERT INTO t (id...) VALUES (NULL...) ON DUPLICATE KEY UPDATE id=VALUES(id), where id is an AUTO_INCREMENT column, could cause ERROR 1062 (23000): Duplicate entry... errors or lost rows. (Bug#27650)
*HASH indexes on VARCHAR columns with binary collations did not ignore trailing spaces from strings before comparisons. This could result in duplicate records being successfully inserted into a MEMORY table with unique key constraints. A consequence was that internal MEMORY tables used for GROUP BY calculation contained duplicate rows that resulted in duplicate-key errors when converting those temporary tables to MyISAM, and that error was incorrectly reported as a table is full error. (Bug#27643)
*The XML output representing an empty result was an empty string rather than an empty element. (Bug#27608)
*An error occurred trying to connect to mysqld-debug.exe. (Bug#27597)
*Comparison of a DATE with a DATETIME did not treat the DATE as having a time part of 00:00:00. (Bug#27590)
*Selecting MIN() on an indexed column that contained only NULL values caused NULL to be returned for other result columns. (Bug#27573)
*If a stored function or trigger was killed, it aborted but no error was thrown, allowing the calling statement to continue without noticing the problem. This could lead to incorrect results. (Bug#27563)
*The fix for Bug#17212 provided correct sort order for misordered output of certain queries, but caused significant overall query performance degradation. (Results were correct (good), but returned much more slowly (bad).) The fix also affected performance of queries for which results were correct. The performance degradation has been addressed. (Bug#27531)
*The CRC32() function returns an unsigned integer, but the metadata was signed, which could cause certain queries to return incorrect results. (For example, queries that selected a CRC32() value and used that value in the GROUP BY clause.) (Bug#27530)
*An interaction between SHOW TABLE STATUS and other concurrent statements that modify the table could result in a divide-by-zero error and a server crash. (Bug#27516)
*When ALTER TABLE was used to add a new DATE column with no explicit default value, '0000-00-00' was used as the default even if the SQL mode included the NO_ZERO_DATE mode to prohibit that value. A similar problem occurred for DATETIME columns. (Bug#27507)
*A race condition between DROP TABLE and SHOW TABLE STATUS could cause the latter to display incorrect information. (Bug#27499)
*Using a TEXT local variable in a stored routine in an expression such as SET var = SUBSTRING(var, 3) produced an incorrect result. (Bug#27415)
*Nested aggregate functions could be improperly evaluated. (Bug#27363)
*A stored function invocation in the WHERE clause was treated as a constant. (Bug#27354)
*Failure to allocate memory associated with transaction_prealloc_size could cause a server crash. (Bug#27322)
*mysqldump crashed if it got no data from SHOW CREATE PROCEDURE (for example, when trying to dump a routine defined by a different user and for which the current user had no privileges). Now it prints a comment to indicate the problem. It also returns an error, or continues if the --force option is given. (Bug#27293)
*The error message for error number 137 did not report which database/table combination reported the problem. (Bug#27173)
*mysqlbinlog produced different output with the -R option than without it. (Bug#27171)
*A large filesort could result in a division by zero error and a server crash. (Bug#27119)
*Times displayed by SHOW PROFILE were incorrectly associated with the profile entry one later than the corrrect one. (Bug#27060)
*Flow control optimization in stored routines could cause exception handlers to never return or execute incorrect logic. (Bug#26977)
*SHOW PROFILE hung if executed before enabling the @@profiling session variable. (Bug#26938)
*Binary logging of prepared statements could produce syntactically incorrect queries in the binary log, replacing some parameters with variable names rather than variable values. This could lead to incorrect results on replication slaves. (Bug#26842, Bug#12826)
*mysqldump would not dump a view for which the DEFINER no longer exists. (Bug#26817)
*Connections from one mysqld server to another failed on Mac OS X, affecting replication and FEDERATED tables. (Bug#26664)
*Creating a temporary table with InnoDB when using the one-file-per-table setting, when the host filesystem for temporary tables is tmpfs would cause an assertion within mysqld. This was due to the use of O_DIRECT when opening the temporary table file. (Bug#26662)
*mysql_upgrade did not detect failure of external commands that it runs. (Bug#26639)
*Some test suite files were missing from some MySQL-test packages. (Bug#26609)
*Aborting a statement on the master that applied to a non-transactional statement broke replication. The statement was written to the binary log but not completely executed on the master. Slaves receiving the statement executed it completely, resulting in loss of data synchrony. Now an error code is written to the error log so that the slaves stop without executing the aborted statement. (That is, replication stops, but synchrony to the point of the stop is preserved and you can investigate the problem.) (Bug#26551)
*Statements within triggers ignored the value of the low_priority_updates system variable. (Bug#26162)
*Index hints (USE INDEX, IGNORE INDEX, FORCE INDEX) cannot be used with FULLTEXT indexes, but were not being ignored. (Bug#25951)
*If CREATE TABLE t1 LIKE t2 failed due to a full disk, an empty t2.frm file could be created but not removed. This file then caused subsequent attempts to create a table named t2 to fail. This is easily corrected at the filesystem level by removing the t2.frm file manually, but now the server removes the file if the create operation does not complete successfully. (Bug#25761)
*Running CHECK TABLE concurrently with a SELECT, INSERT or other statement on Windows could corrupt a MyISAM table. (Bug#25712)
*On Windows, connection handlers did not properly decrement the server's thread count when exiting. (Bug#25621)
*mysql_upgrade did not pass a password to mysqlcheck if one was given. (Bug#25452)
*On Windows, mysql_upgrade was sensitive to lettercase of the names of some required components. (Bug#25405)
*For storage engines that allow the current auto-increment value to be set, using ALTER TABLE ... ENGINE to convert a table from one such storage engine to another caused loss of the current value. (For storage engines that do not support setting the value, it cannot be retained anyway when changing the storage engine.) (Bug#25262)
*Restoration of the default database after stored routine or trigger execution on a slave could cause replication to stop if the database no longer existed. (Bug#25082)
*Due to a race condition, executing FLUSH PRIVILEGES in one thread could cause brief table unavailability in other threads. (Bug#24988)
*Several math functions produced incorrect results for large unsigned values. ROUND() produced incorrect results or a crash for a large number-of-decimals argument. (Bug#24912)
*The result set of a query that used WITH ROLLUP and DISTINCT could lack some rollup rows (rows with NULL values for grouping attributes) if the GROUP BY list contained constant expressions. (Bug#24856)
*Potential memory leaks in the SHOW PROFILE implementation were eliminated. (Bug#24795)
*For queries that used ORDER BY with InnoDB tables, if the optimizer chose an index for accessing the table but found a covering index that enabled the ORDER BY to be skipped, no results were returned. (Bug#24778)
*Concurrent execution of CREATE TABLE ... SELECT and other statements involving the target table suffered from various race conditions, some of which might have led to deadlocks. (Bug#24738)
*On some Linux distributions where LinuxThreads and NPTL glibc versions both are available, statically built binaries can crash because the linker defaults to LinuxThreads when linking statically, but calls to external libraries (such as libnss) are resolved to NPTL versions. This cannot be worked around in the code, so instead if a crash occurs on such a binary/OS combination, print an error message that provides advice about how to fix the problem. (Bug#24611)
*An attempt to execute CREATE TABLE ... SELECT when a temporary table with the same name already existed led to the insertion of data into the temporary table and creation of an empty non-temporary table. (Bug#24508)
*The MERGE storage engine could return incorrect results when several index values that compare equality were present in an index (for example, 'gross' and 'gross ', which are considered equal but have different lengths). (Bug#24342)
*Some upgrade problems are detected and better error messages suggesting that mysql_upgrade be run are produced. (Bug#24248)
*Some views could not be created even when the user had the requisite privileges. (Bug#24040)
*Using CAST() to convert DATETIME values to numeric values did not work. (Bug#23656)
*The AUTO_INCREMENT value would not be correctly reported for InnoDB tables when using SHOW CREATE TABLE statement or mysqldump command. (Bug#23313)
*Implicit conversion of 9912101 to DATE did not match CAST(9912101 AS DATE). (Bug#23093)
*Conversion errors could occur when constructing the condition for an IN predicate. The predicate was treated as if the affected column contains NULL, but if the IN predicate is inside NOT, incorrect results could be returned. (Bug#22855)
*SELECT COUNT(*) from a table containing a DATETIME NOT NULL column could produce spurious warnings with the NO_ZERO_DATE SQL mode enabled. (Bug#22824)
*When using transactions and replication, shutting down the master in the middle of a transaction would cause all slaves to stop replicating. (Bug#22725)
*Using SET GLOBAL to change the lc_time_names system variable had no effect on new connections. (Bug#22648)
*A multiple-table UPDATE could return an incorrect rows-matched value if, during insertion of rows into a temporary table, the table had to be converted from a MEMORY table to a MyISAM table. (Bug#22364)
*yaSSL crashed on pre-Pentium Intel CPUs. (Bug#21765)
*Linux binaries were unable to dump core after executing a setuid() call. (Bug#21723)
*A slave that used --master-ssl-cipher could not connect to the master. (Bug#21611)
*Quoted labels in stored routines were mishandled, rendering the routines unusable. (Bug#21513)
*The server could abort or deadlock for INSERT DELAYED statements for which another insert was performed implicitly (for example, via a stored function that inserted a row). (Bug#21483)
*Stack overflow caused server crashes. (Bug#21476)
*CURDATE() is less than NOW(), either when comparing CURDATE() directly (CURDATE() < NOW() is true) or when casting CURDATE() to DATE (CAST(CURDATE() AS DATE) < NOW() is true). However, storing CURDATE() in a DATE column and comparing col_name < NOW() incorrectly yielded false. This is fixed by comparing a DATE column as DATETIME for comparisons to a DATETIME constant. (Bug#21103)
*CREATE TABLE IF NOT EXISTS ... SELECT caused a server crash if the target table already existed and had a BEFORE INSERT trigger. (Bug#20903)
*Deadlock occurred for attempts to execute CREATE TABLE IF NOT EXISTS ... SELECT when LOCK TABLES had been used to acquire a read lock on the target table. (Bug#20662, Bug#15522)
*Changing a utf8 column in an InnoDB table to a shorter length did not shorten the data values. (Bug#20095)
*For dates with 4-digit year parts less than 200, an incorrect implicit conversion to add a century was applied for date arithmetic performed with DATE_ADD(), DATE_SUB(), + INTERVAL, and - INTERVAL. (For example, DATE_ADD('0050-01-01 00:00:00', INTERVAL 0 SECOND) became '2050-01-01 00:00:00'.) (Bug#18997)
*Using CREATE TABLE LIKE ... would raise an assertion when replicated to a slave. (Bug#18950)
*Granting access privileges to an individual table where the database or table name contained an underscore would fail. (Bug#18660)
*The -lmtmalloc library was removed from the output of mysql_config on Solaris, as it caused problems when building DBD::mysql (and possibly other applications) on that platform that tried to use dlopen() to access the client library. (Bug#18322)
*The check-cpu script failed to detect AMD64 Turion processors correctly. (Bug#17707)
*Trying to shut down the server following a failed LOAD DATA INFILE caused mysqld to crash. (Bug#17233)
*The omission of leading zeros in dates could lead to erroneous results when these were compared with the output of certain date and time functions. (Bug#16377)
*INSERT...ON DUPLICATE KEY UPDATE could cause Error 1032: Can't find record in ... for inserts into an InnoDB table unique index using key column prefixes with an underlying utf8 string column. (Bug#13191)
*Having the EXECUTE privilege for a routine in a database should make it possible to USE that database, but the server returned an error instead. This has been corrected. As a result of the change, SHOW TABLES for a database in which you have only the EXECUTE privilege returns an empty set rather than an error. (Bug#9504)

更新時間：2007-05-15
更新細節：

What's new in this version:

Functionality added or changed:
- If you use SSL for a client connection, you can tell the client not to authenticate the server certificate by specifying neither --ssl-ca nor --ssl-capath. The server still verifies the client according to any applicable requirements established via GRANT statements for the client, and it still uses any --ssl-ca/--ssl-capath values that were passed to server at startup time. (Bug#25309)
- Prefix lengths for columns in SPATIAL indexes are no longer displayed in SHOW CREATE TABLE output. mysqldump uses that statement, so if a table with SPATIAL indexes containing prefixed columns is dumped and reloaded, the index is created with no prefixes. (The full column width of each column is indexed.) (Bug#26794)
- The output of mysql --xml and mysqldump --xml now includes a valid XML namespace. (Bug#25946)
- The mysql_create_system_tables script was removed because mysql_install_db no longer uses it in MySQL 5.0.
- The syntax for index hints has been extended to enable explicit specification that the hint applies only to join processing. See Section 13.2.7.2, Index Hint Syntax. (Bug#21174)
- Binary distributions for some platforms did not include shared libraries; now shared libraries are shipped for all platforms except AIX 5.2 64-bit. (Bug#13450, Bug#16520, Bug#26767)
- NDB Cluster: It is now possible to restore selected databases or tables using ndb_restore. (Bug#26899)
- NDB Cluster: Several options have been added for use with ndb_restore --print_data to facilitate the creation of data dump files. (Bug#26900)
- If a set function S with an outer reference S(outer_ref) cannot be aggregated in the outer query against which the outer reference has been resolved, MySQL interprets S(outer_ref) the same way that it would interpret S(const). However, standard SQL requires throwing an error in this situation. An error now is thrown for such queries if the ANSI SQL mode is enabled. (Bug#27348)
- To satisfy different user requirements, we provide several servers. mysqld is an optimized server that is a smaller, faster binary. Each package now also includes mysqld-debug, which is compiled with debugging support but is otherwise configured identically to the non-debug server.
- Added the --secure-file-priv option for mysql-test-run.pl, which limits the effect of the load_file command for mysqltest and for the LOAD DATA and SELECT ... INTO OUTFILE statements to work with files in a given directory. (Bug#18628)
- Added the hostname system variable, which the server sets at startup to the server hostname.
- The server now includes a timestamp in error messages that are logged as a result of unhandled signals (such as mysqld got signal 11 messages). (Bug#24878)
Bugs fixed:
- The patches for Bug#19370 and Bug#21789 were reverted.
- NDB Cluster: NDB tables having MEDIUMINT AUTO_INCREMENT columns were not restored correctly by ndb_restore, causing spurious duplicate key errors. This issue did not affect TINYINT, INT, or BIGINT columns with AUTO_INCREMENT. (Bug#27775)
- NDB Cluster: NDB tables with indexes whose names contained space characters were not restored correctly by ndb_restore (the index names were truncated). (Bug#27758)
- NDB Cluster: Some queries that updated multiple tables were not backed up correctly. (Bug#27748)
- NDB Cluster: Joins on multiple tables containing BLOB columns could cause data nodes run out of memory, and to crash with the error NdbObjectIdMap::expand unable to expand. (Bug#26176)
- NDB Cluster (APIs): Using NdbBlob::writeData() to write data in the middle of an existing blob value (that is, updating the value) could overwrite some data past the end of the data to be changed. (Bug#27018)
- NDB Cluster: Under certain rare circumstances, DROP TABLE or TRUNCATE of an NDB table could cause a node failure or forced cluster shutdown. (Bug#27581)
- NDB Cluster: Memory usage of a mysqld process grew even while idle. (Bug#27560)
- NDB Cluster: In some cases, AFTER UPDATE and AFTER DELETE triggers on NDB tables that referenced subject table did not see the results of operation which caused invocation of the trigger, but rather saw the row as it was prior to the update or delete operation.
This was most noticeable when an update operation used a subquery to obtain the rows to be updated. An example would be UPDATE tbl1 SET col2 = val1 WHERE tbl1.col1 IN (SELECT col3 FROM tbl2 WHERE c4 = val2) where there was an AFTER UPDATE trigger on table tbl1. In such cases, the trigger would fail to execute.
The problem occurred because the actual update or delete operations were deferred to be able to perform them later as one batch. The fix for this bug solves the problem by disabling this optimization for a given update or delete if the table has an AFTER trigger defined for this operation. (Bug#26242)
- NDB Cluster: Condition pushdown did not work with prepared statements. (Bug#26225)
- NDB Cluster: When trying to create tables on an SQL node not connected to the cluster, a misleading error message Table 'tbl_name' already exists was generated. The error now generated is Could not connect to storage engine. (Bug#18676)
- NDB Cluster: Error messages displayed when running in single user mode were inconsistent. (Bug#27021)
- NDB Cluster: On Solaris, the value of an NDB table column declared as BIT(33) was always displayed as 0. (Bug#26986)
- NDB Cluster: The output from ndb_restore --print_data was incorrect for a backup made of a database containing tables with TINYINT or SMALLINT columns. (Bug#26740)
- NDB Cluster: After entering single user mode it was not possible to alter non-NDB tables on any SQL nodes other than the one having sole access to the cluster. (Bug#25275)
- NDB Cluster: The failure of a data node while restarting could cause other data nodes to hang or crash. (Bug#27003)
- NDB Cluster: The management client command node_id STATUS displayed the message Node node_id: not connected when node_id was not the node ID of a data node. (Bug#21715)
Note
The ALL STATUS command in the cluster management client still displays status information for data nodes only. This is by design. See Section 15.7.2, Commands in the MySQL Cluster Management Client, for more information.
- NDB Cluster: It was not possible to set LockPagesInMainMemory equal to 0. (Bug#27291)
- NDB Cluster: A race condition could sometimes occur if the node acting as master failed while node IDs were still being allocated during startup. (Bug#27286)
- NDB Cluster: When a data node was taking over as the master node, a race condition could sometimes occur as the node was assuming responsibility for handling of global checkpoints. (Bug#27283)
- NDB Cluster: mysqld processes would sometimes crash under high load. (Bug#26825)
- NDB Cluster: Some values of MaxNoOfTables caused the error Job buffer congestion to occur. (Bug#19378)
- Some equi-joins containing a WHERE clause that included a NOT IN subquery caused a server crash. (Bug#27870)
- Windows binaries contained no debug symbol file. Now .map and .pdb files are included in 32-bit builds for mysqld-nt.exe, mysqld-debug.exe, and mysqlmanager.exe. (Bug#26893)
- The test for the MYSQL_OPT_SSL_VERIFY_SERVER_CERT option for mysql_options() was performed incorrectly. Also changed as a result of this bugfix: The arg option for the mysql_options() C API function was changed from char * to void *. (Bug#24121)
- The range optimizer could consume a combinatorial amount of memory for certain classes of WHERE clauses. (Bug#26624)
- Conversion of DATETIME values in numeric contexts sometimes did not produce a double (YYYYMMDDHHMMSS.uuuuuu) value. (Bug#16546)
- Passing nested row expressions with different structures to an IN predicate caused a server crash. (Bug#27484)
- SELECT DISTINCT could return incorrect results if the select list contained duplicated columns. (Bug#27659)
- A subquery could get incorrect values for references to outer query columns when it contained aggregate functions that were aggregated in outer context. (Bug#27321)
- In some cases, the optimizer preferred a range or full index scan access method over lookup access methods when the latter were much cheaper. (Bug#19372)
- Duplicates were not properly identified among (potentially) long strings used as arguments for GROUP_CONCAT(DISTINCT). (Bug#26815)
- For InnoDB, fixed consistent-read behavior of the first read statement, if the read was served from the query cache, for the READ COMMITTED isolation level. (Bug#21409)
- The decimal.h header file was incorrectly omitted from binary distributions. (Bug#27456)
- Duplicate members in SET definitions were not detected. Now they result in a warning; if strict SQL mode is enabled, an error occurs instead. (Bug#27069)
- For INSERT INTO ... SELECT where index searches used column prefixes, insert errors could occur when key value type conversion was done. (Bug#26207)
- For SHOW ENGINE INNODB STATUS, the LATEST DEADLOCK INFORMATION was not always cleared properly. (Bug#25494)
- mysqldump could crash or exhibit incorrect behavior when some options were given very long values, such as --fields-terminated-by="some very long string". The code has been cleaned up to remove a number of fixed-sized buffers and to be more careful about error conditions in memory allocation. (Bug#26346)
- Setting a column to NOT NULL with an ON DELETE SET NULL clause foreign key crashes the server. (Bug#25927)
- The values displayed for the Innodb_row_lock_time, Innodb_row_lock_time_avg, and Innodb_row_lock_time_max status variables were incorrect. (Bug#23666)
- COUNT(decimal_expr) sometimes generated a spurious truncation warning. (Bug#21976)
- With NO_AUTO_VALUE_ON_ZERO SQL mode enabled, LOAD DATA operations could assign incorrect AUTO_INCREMENT values. (Bug#27586)
- Incorrect results could be returned for some queries that contained a select list expression with IN or BETWEEN together with an ORDER BY or GROUP BY on the same expression using NOT IN or NOT BETWEEN. (Bug#27532)
- Queries containing subqueries with COUNT(*) aggregated in an outer context returned incorrect results. This happened only if the subquery did not contain any references to outer columns. (Bug#27257)
- Use of an aggregate function from an outer context as an argument to GROUP_CONCAT() caused a server crash. (Bug#27229)
- REPAIR TABLE ... USE_FRM with an ARCHIVE table deleted all records from the table. (Bug#26138)
- On Windows, debug builds of mysqld could fail with heap assertions. (Bug#25765)
- On Windows, debug builds of mysqlbinlog could fail with a memory error. (Bug#23736)
- String truncation upon insertion into an integer or year column did not generate a warning (or an error in strict mode). (Bug#26359, Bug#27176)
- In out-of-memory conditions, the server might crash or otherwise not report an error to the Windows event log. (Bug#27490)
- The temporary file-creation code was cleaned up on Windows to improve server stability. (Bug#26233)
- Out-of-memory errors for slave I/O threads were not reported. Now they are written to the error log. (Bug#26844)
- mysqldump crashed for MERGE tables if the --complete-insert (-c) option was given. (Bug#25993)
- In certain situations, MATCH ... AGAINST returned false hits for NULL values produced by LEFT JOIN when no full-text index was available. (Bug#25729)
- OPTIMIZE TABLE might fail on Windows when it attempts to rename a temporary file to the original name if the original file had been opened, resulting in loss of the .MYD file. (Bug#25521)
- GRANT statements were not replicated if the server was started with the --replicate-ignore-table or --replicate-wild-ignore-table option. (Bug#25482)
- A problem in handling of aggregate functions in subqueries caused predicates containing aggregate functions to be ignored during query execution. (Bug#24484)
- Improved out-of-memory detection when sending logs from a master server to slaves, and log a message when allocation fails. (Bug#26837)
- MBROverlaps() returned incorrect values in some cases. (Bug#24563)
- SHOW CREATE VIEW qualified references to stored functions in the view definition with the function's database name, even when the database was the default database. This affected mysqldump (which uses SHOW CREATE VIEW to dump views) because the resulting dump file could not be used to reload the database into a different database. SHOW CREATE VIEW now suppresses the database name for references to functions in the default database. (Bug#23491)
- With innodb_file_per_table enabled, attempting to rename an InnoDB table to a non-existent database caused the server to exit. (Bug#27381)
- mysql_install_db could terminate with an error after failing to determine that a system table already existed. (Bug#27022)
- For InnoDB tables having a clustered index that began with a CHAR or VARCHAR column, deleting a record and then inserting another before the deleted record was purged could result in table corruption. (Bug#26835)
- Selecting the result of AVG() within a UNION could produce incorrect values. (Bug#24791)
- An INTO OUTFILE clause is allowed only for the final SELECT of a UNION, but this restriction was not being enforced correctly. (Bug#23345)
- Duplicate entries were not assessed correctly in a MEMORY table with a BTREE primary key on a utf8 ENUM column. (Bug#24985)
- For MyISAM tables, COUNT(*) could return an incorrect value if the WHERE clause compared an indexed TEXT column to the empty string (''). This happened if the column contained empty strings and also strings starting with control characters such as tab or newline. (Bug#26231)
- For DELETE FROM tbl_name ORDER BY col_name (with no WHERE or LIMIT clause), the server did not check whether col_name was a valid column in the table. (Bug#26186)
- ALTER VIEW requires the CREATE VIEW and DROP privileges for the view. However, if the view was created by another user, the server erroneously required the SUPER privilege. (Bug#26813)
- In a view, a column that was defined using a GEOMETRY function was treated as having the LONGBLOB data type rather than the GEOMETRY type. (Bug#27300)
- With the NO_AUTO_VALUE_ON_ZERO SQL mode enabled, LAST_INSERT_ID() could return 0 after INSERT ... ON DUPLICATE KEY UPDATE. Additionally, the next rows inserted (by the same INSERT, or the following INSERT with or without ON DUPLICATE KEY UPDATE), would insert 0 for the auto-generated value if the value for the AUTO_INCREMENT column was NULL or missing. (Bug#23233)
- For a stored procedure containing a SELECT statement that used a complicated join with an ON expression, the expression could be ignored during re-execution of the procedure, yielding an incorrect result. (Bug#20492)
- When RAND() was called multiple times inside a stored procedure, the server did not write the correct random seed values to the binary log, resulting in incorrect replication. (Bug#25543)
- SOUNDEX() returned an invalid string for international characters in multi-byte character sets. (Bug#22638)
- Row equalities in WHERE clauses could cause memory corruption. (Bug#27154)
- GROUP BY on a ucs2 column caused a server crash when there was at least one empty string in the column. (Bug#27079)
- Evaluation of an IN() predicate containing a decimal-valued argument caused a server crash. (Bug#27362)
- Storing NULL values in spatial fields caused excessive memory allocation and crashes on some systems. (Bug#27164)
- mysql_stmt_fetch() did an invalid memory deallocation when used with the embedded server. (Bug#25492)
- In a MEMORY table, using a BTREE index to scan for updatable rows could lead to an infinite loop. (Bug#26996)
- The range optimizer could cause the server to run out of memory. (Bug#26625)
- The parser accepted illegal code in SQL exception handlers, leading to a crash at runtime when executing the code. (Bug#26503)
- Difficult repair or optimization operations could cause an assertion failure, resulting in a server crash. (Bug#25289)
- Increasing the width of a DECIMAL column could cause column values to be changed. (Bug#24558)
- Replication between master and slave would infinitely retry binary log transmission where the max_allowed_packet on the master was larger than that on the slave if the size of the transfer was between these two values. (Bug#23775)
- Invalid optimization of pushdown conditions for queries where an outer join was guaranteed to read only one row from the outer table led to results with too few rows. (Bug#26963)
- For INSERT ... ON DUPLICATE KEY UPDATE statements on tables containing AUTO_INCREMENT columns, LAST_INSERT_ID() was reset to 0 if no rows were successfully inserted or changed. Not changed includes the case where a row was updated to its current values, but in that case, LAST_INSERT_ID() should not be reset to 0. Now LAST_INSERT_ID() is reset to 0 only if no rows were successfully inserted or touched, whether or not touched rows were changed. (Bug#27033)
This bug was introduced by the fix for Bug#19978.
- For an INSERT statement that should fail due to a column with no default value not being assigned a value, the statement succeeded with no error if the column was assigned a value in an ON DUPLICATE KEY UPDATE clause, even if that clause was not used. (Bug#26261)
- A result set column formed by concatention of string literals was incomplete when the column was produced by a subquery in the FROM clause. (Bug#26738)
- When using the result of SEC_TO_TIME() for time value greater than 24 hours in an ORDER BY clause, either directly or through a column alias, the rows were sorted incorrectly as strings. (Bug#26672)
- If the server was started with --skip-grant-tables, Selecting from INFORMATION_SCHEMA tables causes a server crash. (Bug#26285)
- Incompatible change: INSERT DELAYED statements are not supported for MERGE tables, but the MERGE storage engine was not rejecting such statements, resulting in table corruption. Applications previously using INSERT DELAYED into MERGE table will break when upgrading to versions with this fix. To avoid the problem, remove DELAYED from such statements. (Bug#26464)
- NDB Cluster: An invalid pointer was returned following a FSCLOSECONF signal when accessing the REDO logs during a node restart or system restart. (Bug#26515)
- NDB Cluster: An inadvertent use of unaligned data caused ndb_restore to fail on some 64-bit platforms, including Sparc and Itanium-2. (Bug#26739)
- NDB Cluster: An infinite loop in an internal logging function could cause trace logs to fill up with Unknown Signal type error messages and thus grow to unreasonable sizes. (Bug#26720)
- NDB Cluster: The failure of a data node when restarting it with --initial could lead to failures of subsequent data node restarts. (Bug#26481)
- NDB Cluster: Takeover for local checkpointing due to multiple failures of master nodes was sometimes incorrect handled. (Bug#26457)
- NDB Cluster: The LockPagesInMemory parameter was not read until after distributed communication had already started between cluster nodes. When the value of this parameter was 1, this could sometimes result in data node failure due to missed heartbeats. (Bug#26454)
- NDB Cluster: Under some circumstances, following the restart of a management, all cluster data nodes would connect to it normally, but some of them subsequently failed to log any events to the management node. (Bug#26293)
- NDB Cluster: An error was produced when SHOW TABLE STATUS was used on an NDB table that had no AUTO_INCREMENT column. (Bug#21033)
- SELECT ... INTO OUTFILE with a long FIELDS ENCLOSED BY value could crash the server. (Bug#27231)
- DOUBLE values such as 20070202191048.000000 were being treated as illegal arguments by WEEK(). (Bug#23616)
- AFTER UPDATE triggers were not activated by the update part of INSERT ... ON DUPLICATE KEY UPDATE statements. (Bug#27006, Bug#27210)
This bug was introduced by the fix for Bug#19978.
- For INSERT ... ON DUPLICATE KEY UPDATE statements where some AUTO_INCREMENT values were generated automatically for inserts and some rows were updated, one auto-generated value was lost per updated row, leading to faster exhaustion of the range of the AUTO_INCREMENT column. (Bug#24432)
Because the original problem can affect replication (different values on master and slave), it is recommended that the master and its slaves be upgraded to the current version.
- IN ((subquery)), IN (((subquery))), and so forth, are equivalent to IN (subquery), which is always interpreted as a table subquery (so that it is allowed to return more than one row). MySQL was treating the over-parenthesized subquery as a single-row subquery and rejecting it if it returned more than one row. This bug primarily affected automatically generated code (such as queries generated by Hibernate), because humans rarely write the over-parenthesized forms. (Bug#21904)
- For MERGE tables defined on underlying tables that contained a short VARCHAR column (shorter than four characters), using ALTER TABLE on at least one but not all of the underlying tables caused the table definitions to be considered different from that of the MERGE table, even if the ALTER TABLE did not change the definition. (Bug#26881)
- If a thread previously serviced a connection that was killed, excessive memory and CPU use by the thread occurred if it later serviced a connection that had to wait for a table lock. (Bug#25966)
- CURDATE() is less than NOW(), either when comparing CURDATE() directly (CURDATE() < NOW() is true) or when casting CURDATE() to DATE (CAST(CURDATE() AS DATE) < NOW() is true). However, storing CURDATE() in a DATE column and comparing col_name < NOW() incorrectly yielded false. This is fixed by comparing a DATE column as DATETIME for comparisons to a DATETIME constant. (Bug#21103)
- A view on a join is insertable for INSERT statements that store values into only one table of the join. However, inserts were being rejected if the inserted-into table was used in a self-join because MySQL incorrectly was considering the insert to modify multiple tables of the view. (Bug#25122)
- Expressions involving SUM(), when used in an ORDER BY clause, could lead to out-of-order results. (Bug#25376)
- LOAD DATA INFILE sent an okay to the client before writing the binary log and committing the changes to the table had finished, thus violating ACID requirements. (Bug#26050)
- Views that used a scalar correlated subquery returned incorrect results. (Bug#26560)
- IF(expr, unsigned_expr, unsigned_expr) was evaluated to a signed result, not unsigned. This has been corrected. The fix also affects constructs of the form IS [NOT] {TRUE|FALSE}, which were transformed internally into IF() expressions that evaluated to a signed result. (Bug#24532)
For existing views that were defined using IS [NOT] {TRUE|FALSE} constructs, there is a related implication. The definitions of such views were stored using the IF() expression, not the original construct. This is manifest in that SHOW CREATE VIEW shows the transformed IF() expression, not the original one. Existing views will evaluate correctly after the fix, but if you want SHOW CREATE VIEW to display the original construct, you must drop the view and re-create it using its original definition. New views will retain the construct in their definition.
- BENCHMARK() did not work correctly for expressions that produced a DECIMAL result. (Bug#26093)
- For some values of the position argument, the INSERT() function could insert a NUL byte into the result. (Bug#26281)
- Inserting utf8 data into a TEXT column that used a single-byte character set could result in spurious warnings about truncated data. (Bug#25815)
- EXPLAIN EXTENDED did not show WHERE conditions that were optimized away. (Bug#22331)
- INSERT DELAYED statements inserted incorrect values into BIT columns. (Bug#26238)
- For expr IN(value_list), the result could be incorrect if BIGINT UNSIGNED values were used for expr or in the value list. (Bug#19342)
- When a TIME_FORMAT() expression was used as a column in a GROUP BY clause, the expression result was truncated. (Bug#20293)
- For SUBSTRING() evaluation using a temporary table, when SUBSTRING() was used on a LONGTEXT column, the max_length metadata value of the result was incorrectly calculated and set to 0. Consequently, an empty string was returned instead of the correct result. (Bug#15757)
- Use of a GROUP BY clause that referred to a stored function result together with WITH ROLLUP caused incorrect results. (Bug#25373)
- Use of a subquery containing GROUP BY and WITH ROLLUP caused a server crash. (Bug#26830)
- Use of a subquery containing a UNION with an invalid ORDER BY clause caused a server crash. (Bug#26661)
- In certain cases it could happen that deleting a row corrupted an RTREE index. This affected indexes on spatial columns. (Bug#25673)
- SSL connections failed on Windows. (Bug#26678)
- Added support for --debugger=dbx for mysql-test-run.pl and fixed support for --debugger=devenv, --debugger=DevEnv, and --debugger=/path/to/devenv. (Bug#26792)
- X() IS NULL and Y() IS NULL comparisons failed when X() and Y() returned NULL. (Bug#26038)
- UNHEX() IS NULL comparisons failed when UNHEX() returned NULL. (Bug#26537)
- The REPEAT() function did not allow a column name as the count parameter. (Bug#25197)
- On 64-bit Windows, large timestamp values could be handled incorrectly. (Bug#26536)
- In some error messages, inconsistent format specifiers were used for the translations in different languages. comp_err (the error message compiler) now checks for mismatches. (Bug#26571)
- On Windows, the server exhibited a file-handle leak after reaching the limit on the number of open file descriptors. (Bug#25222)
- A reference to a non-existent column in the ORDER BY clause of an UPDATE ... ORDER BY statement could cause a server crash. (Bug#25126)
- A multiple-row delayed insert with an auto increment column could cause duplicate entries to be created on the slave in a replication environment. (Bug#25507, Bug#26116)
- Duplicating the usage of a user variable in a stored procedure or trigger would not be replicated correctly to the slave. (Bug#25167)
- User defined variables used within stored procedures and triggers are not replicated correctly when operating in statement-based replication mode. (Bug#20141, Bug#14914)
- Loading data using LOAD DATA INFILE may not replicate correctly (due to character set incompatibilities) if the character_set_database variable is set before the data is loaded. (Bug#15126)
- DROP TRIGGER statements would not be filtered on the slave when using the replication-wild-do-table option. (Bug#24478)
- MySQL would not compile when configured using --without-query-cache. (Bug#25075)
- When using certain server SQL modes, the mysql.proc table was not created by mysql_install_db. In addition, the creation of this and other MySQL system tables was not checked for by mysql-test-run.pl. (Bug#23669, Bug#20166)
- VIEW restrictions were applied to SELECT statements after a CREATE VIEW statement failed, as though the CREATE had succeeded. (Bug#25897)
- An INSERT trigger invoking a stored routine that inserted into a table other than the one on which the trigger was defined would fail with a Table '...' doesn't exist referring to the second table when attempting to delete records from the first table. (Bug#21825)
- A stored procedure that made use of cursors failed when the procedure was invoked from a stored function. (Bug#25345)
- When nesting stored procedures within a trigger on a table, a false dependency error was thrown when one of the nested procedures contained a DROP TABLE statement. (Bug#22580)
- When attempting to call a stored procedure creating a table from a trigger on a table tbl in a database db, the trigger failed with ERROR 1146 (42S02): Table 'db.tbl' doesn't exist. However, the actual reason that such a trigger fails is due to the fact that CREATE TABLE causes an implicit COMMIT, and so a trigger cannot invoke a stored routine containing this statement. A trigger which does so now fails with ERROR 1422 (HY000): Explicit or implicit commit is not allowed in stored function or trigger, which makes clear the reason for the trigger's failure. (Bug#18914)
- Local variables in stored routines or triggers, when declared as the BIT type, were interpreted as strings. (Bug#12976)
- When a stored routine attempted to execute a statement accessing a nonexistent table, the error was not caught by the routine's exception handler. (Bug#8407, Bug#20713)
- NOW() returned the wrong value in statements executed at server startup with the --init-file option. (Bug#23240)
- Instance Manager did not remove the angel PID file on a clean shutdown. (Bug#22511)
- The server could crash if two or more threads initiated query cache resize operation at moments very close in time. (Bug#23527)
- The conditions checked by the optimizer to allow use of indexes in IN predicate calculations were unnecessarily tight and were relaxed. (Bug#20420)
- Several deficiencies in resolution of column names for INSERT ... SELECT statements were corrected. (Bug#25831)
- Indexes on TEXT columns were ignored when ref accesses were evaluated. (Bug#25971)
- The update columns for INSERT ... SELECT ... ON DUPLICATE KEY UPDATE could be assigned incorrect values if a temporary table was used to evaluate the SELECT. (Bug#16630)
- CONNECTION is no longer treated as a reserved word. (Bug#12204)
- A user-defined variable could be assigned an incorrect value if a temporary table was employed in obtaining the result of the query used to determine its value. (Bug#24010)
- Queries that used a temporary table for the outer query when evaluating a correlated subquery could return incorrect results. (Bug#23800)
- For index reads, the BLACKHOLE engine did not return end-of-file (which it must because BLACKHOLE tables contain no rows), causing some queries to crash. (Bug#19717)