Appendix C. MySQL Change History

Table of Contents

C.1. Changes in Release 6.0.x (Development)
C.1.1. Changes in MySQL 6.0.12 (Not yet released)
C.1.2. Changes in MySQL 6.0.11 (11 May 2009)
C.1.3. Changes in MySQL 6.0.10 (03 March 2009)
C.1.4. Changes in MySQL 6.0.9 (10 January 2009)
C.1.5. Changes in MySQL 6.0.8 (03 November 2008)
C.1.6. Changes in MySQL 6.0.7 (29 September 2008)
C.1.7. Changes in MySQL 6.0.6 (11 August 2008)
C.1.8. Changes in MySQL 6.0.5 (12 June 2008)
C.1.9. Changes in MySQL 6.0.4 (12 February 2008)
C.1.10. Changes in MySQL 6.0.3 (16 November 2007)
C.1.11. Changes in MySQL 6.0.2 (04 September 2007)
C.1.12. Changes in MySQL 6.0.1 (Not released)
C.1.13. Changes in MySQL 6.0.0 (30 April 2007 Alpha)
C.2. Changes in Release 5.2.x (Development)
C.2.1. Changes in MySQL 5.2.5 (08 August 2007)
C.2.2. Changes in MySQL 5.2.4 (Not released)
C.2.3. Changes in MySQL 5.2.3 (15 February 2007)
C.2.4. Changes in MySQL 5.2.2 (Not released)
C.2.5. Changes in MySQL 5.2.1 (Not released Alpha)
C.3. MySQL Enterprise Monitor Change History
C.3.1. Changes in MySQL Enterprise Monitor 2.0.6 (Not yet released)
C.3.2. Changes in MySQL Enterprise Monitor 2.0.5 (18th March 2009)
C.3.3. Changes in MySQL Enterprise Monitor 2.0.4 (5th February 2009)
C.3.4. Changes in MySQL Enterprise Monitor 2.0.3 (23rd January 2009)
C.3.5. Changes in MySQL Enterprise Monitor 2.0.2 (14th January 2009)
C.3.6. Changes in MySQL Enterprise Monitor 2.0.1 (15th December 2008)
C.3.7. Changes in MySQL Enterprise Monitor 2.0.0 (11th December 2008)
C.4. MySQL Connector/ODBC (MyODBC) Change History
C.4.1. Changes in MySQL Connector/ODBC 5.1.6 (Not yet released)
C.4.2. Changes in MySQL Connector/ODBC 5.1.5 (18 August 2008)
C.4.3. Changes in MySQL Connector/ODBC 5.1.4 (15 April 2008)
C.4.4. Changes in MySQL Connector/ODBC 5.1.3 (26 March 2008)
C.4.5. Changes in MySQL Connector/ODBC 5.1.2 (13 February 2008)
C.4.6. Changes in MySQL Connector/ODBC 5.1.1 (13 December 2007)
C.4.7. Changes in MySQL Connector/ODBC 5.1.0 (10 September 2007)
C.4.8. Changes in MySQL Connector/ODBC 5.0.12 (Never released)
C.4.9. Changes in MySQL Connector/ODBC 5.0.11 (31 January 2007)
C.4.10. Changes in MySQL Connector/ODBC 5.0.10 (14 December 2006)
C.4.11. Changes in MySQL Connector/ODBC 5.0.9 (22 November 2006)
C.4.12. Changes in MySQL Connector/ODBC 5.0.8 (17 November 2006)
C.4.13. Changes in MySQL Connector/ODBC 5.0.7 (08 November 2006)
C.4.14. Changes in MySQL Connector/ODBC 5.0.6 (03 November 2006)
C.4.15. Changes in MySQL Connector/ODBC 5.0.5 (17 October 2006)
C.4.16. Changes in Connector/ODBC 5.0.3 (Connector/ODBC 5.0 Alpha 3) (20 June 2006)
C.4.17. Changes in Connector/ODBC 5.0.2 (Never released)
C.4.18. Changes in Connector/ODBC 5.0.1 (Connector/ODBC 5.0 Alpha 2) (05 June 2006)
C.4.19. Changes in MySQL Connector/ODBC 3.51.27 (20 November 2008)
C.4.20. Changes in MySQL Connector/ODBC 3.51.26 (07 July 2008)
C.4.21. Changes in MySQL Connector/ODBC 3.51.25 (11 April 2008)
C.4.22. Changes in MySQL Connector/ODBC 3.51.24 (14 March 2008)
C.4.23. Changes in MySQL Connector/ODBC 3.51.23 (09 January 2008)
C.4.24. Changes in MySQL Connector/ODBC 3.51.22 (13 November 2007)
C.4.25. Changes in MySQL Connector/ODBC 3.51.21 (08 October 2007)
C.4.26. Changes in MySQL Connector/ODBC 3.51.20 (10 September 2007)
C.4.27. Changes in MySQL Connector/ODBC 3.51.19 (10 August 2007)
C.4.28. Changes in MySQL Connector/ODBC 3.51.18 (08 August 2007)
C.4.29. Changes in MySQL Connector/ODBC 3.51.17 (14 July 2007)
C.4.30. Changes in MySQL Connector/ODBC 3.51.16 (14 June 2007)
C.4.31. Changes in MySQL Connector/ODBC 3.51.15 (07 May 2007)
C.4.32. Changes in MySQL Connector/ODBC 3.51.14 (08 March 2007)
C.4.33. Changes in MySQL Connector/ODBC 3.51.13 (Never released)
C.4.34. Changes in MySQL Connector/ODBC 3.51.12 (11 February 2005)
C.4.35. Changes in MySQL Connector/ODBC 3.51.11 (28 January 2005)
C.5. MySQL Connector/NET Change History
C.5.1. Changes in MySQL Connector/NET Version 6.1.x
C.5.2. Changes in MySQL Connector/NET Version 6.0.x
C.5.3. Changes in MySQL Connector/NET Version 5.3.x
C.5.4. Changes in MySQL Connector/NET Version 5.2.x
C.5.5. Changes in MySQL Connector/NET Version 5.1.x
C.5.6. Changes in MySQL Connector/NET Version 5.0.x
C.5.7. Changes in MySQL Connector/NET Version 1.0.x
C.5.8. Changes in MySQL Connector/NET Version 0.9.0 (30 August 2004)
C.5.9. Changes in MySQL Connector/NET Version 0.76
C.5.10. Changes in MySQL Connector/NET Version 0.75
C.5.11. Changes in MySQL Connector/NET Version 0.74
C.5.12. Changes in MySQL Connector/NET Version 0.71
C.5.13. Changes in MySQL Connector/NET Version 0.70
C.5.14. Changes in MySQL Connector/NET Version 0.68
C.5.15. Changes in MySQL Connector/NET Version 0.65
C.5.16. Changes in MySQL Connector/NET Version 0.60
C.5.17. Changes in MySQL Connector/NET Version 0.50
C.6. MySQL Visual Studio Plugin Change History
C.6.1. Changes in MySQL Visual Studio Plugin 1.0.3 (Not yet released)
C.6.2. Changes in MySQL Visual Studio Plugin 1.0.2 (Not yet released)
C.6.3. Changes in MySQL Visual Studio Plugin 1.0.1 (4 October 2006)
C.6.4. Changes in MySQL Visual Studio Plugin 1.0.0 (4 October 2006)
C.7. MySQL Connector/J Change History
C.7.1. Changes in MySQL Connector/J 5.1.x
C.7.2. Changes in MySQL Connector/J 5.0.x
C.7.3. Changes in MySQL Connector/J 3.1.x
C.7.4. Changes in MySQL Connector/J 3.0.x
C.7.5. Changes in MySQL Connector/J 2.0.x
C.7.6. Changes in MySQL Connector/J 1.2b (04 July 1999)
C.7.7. Changes in MySQL Connector/J 1.2.x and lower
C.8. MySQL Connector/MXJ Change History
C.8.1. Changes in MySQL Connector/MXJ 5.0.6 (04 May 2007)
C.8.2. Changes in MySQL Connector/MXJ 5.0.5 (14 March 2007)
C.8.3. Changes in MySQL Connector/MXJ 5.0.4 (28 January 2007)
C.8.4. Changes in MySQL Connector/MXJ 5.0.3 (24 June 2006)
C.8.5. Changes in MySQL Connector/MXJ 5.0.2 (15 June 2006)
C.8.6. Changes in MySQL Connector/MXJ 5.0.1 (Never released)
C.8.7. Changes in MySQL Connector/MXJ 5.0.0 (09 December 2005)
C.9. MySQL Connector/C++ Change History
C.9.1. Changes in MySQL Connector/C++ 1.0.x
C.10. MySQL Proxy Change History
C.10.1. Changes in MySQL Proxy 0.7.0 (Not yet released)
C.10.2. Changes in MySQL Proxy 0.6.1 (06 February 2008)
C.10.3. Changes in MySQL Proxy 0.6.0 (11 September 2007)
C.10.4. Changes in MySQL Proxy 0.5.1 (30 June 2007)
C.10.5. Changes in MySQL Proxy 0.5.0 (19 June 2007)

This appendix lists the changes from version to version in the MySQL source code through the latest version of MySQL 6.0, which is currently MySQL 6.0.12. Starting with MySQL 5.0, we began offering a new version of the Manual for each new series of MySQL releases (5.0, 5.1, and so on). For information about changes in previous release series of the MySQL database software, see the corresponding version of this Manual. For information about legacy versions of the MySQL software through the 4.1 series, see MySQL 3.23, 4.0, 4.1 Reference Manual.

We update this section as we add new features in the 6.0 series, so that everybody can follow the development process.

Note that we tend to update the manual at the same time we make changes to MySQL. If you find a recent version of MySQL listed here that you can't find on our download page (, it means that the version has not yet been released.

The date mentioned with a release version is the date of the last Bazaar commit on which the release was based, not the date when the packages were made available. The binaries are usually made available a few days after the date of the tagged ChangeSet, because building and testing all packages takes some time.

The manual included in the source and binary distributions may not be fully accurate when it comes to the release changelog entries, because the integration of the manual happens at build time. For the most up-to-date release changelog, please refer to the online version instead.

C.1. Changes in Release 6.0.x (Development)

An overview of which features were added in MySQL 6.0 can be found here: Section 1.4.1, “What Is New in MySQL 6.0”.

For a full list of changes, please refer to the changelog sections for each individual 6.0 release.

C.1.1. Changes in MySQL 6.0.12 (Not yet released)

Functionality added or changed:

  • The time zone tables for Windows available at have been updated. (Bug#39923)

  • The mysqltest program now has a move_file from_file to_file command for renaming files. This should be used in test cases rather than invoking an external command that might be platform specific. (Bug#39542)

Bugs fixed:

  • Important Change: Replication: The CHANGE MASTER TO statement required the value for RELAY_LOG_FILE to be an absolute path, while the MASTER_LOG_FILE path could be relative.

    The inconsistent behavior is resolved by allowing relative paths for RELAY_LOG_FILE, and by using the same basename for RELAY_LOG_FILE as for MASTER_LOG_FILE. For more information, see Section, “CHANGE MASTER TO Syntax”. (Bug#12190)

  • Important Change: Replication: The transactional behavior of STOP SLAVE has changed. Formerly, it took effect immediately, even inside a transaction; now, it waits until the current replication event group (if any) has finished executing, or until the user issues a KILL QUERY or KILL CONNECTION statement.

    This was done in order to solve the problem encountered when replication was stopped while a nontransactional slave was replicating a transaction on the master. (It was impossible to roll back a mixed-engines transaction when one of the engines was nontransactional, which meant that the slave could not safely re-apply any transaction that had been interrupted by STOP SLAVE.) (Bug#319, Bug#38205)

    See also Bug#43217.

  • Important Change: An option that requires a value, when specified in an option file without a value, was assigned the text of the next line in the file as the value. Now, if you fail to specify a required value in an option file, the server aborts with an error.

    This change does not effect how options are handled by the server when they are used on the command line. For example, starting the server using mysqld_safe --relay-log --relay-log-index & causes the server to create relay log files named --relay-log-index.000001, --relay-log-index.000002, and so on, because the --relay-log option expects an argument. (Bug#25192)

  • Partitioning: When a value was equal to a PARTITION ... VALUES LESS THAN (value) value other than MAXVALUE, the corresponding partition was not pruned. (Bug#42944)

  • Replication: Issuing the following statements, in the order shown, could cause a deadlock between the user thread and I/O thread:



    See also Bug#38715, Bug#38716.

  • Replication: Unrelated errors occurring during the execution of RESET SLAVE could cause the slave to crash. (Bug#44179)

  • Replication: When using semi-synchronous replication:

    • KILL statements were not always obeyed for a session blocked by a semi-synchronous ACK signal.

    • SHOW PROCESSLIST did not provide any indication that a session was blocked by the ACK signal.


    See also Bug#40935.

  • Replication: Replicating TEXT or VARCHAR columns declared as NULL on the master but NOT NULL on the slave caused the slave to crash. (Bug#43789)

    See also Bug#38850, Bug#43783, Bug#43785.

  • Replication: Executing the sequence of statements RESET SLAVE, RESET MASTER, and FLUSH LOGS, when binary log or relay log files listed in the index file could not be found, could cause the server to crash. This could happen, for example, when these files had been moved or deleted manually. (Bug#41902)

  • Replication: MySQL creates binary logs in a numbered sequence, with a maximum possible 4294967295 concurrent log files, 4294967295 being the maximum value for an unsigned long integer. However, binary log file extensions were turned into negative numbers once the variable used to hold the value reached the maximum value for a signed long integer (2147483647). Consequently, when the sequence value was incremented to the next (negative) number, this caused MySQL to try to create the file using a .000000 extension, causing the server to fail since this file already existed.

    Negative file extensions are now disallowed, and an error is returned when the limit is reached. In addition, FLUSH LOGS now also reports warnings to the user, if the extension number has reached the limit, and warnings are printed to the error log when the limit is approaching. (Bug#40611)

  • Replication: Updating a table having no primary key, using an unindexed CHAR column as the key, caused row-based replication to fail. (Bug#40045)

  • Replication: The --slave-skip-errors option had no effect when using row-based logging format. (Bug#39393)

  • Replication: Issuing concurrent STOP SLAVE, START SLAVE, and RESET SLAVE statements using different connections caused the replication slave to crash. (Bug#38716)

    See also Bug#38715, Bug#44312.

  • Replication: The following erors were not correctly reported:

    • Failures during slave thread initialization

    • Failures while initializing the relay log position (immediately following the starting of the slave thread)

    • Failures while processing queries passed through the --init_slave option.

    Information about these types of failures can now be found in the output of SHOW SLAVE STATUS. (Bug#38197)

  • Replication: Killing the thread executing a DDL statement, after it had finished its execution but before it had written the binlog event, caused the error code in the binlog event to be set (incorrectly) to ER_SERVER_SHUTDOWN or ER_QUERY_INTERRUPTED, which caused replication to fail. (Bug#37145)

    See also Bug#27571, Bug#22725.

  • Replication: Column aliases used inside subqueries were ignored in the binary log. (Bug#35515)

  • For settings of lower_case_table_names greater than 0, some queries for INFORMATION_SCHEMA tables left entries with incorrect lettercase in the table definition cache. (Bug#44738)

  • Valgrind warnings for the DECODE(), ENCRYPT(), and FIND_IN_SET() functions were corrected. (Bug#44358, Bug#44365, Bug#44367)

  • On Windows, entries for build-vs9.bat and build-vs9_x64.bat were missing in win/ (Bug#44353)

  • Not all lock types had proper descriptive strings, resulting in garbage output from mysqladmin debug. (Bug#44164)

  • Use of HANDLER statements with INFORMATION_SCHEMA tables caused a server crash. Now HANDLER is prohibited with such tables. (Bug#44151)

  • On Windows, if the mysql client was reading input from a pipe, it could crash attempting to read after EOF. (Bug#44133)

  • MySQL Server allowed the creation of a merge table based on views but crashed when attempts were made to read from that table. The following example demonstrates this:

    #Create a test table
    CREATE TABLE tmp (id int, c char(2));                                           
    #Create two VIEWs upon it
    CREATE VIEW v1 AS SELECT * FROM tmp;                                            
    CREATE VIEW v2 AS SELECT * FROM tmp;                                            
    #Finally create a MERGE table upon the VIEWs
    CREATE TABLE merge (id int, c char(2))
    #Reading from the merge table lead to a crash
    SELECT * FROM merge;

    The final line of the code generated the crash. (Bug#44040)

  • Some schema names longer than 8 characters were not supported by IBMDB2I. The engine has been updated to allow digits and underscore characters to be used in names longer than 8 characters. (Bug#44025)

  • In some circumstances, when a table is created with the IBMDB2I engine, the CREATE TABLE statement will return successfully but the table will not exist. (Bug#44022)

  • The ucs2_swedish_ci and utf8_swedish_ci collations did not work with indexes using the IBMDB2I storage engine. Support is now provided for MySQL when running on IBM i 6.1 or higher. (Bug#44020)

  • Invoking SHOW TABLE STATUS from within a stored procedure could cause a Packets out of order error. (Bug#43962)

  • myisamchk could display a negative Max keyfile length value. (Bug#43950)

  • On 64-bit systems, a key_buffer_size value larger than 4GB could couse MyISAM index corruption. (Bug#43932)

  • mysqld_multi incorrectly passed --no-defaults to mysqld_safe. (Bug#43876)

  • SHOW VARIABLES did not properly display the value of slave_skip_errors. (Bug#43835)

  • On Windows, a server crash occurred for attempts to insert a floating-point value into a CHAR column with a maximum length less than the converted floating-point value length. (Bug#43833)

  • Incorrect initialization of MyISAM table indexes could cause incorrect query results. (Bug#43737)

  • libmysqld crashed when it was reinitialized. (Bug#43706, Bug#44091)

  • UNION of floating-point numbers did unnecessary rounding. (Bug#43432)

  • ALTER DATABASE ... UPGRADE DATA DIRECTORY NAME failed when the database contained views. (Bug#43385)

  • Certain statements might open a table and then wait for an impending global read lock without noticing whether they hold a table being waiting for by the global read lock, causing a hang. Affected statements are SELECT ... FOR UPDATE, LOCK TABLES ... WRITE, TRUNCATE TABLE, and LOAD DATA INFILE. (Bug#43230)

  • Using an XML function such as ExtractValue() more than once in a single query could produce erroneous results. (Bug#43183)

    See also Bug#43937.

  • DROP DATABASE did not clear the message list. (Bug#43012, Bug#43138)

  • Full-text prefix searches could hang the connection and cause 100% CPU consumption. (Bug#42907)

  • Comparison of TIME values could lose the sign of operands. (Bug#42664)

  • MAKETIME() could lose the sign of negative arguments. (Bug#42662)

  • SEC_TO_TIME() could lose the sign of negative arguments. (Bug#42661)

  • InnoDB had excessive contention for a character set mutex. (Bug#42649)

  • Incorrect elevation of warning messages to error messages for unsafe statements caused a server crash. (Bug#42640)

  • CHECK TABLE suggested use of REPAIR TABLE for corrupt tables for storage engines not supported by REPAIR TABLE. Now CHECK TABLE suggests that the user dump and reload the table. (Bug#42563)

  • A problem in plugin.h - plugins could be getting a definition of MYSQL_LEX_STRING which was different from the server expectations. It would cause affected plugins to crash. (Bug#42461)

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

  • There was a race condition when changing innodb_commit_concurrency at runtime from zero to nonzero or from nonzero to zero. Now this variable cannot be changed at runtime from zero to nonzero or vice versa. The value can still be changed from one nonzero value to another. (Bug#42101)

    See also Bug#45749.

  • The state of a thread for the embedded server was always displayed as Writing to net, which is incorrect because there is no network connection for the embedded server. (Bug#41971)

  • Compressing a table with the myisampack utility caused the server to produce Valgrind warnings when it opened the table. (Bug#41541)

  • For a MyISAM table with DELAY_KEY_WRITE enabled, the index file could be corrupted without the table being marked as crashed if the server was killed. (Bug#41330)

  • Killing an INSERT ... SELECT statement for a MyISAM table could cause table corruption if the table had indexes. (Bug#40827)

  • mysqld_safe did not treat dashes and underscores as equivalent in option names. (Bug#40368)

  • If a transaction was implicitly committed by a START TRANSACTION or BEGIN statement, metadata locks held by the transaction incorrectly could be released before the commit actually occurred. (Bug#40188)

  • A multiple-table DELETE IGNORE statement involving a foreign key constraint caused an assertion failure. (Bug#40127)

  • Multiple-table UPDATE statements did not properly activate triggers. (Bug#39953)

  • The mysql_setpermission operation for removing database privileges removed global privileges instead. (Bug#39852)

  • A stored routine contain a C-style comment could not be dumped and reloaded. (Bug#39559)

  • In an UPDATE or DELETE via a secondary index, InnoDB did not store the cursor position. This made InnoDB crash in semi-consistent read while attempting to unlock a nonmatching record. (Bug#39320)

  • The functions listed in Section, “Creating Geometry Values Using MySQL-Specific Functions”, previously accepted WKB arguments and returned WKB values. They now accept WKB or geometry arguments and return geometry values.

    The functions listed in Section, “Creating Geometry Values Using WKB Functions”, previously accepted WKB arguments and returned geometry values. They now accept WKB or geometry arguments and return geometry values. (Bug#38990)

  • On WIndows, running the server with myisam_use_mmap enabled caused MyISAM table corruption. (Bug#38848)

  • mysqlbinlog had a memory leak in its option-processing code. (Bug#38468)

  • Setting the general_log_file or slow_query_log_file system variable to a nonconstant expression caused the variable to become unset. (Bug#38124)

  • CHECK TABLE did not properly check whether MyISAM tables created by servers from MySQL 4.0 or older needed to be upgraded. This could cause problems upgrading to MySQL 5.1 or higher. (Bug#37631)

  • mysql_install_db failed if run as root and the root directory (/) was not writable. (Bug#36462)

  • An UPDATE statement that updated a column using the same DES_ENCRYPT() value for each row actually updated different rows with different values. (Bug#35087)

  • Inserting the result of CONCAT() invoked with a utf32 string and a number for arguments caused a server crash. (Bug#34021)

  • For shared-memory connections, the read and write methods did not properly handle asynchronous close events, which could lead to the client locking up waiting for a server response. For example, a call to mysql_real_query() would block forever on the client side if the executed statement was aborted on the server side. Thanks to Armin Schöffmann for the bug report and patch. (Bug#33899)

  • The default values for the general query log and slow query log file are documented to be based on the server host name and located in the data directory. However, they were in fact being based on the basename and location of the process ID (PID) file. The name and location defaults for the PID file are based on the server host name and data directory, so if it was not assigned a different name explicitly, its defaults were used and the general query log and slow query log file defaults were as documented. But if the PID file was assigned a value with the --pid-file option, the defaults for the general query log and slow query log file were incorrect. This has been rectified so that the defaults for all three files are based on the server host name and data directory.

    A remaining problem is that the binary log and relay log .NNNNNN and .index basename defaults are based on the PID file basename, contrary to the documentation. This issue is to be addressed as Bug#45359. (Bug#33693)

  • The following statements generated an incorrect and confusing error message when used with ENGINE=MyISAM:

    Such statements now fail with Error 1478, Table storage engine 'MyISAM' does not support the create option 'TABLESPACE or LOGFILE GROUP'. (Bug#31293)

  • myisamchk and myisampack were not being linked with the library that enabled support for * filename pattern expansion. (Bug#29248)

  • COMMIT did not delete savepoints if there were no changes in the transaction. (Bug#26288)

  • Several memory allocation functions were not being checked for out-of-memory return values. (Bug#25058)

  • Previously, the server handled character data types for a routine parameter, local routine variable created with DECLARE, or function return value as follows: If there was no CHARACTER SET attribute, the database character set and its default collation were used. If the CHARACTER SET attribute was present, the COLLATE attribute was not supported, so the character set's default collation was used. (This includes use of BINARY, because in this context BINARY specifies the binary collation of the character set.)

    Now for character data types, if there is a CHARACTER SET attribute in the declaration, the specified character set and its default collation is used. If the COLLATE is also present, that collation is used rather than the default collation. If there is no CHARACTER SET attribute, the database character set and collation in effect at routine creation time are used. (The database character set and collation are given by the value of the character_set_database and collation_database system variables.) (Bug#24690)

  • Several data-modification statements were not being counted toward the MAX_UPDATES_PER_HOUR user resource limit. (Bug#21793)

C.1.2. Changes in MySQL 6.0.11 (11 May 2009)

Functionality added or changed:

  • Incompatible Change: The optimizer_switch system variable controls optimizations that can be switched on and off. The syntax for flags in its value has changed from 'no_opt_name' to 'opt_name={on|off|default}'. For information about the new syntax, see Section 7.2.22, “Using optimizer_switch to Control the Optimizer”.

  • Replication: The global server variables sync_master_info and sync_relay_log_info are introduced for use on replication slaves to control synchronization of, respectively, the and files.

    In each case, setting the variable to a nonzero integer value N causes the slave to synchonize the corresponding file to disk after every N events. Setting its value to 0 allows the operation system to handle syncronization of the file instead.

    The actions of these variables, when enabled, are analogous to how the sync_binlog variable works with regard to binary logs on a replication master.

    These variables can also be set in my.cnf, or by using the server options --sync-master-info and --sync-relay-log-info respectively.

    An additional system variable relay_log_recovery is also now available. When enabled, this variable causes a replication slave to discard relay log files obtained from the replication master following a crash.

    This variable can also be set in my.cnf, or by using the --relay-log-recovery server option.

    This fix improves and expands upon one made in MySQL 6.0.10 which introduced the sync_relay_log variable. For more information about all of the server system variables introduced by these fixes, see Section, “Replication Slave Options and Variables”. (Bug#31665, Bug#35542, Bug#40337)

  • 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 deprecated mysql_fix_privilege_tables script has been removed. (Bug#42589)

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

  • The RESTORE statement now has a SKIP_GAP_EVENT option that causes the restore operation not to write the gap event to the binary log that causes any replication slaves to stop replication. This is useful when RESTORE is run on a master server and the backup image does not contain databases that are replicated to the slaves. (Bug#39780)

  • Previously, the --secure-file-priv option and secure_file_priv system variable, if set to a directory, limited BACKUP DATABASE and RESTORE operations to files in the given directory. Now the --secure-backup-file-priv option and secure_backup_file_priv system variable apply instead. (Bug#39581)

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

  • A new program, mysqlbackup, displays information from backups created with the BACKUP DATABASE statement.

  • MySQL now implements the SQL standard SIGNAL and RESIGNAL statements. See Section 12.8.8, “SIGNAL and RESIGNAL.

Bugs fixed:

  • Incompatible Change: For system variables that take values of ON or OFF, OF was accepted as a legal variable. Now system variables that take “enumeration” values must be assigned the full value. This affects some other variables that previously could be assigned using unambiguous prefixes of allowable values, such as tx_isolation. (Bug#34828)

  • Incompatible Change: If a data definition language (DDL) statement occurred for a table that was being used by another session in an active transaction, statements could be written to the binary log in the wrong order. For example, this could happen if DROP TABLE occurred for a table being used in a transaction. This is now prevented by deferring release of metadata locks on tables used within a transaction until the transaction ends.

    This bug fix results in some incompatibilities with previous versions:

    • A table that is being used by a transaction within one session cannot be used in DDL statements by other sessions until the transaction ends.

    • FLUSH TABLES WITH READ LOCK blocks for active transactions that hold metadata locks until those transactions end. The same is true for attempts to set the global value of the read_only system variable.


  • Important Change: Replication: CHANGE MASTER TO ... MASTER_HOST='' — explicitly setting MASTER_HOST equal to an empty string — created a file with an empty host field. This led to a The server is not configured as slave error when attempting to execute a START SLAVE statement. Now, if MASTER_HOST is set to an empty string, the CHANGE MASTER TO statement fails with an error. (Bug#28796)

  • Replication: Important Note: Binary logging with --binlog_format=ROW failed when a change to be logged included more than 251 columns. This issue was not known to occur with mixed-format or statement-based logging. (Bug#42977)

    See also Bug#42914.

  • Replication: The SHOW SLAVE STATUS connection thread competed with the slave SQL thread for use of the error message buffer. As a result, the connection thread sometimes received incomplete messages. This issue was uncovered with valgrind when message strings were passed without NULL terminators, causing the error Conditional jump or move depends on uninitialised value(s). (Bug#43076)

  • Replication: This fix handles 2 issues encountered on replication slaves during startup:

    1. A failure while allocating the master info structure caused the slave to crash.

    2. A failure during recovery caused the relay log file not to be properly initialized which led to a crash on the slave.


  • Replication: Assigning an invalid directory for the --slave-load-tmpdir caused the replication slave to crash. (Bug#42861)

  • Replication: The mysql.procs_priv system table was not replicated. (Bug#42217)

  • 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: An INSERT DELAYED into a TIMESTAMP column issued concurrently with an insert on the same column not using DELAYED, but applied after the other insert, was logged using the same timestamp as generated by the other (non-DELAYED) insert. (Bug#41719)

  • 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 MIXED binary logging format did not switch to row-based mode for statements containing the LOAD_FILE() function. (Bug#39701)

  • 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: When using row-based format, replication failed with the error Could not execute Write_rows event on table ...; Field '...' doesn't have a default value when an INSERT was made on the master without specifying a value for a column having no default, even if strict server SQL mode was not in use and the statement would otherwise have succeeded on the master. Now the SQL mode is checked, and the statement is replicated unless strict mode is in effect. For more information, see Section 5.1.8, “Server SQL Modes”. (Bug#38173)

    See also Bug#38262, Bug#43992.

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

  • Replication: The value of Slave_IO_running in the output of SHOW SLAVE STATUS did not distinguish between all 3 possible states of the slave I/O thread (not running; running but not connected; connected). Now the value Connecting (rather than No) is shown when the slave I/O thread is running but the slave is not connected to a replication master.

    The server system variable Slave_running also reflects this change, and is now consistent with what is shown for Slave_IO_running. (Bug#30703, Bug#41613)

  • Replication: Queries which were written to the slow query log on the master were not written to the slow query log on the slave. (Bug#23300)

  • Replication: When the server SQL mode included IGNORE_SPACE, statement-based replication of LOAD DATA INFILE ... INTO tbl_name failed because the statement was read incorrectly from the binary log; a trailing space was omitted, causing the statement to fail with a syntax error when run on the slave. (Bug#22504)

    See also Bug#43746.

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


  • Memory corruption of join buffers could occur when using the Batched Key Access algorithm with incremental join buffers to execute join operations for a query over several tables that selects BLOB values. (Bug#44250)

  • The server could crash at startup when initializing plugins listed in the plugin table. (Bug#44137)

  • A RESTORE operation that restored a MyISAM table using the native MyISAM restore driver could cause the MyISAM key cache to be disabled. (Bug#44068)

  • In some cases, when the Batched Key Access algorithm is used with join_cache_level equal to 6, multi-join queries could return incorrect results. (Bug#44019)

  • valgrind would report errors for the StorageInterface, StorageHAndler and CmdGen portions of Falcon. (Bug#43995)

  • On 64-bit debug builds, code in safemalloc resulted in errors due to use of a 32-bit value for 64-bit allocations. (Bug#43885)

  • When performing a high number of concurrent index updates on a Falcon table, mysqld could crash due to an assertion. (Bug#43765)

  • An attempt by a user who did not have the SUPER privilege to kill a system thread could cause a server crash. (Bug#43748)

  • On Windows, incorrectly specified link dependencies in CMakeLists.txt resulted in link errors for mysql_embedded, mysqltest_embedded, and mysql_client_test_embedded. (Bug#43715)

  • make distcheck failed to properly handle subdirectories of storage/ndb. (Bug#43614)

  • Incorrect use of parser information could lead to acquisition of incorrect lock types. (Bug#43568)

  • Upgrading MySQL to 6.0.10 from 6.0.9 when using Falcon tables and the mysql_upgrade tool would cause mysqld to crash during start up. (Bug#43562)

  • Running a SELECT using a range query on FLOAT on a Maria table could return invalid result sets. (Bug#43552)

  • Running a SELECT using a range query on with <> or < with a negative values on a Maria table could return invalid result sets. (Bug#43530)

  • Running a SELECT on a multi-range query with a LIMIT clause on a Maria table could return invalid result sets. (Bug#43527)

  • Executing a LIMIT ... FOR UPDATE statement on a Falcon table when using transactions with concurrent threads could cause a crash because the record information cannot be accessed correctly. (Bug#43488)

  • When performing SELECT statements on a Falcon table using an indexed INTEGER column could return incorrect row matches. (Bug#43452)

  • RESTORE on a case-insensitive server failed if the backup image contained databases or tables with uppercase names. Now, RESTORE handles this case by converting the names to lowercase in the restore catalog, as long as there are no duplicate names after the conversion. (Bug#43363)

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

  • BACKUP DATABASE stored incorrect table counts in the backup image. (Bug#43324)

  • Assigning a value to the backupdir system variable resulted in Valgrind errors. (Bug#43303)

  • mysql crashed if a request for the current database name returned an empty result, such as after the client has executed a preceding SET sql_select_limit=0 statement. (Bug#43254)

  • SQL statements executed by BACKUP DATABASE and RESTORE were logged in the general query log. (Bug#43166)

  • If the value of the version_comment system variable was too long, the mysql client displayed a truncated startup message. (Bug#43153)

  • Compilation failures on Windows Vista using Visual Studio 2008 Professional were corrected. (Bug#43120)

  • Recovering a Falcon table from a failure when the table contains BLOB columns could cause an assertion failure. (Bug#43106)

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

  • mysqld would crash when using Falcon tables during shutdown if the server was running in embedded mode. (Bug#43048)

  • The MySQL Backup library had incorrect logic and error reporting for metadata saving. (Bug#42959)

  • Queries of the following form returned an empty result:

    SELECT ... WHERE ... (col=col AND col=col) OR ... (false expression)


  • A two-way join query with a GROUP BY or ORDER BY clause could produce incorrect results when rows of the first table are accessed by an index compatible with the GROUP BY or ORDER BY list while the second table is joined using the Batched Key Access algorithm. (Bug#42955)

  • The strings/CHARSET_INFO.txt file was not included in source distributions. (Bug#42937)

  • When running REPAIR on a crashed Falcon table can crash mysqld if pages have been incorrectly marked dirty, but not locked, during write. (Bug#42824)

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

  • Recovery of Falcon tables while there were active transaction during the crash may fail to recover completely. (Bug#42743)

  • Use of semijoin optimization could cause a server crash. (Bug#42740)

  • When Falcon is populating the INFORMATION_SCHEMA.TABLESPACES table, an exception can be raised because required result set has been closed before the resultset has been completed. This can happen during a BACKUP operation. (Bug#42725, Bug#42830)

  • Assigning a value to the backupdir system variable resulted in a memory leak. (Bug#42695)

  • Assigning an incorrect value to the backup_progress_log_file system variable resulted in Valgrind errors. (Bug#42685)

  • When performing SELECT queries on tables containing TIMESTAMP or DATETIME colums with indexes using a WHERE clause comparing the field value to NULL using the <= or <> operators, the wrong information would be returned. (Bug#42683, Bug#43623, Bug#43620, Bug#42681)

  • A dangling pointer in mysys/my_error.c could lead to client crashes. (Bug#42675)

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

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

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


    InnoDB Plugin versions 1.0.4 and higher will take advantage of this bug fix. Although the InnoDB Plugin is source code compatible with multiple MySQL releases, a given binary InnoDB Plugin can be used only with a specific MySQL release. When InnoDB Plugin 1.0.4 is released, it is expected to be compiled for MySQL 5.1.34. For 5.1.33, you can use InnoDB Plugin 1.0.3, but you must build from source.


    This regression was introduced by Bug#29263.

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

  • Recovery of a Falcon table with a large number of rows can cause a failure in the page type written for the internal FALCON_USER and FALCON_TEMPORARY tablespaces. (Bug#42560)

  • Passing an unknown time zone specification to CONVERT_TZ() resulted in a memory leak. (Bug#42502)

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

  • Previously, RESTORE would crash if the backup image contained tables originally stored in a tablespace that no longer existed at RESTORE time. Now the tablespace is recreated like it was at BACKUP DATABASE time if it does not exist when RESTORE is executed. (Bug#42402)

  • If the server was started with --thread_handling=pool-of-threads, the MAX_QUERIES_PER_HOUR user resource limit. (Bug#42384)

  • Recovery of Falcon tables with indexes can fail because the index page information has not been recorded properly. (Bug#42344)

  • Using a LIKE clause on a Maria table using an index and the CP1251 collation would return invalid data. (Bug#42299)

  • Running a SELECT using a JOIN on a Maria table could return invalid result sets. (Bug#42298)

  • Running multi-range queries on Maria tables could cause a crash. (Bug#42297)

  • Using a falcon-scavenge-schedule of * * * * * would cause Falcon to never execute the required threads to operate. (Bug#42275)

  • If the server was started with an option that had a missing or invalid value, a subsequent error that would cause normally the server to shut down could cause it to crash instead. (Bug#42244)

  • Using ORDER BY and or LIMIT on Falcon tables could give inconsistent results for rows that contain NULL columns in the corresponding ORDER BY clause. (Bug#42208)

  • For InnoDB tables, there was a race condition for ALTER TABLE, OPTIMIZE TABLE, CREATE INDEX, and DROP INDEX operations when periodically checking whether table copying can be committed. (Bug#42152)

  • In InnoDB recovery after a server crash, table lookup could fail and corrupt the data dictionary cache. (Bug#42075)

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

  • BACKUP DATABASE and RESTORE did not implement backup and restore of privileges for stored procedures and stored functions. (Bug#41979)

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

  • Recovering a Falcon table that uses BLOB columns could cause unbounded tablespace growth before recovery completes. (Bug#41840)

  • Recovery of Falcon tables could fail with an indicating that a wrong page type was identified in the Falcon serial log. (Bug#41837, Bug#42745, Bug#44114)

  • RESTORE crashed for Falcon tables. (Bug#41722)

  • With more than two arguments, LEAST(), GREATEST(), and CASE could unnecessarily return Illegal mix of collations errors. (Bug#41627)

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

  • RESTORE failed if it tried to restore a privilege for a nonexistent object. (Bug#41578)

  • In InnoDB recovery after a server crash, rollback of a transaction that updated a column from NULL to NULL could cause another crash. (Bug#41571)

  • The mysql client could misinterpret its input if a line was longer than an internal buffer. (Bug#41486)

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

  • The Falcon CycleManager has been updated, which addresses a number of issues when examining records in various transaction states and their visisbility/isolation in relation to other threads. (Bug#41391, Bug#41478, Bug#41742, Bug#41850, Bug#42459, Bug#41661, Bug#42185, Bug#43146, Bug#43298, Bug#43299, Bug#34624, Bug#42189)

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

  • If the tables underlying a MERGE table had a primary key but the MERGE table itself did not, inserting a duplicate row into the MERGE table caused a server crash. (Bug#41305)

  • In the help command output displayed by mysql, the description for the \c (clear) command was misleading. (Bug#41268)

  • Several resource leaks were corrected in the error-handling code for the MySQL Backup library. (Bug#41250, Bug#41294)

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

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

  • Using RESTORE to restore a database through a named pipe resulted in corrupt data. (Bug#40975)

  • Performing SELECT operations on Falcon tables using the maximum BIG INT value would fail to return matching rows. (Bug#40950)

  • For some queries, an equality propagation problem could cause a = b and b = a to be handled differently. (Bug#40925)

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

  • Indexes on Falcon tables using numeric columns could return incorrect information. (Bug#40607, Bug#41582, Bug#40950)

  • The load_defaults(), my_search_option_files() and my_print_default_files() functions in the C client library were subject to a race condition in multi-threaded operation. (Bug#40552)

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

  • Falcon could cause an assertion when the system has run out of memory and tries to report the memory allocation failure. (Bug#40155)

  • The backup logs became unusable if a BACKUP DATABASE operation was interrupted. (Bug#39924)

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

  • mysql_upgrade did not remove the online_backup and online_backup_progress tables from the mysql database. (These are what the backup_history and backup_progress tables were called previously.) (Bug#39655)

  • With row-based binary logging, replication of InnoDB tables containing NULL-valued BIT columns could fail. (Bug#39648)

  • When using Falcon and the system runs out of all memory and swap space, mysqld could hang while attempting to write an error message. (Bug#39552)

  • The mysql_stmt_close() C API function did not flush all pending data associated with the prepared statement. (Bug#39519)

  • Updating Falcon tables after an online ALTER ADD COLUMN operation could fail. (Bug#39445)

  • Following ALTER TABLE ... DISCARD TABLESPACE for an InnoDB table, an attempt to determine the free space for the table before the ALTER TABLE operation had completely finished could cause a server crash. (Bug#39438)

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

  • If --basedir was specified, mysqld_safe did not use it when attempting to locate my_print_defaults. (Bug#39326)

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

  • Performing an online ALTER TABLE statement against a Falcon table, the Falcon serial log could grow beyond the maximum permitted size for a serial log, ignoring both the rotation and truncation. (Bug#39130)

  • Previously, the num_objects column in the backup_history table showed only the number of tables in the backup image. It now shows the number of objects with names (tablespaces, databases, tables, views, stored programs). (Bug#39109)

  • BACKUP DATABASE treated the database list in case-sensitive fashion, even on case-insensitive file systems. (Bug#39063)

  • The ALTER ROUTINE privilege incorrectly allowed SHOW CREATE TABLE. (Bug#38347)

  • BACKUP DATABASE crashed if there was no default database. (Bug#38294)

  • Setting a savepoint with the same name as an existing savepoint incorrectly deleted any other savepoints that had been set in the meantime. For example, setting savepoints named a, b, c, b resulted in savepoints a, b, rather than the correct savepoints a, c, b. (Bug#38187)

  • Locking of myisam.log did not work correctly on Windows. (Bug#38133, Bug#41224)

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

  • Setting the session value of the debug system variable also set the global value. (Bug#38054)

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

  • A workload consisting of CREATE TABLE ... SELECT and DML operations could cause deadlock. (Bug#37433)

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

  • Trying to recover Falcon tables after a crash when the corresponding tables and tablespaces have not been created before the crash could cause a recovery failure. (Bug#36993)

  • When MySQL was configured with the --with-max-indexes=128 option, mysqld crashed. (Bug#36751)

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

  • Setting the join_buffer_size variable to its minimum value produced spurious warnings. (Bug#36446)

  • The audit plugin was not receiving MYSQL_AUDIT_GENERAL_ERROR events. (Bug#36098)

  • The use of NAME_CONST() can result in a problem for CREATE TABLE ... SELECT statements when the source column expressions refer to local variables. Converting these references to NAME_CONST() expressions can result in column names that are different on the master and slave servers, or names that are too long to be legal column identifiers. A workaround is to supply aliases for columns that refer to local variables.

    Now a warning is issued in such cases that indicate possible problems. (Bug#35383)

  • SHOW CREATE EVENT output did not include the DEFINER clause. (Bug#35297)

  • mysqld would crash in a concurrent workload with INSERT/CREATE TABLE/DROP TABLE or INSERT/ALTER TABLE combinations on Falcon tables. (Bug#35255)

  • It was not possible to interrupt a long running BACKUP DATABASE or RESTORE operation. (Bug#35079)

  • Several deprecated or obsolete settings were removed from the sample option files. (Bug#34521)

  • Searching for 0x00 in Falcon tables using the VARBINARY column type would fail to return the correct rows. In addition, a crash could be encountered when modifying a column to the VARBINARY type. (Bug#34478, Bug#33190, Bug#23692)

  • A subquery using SELECT ... FOR UPDATE on a Falcon table fails to lock table correctly during the UPDATE. (Bug#34182)

  • With Falcon tables running concurrent transactions, some transactions may not be rolled back correctly, leading to an infinite loop. (Bug#34174)

  • INSTALL PLUGIN and UNINSTALL PLUGIN did not handle plugin identifiers consistently with respect to lettercase. (Bug#33731)

  • RESTORE often would not correctly identify the tablespace into which a Falcon table should be restored. (Bug#33569)

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

  • If Falcon runs out of memory while inserting records and you try to alter the affected table, you may get a record memory is exhausted error, and the table can no longer be used or accessed. (Bug#33177)

  • The DDL blocker for BACKUP DATABASE and RESTORE did not block all statements that it should. The blocker is now called the Backup Metadata Lock and blocks statements that change database metadata. (Bug#32702)

  • Detection by configure of several functions such as setsockopt(), bind(), sched_yield(), and gtty() could fail. (Bug#31506)

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

  • When an InnoDB tablespace filled up, an error was logged to the client, but not to the error log. Also, the error message was misleading and did not indicate the real source of the problem. (Bug#31183)

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

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

  • For InnoDB tables that have their own .ibd tablespace file, a superfluous ibuf cursor restoration fails! message could be written to the error log. This warning has been suppressed. (Bug#27276)

  • Internal base64_xxx() functions were renamed to have a prefix of my_ to avoid conflicts with other libraries. (Bug#26818)

  • The Time column for SHOW PROCESSLIST output and the value of the TIME column of the INFORMATION_SCHEMA.PROCESSLIST table now can have negative values. Previously, the column was unsigned and negative values were displayed incorrectly as large positive values. Negative values can occur if a thread alters the time into the future with SET TIMESTAMP = value or the thread is executing on a slave and processing events from a master that has its clock set ahead of the slave. (Bug#22047)

  • Restoring a mysqldump dump file containing FEDERATED tables failed because the file contained the data for the table. Now only the table definition is dumped (because the data is located elsewhere). (Bug#21360)

  • SHOW CREATE DATABASE did not account for the value of the lower_case_table_names system variable. (Bug#21317)

  • Incorrect length metadata could be returned for LONG TEXT columns when a multibyte server character set was used. (Bug#19829)

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

C.1.3. Changes in MySQL 6.0.10 (03 March 2009)

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)

    See also Bug#44270.

  • Replication: A new global server variable sync_relay_log is introduced for use on replication slaves. Setting this variable to a nonzero integer value N causes the slave to synchonize the relay log to disk after every N events. Setting its value to 0 allows the operation system to handle syncronization of the file. The action of this variable, when enabled, is analogous to how the sync_binlog variable works with regard to binary logs on a replication master.

    This variable can also be set in my.cnf, or by using the server option --sync-relay-log.

    For more information, see Section, “Replication Slave Options and Variables”. (Bug#31665, Bug#35542, Bug#40337)

  • Replication: In circular replication, it was sometimes possible for an event to propagate such that it would be reapplied on all servers. This could occur when the originating server was removed from the replication circle and so could no longer act as the terminator of its own events, as normally happens in circular replication.

    In order to prevent this from occurring, a new IGNORE_SERVER_IDS option is introduced for the CHANGE MASTER TO statement. This option takes a list of replication server IDs; events having a server ID which appears in this list are ignored and not applied. For more information, see Section, “CHANGE MASTER TO Syntax”. (Bug#25998)

    See also Bug#27808.

  • The libedit library was upgraded to version 2.11. (Bug#42433)

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

  • Columns that provide a catalog value in INFORMATION_SCHEMA tables (for example, TABLES.TABLE_CATALOG) now have a value of def rather than NULL. (Bug#35427)

  • now supports --client-bindir and --client-libdir options for specifying the directory where client binaries and libraries are located. (Bug#34995)

Bugs fixed:

  • Security Fix: Using an XPath expression employing a scalar expression as a FilterExpr with ExtractValue() or UpdateXML() caused the server to crash. Such expressions now cause an error instead. (Bug#42495)

  • Incompatible Change: The fix for Bug#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 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)

  • Incompatible Change: Falcon supported case-sensitive tablespace names. The code has been changed so that all tablespace names are converted to uppercase names during creation. Because of this change:

    • It is not possible to drop existing tablespace created by previous versions, if its name wasn't in upper case.

    • It is not possible to create tables using tablespace created by previous versions, if tablespace name wasn't in upper case.

    (Bug#35257, Bug#33719)

  • Important Change: Replication: If a trigger was defined on an InnoDB table and this trigger updated a nontransactional table, changes performed on the InnoDB table were replicated and were visible on the slave before they were committed on the master, and were not rolled back on the slave after a successful rollback of those changes on the master.

    As a result of the fix for this issue, the semantics of mixing nontransactional and transactional tables in a transaction in the first statement of a transaction have changed. Previously, if the first statement in a transaction contained nontransactional changes, the statement was written directly to the binary log. Now, any statement appearing after a BEGIN (or immediately following a COMMIT if AUTOCOMMIT = 0) is always considered part of the transaction and cached. This means that nontransactional changes do not propagate to the slave until the transaction is committed and thus written to the binary log.

    See Section, “Replication and Transactions”, for more information about this change in behavior. (Bug#40116)

  • Important Change: Replication: MyISAM transactions replicated to a transactional slave left the slave in an unstable condition. This was due to the fact that, when replicating from a nontransactional storage engine to a transactional engine with AUTOCOMMIT turned off, no BEGIN and COMMIT statements were written to the binary log; thus, on the slave, a never-ending transaction was started.

    The fix for this issue includes enforcing AUTOCOMMIT mode on the slave by replicating all AUTOCOMMIT=1 statements from the master. (Bug#29288)

  • Partitioning: A comparison with an invalid DATE value in a query against a partitioned table could lead to a crash of the MySQL server.


    Invalid DATE and DATETIME values referenced in the WHERE clause of a query on a partitioned table are treated as NULL. See Section 17.4, “Partition Pruning”, for more information.


  • Partitioning: A query that timed out when run against a partitioned table failed silently, without providing any warnings or errors, rather than returning Lock wait timeout exceeded. (Bug#40515)

  • Partitioning: ALTER TABLE ... REORGANIZE PARTITION could crash the server when the number of partitions was not changed. (Bug#40389)

    See also Bug#41945.

  • Partitioning: ALTER TABLE ... ADD PARTITION and ALTER TABLE ... DROP PARTITION could cause the MySQL server to crash. This was only known to occur on Windows platforms where MySQL had been built with the EXTRA_DEBUG option. (Bug#38784)

  • Partitioning: SHOW TABLE STATUS could show a nonzero value for the Mean record length of a partitioned InnoDB table, even if the table contained no rows. (Bug#36312)

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

  • Partitioning: Unnecessary calls were made in the server code for performing bulk inserts on partitions for which no inserts needed to be made. (Bug#35845)

    See also Bug#35843.

  • Partitioning: For partitioned tables with more than ten partitions, a full table scan was used in some cases when only a subset of the partitions were needed. (Bug#33730)

  • Replication: On Windows, RESET MASTER failed in the event of a missing binlog file rather than issuing a warning and completing the rest of the statement. (Bug#42150, Bug#42288)

  • Replication: Per-table AUTO_INCREMENT option values were not replicated correctly for InnoDB tables. (Bug#41986)

  • Replication: Some log_event types did not skip the post-header when reading. (Bug#41961)

  • Replication: Attempting to read a binary log containing an Incident_log_event having an invalid incident number could cause the debug server to crash. (Bug#40482)

  • Replication: When CHANGE MASTER TO ... SET MASTER_HEARTBEAT_PERIOD ... failed, no error code was set. (Bug#40459)

  • Replication: When using row-based replication, an update of a primary key that was rolled back on the master due to a duplicate key error was not rolled back on the slave. (Bug#40221)

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

  • 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, Bug#38934)

  • Replication: A slave compiled using --with-libevent and run with --thread-handling=pool-of-threads could sometimes crash. (Bug#36929)

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

    See also Bug#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)

  • Replication: mysqlbinlog sometimes failed when trying to create temporary files; this was because it ignored the specified temp file directory and tried to use the system /tmp directory instead. (Bug#35546)

    See also Bug#35543.

  • Replication: In statement mode, mysqlbinlog failed to issue a SET @@autommit statement when the autocommit mode was changed. (Bug#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)

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

  • The optimizer could underestimate the memory required for column descriptors during join processing and cause memory corruption or a server crash. (Bug#42744)

  • A '%' character in SQL statements could cause the server to crash. (Bug#42634)

  • For the batched-key access method, numbers of records were being specified rather than numbers of ranges. (Bug#42593)

  • Certain queries could result in Valgrind warnings in the optimizer. (Bug#42534)

  • An optimization introduced for Bug#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)

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

  • Performing a BACKUP and RESTORE on a Maria table while an existing workload is in progress could lead to a corrupted table and possible crash. (Bug#42519)

  • The default Falcon memory parameters have been updated, which should help to improve performance. The new settings for all the memory parameters are as follows:

    • falcon_record_memory_max is now 250 MB

    • falcon_page_cache_size is now 250 MB

    • falcon_record_scavenge_threshold is 90% (of record memory max)

    • falcon_record_scavenge_floor is 80% (of scavenge threshold)

    • falcon_record_chill_threshold is 5 MB

    • falcon_index_chill_threshold is now 4MB

    (Bug#42510, Bug#36442)

  • When running Falcon during a very high concurrency workload, mysqld could fail. (Bug#42475)

  • Falcon would fail to create a table in a TABLESPACE that had not already been opened by a previous operation. (Bug#42414, Bug#42743)

  • The recovery of Falcon tablespaces could fail because the tablespace information had become corrupt. (Bug#42392)

  • The SSL certficates included with MySQL distributions were regenerated because the previous ones had expired. (Bug#42366)

  • A deadlocked Maria table would incorrectly be marked as crashed. (Bug#42201)

  • INSERT operations to a Falcon table involving BIT columns with an index would fail to find the correct rows to update. (Bug#42196)

  • User variables within triggers could cause a crash if the mysql_change_user() C API function was invoked. (Bug#42188)

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

  • For Falcon tables, range queries using an index prefix were slow when Multi-Range Read index scans were disabled. (Bug#42136, Bug#41890)

  • The ALTER ONLINE TABLE statement for Falcon tables would not include support for add a primary key. (Bug#42099)

  • Sequences and auto increment values in Falcon tables would not reset, even when a TRUNCATE TABLE operation was executed. The behavior has now been updated to reset the values to the original table definition when TRUNCATE TABLE is applied. (Bug#42079)

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


  • Queries executed using a join buffer could return incorrect results. (Bug#42020)

  • Some queries using NAME_CONST(.. COLLATE ...) led to a server crash due to a failed type cast. (Bug#42014)

  • The MAP file was not included in Windows distribution, but is needed by the InnoDB plugin. MAP file generation has again been enabled. (Bug#42001)

  • The optimizer underestimated the number of field descriptors for the join buffer in some cases. (Bug#41919)

  • Internal misconfiguration of the hash table used for the join buffer could cause a server crash. (Bug#41894)

  • String reallocation could cause memory overruns. (Bug#41868)

  • Queries executed using semi-join materialization could cause a crash if the outer query has a HAVING clause. (Bug#41842)

  • Running concurrent nontransactional queries on a Falcon table could cause a crash. (Bug#41835)

  • mysql_install_db did not pass some relevant options to mysqld. (Bug#41828)

  • A Valgrind warning in open_tables() was corrected. (Bug#41759)

  • A Valgrind warning in setup_wild() was corrected. (Bug#41729)

  • For Falcon tables, concurrent execution of a statement which in the general case should acquire a TL_READ_NO_INSERT lock on the table (for example multiple-table update, DML with subqueries, or statements involving new foreign key checks) and a statement that modifies the table might lead to warnings in the error log or even to deadlocks. (Bug#41688, Bug#42069)

  • 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, nonmatching semi-consistently read rows were not unlocked when they should have been. (Bug#41671)

  • resolve_stack_dump was unable to resolve the stack trace format produced by mysqld in MySQL 5.1 and up (see Section, “Using a Stack Trace”). (Bug#41612)

  • In example option files provided in MySQL distributions, the thread_stack value was increased from 64K to 128K. (Bug#41577)

  • REPAIR TABLE crashed for compressed MyISAM tables. (Bug#41574)

  • The ALTER TABLESPACE statement would fail on Falcon tablespaces because of incorrect assumption about TABLESPACE support for the Falcon engine. (Bug#41548)

  • When opening a Falcon TABLESPACE, the server could crash if the tablespace header could not be read correctly, including if the tablespace had become corrupt or deleted. Now an error will be thrown and reported to the error log. (Bug#41545)

  • The optimizer could ignore an error and rollback request during a filesort, causing an assertion failure. (Bug#41543)

  • Recovery of Maria tables with BLOB columns could fail to complete correctly. (Bug#41493)

  • DATE_FORMAT() could cause a server crash for year-zero dates. (Bug#41470)

  • BACKUP DATABASE and RESTORE did not reset the message list displayed by SHOW WARNINGS. (Bug#41468, Bug#41359)

  • SET PASSWORD caused a server crash if the account name was given as CURRENT_USER(). (Bug#41456)

  • When substituting system constant functions with a constant result, the server was not expecting NULL function return values and could crash. (Bug#41437)

  • The mysql-test/include/UnicodeData.txt file, if present, was not included in MySQL distributions. (Bug#41436)

  • When using TRUNCATE on a Falcon table, the sequence value for auto increment columns would not be reset correctly. (Bug#41411)

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

  • Queries such as SELECT ... CASE AVG(...) WHEN ... that used aggregate functions in a CASE expression crashed the server. (Bug#41363)

  • INSERT INTO .. SELECT ... FROM and CREATE TABLE ... SELECT ... FROM a TEMPORARY table could inadvertently change the locking type of the temporary table from a write lock to a read lock, causing statement failure. (Bug#41348)

  • Recovery of Falcon tables after a crash if falcon_page_size had been set to 32K and BLOB columns were used in the Falcon tables. (Bug#41227)

  • On Windows, the server could not be started with the --thread-handling=pool-of-threads option. (Bug#41218)

  • Transactions in Falcon tables could be recorded incorrectly, leading other waiting transactions to complete even though the original transaction information had not been successfully made durable. (Bug#41194)

  • For a query that is executed using a range access method over an index that matches the ordering and there is an ORDER BY clause, EXPLAIN showed Using MRR even though Multi-Range Read access was not used. (Bug#41136)

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

  • FULLTEXT indexes did not work for Unicode columns that used a custom UCA collation. (Bug#41084)

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

  • When a storage engine plugin failed to initialize before allocating a slot number, it would acidentally unplug the engine in slot 0. (Bug#41013)

  • Some queries that used a “range checked for each record” scan could return incorrect results. (Bug#40974)

  • For BACKUP DATABASE, errors from the commit blocker were not logged. (Bug#40970)

  • Certain SELECT queries could fail with a Duplicate entry error. (Bug#40953)

  • For debug servers, OPTIMIZE TABLE on a compressed table caused a server crash. (Bug#40949)

  • The Windows installer displayed incorrect product names in some images. (Bug#40845)

  • The CSV engine did not parse '\X' characters when they occurred in unquoted fields. (Bug#40814)

  • Comparison of empty strings for the latin2_czech_cs character set could hang. (Bug#40805)

  • The Falcon storage engine has been updated to incorporate new code for the built-in scavenger service, which handles the caching of records in memory. This fixes a number of different issues related to the visibility of different records during certain operations and improves the memory usage. The same fix also corrects the behavior where the space allocated for BLOB records would not be recovered correctly, causing the size of the Falcon table space files to increase with each BLOB INSERT or UPDATE operation. (Bug#40801, Bug#34893, Bug#36700, Bug#40342, Bug#41831, Bug#41870)

  • IF(..., CAST(longtext_val AS UNSIGNED), signed_val) as an argument to an aggregate function could cause an assertion failure. (Bug#40761)

  • Changing innodb_thread_concurrency at runtime could cause errors. (Bug#40760)

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

  • When archive tables were joined on their primary keys, a query returned no result if the optimizer chose to use this index. (Bug#40677)

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

  • SELECT statements could be blocked by INSERT DELAYED statements that were waiting for a lock, even with low_priority_updates enabled. (Bug#40536)

  • If a RESTORE operation was in progress on a master server, slaves were not prohibited from starting replication of the master. (Bug#40434)

  • TRUNCATE TABLE for an InnoDB table did not flush cached queries for the table. (Bug#40386)

  • For InnoDB tables that used ROW_FORMAT=REDUNDANT, storage size of NULL columns could be determined incorrectly. (Bug#40369)

  • When building Falcon as a plugin, the plugin would be installed into the wrong directory and would fail to be located when trying to install the plugin. (Bug#40336)

  • Backup completed” was logged for nonsuccessful BACKUP DATABASE operations. “Restore completed” was logged for nonsuccessful RESTORE operations. (Bug#40305)

  • The internal dependency mechanism for handling records and transactions within Falcon has been updated. This fixes a number of issues with transactions and concurrent workloads within Falcon tables. (Bug#40274, Bug#36410)

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

  • The ':' character was incorrectly disallowed in table names. (Bug#40104)

  • For an InnoDB table, DROP TABLE or ALTER TABLE ... DISCARD TABLESPACE could take a long time or cause a server crash. (Bug#39939)

  • Threads were set to the Table lock state in such a way that use of this state by other threads to check for a lock wait was subject to a race condition. (Bug#39897)

  • When a MEMORY table became full, the error generated was returned to the client but was not written to the error log. (Bug#39886)

  • Storage engine plugins on Windows could've been built with a definition of time_t which was different from the server expectations. The difference could cause affected plugins to crash. In addition, the use of the time_t type in the storage engine API layer has been enforced. (Bug#39802, Bug#40092)

  • For a server started with the --temp-pool option on Windows, temporary file creation could fail. This option now is ignored except on Linux systems, which was its original intended scope. (Bug#39750)

  • The implementation of the backup_wait_timeout system variable was machine dependent and did not work correctly on big-endian machines. (Bug#39749, Bug#40808)

  • ALTER TABLE on a table with FULLTEXT index that used a pluggable FULLTEXT parser could cause debug servers to crash. (Bug#39746)

  • When performing concurrent DROP INDEX and INSERT or UPDATE operations on a Falcon table, an assertion could occur when recovering from a crashed instance. (Bug#39678)

  • The server crashed if an integer field in a CSV file did not have delimiting quotes. (Bug#39616)

  • InnoDB could hang trying to open an adaptive hash index. (Bug#39483)

  • Queries with that end with ... WHERE condition ORDER BY index_columns LIMIT N could produce rows that did not match the WHERE clause for certain kinds of conditions and table data distributions. (Bug#39447)

  • The internal buffering logic for BACKUP DATABASE had a problem that could lead to corrupt backup images. (Bug#39375)

  • A bad pointer dereference caused BACKUP DATABASE to crash. (Bug#39361)

  • INFORMATION_SCHEMA access optimizations did not work properly in some cases. (Bug#39270)

  • Cardinality for merge tables kept approaching zero in myrg_attach_children() because m_info->rec_per_key_part was initialized to 0 only when the function was first called. (Bug#39185)

  • The expression ROW(...) IN (SELECT ... FROM DUAL) always returned TRUE. (Bug#39069)

  • When the Falcon storage engine encountered an I/O error, mysqld would crash. Errors now raise an exception, which is reported to the error log and Falcon will fail to initialize. (Bug#38970, Bug#41545)

  • SELECT * FROM INFORMATION_SCHEMA.ROUTINES could fail if there was no default database. (Bug#38916)

  • InnoDB could fail to generate AUTO_INCREMENT values after an UPDATE statement for the table. (Bug#38839)

  • The greedy optimizer could cause a server crash due to improper handling of nested outer joins. (Bug#38795)

  • Use of COUNT(DISTINCT) prevented NULL testing in the HAVING clause. (Bug#38637)

  • Building MySQL on FreeBSD would result in a failure during the gen_lex_hash phase of the build. (Bug#38364)

  • A mix of TRUNCATE TABLE with LOCK TABLES and UNLOCK TABLES for an InnoDB could cause a server crash. (Bug#38231)

  • The ExtractValue() function did not work correctly with XML documents containing a DOCTYPE declaration. (Bug#38227)

  • The innodb_stats_on_metadata system variable was not displayed by SHOW VARIABLES and was not settable at runtime. (Bug#38189)

  • Enabling the sync_frm system variable had no effect on the handling of .frm files for views. (Bug#38145)

  • Use of spatial data types in prepared statements could cause memory leaks or server crashes. (Bug#37956, Bug#37671)

  • An error in a debugging check caused crashes in debug servers. (Bug#37936)

  • An initialization procedure for materialized subquery execution was not called due to an early optimization of MIN()/MAX() queries. (Bug#37896)

  • The presence of a /* ... */ comment preceding a query could cause InnoDB to use unnecessary gap locks. (Bug#37885)

  • An assertion failure could occur when trying to execute a query with a subquery such that one of the subquery's tables was accessed using the DS-MRR access method. (Bug#37842)

  • For comparison of NULL to a subquery result inside IS NULL, the comparison could evaluate to NULL rather than to TRUE or FALSE. This occurred for expressions such as:



  • When using ALTER TABLE on an InnoDB table, the AUTO_INCREMENT value could be changed to an incorrect value. (Bug#37788)

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

  • Primary keys were treated as part of a covering index even if only a prefix of a key column was used. (Bug#37742)

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

  • The internal-use-only filename character set was visible in the output of some SHOW statements and in the contents of the COLLATION_CHARACTER_SET_APPLICABILITY table of INFORMATION_SCHEMA. (Bug#37554)

  • Storing TIMESTAMP values in Falcon tables on a machine supporting big endian storage (for example SPARC), the time stamp information returned would be incorrect. (Bug#37281)

  • Certain boolean-mode FULLTEXT searches that used the truncation operator did not return matching records and calculated relevance incorrectly. (Bug#37245)

  • Previously, InnoDB performed REPLACE INTO T SELECT ... FROM S WHERE ... by setting shared next-key locks on rows from S. Now InnoDB selects rows from from S with shared locks or as a consistent read, as for INSERT ... SELECT. This reduces lock contention between sessions. (Bug#37232)

  • When creating an index on a Falcon table with a very large dataset, mysqld would crash. (Bug#37056)

  • For an InnoDB table with a FOREIGN KEY constraint, TRUNCATE TABLE may be performed using row by row deletion. If an error occurred during this deletion, the table would be only partially emptied. Now if an error occurs, the truncation operation is rolled back and the table is left unchanged. (Bug#37016)

  • Subquery materialization produced incorrect results when comparing different types. (Bug#36752)

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

  • Previously, statements inside a stored program did not clear the warning list. For example, warnings or errors generated by statements within a trigger or stored function would be accumulated and added to the message list for the statement that activated the trigger or invoked the function, “polluting” the output of SHOW WARNINGS or SHOW ERRORS for the outer statement. Normally, messages for a statement that can generate messages replace messages from the previous such statement. The effect was that a statement could have a different effect on the message list depending on whether it executed inside or outside of a stored program.

    Now within a stored program, successive statements that can generate messages update the message list and replace messages from the previous such statement. Only messages from the last of these statements is copied to the message list for the outer statement. (Bug#36649)

  • myisampack --join did not create the destination table .frm file. (Bug#36573)

  • When parsing or formatting interval values of DAY_MICROSECOND type, fractional seconds were not handled correctly when more-significant fields were implied or omitted. (Bug#36466)

  • comp_err sometimes crashed due to improper mutex use. (Bug#36428)

  • The mysql client sometimes improperly interpreted string escape sequences in nonstring contexts. (Bug#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)

  • Some error numbers were incorrect. (Bug#36062)

  • For upgrades to MySQL 5.1 or higher, mysql_upgrade did not re-encode database or table names that contained nonalphanumeric characters. (They would still appear after the upgrade with the #mysql50# prefix described in Section 8.2.3, “Mapping of Identifiers to File Names”.) To correct this problem, it was necessary to run mysqlcheck --all-databases --check-upgrade --fix-db-names --fix-table-names manually. mysql_upgrade now runs that command automatically after performing the initial upgrade. (Bug#35934)

  • SHOW CREATE TABLE did not display a printable value for the default value of BIT columns. (Bug#35796)

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

  • InnoDB could fail to generate AUTO_INCREMENT values if rows previously had been inserted containing literal values for the AUTO_INCREMENT column. (Bug#35498, Bug#36411, Bug#39830)

  • Result set metadata for columns retrieved from INFORMATION_SCHEMA tables did not have the db or org_table members of the MYSQL_FIELD structure set. (Bug#35428)

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

  • The CREATE_OPTIONS column for INFORMATION_SCHEMA.TABLES did not display the KEY_BLOCK_SIZE option. (Bug#35275)

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

  • The mysql client incorrectly parsed statements containing the word “delimiter” in mid-statement. (Bug#33812)

    See also Bug#38158.

  • Falcon would allow you to explicitly create a table within the internal FALCON_TEMPORARY tablespace. You can no longer explicitly select the FALCON_TEMPORARY tablespace. (Bug#33720)

  • It was possible to set Falcon memory parameters to values larger than the maximum memory supported by the supported by the host environment. (Bug#33583)

  • The mysqldump command would not include the TABLESPACE information for Falcon tables within the dump information. (Bug#33148)

  • Three conditions were discovered that could cause an upgrade from MySQL 5.0 to 5.1 to fail: 1) Triggers associated with a table that had a #mysql50# prefix in the name could cause assertion failure. 2) ALTER DATABASE ... UPGRADE DATA DIRECTORY NAME failed for databases that had a #mysql50# prefix if there were triggers in the database. 3) mysqlcheck --fix-table-name didn't use UTF8 as the default character set, resulting in parsing errors for tables with nonlatin symbols in their names and trigger definitions. (Bug#33094, Bug#41385)

  • libmysqld was not built with all character sets. (Bug#32831)

  • Queries with dependent subqueries were slow. (Bug#32665)

  • Falcon would allow you to create a Falcon TABLESPACE with the same filename as existing datafiles (including datafiles of other engines). All Falcon tablespaces are now created with a .fts extension, regardless of the specified filename. (Bug#32398)

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

  • Attempts to open a valid MERGE table sometimes resulted in a ER_WRONG_MRG_TABLE error. This happened after failure to open an invalid MERGE table had also generated an ER_WRONG_MRG_TABLE error. (Bug#32047)

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

  • Server variables could not be set to their current values on Linux platforms. (These fixes are in addition to those made in MySQL 6.0.5 and 6.0.9.) (Bug#31177)

    See also Bug#6958.

  • ALTER TABLE statements that added a column and added a nonpartial index on the column failed to add the index. (Bug#31031)

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

  • Static storage engines and plugins that were disabled and dynamic plugins that were installed but disabled were not listed in the INFORMATION_SCHEMA appropriate PLUGINS or ENGINES table. (Bug#29263)

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

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

  • SSL support was not included in some “generic” RPM packages. (Bug#26760)

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

  • DROP TABLE for INFORMATION_SCHEMA tables produced an Unknown table error rather than the more appropriate Access denied. (Bug#24062)

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

  • For the DIV operator, incorrect results could occur for noninteger operands that exceed BIGINT range. Now, if either operand has a noninteger type, the operands are converted to DECIMAL and divided using DECIMAL arithmetic before converting the result to BIGINT. If the result exceeds BIGINT range, an error occurs. (Bug#8457)

C.1.4. Changes in MySQL 6.0.9 (10 January 2009)

Functionality added or changed:

  • BACKUP DATABASE and RESTORE now indicate in the server's error log which databases are being backed up or restored. (Bug#40307)

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

  • MySQL support for adding collations using LDML specifications did not support the <i> identity rule that indicates one character sorts identically to another. The <i> rule now is supported. (Bug#37129)

  • Previously, RESTORE overwrote any databases with information from the backup image. Now, RESTORE aborts with an error if the backup image contains any databases that currently exist on the server, unless the optional keyword OVERWRITE is given following the image file name. (Bug#34579)

  • A new statement, PURGE BACKUP LOGS, enables the contents of the MySQL Backup logs to be culled. See Section, “PURGE BACKUP LOGS Syntax”. (Bug#33364)

  • A new algorithm that uses both index access to the joined table and a join buffer has been implemented. It is called the Batched Key Access (BKA) Join algorithm. The algorithm supports inner join, outer join and semi-join operations, including nested outer joins and nested semi-joins. Also, the Block Nested-Loop (BNL) Join algorithm previously used only for inner joins has been extended and can be employed for outer join and semi-join operations, including nested nested outer joins and nested semi-joins. For more information, see Section 7.2.15, “Block Nested-Loop and Batched Key Access Joins”.

    In conjunction with this work, there is a new system variable, join_cache_level, that controls how join buffering is done.

Bugs fixed:

  • Security Enhancement: When the DATA DIRECTORY or INDEX DIRECTORY clause of a CREATE TABLE statement referred to a subdirectory of the data directory via a symlinked component of the data directory path, it was accepted, when for security reasons it should be rejected. (Bug#39277)

  • Incompatible Change: CHECK TABLE ... FOR UPGRADE did not check for collation changes made in MySQL 6.0.1 to latin2_czech_cs (Bug#25420) or collation changes made in MySQL 6.0.6 to big5_chinese_ci, cp866_general_ci, gb2312_chinese_ci, and gbk_chinese_ci. This also affects mysqlcheck and mysql_upgrade, which cause that statement to be executed. See Section 2.11.3, “Checking Whether Table Indexes Must Be Rebuilt”. (Bug#40054)

  • Partitioning: Replication: Changing the transaction isolation level while replicating partitioned InnoDB tables could cause statement-based logging to fail. (Bug#39084)

  • Partitioning: This bug was introduced in MySQL 6.0.5. (Bug#40954)

    This regression was introduced by Bug#30573, Bug#33257, Bug#33555.

  • Partitioning: With READ COMMITTED transaction isolation level, InnoDB uses a semi-consistent read that releases nonmatching rows after MySQL has evaluated the WHERE clause. However, this was not happening if the table used partitions. (Bug#40595)

  • Partitioning: A SELECT using a range WHERE condition with an ORDER BY on a partitioned table caused a server crash. (Bug#40494)

  • Partitioning: For a partitioned table having an AUTO_INCREMENT column: If the first statement following a start of the server or a FLUSH TABLES statement was an UPDATE statement, the AUTO_INCREMENT column was not incremented correctly. (Bug#40176)

  • Partitioning: The server attempted to execute the statements ALTER TABLE ... ANALYZE PARTITION, ALTER TABLE ... CHECK PARTITION, ALTER TABLE ... OPTIMIZE PARTITION, and ALTER TABLE ... REORGANIZE PARTITION on tables that were not partitioned. (Bug#39434)

    See also Bug#20129.

  • Partitioning: The value of the CREATE_COLUMNS column in INFORMATION_SCHEMA.TABLES was not partitioned for partitioned tables. (Bug#38909)

  • Partitioning: When executing an ORDER BY query on a partitioned InnoDB table using an index that was not in the partition expression, the results were sorted on a per-partition basis rather than for the table as a whole. (Bug#37721)

  • Partitioning: Partitioned table checking sometimes returned a warning with an error code of 0, making proper response to errors impossible. The fix also renders the error message subject to translation in non-English deployments. (Bug#36768)

  • Partitioning: When SHOW CREATE TABLE was used on a partitioned table, all of the table's PARTITION and SUBPARTITION clauses were output on a single line, making it difficult to read or parse. (Bug#14326)

  • Replication: Row-based replication failed with nonpartitioned MyISAM tables having no indexes. (Bug#40004)

  • An assertion failure occurred for a join query when a small size of the join buffer was set and the value of record_per_key for the index used for a ref access with this join buffer was big enough. (Bug#41204)

  • Unique indexes on FALCON tables can not be created when the column is NOT NULL. (Bug#40994)

  • Accessing user variables within triggers could cause a server crash. (Bug#40770)

  • For single-table UPDATE statements, an assertion failure resulted from a runtime error in a stored function (such as a recursive function call or an attempt to update the same table as in the UPDATE statement). (Bug#40745)

  • Date values of 000-00-00 inserted into a FALCON table were incorrectly recognized and returned when performing a SELECT on a field with an index. (Bug#40614)

  • Several MySQL Backup-related memory-use issues identified by Valgrind were corrected. (Bug#40480)

  • When executing concurrent CREATE TABLE ... SELECT statements on a Maria table, the error Error: Memory allocated at trnman.c:129 was underrun, discovered at ma_close.c:65 error would be logged in the error file, and the server would eventually crash. (Bug#40416)

  • Prepared statements allowed invalid dates to be inserted when the ALLOW_INVALID_DATES SQL mode was not enabled. (Bug#40365)

  • With statement-based binary logging format and a transaction isolation level of READ COMMITTED or stricter, InnoDB printed an error because statement-based logging might lead to inconsistency between master and slave databases. However, this error was printed even when binary logging was not enabled (in which case, no such inconsistency can occur). (Bug#40360)

  • A query with an outer join where the ON expression evaluated to the constant FALSE could return incorrect results when a join buffer was used for the outer join operation. (Bug#40317)

  • Errors from a BACKUP DATABASE or RESTORE operation were shown by SHOW WARNINGS as warnings, not errors. (Bug#40304)

  • If several errors occurred during a BACKUP DATABASE or RESTORE operation, the final error was returned to the client, even though the first error is usually more pertinent. (Bug#40303)

  • Creation of a tablespace file within FALCON could create a tablespace entry in the INFORMATION_SCHEMA.FALCON_TABLESPACE_IO even the underlying data file had not been created. (Bug#40302)

  • Specifying the --log-backup-output option without an argument set the destination for the backup logs to FILE rather than to the default of TABLE. (Bug#40282)

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

  • The server could generate extra rows in the result set for a query with a nested outer join if the inner tables of the outer join were joined using join buffers. (Bug#40268)

  • If BACKUP DATABASE was used to back up an empty database and binary logging enabled, the backup image was flagged as containing binary log information even though it did not. Using RESTORE with the backup image then crashed trying to parse the binary log file name. (Bug#40262)

  • The backup_history_log_file and backup_progress_log_file system variables were not settable at server startup. Now they are. (Bug#40219)

  • The default value of the backup_history_log and backup_progress_log system variables is ON, but explicitly setting them to DEFAULT set them to OFF. (Bug#40218)

  • When an outer join employed a join buffer to join the first inner table by the Blocked Nested-Loop algorithm, extra NULL-complemented rows could be generated if the WHERE clause contained conditions that can be pushed down to this table. (Bug#40192)

  • When the optimizer joined an inner table of an outer join using both “not exists” optimization and a join buffer, an incorrect result set could be returned. (Bug#40134)

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

  • The MySQL Backup message logger caused an assertion failure. (Bug#39997)

  • Retrieval speed from the following INFORMATION_SCHEMA tables was improved by shortening the VARIABLE_VALUE column to 1024 characters: GLOBAL_VARIABLES, SESSION_VARIABLES, GLOBAL_STATUS, and SESSION_STATUS.

    As a result of this change, any variable value longer than 1024 characters will be truncated with a warning. This affects only the init_connect system variable. (Bug#39955)

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

  • Recovery of a tablespace for FALCON tables could fail if the tablespace was already in use. (Bug#39789)

  • Creating a FALCON table while specifying a specific tablespace and partition to be used for the table will fail if the specified tablespace does not already exist, returning a error indicating general table creation failure. The message has been updated to indicate that the failure is due to nonexistent tablespace. (Bug#39702)

  • With the ONLY_FULL_GROUP_BY SQL mode enabled, the check for nonaggregated 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 nonaggregated columns in the WHERE clause. (Bug#39656)

  • Concurrent execution of BACKUP DATABASE and DML operations on MyISAM tables could produce a deadlock. (Bug#39602)

  • The do_abi_check program run during the build process depends on mysql_version.h but that file was not created first, resulting in build failure. (Bug#39571)

  • CHECK TABLE failed for MyISAM INFORMATION_SCHEMA tables. (Bug#39541)

  • On 64-bit Windows systems, the server accepted key_buffer_size values larger than 4GB, but allocated less. (For example, specifying a value of 5GB resulted in 1GB being allocated.) (Bug#39494)

  • Compiling MySQL with FALCON support enabled with a compiler that does not support exceptions would fail to complete successfully. configure has been updated to switch off FALCON support if the specified compiler does not support exceptions. (Bug#39419)

  • Use of the PACK_KEYS or MAX_ROWS table option in ALTER TABLE should have triggered table reconstruction but did not. (Bug#39372)

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

  • Starting MySQL with FALCON support when MySQL has not been compiled with a compiler supporting exceptions would lead to strange errors and results. MySQL will now fail to initialize if you have compiled without exceptions enabled with the following message:

    081116 12:21:12 [ERROR] Falcon must be compiled with C++ exceptions enabled to work. Please adjust your compile flags.
    [Falcon] Error: Falcon exiting process


  • A server built using yaSSL for SSL support would crash if configured to use an RSA key and a client sent a cipher list containing a non-RSA key as acceptable. (Bug#39178)

  • When built with Valgrind, the server failed to access tables created with the DATA DIRECTORY or INDEX DIRECTORY table option. (Bug#39102)

  • With binary logging enabled CREATE VIEW was subject to possible buffer overwrite and a server crash. (Bug#39040)

  • The fast mutex implementation was subject to excessive lock contention. (Bug#38941)

  • Use of InnoDB monitoring (SHOW ENGINE INNODB STATUS or one of the InnoDB Monitor tables) could cause a server crash due to invalid access to a shared variable in a concurrent environment. (Bug#38883)

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

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

  • The server unnecessarily acquired a query cache mutex even with the query cache disabled, resulting in a small performance decrement. (Bug#38551)

  • On Windows, a five-second delay occurred at shutdown of applications that used the embedded server. (Bug#38522)

  • On Solaris, a scheduling policy applied to the main server process could be unintentionally overwritten in client-servicing threads. (Bug#38477)

  • BACKUP DATABASE failed to use the native driver for a Falcon table if the table was partitioned. (Bug#38426)

  • On Windows, the embedded server would crash in mysql_library_init() if the language file was missing. (Bug#38293)

  • The Event Scheduler no longer logs “started in thread” or “executed” successfully messages to the error log. (Bug#38066)

  • Setting the debug system variable and executing a SELECT statement resulted in a Valgrind warning. (Bug#38023)

  • An incorrectly checked XOR subquery optimization resulted in an assertion failure. (Bug#37899)

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

  • Use of an uninitialized constant in EXPLAIN evaluation caused an assertion failure. (Bug#37870)

  • The server did not shut down upon receipt of a SIGINT signal unless it was run within a debugger. (Bug#37869)

  • A query that could use one index to produce the desired ordering and another index for range access with index condition pushdown could cause a server crash. (Bug#37851)

  • Renaming an ARCHIVE table to the same name with different lettercase and then selecting from it could cause a server crash. (Bug#37719)

  • For queries executed with the batched-key access method, an incorrect value of an internal parameter caused a server crash if join_buffer_size was less then 256. (Bug#37690)

  • Compiling MySQL with FALCON support enabled on Solaris 9 using the Sun Studio compiler would fail with error:

    "Interlock.h", line 149: Error: #error cas not defined. We need>= Solaris 10.


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

    See also Bug#42525.

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

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

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

  • Specifying a database name twice to BACKUP DATABASE caused a server crash. Now BACKUP DATABASE ignores duplicate names. (Bug#36933)

  • If a nondirectory file f without an extension was created in the data directory, the server would allow clients to execute a USE f statement even though f could not be a database. The server now verifies that that the named database corresponds to a directory. (Bug#36897)

  • The FALCON storage would silently recreate missing tablespace files if they did not exist. Errors are now written to the MySQL error log when the FALCON system tablespace files are found to be missing. Warnings are produce in the log file when attempting to access data tablespace files that do not exist. (Bug#36804)

  • Use of CONVERT() with GROUP BY to convert numeric values to CHAR could return truncated results. (Bug#36772)

  • The mysql client, when built with Visual Studio 2005, did not display Japanese characters. (Bug#36279)

  • Setting the slave_compressed_protocol system variable to DEFAULT failed in the embedded server. (Bug#35999)

  • Processing for NULL-complemented rows in the result sets of queries with nested outer joins could be incorrect. (Bug#35835)

  • The columns that store character set and collation names in several INFORMATION_SCHEMA tables were lengthened because they were not long enough to store some possible values: SCHEMATA, TABLES, COLUMNS, CHARACTER_SETS, COLLATIONS, and COLLATION_CHARACTER_SET_APPLICABILITY. (Bug#35789)

  • Queries executed using the batched-key access method could cause an assertion fail when key expressions for a ref access depended on columns not only from the previous join table. (Bug#35685)

  • Selecting from an INFORMATION_SCHEMA table into an incorrectly defined MERGE table caused an assertion failure. (Bug#35068)

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

  • BACKUP DATABASE produced an incorrect error message when the backup image file name contained a nonexistent directory. (Bug#34754)

  • SHOW GLOBAL STATUS shows values that aggregate the session status values for all threads. This did not work correctly for the embedded server. (Bug#34517)

  • There were spurious warnings about "Truncated incorrect DOUBLE value" in queries with MATCH ... AGAINST and > or < with a constant (which was reported as an incorrect DOUBLE value) in the WHERE condition. (Bug#34374)

  • mysqldumpslow did not aggregate times. (Bug#34129)

  • mysql_config did not output -ldl (or equivalent) when needed for --libmysqld-libs, so its output could be insufficient to build applications that use the embedded server. (Bug#34025)

  • For a stored procedure containing a SELECT * ... RIGHT JOIN query, execution failed for the second call. (Bug#33811)

  • The CSV storage engine had been modified to require columns to be explicitly specified as NOT NULL in CREATE TABLE statements.

    However, adding columns via the ALTER TABLE command allowed nullable columns to be added to an existing CSV table. (Bug#33696)


  • If a TEMPORARY table existed with the same name as a regular table, BACKUP DATABASE saved the temporary table, causing a subsequent RESTORE to fail. (Bug#33574)

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

  • Execution of a prepared statement that referred to a system variable caused a server crash. (Bug#32124)

  • Some division operations produced a result with incorrect precision. (Bug#31616)

  • Server variables could not be set to their current values on Linux platforms. (These fixes are in addition to those made in MySQL 6.0.5; additional fixes were made in MySQL 6.0.10.) (Bug#31177)

    See also Bug#6958.

  • For Solaris package installation using pkgadd, the postinstall script failed, causing the system tables in the mysql database not to be created. (Bug#31164)

  • For installation on Solaris using pkgadd packages, the mysql_install_db script was generated in the scripts directory, but the temporary files used during the process were left there and not deleted. (Bug#31052)

  • Searching for text values on a column using a character set that provides multi-weight characters and sequences on an INNODB or FALCON table with an index would fail to find the expanded value. (Bug#29246)

  • Some SHOW statements and retrievals from the INFORMATION_SCHEMA TRIGGERS and EVENTS tables used a temporary table and incremented the Created_tmp_disk_tables status variable, due to the way that TEXT columns are handled. The TRIGGERS.SQL_MODE, TRIGGERS.DEFINER, and EVENTS.SQL_MODE columns now are VARCHAR to avoid this problem. (Bug#29153)

  • XA transaction rollbacks could result in corrupted transaction states and a server crash. (Bug#28323)

  • There were cases where string-to-number conversions would produce warnings for CHAR values but not for VARCHAR values. (Bug#28299)

  • For several read only system variables that were viewable with SHOW VARIABLES, attempting to view them with SELECT @@var_name or set their values with SET resulted in an unknown system variable error. Now they can be viewed with SELECT @@var_name and attempting to set their values results in a message indicating that they are read only. (Bug#28234)

  • ALTER TABLE for an ENUM column could change column values. (Bug#23113)

  • Setting the session value of the max_allowed_packet or net_buffer_length system variable was allowed but had no effect. The session value of these variables is now read only. (Bug#22891)

    See also Bug#32223.

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

C.1.5. Changes in MySQL 6.0.8 (03 November 2008)

Functionality added or changed:

  • Incompatible Change: The tables for MySQL Backup logging have been renamed, and the logging capabilities now are more flexible, similar to the capabilities provided for the general query log and slow query log.

    • The names of the MySQL Backup log tables in the mysql database have been changed from online_backup and online_backup_progress to backup_history and backup_progress.

    • Logging now can be enabled or disabled, it is possible to log to tables or to files, and the names of the log files can be changed. For details, see Section, “MySQL Backup Log Control”.

    • A new statement, FLUSH BACKUP LOGS, closes and reopens the backup log files. A new option for mysql_refresh(), REFRESH_BACKUP_LOG, performs the same operation.

  • Important Change: The --skip-thread-priority option is now deprecated in MySQL 5.1 and is removed in MySQL 6.0 such that the server won't change the thread priorities by default. Giving threads different priorities might yield marginal improvements in some platforms (where it actually works), but it might instead cause significant degradation depending on the thread count and number of processors. Meddling with the thread priorities is a not a safe bet as it is very dependent on the behavior of the CPU scheduler and system where MySQL is being run. (Bug#35164, Bug#37536)

  • Important Change: The --log option now is deprecated and will be removed (along with the log system variable) in the future. Instead, use the --general_log option to enable the general query log and the --general_log_file=file_name option to set the general query log file name. The values of these options are available in the general_log and general_log_file system variables, which can be changed at runtime.

    Similar changes were made for the --log-slow-queries option and log_slow_queries system variable. You should use the --slow_query_log and --slow_query_log_file=file_name options instead (and the slow_query_log and slow_query_log_file system variables).

  • The BUILD/compile-solaris-* scripts now compile MySQL with the mtmalloc library rather than malloc. (Bug#38727)

  • Binary distributions for Solaris, Linux, and Mac OS X now are built with support for the pool-of-threads value of thread_handling. (Bug#38636)

  • BACKUP DATABASE now performs an implicit commit, like RESTORE. (Bug#38261)

  • The deprecated --default-table-type server option has been removed. (Bug#34818)

  • On WIndows, use of POSIX I/O interfaces in mysys was replaced with Win32 API calls (CreateFile(), WriteFile(), and so forth) and the default maximum number of open files has been increased to 16384. The maximum can be increased further by using the --open-files-limit=N option at server startup. (Bug#24509)

  • Previously, prepared CALL statements could be used via the C API only for stored procedures that produce at most one result set, and applications could not use placeholders for OUT or INOUT parameters. For prepared CALL statements used via PREPARE and EXECUTE, placeholders could not be used for OUT or INOUT parameters.

    For the C API, prepared CALL support now is expanded in the following ways:

    • A stored procedure can produce any number of result sets. The number of columns and the data types of the columns need not be the same for all result sets.

    • The final values of OUT and INOUT parameters are available to the calling application after the procedure returns. These parameters are returned as an extra single-row result set following any result sets produced by the procedure itself. The row contains the values of the OUT and INOUT parameters in the order in which they are declared in the procedure parameter list.

    • A new C API function, mysql_stmt_next_result(), is available for processing stored procedure results. See Section 20.10.15, “C API Support for Prepared CALL Statements”.

    • The CLIENT_MULTI_RESULTS flag now is enabled by default. It no longer needs to be enabled when you call mysql_real_connect(). (This flag is necessary for executing stored procedures because they can produce multiple result sets.)

    For PREPARE and EXECUTE, placeholder support for OUT and INOUT parameters is now available. See Section 12.2.1, “CALL Syntax”. (Bug#11638, Bug#17898)

  • MySQL now supports an interface for semisynchronous replication: A commit performed on the master side blocks before returning to the session that performed the transaction until at least one slave acknowleges that it has received and logged the events for the transaction. Semisynchronous replication is implemented through an optional plugin component. See Section 16.2.9, “Semisynchronous Replication”

  • Most statements that previously caused an implicit commit before executing now also cause an implicit commit after executing. Also, the FLUSH statement and mysql_refresh() C API function now cause an implicit commit. See Section 12.4.3, “Statements That Cause an Implicit Commit”.

  • The FILES and TABLESPACES tables have been added to INFORMATION_SCHEMA for tracking the individual files and tablespace details for Falcon. In addition, the TABLES table has been extended to incorporate the TABLESPACE_NAME field to specify the tablespace name that a specific table belongs to.

Bugs fixed:

  • Incompatible Change: CHECK TABLE ... FOR UPGRADE did not check for incompatible collation changes made in MySQL 5.1.21 (Bug#29499) and 5.1.23 (Bug#27562, Bug#29461). This also affects mysqlcheck and mysql_upgrade, which cause that statement to be executed. See Section 2.11.3, “Checking Whether Table Indexes Must Be Rebuilt”. (Bug#39585)

    See also Bug#40984.

  • 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 6.0.8 or higher.

    2. Rename the view to v_new and then back to v_orig.

    3. Downgrade to an older 6.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:

    • Dump your data using mysqldump before downgrading and reload the dump file after downgrading.

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

  • Important Change: Replication: The SUPER privilege is now required to change the session value of binlog_format as well as its global value. For more information about binlog_format, see Section 16.1.2, “Replication Formats”. (Bug#39106)

  • Partitioning: Replication: Replication to partitioned MyISAM tables could be slow with row-based binary logging. (Bug#35843)

  • 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: If an error occurred when evaluating a column of a partitioned table for the partitioning function, the row could be inserted anyway. (Bug#38083)

  • Partitioning: Using INSERT ... SELECT to insert records into a partitioned MyISAM table could fail if some partitions were empty and others are not. (Bug#38005)

  • Replication: Issuing the statement CHANGE MASTER TO ... MASTER_HEARTBEAT_PERIOD = period using a value for period outside the permitted range caused the slave to crash. (Bug#39077)

  • Replication: Replication of BLACKHOLE tables did not work with row-based binary logging. (Bug#38360)

  • Replication: In some cases, a replication master sent a special event to a reconnecting slave to keep the slave's temporary tables, but they still had references to the “old” slave SQL thread and used them to access that thread's data. (Bug#38269)

  • Replication: Replication filtering rules were inappropiately applied when executing BINLOG pseudo-queries. One way in which this problem showed itself was that, when replaying a binary log with mysqlbinlog, RBR events were sometimes not executed if the --replicate-do-db option was specified. Now replication rules are applied only to those events executed by the slave SQL thread. (Bug#36099)

  • Replication: For a CREATE TABLE ... SELECT statement that creates a table in a database other than the current one, the table could be created in the wrong database on replication slaves if row-based binary logging is used. (Bug#34707)

  • Replication: A statement did not always commit or roll back correctly when the server was shut down; the error could be triggered by having a failing UPDATE or INSERT statement on a transactional table, causing an implicit rollback. (Bug#32709)

    See also Bug#38262.

  • Compiling using --with-falcon on Mac OS X fails if you use CXX=gcc. You must specify that the g++ compiler should be used for C++ using CXX=g++. (Bug#41270)

  • When building Falcon support on Solaris 10 on the SPARC platform, falcon would not be compiled even when explicitly enabled. (Bug#40390)

  • Running an online DROP INDEX operation on an index using the same key on a Falcon table would fail with an assertion. (Bug#40265)

  • With innodb_autoinc_lock_mode set to 0 (“traditional” locking), deadlock and lock-wait timeout errors encountered while reading AUTO_INCREMENT values were being reported as a generic AUTO_INCREMENT value allocation failure. (The actual error encountered was printed in the error log.) The transaction was being rolled back but all the user saw was an AUTO_INCREMENT failure code. Now the actual locking error code is returned to the user. (Bug#40224)

  • Optimized builds of mysqld crashed when built with Sun Studio on SPARC platforms. (Bug#40224)

  • Creating a table, or selecting from a table using the FALCON storage engine and with a double quote in the name would cause an assertion failure. (Bug#40158, Bug#39388)

  • Windows builds were missing the MySQL Backup log tables. (Bug#40126)

  • The maximum value for falcon-serial-log-buffer has been reduced to 1000. (Bug#40123)

  • The indexes and record contents of a FALCON table could get out of synchronization during a lrge number of updates. Because FALCON returns data only if it matches both the index and record data the result sets returned could be invalid when comparing the results of an index and nonindex based SELECT. (Bug#40112, Bug#40130)

  • The CHECK TABLE ... FOR UPGRADE statement did not check for incompatible collation changes made in MySQL 5.1.24 (Bug#27877). This also affects mysqlcheck and mysql_upgrade, which cause that statement to be executed. See Section 2.11.3, “Checking Whether Table Indexes Must Be Rebuilt”.

    Prior to this fix, a binary upgrade (performed without dumping tables with mysqldump before the upgrade and reloading the dump file after the upgrade) would corrupt tables that have indexes that use the utf8_general_ci or ucs2_general_ci collation for columns that contain 'ß' LATIN SMALL LETTER SHARP S (German). After the fix, CHECK TABLE ... FOR UPGRADE properly detects the problem and warns about tables that need repair.

    However, the fix is not backward compatible and can result in a downgrading problem under these circumstances:

    1. Perform a binary upgrade to a version of MySQL that includes the fix.

    2. Run CHECK TABLE ... FOR UPGRADE (or mysqlcheck or mysql_upgrade) to upgrade tables.

    3. Perform a binary downgrade to a version of MySQL that does not include the fix.

    The solution is to dump tables with mysqldump before the downgrade and reload the dump file after the downgrade. Alternatively, drop and recreate affected indexes. (Bug#40053)

  • MySQL may crash during the recover of Falcon tables if the server was shutdown after a large data load. (Bug#39951)

  • Non-ASCII error messages were corrupted. (Bug#39949)

  • The Threads_created status variable was not correctly incremented when the server was started with the --thread-handling=pool-of-threads option. (Bug#39916)

  • When the Falcon serial log reaches a state where the serial log can no longer be written to, for example when the disk is full, or when permissions have been changed on an open log, then MySQL could crash. (Bug#39912)

  • On Windows Vista, RESTORE did not correctly calculate the validity point from the backup stream. (Bug#39825)

  • Falcon did not support online add/drop index creation on tables using a NOT NULL column. (Bug#39795)

  • When creating a table with the FALCON engine where the size of the key in the index was larger than supported (the error message did not signify the severity of the problem. The message and error has been updated. (Bug#39708)

  • Recovery of Falcon tables could crash because of an invalid or unrecognised tablespace ID. (Bug#39706)

  • Performing an INSERT on Maria table with a UNIQUE column, MySQL could deadlock. (Bug#39697)

  • Memory would be allocated for the Falcon sector cache even if the cache had been disabled (falcon_use_sectorcache). (Bug#39692)

  • The MySQL Backup backup_history log now contains a backup_file_path column. backup_file contains the basename and backup_file_path contains the directory of the image file path name. (Bug#39690)

  • Some MySQL Backup-related memory-use warnings detected by Valgrind were corrected. (Bug#39598)

  • Creating a table with a comment of 62 characters or longer caused a server crash. (Bug#39591)

  • When loading very large datasets into a Falcon table, MySQL may crash because the size of the Falcon serial log exceeds 4GB. The maximum supported size of the serial log file has been increased from a 32-bit to a 64-bit integer to handle larger log file sizes. (Bug#39575)

  • When recovering a crashed Falcon table when the page size had been set to 32K, MySQL could crash with an assertion. (Bug#39574)

  • The Sun Studio compiler failed to build debug versions of the server due to use of features specific to gcc. (Bug#39451)

  • When performing a recovery of a crashed Falcon table on Windows, MySQL would report an exception when then recovery process completed, even though the recovery may have completed successfully. (Bug#39421)

  • Performing an ALTER TABLE on a Maria table where you are changing the column name but not the type, a full table rebuild may be triggered, instead of just a simple rename. (Bug#39399)

  • Dropping a locked Maria table leads to an assertion failure. (Bug#39395)

  • For a TIMESTAMP column in an InnoDB table, testing the column with multiple conditions in the WHERE clause caused a server crash. (Bug#39353)

  • When using a Falcon table, equals (=) comparison of values of columns of type YEAR does not work when an index is present on the YEAR column(s). (Bug#39342)

  • When running TRUNCATE on a table where other threads are also trying to access the same Falcon table, a deadlock could occur between the two executing threads. (Bug#39321)

  • Performing a INSERT INTO ... ON DUPLICATE KEY UPDATE statement on a Maria table would fail with the error 1178: The storage engine for the table doesn't support UPDATE in WRITE CONCURRENT. (Bug#39248)

  • Maria could fail to find data in a table with an index on a char column. (Bug#39243)

  • Running ALTER TABLE PARTITION on a Maria table would lead to a crash. (Bug#39227)

  • Using Maria, executing FLUSH TABLES WITH READ LOCK after a LOCK TABLES statement would lead to a crash. (Bug#39226)

  • When using Falcon on ReiserFS file systems, the initial size of the serial log could cause problems during recovery if the size of the log file was less than 4KB. The minimum size of the serial log file has now been increased to 8KB to address the problem. (Bug#39212)

  • Running multiple SELECT, INSERT, UPDATE and DELETE queries on the Maria table could lead to a deadlock. (Bug#39210)

  • For BACKUP DATABASE, the server could add a / character to the end of the backup path, even when the path ended with a file name rather than a directory name. (Bug#39189)

  • The server could crash when attempting to insert duplicate empty strings into a utf8 SET column. (Bug#39186)

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

  • Building MySQL with Falcon support using Sun Studio 10 would fail due to GNU CC specific code within MemoryManager.h. (Bug#39181)

  • BACKUP DATABASE failed on PowerMac platforms due to type casting problems. (Bug#39127)

  • MySQL Backup was not handling several errors. (Bug#39089)

  • When performing online ALTER operations that change the indexes on Falcon tables, the indexes could get out of synchronization, leading to a crash. (Bug#39081)

  • Some warnings were being reported as errors. (Bug#39059)

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

  • Repeated CREATE TABLE ... SELECT statements, where the created table contained an AUTO_INCREMENT column, could lead to an assertion failure. (Bug#38821)

  • RESTORE crashed if a trigger and an event had the same name. (Bug#38810)

  • For deadlock between two transactions that required a timeout to resolve, all server tables became inaccessible for the duration of the deadlock. (Bug#38804)

  • Running multiple SELECT operations on the same Falcon table could lead to an assertion within the Transaction::initialize. The same operation could also lead to a deadlock situation on the specified table. (Bug#38739, Bug#38748)

  • When inserting a string into a duplicate-key error message, the server could improperly interpret the string, resulting in a crash. (Bug#38701)

  • A race condition between threads sometimes caused unallocated memory to be addressed. (Bug#38692)

  • 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, --start-and-exit started but did not exit. (Bug#38629)

  • Executing a light INSERT and UPDATE workload with falcon_index_chill_threshold set to 4K and falcon_record_chill_threshold set to to 4K, MySQL could crash. (Bug#38566)

  • A server crash resulted from execution of an UPDATE that used a derived table together with FLUSH TABLES. (Bug#38499)

  • Stored procedures involving substrings could crash the server on certain platforms due to invalid memory reads. (Bug#38469)

  • The binary log file name stored in the binlog_file column of the mysql.backup_history MySQL Backup table now is the file basename (the final component). Previously, the full path name was stored, but this could be too long for the column width. (Bug#38462)

  • On Windows, starting the server with the --external-locking=1 option caused BACKUP DATABASE to fail. (Bug#38342)

  • Inserting data into columns within a Falcon table that contains columns with names containing accented characters would cause the data to be null (empty). (Bug#38304)

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

  • Errors during server startup caused destruction of an uninitialized mutex and assertion failure. (Bug#37961)

  • The handlerton-to-plugin mapping implementation did not free handler plugin references when the plugin was uninstalled, resulting in a server crash after several install/uninstall cycles. Also, on Mac OS X, the server crashed when trying to access an EXAMPLE table after the EXAMPLE plugin was installed. (Bug#37958)

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

  • Access checks were skipped for SHOW PROCEDURE STATUS and SHOW FUNCTION STATUS, which could lead to a server crash or insufficient access checks in subsequent statements. (Bug#37908)

  • Comparisons could hang for SET or ENUM columns that used latin2_czech_cs collation. (Bug#37854)

  • It was possible to create a tasblespace using the name of one of the Falcon system tablespaces, FALCON_MASTER, FALCON_TEMPORARY, or FALCON_BACKLOG without an error message being raised. A suitable error is now produced when an attempt is made to create a table with the same name as a Falcon system tablespace. (Bug#37668)

  • SHOW PROCESSLIST displayed “copy to tmp table” when no such copy was occurring. (Bug#37550)

  • The <=> operator could return incorrect results when comparing NULL to DATE, TIME, or DATETIME values. (Bug#37526)

  • MySQL Backup was not consistently checking for BSTREAM_ERROR errors. (Bug#37522)

  • The combination of a subquery with a GROUP BY, an aggregate function calculated outside the subquery, and a GROUP BY on the outer SELECT could cause the server to crash. (Bug#37348)

  • Incorrect BLOB handling by RESTORE could result in a server crash. (Bug#37212)

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

  • If thread-pooling was used and a connection attempt was denied on the grounds of exceeding the user limits, the number of active connections for that user was erroneously decreased twice. The difference between the actual number connections and the internal count could then cause debug builds of the server to raise an assertion. (Bug#36970)

  • Long error messages for RESTORE could be truncated. (Bug#36854)

  • Running in strict mode, with a auto_increment_increment and auto_increment_offset set to a value larger than supportedf by the specified auto increment column within a Falcon table, a crash would occur. (Bug#36473)

  • In some cases, references to views were confused with references to anonymous tables and privilege checking was not performed. (Bug#36086)

  • For crash reports on Windows, symbol names in stack traces were not correctly resolved. (Bug#35987)

  • ALTER EVENT changed the PRESERVE attribute of an event even when PRESERVE was not specified in the statement. (Bug#35981)

  • Host name values in SQL statements were not being checked for '@', which is illegal according to RFC952. (Bug#35924)

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

  • With the PAD_CHAR_TO_FULL_LENGTH SQL mode enabled, a ucs2 CHAR column returned additional garbage after trailing space characters. (Bug#35720)

  • RESTORE did not set the validity_point_time, binlog_pos, and binlog_file fields of the backup_history log table row. (Bug#35240)

  • With binary logging enabled, CREATE TABLE ... SELECT and INSERT INTO ... SELECT failed if the source table was a log table. (Bug#34306)

  • If BACKUP DATABASE and RESTORE were done in a session with autocommit disabled, a later DROP TABLE or RESTORE in the same session failed. (Bug#34204)

  • The secure_file_priv system variable now applies to BACKUP DATABASE and RESTORE operations: If the value is nonempty, backup and restore operations can read and write files only in the given directory. (Bug#34171)

  • mysql_real_connect() did not check whether the MYSQL connection handler was already connected and connected again even if so. Now an CR_ALREADY_CONNECTED error occurs. (Bug#33831)

  • Shutting down the MySQL Server immediately following the execution of a BACKUP DATABASE statement caused the server to crash if the database to be backed up contained any Falcon tables. (Bug#33575)

  • The server crashed for BACKUP DATABASE if the backup progress tables in the mysql database were missing or created incorrectly. (Bug#33352)

  • CHECKSUM TABLE was not killable with KILL QUERY. (Bug#33146)

  • A trigger for an InnoDB table activating multiple times could lead to AUTO_INCREMENT gaps. (Bug#31612)

  • mysqldump could fail to dump views containing a large number of columns. (Bug#31434)

  • The server could improperly type user-defined variables used in the select list of a query. (Bug#26020)

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

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

C.1.6. Changes in MySQL 6.0.7 (29 September 2008)

Functionality added or changed:

  • Important Change: mysqlbinlog now supports --verbose and --base64-output=DECODE-ROWS options to display row events as commented SQL statements. (The default otherwise is to display row events encoded as base-64 strings using BINLOG statements.) See Section, “mysqlbinlog Row Event Display”. (Bug#31455)

  • Falcon builds on AMD64 platforms now. (Bug#38535)

  • mysqltest now installs signal handlers and generates a stack trace if it crashes. (Bug#37003)

  • A new system variable, backupdir, enables the default directory to be specified for BACKUP DATABASE and RESTORE operations when the image file path name is not a full path name. The default value for this variable is the data directory. (Bug#35230)

  • The mysql.online_backup and mysql.online_backup_progress tables now have a default character set of utf8 rather than latin1. (Bug#33836)

  • mysqltest was changed to be more robust in the case of a race condition that can occur for rapid disconnect/connect sequences with the server. The account used by mysqltest could reach its allowed simultaneous-sessions user limit if the connect attempt occurred before the server had fully processed the preceding disconnect. mysqltest now checks specificaly for a user-limits error when it connects; if that error occurs, it delays briefly before retrying. (Bug#23921)

  • Previously, BACKUP DATABASE did not back up privileges and RESTORE did not restore them. Now privileges for backed-up databases are saved. This includes privileges at the database level and below (table, column, routine). Global privileges are not saved. For additional information about how privileges are backed up, see Section 6.3.1, “Quick Guide to MySQL Backup”.

  • A new session system variable, backup_wait_timeout, controls the number of seconds a BACKUP DATABASE or RESTORE operation waits for a blocked DDL statements before aborting with an error.

  • The CREATE TABLESPACE privilege has been introduced. This privilege exists at the global (superuser) level and enables you to create, alter, and drop tablespaces and logfile groups.

  • Improvements made to MySQL Backup (the BACKUP DATABASE and RESTORE statements):

    • A native driver for the MyISAM storage engine is included. This results in faster times for backup and restore operations, although the size of backup image files is larger.

Bugs fixed:

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

    • Per-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.)

    • Process-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. (Bug#37226, Bug#33031)

  • Incompatible Change: Some performance problems of SHOW ENGINE INNODB STATUS were reduced by removing used cells and Total number of lock structs in row lock hash table from the output. Now these values are present only if the UNIV_DEBUG symbol is defined at MySQL build time. (Bug#36941, Bug#36942)

  • Important Change: The INFORMATION_SCHEMA.FALCON_TABLES table has been removed. (Bug#29211, Bug#34705, Bug#34706)

  • Partitioning: When a partitioned table had a TIMESTAMP column defined with CURRENT_TIMESTAMP as the default but with no ON UPDATE clause, the column's value was incorrectly set to CURRENT_TIMESTAMP when updating across partitions. (Bug#38272)

  • Partitioning: A LIST partitioned MyISAM table returned erroneous results when an index was present on a column in the WHERE clause and NOT IN was used on that column.

    Searches using the index were also much slower then if the index were not present. (Bug#35931)

  • Partitioning: SELECT COUNT(*) was not correct for some partitioned tables using a storage engine that did not support HA_STATS_RECORDS_IS_EXACT. Tables using the ARCHIVE storage engine were known to be affected.

    This was because ha_partition::records() was not implemented, and so the default handler::records() was used in its place. However, this is not correct behavior if the storage engine does not support HA_STATS_RECORDS_IS_EXACT.

    The solution was to implement ha_partition::records() as a wrapper around the underlying partition records.

    As a result of this fix, the rows column in the output of EXPLAIN PARTITIONS now includes the total number of records in the partitioned table. (Bug#35745)

  • Replication: Server code used in binary logging could in some cases be invoked even though binary logging was not actually enabled, leading to asserts and other server errors. (Bug#38798)

  • Replication: Row-based replication broke for utf8 CHAR columns longer than 85 characters. (Bug#37426)

  • Replication: When autocommit was set equal to 1 after starting a transaction, the binary log did not commit the outstanding transaction. The reason this happened was that the binary log commit function saw only the values of the new settings, and decided that there was nothing to commit.

    This issue was first observed when using the Falcon storage engine, but it is possible that it affected other storage engines as well. (Bug#37221)

  • Replication: Some kinds of internal errors, such as Out of memory errors, could cause the server to crash when replicating statements with user variables.

    certain internal errors. (Bug#37150)

  • Replication: Row-based replication did not correctly copy TIMESTAMP values from a big-endian storage engine to a little-endian storage engine. (Bug#37076)

  • Replication: The --replicate-*-table options were not evaluated correctly when replicating multi-table updates.

    As a result of this fix, replication of multi-table updates no longer fails when an update references a missing table but does not update any of its columns. (Bug#37051)

  • Replication: Performing an insert on a table having an AUTO_INCREMENT column and an INSERT trigger that was being replicated from a master running MySQL 5.0 or any version of MySQL 5.1 up to and including MySQL 5.1.11 to a slave running MySQL 5.1.12 or later caused the replication slave to crash. (Bug#36443)

    See also Bug#33029.

  • Multiple concurrent inserts to a Maria table could lead to a deadlock situation. (Bug#39363)

  • When renaming a Falcon table the corresponding indexes could become corrupt or unavailable. (Bug#39354)

  • When performing an online DROP INDEX on a Falcon table, the operation may conflict with other index operations such as including index scans. When one client drops an index, another client may initiate a concurrent index operation that accesses the mapping object of the index being dropped, and this can cause a crash. (Bug#39349, Bug#39350, Bug#39845, Bug#39846)

  • Explicitly running an online index operation on a Falcon table using ALTER ONLINE TABLE ... would fail with an error specifying that the specified operation was not supported. (Bug#39347)

  • Running LOAD DATA INFILE on a large source data into a Falcon table with millions of rows, a crash could occur. (Bug#39296)

  • Compiling Falcon on Solaris SPARC or x86 using the Sun Studio 12 compiler would lead to exceptions being disabled. Exceptions are required by Falcon and the build and binary would ultimately fail during execution. (Bug#39241)

  • Host name lookup failure could lead to a server crash. (Bug#39153)

  • When recovering from a serial log containing many CREATE TABLESPACE and DROP TABLESPACE statements, Falcon could lose data from tablespaces not referenced by these statements. (Bug#39138)

    See also Bug#39789.

  • When specifying an alternative log directory for FALCON using serial_log_directory the operation would fail silently if the directory did not exist. MySQL will now fail to start if the serial log in the specified directory cannot be opened or created, or if the falcon_master.fts cannot be opened or created. (Bug#39098, Bug#38377)

  • Falcon key pages were written to the serial log in the wrong order. This had the potential to cause problems if a failure of the server occurred during recovery. (Bug#39025)

  • Falcon could hang trying to perform an UPDATE in one transaction while waiting for another transaction to be committed or rolled back. (Bug#38947)

  • It was not possible to build the server with Falcon support on SPARC when using the Sun Studio compiler. (Bug#38891)

  • On Solaris platforms, when the server was built with Falcon support and the data directory set in user's home directory, mysql_install_db failed. (Bug#38843)

  • Falcon did not honor the --datadir option and created its files in the current directory instead. This error was apparent only when running the embedded version of MySQL. (Bug#38770)

  • When built with Falcon support on 64-bit SPARC platforms, mysqld hung on startup. This occurred whether Sun Studio or gcc was used to compile the server. (Bug#38766)

  • Falcon did not build on Linux with Valgrind enabled. (Bug#38746)

  • Performing a DELETE on a Maria table where the table has been locked using LOCK TABLE ... WRITE CONCURRENT would result in an assertion failure. (Bug#38606)

  • When using mysql_install_db on MySQL built with Sun Studio 12 with the --with-debug option enabled, the server would crash. (Bug#38594)

  • Server-side cursors were not initialized properly, which could cause a server crash. (Bug#38486)

  • A server crash or Valgrind warnings could result when a stored procedure selected from a view that referenced a function. (Bug#38291)

  • A failure to clean up binary log events was corrected (detected by Valgrind). (Bug#38290)

  • Queries containing a subquery with DISTINCT and ORDER BY could cause a server crash. (Bug#38191)

  • CREATE TABLESPACE failed when invoked immediately following a DROP TABLESPACE statement that used the same tablespace name. (Bug#38186, Bug#38743)

  • Over-aggressive lock acquisition by InnoDB when calculating free space for tablespaces could result in performance degradation when multiple threads were executing statements on multi-core machines. (Bug#38185)

  • The fix for Bug#20748 caused a problem such that on Unix, MySQL programs looked for options in ~/my.cnf rather than the standard location of ~/.my.cnf. (Bug#38180)

  • UUID() values could have hyphens in the wrong place. (Bug#38160)

  • Queries with a HAVING clause could return a spurious row. (Bug#38072)

  • MyISAM tables with non-ASCII characters in their names could not be backed up because the MyISAM native backup driver did not handle them properly. (Bug#38045)

  • Dropping and re-creating a Falcon table, then adding indexes to the re-created table, could cause spurious errors or possibly a crash of the server. (Bug#38039)

  • If the table definition cache contained tables with many BLOB columns, much memory could be allocated to caching BLOB values. Now a size limit on the cached BLOB values is enforced. (Bug#38002)

  • The server returned incorrect results for WHERE ... OR ... GROUP BY queries against InnoDB tables. (Bug#37977)

  • SUM(DISTINCT) and AVG(DISTINCT) for an empty result set in a subquery were not properly handled as being able to return NULL. (Bug#37891)

  • For InnoDB tables, ORDER BY ... DESC sometimes returned results in ascending order. (Bug#37830)

  • The server returned unexpected results if a right side of the NOT IN clause consisted of the NULL value and some constants of the same type. For example, this query might return 3, 4, 5, and so forth if a table contained those values:



  • Executing large numbers of SQL statements using LIMIT on Falcon tables eventually led to a crash of the server. (Bug#37726)

  • Setting the session value of the innodb_table_locks system variable caused a server crash. (Bug#37669)

  • Nesting of IF() inside of SUM() could cause an extreme server slowdown. (Bug#37662)

  • For BACKUP DATABASE, if the WITH COMPRESSION clause was not used, an uninitialized variable could cause unpredictable results. (Bug#37654)

  • Killing a query that used an EXISTS subquery as the argument to SUM() or AVG() caused a server crash. (Bug#37627)

  • mysqld failed to build using the Sun Studio compiler. (Bug#37603)

  • When using indexed ORDER BY sorting, incorrect query results could be produced if the optimizer switched from a covering index to a noncovering index. (Bug#37548)

  • After TRUNCATE TABLE for an InnoDB table, inserting explicit values into an AUTO_INCREMENT column could fail to increment the counter and result in a duplicate-key error for subsequent insertion of NULL. (Bug#37531)

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

  • The optimizer_switch system variable takes a comma-separated list of values, but only the first value in the list was used. (Bug#37120)

  • Executing ALTER TABLE ADD PARTITION followed by ALTER TABLE DROP PARTITION on a Falcon table, and then killing the thread performing these statements could cause the server to crash. (Bug#37072)

  • NOT IN subqueries that selected MIN() or MAX() values but produced an empty result could cause a server crash. (Bug#37004)

  • A server crash resulted from attempts at semi-join and materialization optimizations for subqueries with a parent of SELECT ... FROM DUAL. (Bug#36896)

  • Server crashed when starting a new BACKUP DATABASE or RESTORE statement while a BACKUP DATABASE or RESTORE was ongoing. (Bug#36795)

  • The CSV storage engine returned success even when it failed to open a table's data file. (Bug#36638)

  • SELECT DISTINCT from a simple view on an InnoDB table, where all selected columns belong to the same unique index key, returned incorrect results. (Bug#36632)

  • RESTORE could fail if the server on which the restore operation took place had enabled triggers or events. (Bug#36530)

  • The parser incorrectly allowed MySQL error code 0 to be specified for a condition handler. (This is incorrect because the condition must be a failure condition and 0 indicates success.) (Bug#36510)

  • CHAR(256 USING utf32) could generate a result with an incorrect length and result in a server crash. (Bug#36418)

  • If initialization of an INFORMATION_SCHEMA plugin failed, INSTALL PLUGIN freed some internal plugin data twice. (Bug#36399)

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

  • The server could crash with an assertion failure (or cause the client to get a “Packets out of order” error) when the expected query result was that it should terminate with a “Subquery returns more than 1 row” error. (Bug#36135)

  • Executing TRUNCATE statements with interleaving transactions could cause mysqld to crash. (Bug#35991)

    See also Bug#22165.

  • When using both an INSERT BEFORE trigger to create a row and AFTER INSERT trigger to delete the same row on a FALCON table, the record count as reported by SHOW TABLE STATUS could get out of sync with the actual record contents. This was caused by the changes now being correctly updated in the table status information. (Bug#35939)

  • Multiple threads executing repeated queries on the same Falcon table led eventually to a crash of the server. (Bug#35932, Bug#36410)

  • The UUID() function returned UUIDs with the wrong time; this was because the offset for the time part in UUIDs was miscalculated. (Bug#35848)

  • The configure script did not allow utf8_hungarian_ci to be specified as the default collation. (Bug#35808)

  • For CREATE TABLE, the parser did not enforce that parentheses were present in a CHECK (expr) clause; now it does. The parser did not enforce that CONSTRAINT [symbol] without a following CHECK clause was illegal; now it does. (Bug#35578, Bug#11714, Bug#38696)

  • Freeing of an internal parser stack during parsing of complex stored programs caused a server crash. (Bug#35577, Bug#37269, Bug#37228)

  • mysqlbinlog left temporary files on the disk after shutdown, leading to the pollution of the temporary directory, which eventually caused mysqlbinlog to fail. This caused problems in testing and other situations where mysqlbinlog might be invoked many times in a relatively short period of time. (Bug#35543)

  • The code for detecting a byte order mark (BOM) caused mysql to crash for empty input. (Bug#35480)

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

  • For uncorrelated subqueries without a WHERE clause, use of semi-join or materialization options could result in slow performance, or use of the LooseScan strategy could produce incorrect results. (Bug#35468)

  • CSV tables with CHAR columns caused BACKUP DATABASE to produce a server crash. (Bug#35117)

  • If a view depended on a base table that had been dropped, BACKUP DATABASE caused a server crash. (Bug#34902)

  • If a view was altered before backing up a database, BACKUP DATABASE caused a server crash. (Bug#34867)

  • Table checksum calculation could cause a server crash for FEDERATED tables with BLOB columns containing NULL values. (Bug#34779)

  • BACKUP DATABASE caused a server crash if it attempted to back up a view that depended on another view. (Bug#34758, Bug#35347)

  • A significant slowdown occurred when many SELECT statements that return many rows from InnoDB tables were running concurrently. (Bug#34409)

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

  • Changes to build files were made to enable the MySQL distribution to compile on Microsoft Visual C++ Express 2008. (Bug#33907)

  • Fast ALTER TABLE operations were not fast for columns that used multibyte character sets. (Bug#33873)

  • ORDER BY failed to take into account accents and lettercases in multi-level collations (latin2_czech_cs and cp1250_czech_cs). (Bug#33791, Bug#30462)

  • The internal functions my_getsystime(), my_micro_time(), and my_micro_time_and_time() did not work correctly on Windows. One symptom was that uniqueness of UUID() values could be compromised. (Bug#33748)

  • The SHOW FUNCTION CODE and SHOW PROCEDURE CODE statements are not present in nondebug builds, but attempting to use them resulted in a “syntax error” message. Now the error message indicates that the statements are disabled and that you must use a debug build. (Bug#33637)

  • If a large number of databases were named in the BACKUP DATABASE statement, the server crashed. (Bug#33568)

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

  • BACKUP DATABASE did not properly set the flags in the first two bytes of the backup image. (Bug#33120)

  • Unindexed ORDER BY did not work on short utf32 columns, or on utf16 columns with a short max_sort_length value. (Bug#33073)

  • BACKUP DATABASE followed by RESTORE could mangle object names if a nonstandard charset was used. (Bug#33023)

  • After an upgrade to MySQL 6.0.4 or higher, columns that used the old 3-byte Unicode utf8 character set are treated as having the utf8mb3 character set. mysql_upgrade did not convert all system tables in the mysql database to use the new 4-byte Unicode utf8 character set rather than utf8mb3. This caused problems such as that the event scheduler would not start. mysql_upgrade now performs the utf8mb3 to utf8 conversion for system tables. (Bug#33002, Bug#33053)

  • It was possible to insert invalid Unicode characters (with code point values greater than U+10FFFF) into utf8 and utf32 columns. (Bug#32914)

  • UNION constructs cannot contain SELECT ... INTO except in the final SELECT. However, if a UNION was used in a subquery and an INTO clause appeared in the top-level query, the parser interpreted it as having appeared in the UNION and raised an error. (Bug#32858)

  • Inserting CURRENT_TIME, CURRENT_DATE, or CURRENT_TIMESTAMP into a VARCHAR column didn't work for non-ASCII character sets such as ucs2, utf16, or utf32. (Bug#32390)

  • mysql_upgrade attempted to use the /proc file system even on systems that do not have it. (Bug#31605)

  • mysql_install_db failed if run with the default table type set to NDB. (Bug#31315)

  • Making INFORMATION_SCHEMA the default database caused the DROP TABLESPACE statement to be disabled. (Bug#31302)

  • Several MySQL programs could fail if the HOME environment variable had an empty value. (Bug#30394)

  • The Serbian translation for the ER_INCORRECT_GLOBAL_LOCAL_VAR error was corrected. (Bug#29738)

  • The BUILD/check-cpu build script failed if gcc had a different name (such as gcc.real on Debian). (Bug#27526)

  • ALTER TABLE could not be used to add columns to a table if the table had an index on a utf8 column with a TEXT data type. (Bug#26180)

  • The XPath boolean() function did not cast string and nodeset values correctly in some cases. It now returns TRUE for any nonempty string or nodeset and 0 for a NULL string, as specified in the XPath standard.. (Bug#26051)

  • Using ALTER TABLE with interleaving transactions could cause mysqld to crash. (Bug#22165)

  • The FLUSH PRIVILEGES statement did not produce an error when it failed. (Bug#21226)

  • After executing a prepared statement that accesses a stored function, the next execution would fail to find the function if the stored function cache was flushed in the meantime. (Bug#12093, Bug#21294)

  • perror did not work for errors described in the sql/share/errmsg.txt file. (Bug#10143)

C.1.7. Changes in MySQL 6.0.6 (11 August 2008)

Functionality added or changed:

  • Important Change: Incompatible Change: The FEDERATED storage engine is now disabled by default in binary distributions. The engine is still available and can be enabled by starting the server with the --federated option. (Bug#37069)

  • Incompatible Change: The engines column in the mysql.online_backup table has been renamed to drivers to better reflect its contents. (Bug#34965)

  • Incompatible Change: A change has been made to the way that the server handles prepared statements. This affects prepared statements processed at the SQL level (using the PREPARE statement) and those processed using the binary client-server protocol (using the mysql_stmt_prepare() C API function).

    Previously, changes to metadata of tables or views referred to in a prepared statement could cause a server crash when the statement was next executed, or perhaps an error at execute time with a crash occurring later. For example, this could happen after dropping a table and recreating it with a different definition.

    Now metadata changes to tables or views referred to by prepared statements are detected and cause automatic repreparation of the statement when it is next executed. Metadata changes occur for DDL statements such as those that create, drop, alter, rename, or truncate tables, or that analyze, optimize, or repair tables. Repreparation also occurs after referenced tables or views are flushed from the table definition cache, either implicitly to make room for new entries in the cache, or explicitly due to FLUSH TABLES.

    Repreparation is automatic, but to the extent that it occurs, performance of prepared statements is diminished.

    Table content changes (for example, with INSERT or UPDATE) do not cause repreparation, nor do SELECT statements.

    An incompatibility with previous versions of MySQL is that a prepared statement may now return a different set of columns or different column types from one execution to the next. For example, if the prepared statement is SELECT * FROM t1, altering t1 to contain a different number of columns causes the next execution to return a number of columns different from the previous execution.

    Older versions of the client library cannot handle this change in behavior. For applications that use prepared statements with the new server, an upgrade to the new client library is strongly recommended.

    Along with this change to statement repreparation, the default value of the table_definition_cache system variable has been increased from 128 to 256. The purpose of this increase is to lessen the chance that prepared statements will need repreparation due to referred-to tables/views having been flushed from the cache to make room for new entries.

    A new status variable, Com_stmt_reprepare, has been introduced to track the number of repreparations. (Bug#27420, Bug#27430, Bug#27690)

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

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

    • REPAIR TABLE without USE_FRM upgrades the .frm file to the current version.

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


  • Important Change: The Maria Storage Engine is now available as standard. Maria is a crash safe version of MyISAM. Maria supports all of the main functionality of the MyISAM engine, but includes recovery support (in the event of a system crash), full logging (including CREATE, DROP, RENAME, and TRUNCATE operations), all MyISAM row formats and a new Maria-specific row format. Maria is documented at Section 13.6, “The Maria Storage Engine”.

  • Important Note: When MySQL is built with the Maria engine, all internal temporary on disk tables will use the Maria engine. Using Maria temporary tables in plkace of MyISAM tables should result in a performance gain.

  • On Unix, it is now possible for the output file for BACKUP DATABASE to be an existing FIFO. (Bug#37012)

  • mysql_upgrade now has a --tmpdir option to enable the location of temporary files to be specified. (Bug#36469)

  • mysqldump now adds the LOCAL qualifier to the FLUSH TABLES statement that is sent to the server when the --master-data option is enabled. This prevents the FLUSH TABLES statement from replicating to slaves, which is disadvantageous because it would cause slaves to block while the statement executes. (Bug#35157)

    See also Bug#38303.

  • The use of the SQL_CACHE and SQL_NO_CACHE options in SELECT statements now is checked more restrictively: 1) Previously, both options could be given in the same statement. This is no longer true; only one can be given. 2) Previously, these options could be given in SELECT statements that were not at the top-level. This is no longer true; the options are disallowed in subqueries (including subqueries in the FROM clause, and SELECT statements in unions other than the first SELECT. (Bug#35020)

  • MySQL source distributions are now available in Zip format. (Bug#27742)

  • The undocumented, deprecated, and not useful SHOW COLUMN TYPES statement has been removed. (Bug#5299)

  • The server now supports a Debug Sync facility for thread synchronization during testing and debugging. To compile in this facility, configure MySQL with the --enable-debug-sync option. The debug_sync system variable provides the user interface Debug Sync. mysqld and support a --debug-sync-timeout option to enable the facility and set the default synchronization point timeout.

  • now supports a --mysqltest option for specifying options to the mysqltest program.

  • Several improvements were made to MySQL Backup (the BACKUP DATABASE and RESTORE statements):

    • Drivers are now included for storage engines that do not store any data or rely on other storage engines for data storage: MERGE, FEDERATED, BLACKHOLE, EXAMPLE.

    • The backup kernel better determines the dependency ordering of objects to be backed up so that they can be restored in the proper order.

    • Restored events and triggers are not reactivated until the restore operation completes.

  • BACKUP DATABASE now has a WITH COMPRESSION clause. This causes the image file to be compressed, which reduces its size. Compression also may result in improved backup time by reducing writes to disk.

  • When reading from FALCON tables, FALCON can take advantage of reading from the disk in larger blocks. When enabled, disk reads are in blocks of 64KB. When switched off, disk reads are based on the page size as set by falcon_page_size.

Bugs fixed:

  • Important Change: Security Fix: Additional corrections were made for the symlink-related privilege problem originally addressed in MySQL 6.0.5. 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.

  • 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: Access privileges for several statements are more accurately checked:


  • Incompatible Change: Certain characters were sorted incorrectly for the following collations: TILDE and GRAVE ACCENT in big5_chinese_ci; LATIN SMALL LETTER J in cp866_general_ci; TILDE in gb2312_chinese_ci; and TILDE in gbk_chinese_ci.

    As a result of this fix, any indexes on columns that use these collations and contain the affected characters must be rebuilt when upgrading to 6.0.6 or higher. To do this, use ALTER TABLE to drop and re-add the indexes, or mysqldump to dump the affected tables and mysql to reload the dump file. (Bug#25420)

  • Incompatible Change: An additional correction to the original MySQL 6.0.4 fix was made to normalize directory names before adding them to the list of directories. This prevents /etc/ and /etc from being considered different, for example. (Bug#20748)

    See also Bug#38180.

  • Important Change: Partitioning: The statements ANALYZE TABLE, CHECK TABLE, OPTIMIZE TABLE, and REPAIR TABLE are now supported for partitioned tables.

    Also as a result of this fix, the following statements which were disabled in MySQL 6.0.5 have been re-enabled:






    See also Bug#39434.

  • Important Change: Previously, Falcon failed silently when attempting to read incompatible datafiles created by an earlier version of the storage engine. Now, when Falcon encounters such datafiles, it refuses to start, and an appropriate error is issued instead. (Bug#35190)

  • Important Change: The server no longer issues warnings for truncation of excess spaces for values inserted into CHAR columns. This reverts a change in the previous release that caused warnings to be issued. (Bug#30059)

  • Partitioning: myisamchk failed with an assertion error when analyzing a partitioned MyISAM table. (Bug#37537)

  • Partitioning: When an attempt is made to change a table to an unsupported storage engine, the server normally uses the default storage engine in place of the requested engine while issuing a warning. However, if the table was partitioned, the same ALTER TABLE statement failed with the error, The mix of handlers in the partitions is not allowed in this version of MySQL. This happened even if the server was not running in NO_ENGINE_SUBSTITUTION mode. Now the behavior for partitioned tables is the same as for other MySQL tables; the substitution is made, and a warning is issued. (Bug#35765)

  • Partitioning: MyISAM recovery enabled with the --myisam-recover option did not work for partitioned MyISAM tables. (Bug#35161)

  • Partitioning: When one user was in the midst of a transaction on a partitioned table, a second user performing an ALTER TABLE on this table caused the server to hang. (Bug#34604)

  • Partitioning: Inserts failed on partitioned tables containing user-supplied values for an AUTO_INCREMENT column. (Bug#33479)

  • Partitioning: Partition-level TABLESPACE options were ignored for Falcon tables. (Bug#33404)

  • Partitioning: For InnoDB tables, there was a race condition involving the data dictionary and repartitioning. (Bug#33349)

  • Replication: CREATE PROCEDURE and CREATE FUNCTION statements containing extended comments were not written to the binary log correctly, causing parse errors on the slave. (Bug#36570)

    See also Bug#32575.

  • Replication: When flushing tables, there was a slight chance that the flush occurred between the processing of one table map event and the next. Since the tables were opened one by one, subsequent locking of tables would cause the slave to crash. This problem was observed when replicating NDBCLUSTER or InnoDB tables, when executing multi-table updates, and when a trigger or a stored routine performed an (additional) insert on a table so that two tables were effectively being inserted into in the same statement. (Bug#36197)

  • Replication: INSTALL PLUGIN and UNINSTALL PLUGIN caused row-based replication to fail.


    These statements are not replicated; however, when using row-based logging, the changes they introduce in the mysql system tables are written to the binary log.


  • Replication: CREATE VIEW statements containing extended comments were not written to the binary log correctly, causing parse errors on the slave. Now, all comments are stripped from such statements before being written to the binary log. (Bug#32575)

    See also Bug#36570.

  • The minimum page size accepted by FALCON has been increased from 1K to 2K. (Bug#39707)

  • Trying to execute a DDL statement on a Falcon table while a transaction was being rolled back could cause the server to crash. (Bug#38933)

  • When building FALCON using the Sun Studio 12 compiler, a requirement for the GNU Standard C++ (libstdc++) library would be added to the build requirements, causing the build to fail. (Bug#38556)

  • The Falcon memory manager did not always perform initialization of internal objects correctly. (Bug#38519)

    See also Bug#38770.

  • Disconnecting a session where you have a applied a WRITE CONCURRENT lock on Maria tables would lead to a crash. (Bug#38492)

  • Range queries on a Maria table could fail to return the correct rows. (Bug#38466)

  • The Windows my-template.ini template file contained a reference to the myisam_max_extra_sort_file_size system variable, which no longer exists, causing the installed server to fail upon startup. (Bug#38371)

  • Incorrect handling of aggregate functions when loose index scan was used caused a server crash. (Bug#38195)

  • The fix for Bug#33812 had the side effect of causing the mysql client not to be able to read some dump files produced with mysqldump. To address this, that fix was reverted. (Bug#38158)

  • The MyISAM backup driver was subject to a race condition that allowed multiple RESTORE operations to occur simultaneously. This could result in locking conflicts, incorrect entries in the progress tables, or other problems. (Bug#38108)

  • Concurrent adding or dropping of indexes and execution of DML statements on a Falcon table could cause the server to crash. (Bug#38044)

  • Executing ALTER TABLE and DML statements concurrently on Falcon tables could cause the server to hang. (Bug#38043)

  • ALTER TABLE ... ADD KEY and ALTER TABLE ... DROP KEY were not always handled correctly for Falcon tables, resulting in spurious duplicate key and other errors. (Bug#38041)

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

  • MySQL server binaries built using gcc4.3 could crash when running large numbers of DML statements on Falcon tables. (Bug#37725)

  • When building FALCON using the Sun Studio 12 compiler on OpenSolaris the build would fail due to a missing header file, Interlock.h. (Bug#37679)

  • Building MySQL with SSL and Falcon enabled would lead to a build failure. (Bug#37517)

  • A large number of updates on a Falcon table followed by a query of the form SELECT AVG(int_non_key_column) FROM table WHERE int_non_key_column < constant GROUP BY int_key_column LIMIT limit could crash the server. (Bug#37344)

  • Queries with complex conditions in the WHERE clause on Falcon tables when falcon_page_size was set to a low value could cause the server to crash. (Bug#37343)

  • Within stored programs or prepared statements, REGEXP could return incorrect results due to improper initialization. (Bug#37337)

  • When running a concurrent scenario involving transactions, each executing a small number of DELETE and UPDATE operations on a small number of records on FALCON tables, a deadlock could occur. (Bug#37251)

  • When performing operations on a table in one client while a different client is performing a TRUNCATE operation on the same FALCON table a deadlock could be introduced. (Bug#37080)

  • The falcon_max_transaction_backlog has been removed. The option was originally introduced to ensure that the backlog of transactions did not exceed a certain level with the gopher thread. FALCON now uses multiple gopher threads. The transaction backlog is handled internally by FALCON. (Bug#36991)

  • The falcon_initial_allocation has been removed. The option created new tablespace files with the specified size to force allocation on disk of specified block of contiguous space. The option had little effect on the performance of the tablespace files, and has therefore been removed. (Bug#36990)

  • The falcon_index_chill_threshold and falcon_record_chill_threshold options have been modified so that the specification for the size can be specified in bytes, and support the KB, MB, and GB modifiers. (Bug#36825)

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

  • If the length of a field was 3, internal InnoDB to integer type conversion didn't work on big-endian machines in the row_search_autoinc_column() function. (Bug#36793)

  • For a view that referred to a MyISAM table, the contents of the table could be empty after BACKUP DATABASE followed by RESTORE. (Bug#36782)

  • Data loss could be caused by attempts to read data from a database being restored by a RESTORE operation. (Bug#36778)

  • Some warnings were being reported as errors. (Bug#36777)

  • Data loss could be caused by activation of a trigger for a MyISAM table being restored by a RESTORE operation. (Bug#36749)

  • mysql_install_db from a Falcon-enabled build crashed on Solaris/SPARC. (Bug#36745)

  • On Windows 64-bit systems, temporary variables of long types were used to store ulong values, causing key cache initialization to receive distorted parameters. The effect was that setting key_buffer_size to values of 2GB or more caused memory exhaustion to due allocation of too much memory. (Bug#36705)

  • Multiple-table UPDATE statements that used a temporary table could fail to update all qualifying rows or fail with a spurious duplicate-key error. (Bug#36676)

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

  • The online backup stream library failed to parse the backup stream on 64-bit systems. (Bug#36624)

  • FALCON would try to open a number of files during startup that are not required by the MySQL storage engine implmentation. These operations have been removed. (Bug#36620)

  • On 64-bit platforms, BACKUP DATABASE hung for backups of more than 32KB. (Bug#36586)

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

  • A REGEXP match could return incorrect rows when the previous row matched the expression and used CONCAT() with an empty string. (Bug#36488)

  • The server could not be compiled with Falcon support on Solaris/x86. (Bug#36486)

  • mysqltest ignored the value of --tmpdir in one place. (Bug#36465)

  • The ER_TRUNCATED_WRONG_VALUE warning condition was sometimes raised as an error. (Bug#36457)

  • When one MySQL client application committed a transaction affecting a Falcon table at the same time that another client dropped this table, the DROP TABLE statement did not “see” that transaction. This led to a situation such that a row affected by the transaction was later accessed in a manner that referred to the deleted table, resulting in a crash of the server. (Bug#36438)

  • was incorrectly installed in the lib/mysql directory rather than in lib/mysql/plugin. (Bug#36434)

  • Compiling the server with Falcon support failed on Solaris 10 due to problems with DTrace. This occurred even when the build was configured using --disable-dtrace. (Bug#36403)

  • Compiling the server with Falcon support failed on Solaris 10 for x86 platforms failed due to use of assembler code specific to gcc. (Bug#36400)

  • Dropping a Falcon tablespace concurrently with dropping a table using that tablespace caused the server to crash. (Bug#36396)

  • Attempting to compile the server with Falcon support using the Sun Studio 12 compiler failed with the error "Value.h", line 185: Error: A union member cannot have a user-defined assignment operator. (Bug#36368)

  • The default drivers for BACKUP DATABASE and RESTORE now support a cancel operation, which also allows better cleanup if a driver error occurs. (Bug#36323)

  • The server crashed while parsing large floating-point numbers such as 1e37 or -1e15. (Bug#36320)

  • When updating an existing instance (for example, from MySQL 5.0 to 5.1, or 5.1 to 6.0), the Instance Configuration Wizard unnecessarily prompted for a root password when there was an existing root password. (Bug#36305)

  • Following a number of INSERT ... SELECT statements on a Falcon table, creating a second Falcon table using the same tablespace as the table into which the inserts were made and then performing a simple INSERT on the new table caused the server to crash. (Bug#36294, Bug#36367)

    See also Bug#29648.

  • For InnoDB tables, the DATA_FREE column of the INFORMATION_SCHEMA.TABLES displayed free space in kilobytes rather than bytes. Now it displays bytes. (Bug#36278)

  • BACKUP DATABASE failed to back up views that depend on tables in a different database. (Bug#36265)

  • The project files created for Windows were missing the GenError project dependency. (Bug#36257)

  • The mysql client failed to recognize comment lines consisting of -- followed by a newline. (Bug#36244)

  • CREATE INDEX for InnoDB tables could under very rare circumstances cause the server to crash.. (Bug#36169)

  • A read past the end of the string could occur while parsing the value of the --innodb-data-file-path option. (Bug#36149)

  • Conversion of a FLOAT ZEROFILL value to string could cause a server crash if the value was NULL. (Bug#36139)

  • The combination of semi-join and materialization both being enabled could lead to assertion failure during subquery processing. (Bug#36137)

  • Range optimizer evaluation of IN subqueries to be handled with the materialization strategy could lead to assertion failure. (Bug#36133)

  • A server crash could occur during the cleanup phase of subquery execution. (Bug#36128)

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

  • A SELECT ... LIKE query issued following a number of INSERT statements on a Falcon table failed to return all matching records. (Bug#36097)

  • mysqltest was performing escape processing for the --replace_result command, which it should not have been. (Bug#36041)

  • An error in calculation of the precision of zero-length items (such as NULL) caused a server crash for queries that employed temporary tables. (Bug#36023)

  • For EXPLAIN EXTENDED, execution of an uncorrelated IN subquery caused a crash if the subquery required a temporary table for its execution. (Bug#36011)

  • The MERGE storage engine did a table scan for SELECT COUNT(*) statements when it could calculate the number of records from the underlying tables. (Bug#36006)

  • The server crashed inside NOT IN subqueries with an impossible WHERE or HAVING clause, such as NOT IN (SELECT ... FROM t1, t2, ... WHERE 0). (Bug#36005)

  • mysql_stmt_prepare() did not reset the list of messages (those messages available via SHOW WARNINGS). (Bug#36004)

  • The Event Scheduler was not designed to work under the embedded server. It is now disabled for the embedded server, and the event_scheduler system variable is not displayed. (Bug#35997)

  • Grouping or ordering of long values in unindexed BLOB or TEXT columns with the gbk or big5 character set crashed the server. (Bug#35993)

  • SET GLOBAL debug='' resulted in a Valgrind warning in DbugParse(), which was reading beyond the end of the control string. (Bug#35986)

  • If a SELECT table list contained at least one INFORMATION_SCHEMA table, the required privileges for accessing the other tables were reduced. (Bug#35955)

  • Some syntactically invalid statements could cause the server to return an error message containing garbage characters. (Bug#35936)

  • MySQL could not be built using Sun Studio due to the use of compiler options specific to gcc. (Bug#35929)

  • The “prefer full scan on clustered primary key over full scan of any secondary key” optimizer rule introduced by Bug#26447 caused a performance regression for some queries, so it has been disabled. (Bug#35850)

  • The server ignored any covering index used for ref access of a table in a query with ORDER BY if this index was incompatible with the ORDER BY list and there was another covering index compatible with this list. As a result, suboptimal execution plans were chosen for some queries that used an ORDER BY clause. (Bug#35844)

  • mysql_upgrade did not properly update the mysql.event table. (Bug#35824)

  • The current system time (as returned by NOW() or synonyms) became constant after a RESTORE operation. (Bug#35806)

  • Processing of an uncorrelated subquery using semi-join could cause incorrect results or a server crash. (Bug#35767)

  • An incorrect error and message was produced for attempts to create a MyISAM table with an index (.MYI) file name that was already in use by some other MyISAM table that was open at the same time. For example, this might happen if you use the same value of the INDEX DIRECTORY table option for tables belonging to different databases. (Bug#35733)

  • Enabling the read_only system variable while autocommit mode was enabled caused SELECT statements for transactional storage engines to fail. (Bug#35732)

  • The range optimizer ignored conditions on inner tables in semi-join IN subqueries, causing the optimizer to miss good query execution plans. (Bug#35674)

  • An empty bit-string literal (b'') caused a server crash. Now the value is parsed as an empty bit value (which is treated as an empty string in string context or 0 in numeric context). (Bug#35658)

  • On 64-bit systems, assigning values of 2 63 – 1 or larger to key_buffer_size caused memory overruns. (Bug#35616)

  • For InnoDB tables, REPLACE statements used “traditional” style locking, regardless of the setting of innodb_autoinc_lock_mode. Now REPLACE works the same way as “simple inserts” instead of using the old locking algorithm. (REPLACE statements are treated in the same way as as INSERT statements.) (Bug#35602)

  • Different invocations of CHECKSUM TABLE could return different results for a table containing columns with spatial data types. (Bug#35570)

  • A semi-join subquery in the ON clause in the absence of a WHERE clause caused a server crash. (Bug#35550)

  • InnoDB was not updating the Handler_delete or Handler_update status variables. (Bug#35537)

  • The method for enumerating view dependencies could cause the server to deadlock. (Bug#35395)

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

  • Simultaneous inserts and updates on an updateable view referencing a Falcon table could sometimes cause duplicate key errors. (Bug#35322)

  • The combination of GROUP_CONCAT(), DISTINCT, and LEFT JOIN could crash the server when the right table is empty. (Bug#35298)

  • Accessing a MERGE table with an empty underlying table list incorrectly resulted in a “wrong index” error message rather than “end of file.” (Bug#35274)

  • BACKUP DATABASE caused a server crash upon encountering a table row that has been marked for deletion but not removed. (Bug#35249)

  • For InnoDB tables, ALTER TABLE DROP failed if the name of the column to be dropped began with “foreign”. (Bug#35220)

  • The table pullout strategy was not reflected in EXPLAIN EXTENDED output if not all of the subquery tables were pulled out. (Bug#35160)

  • Access-denied messages for INFORMATION_SCHEMA incorrectly showed the name of the default database instead. (Bug#35096)

  • Passing an invalid parameter to CHAR() in an ORDER BY clause caused the server to hang. (Bug#34949)

  • Some binaries produced stack corruption messages due to being built with versions of bison older than 2.1. Builds are now created using bison 2.3. (Bug#34926)

  • Concurrent execution of FLUSH TABLES along with SHOW FUNCTION STATUS or SHOW PROCEDURE STATUS could cause a server crash. (Bug#34895)

  • Creating a new Falcon table using CREATE TABLE ... SELECT where the table uses a primary key, and rows contain duplicate keys, could lead to a table being created but not populated. Because the pending (bad) record was not committed, the table remains in a state that means it cannot be dropped or recreated. (Bug#34892)

  • The log_output system variable could be set to an illegal value. (Bug#34820)

  • A server crash or memory overrun could occur with a dependent subquery and joins. (Bug#34799)

  • An assertion could be raised when the dependencies on a transaction could not be released after a specified time when using FALCON tables. (Bug#34602)

  • InnoDB could crash if overflow occurred for an AUTO_INCREMENT column. (Bug#34335)

  • On Windows 64-bit builds, an apparent compiler bug caused memory overruns for code in innobase/mem/*. Removed optimizations so as not to trigger this problem. (Bug#34297)

  • Several additional configuration scripts in the BUILD directory now are included in source distributions. These may be useful for users who wish to build MySQL from source. (See Section 2.9.3, “Installing from the Development Source Tree”, for information about what they do.) (Bug#34291)

  • For InnoDB tables, loss of data resulted from performing inserts concurrently with a RESTORE operation. (Bug#34210)

  • In some cases, concurrent INSERT and DELETE statements on the same Falcon table could cause the server to crash, due to a failure to find a record that should have been in the table. (Bug#33933)

  • A number of problems in new subquery optimization code meant that MySQL could pick an incorrect query plan when using InsideOut and/or FirstMatch subquery optimizations, which in turn would cause wrong query results. (Bug#33743)

  • If CREATE TABLE or ALTER TABLE of a Falcon table failed, it was not possible to create another table in the same database having the same name unless the server was restarted. In some cases, subsequent CREATE TABLE statements could cause the server to crash. (Bug#33723)

  • Attempts to access a FEDERATED table using a nonexistent server did not reliably return a proper error. (Bug#33702)

  • It was possible for multiple mysqld instances to use the same Falcon tablespace and metadata files, which could lead to corruption of the tablespace files, metadata files, or both. (Bug#33607)

  • TIMESTAMP columns were restored to the current date and time (not their actual values) by a RESTORE operation. (Bug#33573)

  • Use of 61 nested subqueries caused a server crash. (Bug#33509)

  • An ALTER TABLE ... TABLESPACE statement referencing a nonexistant tablespace on a Falcon table failed with an inappropriate error message the first time it was executed. A second attempt to execute the statement led to a crash of the MySQL server. (Bug#33397)

  • Executing a FLUSH PRIVILEGES statement after creating a temporary table in the mysql database with the same name as one of the MySQL system tables caused the server to crash.


    While it is possible to shadow a system table in this way, the temporary table exists only for the current user and connection, and does not effect any user privileges.


  • Selecting from a view that referenced the same table in the FROM clause and an IN clause caused a server crash. (Bug#33245)

  • When creating a new tablespace and specifying the name of an existing tablespace file, an incorrect error message would be reported specifying that the tablespace already existed. The error message has been updated to reflect the actual error. (Bug#33213)

  • There was a race condition between the event scheduler and the server shutdown thread. (Bug#32771)

  • Assignment of relative path names to general_log_file or slow_query_log_file did not always work. (Bug#32748)

  • Deeply nested subqueries could cause stack overflow or a server crash. (Bug#32680)

  • Query results from a FEDERATED table were corrupt if the query included an ORDER BY on a TEXT column. (Bug#32426)

  • Conversion of binary values to multi-byte character sets could fail to left-pad values to the correct length. This could result in a server crash. (Bug#32394)

  • On all x86 platforms, the default was to attempt to build the server with the Falcon storage engine, even if Falcon was not supported for a given platform. (Bug#32287)

  • Killing a statement that invoked a stored function could return an incorrect error message indicating table corruption rather than that the statement had been interrupted. (Bug#32140)

  • Occurrence of an error within a stored routine did not always cause immediate statement termination. (Bug#31881)

  • For DROP FUNCTION db_name.func_name (that is, when the function name is qualified with the database name), the statement should apply only to a stored function named func_name in the given database. However, if a UDF with the same name existed, the statement dropped the UDF instead. (Bug#31767)

  • On NetWare, mysql_install_db could appear to execute normally even if it failed to create the initial databases. (Bug#30129)

  • A problem related to HP-UX compilers that caused incorrect WEIGHT_STRING() results was fixed. (Bug#29825)

  • TRUNCATE TABLE for InnoDB tables returned a count showing too many rows affected. Now the statement returns 0 for InnoDB tables. (Bug#29507)

  • InnoDB could return an incorrect rows-updated value for UPDATE statements. (Bug#29157)

  • The mysql.servers table was not created during installation on Windows. (Bug#28680, Bug#32797)

  • The jp test suite was not working. (Bug#28563)

  • The internal init_time() library function was renamed to my_init_time() to avoid conflicts with external libraries. (Bug#26294)

  • In some cases, the parser interpreted the ; character as the end of input and misinterpreted stored program definitions. (Bug#26030)

  • Statements to create, alter, or drop a view were not waiting for completion of statements that were using the view, which led to incorrect sequences of statements in the binary log when statement-based logging was enabled. (Bug#25144)

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

  • InnoDB exhibited thread thrashing with more than 50 concurrent connections under an update-intensive workload. (Bug#22868)

  • DROP DATABASE did not drop orphaned FOREIGN KEY constraints. (Bug#18942)

  • Delayed-insert threads were counted as connected but not as created, incorrectly leading to a Threads_connected value greater than the Threads_created value. (Bug#17954)

  • The parser used signed rather than unsigned values in some cases that caused legal lengths in column declarations to be rejected. (Bug#15776)

  • Stored procedure exception handlers were catching fatal errors (such as out of memory errors), which could cause execution not to stop to due a continue handler. Now fatal errors are not caught by exception handlers and a fatal error is returned to the client. (Bug#15192)

  • On Windows, moving an InnoDB .ibd file and then symlinking to it in the database directory using a .sym file caused a server crash. (Bug#11894)

  • If a connection was waiting for a GET_LOCK() lock or a SLEEP() call, and the connection aborted, the server did not detect this and thus did not close the connection. This caused a waste of system resources allocated to dead connections. Now the server checks such a connection every five seconds to see whether it has been aborted. If so, the connection is killed (and any lock request is aborted). (Bug#10374)

C.1.8. Changes in MySQL 6.0.5 (12 June 2008)

Functionality added or changed:

  • Performance: The performance of internal functions that trim multiple spaces from strings when comparing them has been improved. (Bug#14637)

  • Incompatible Change: In MySQL 5.1.6, when log tables were implemented, the default log destination for the general query and slow query log was TABLE. This default has been changed to FILE, which is compatible with MySQL 5.0, but incompatible with earlier releases of MySQL 5.1 from 5.1.6 to 5.1.20. If you are upgrading from MySQL 5.0 to 5.1.21 or higher, no logging option changes should be necessary. However, if you are upgrading from 5.1.6 through 5.1.20 to 5.1.21 or higher and were using TABLE logging, use the --log-output=TABLE option explicitly to preserve your server's table-logging behavior.

    In MySQL 5.1.x, this bug was addressed twice because it turned out that the default was set in two places, only one of which was fixed the first time. (Bug#29993)

  • Incompatible Change: The server now includes dtoa, a library for conversion between strings and numbers by David M. Gay. In MySQL, this library provides the basis for improved conversion between string or DECIMAL values and approximate-value (FLOAT/DOUBLE) numbers:

    • Consistent conversion results across platforms, which eliminates, for example, Unix versus Windows conversion differences.

    • Accurate representation of values in cases where results previously did not provide sufficient precision, such as for values close to IEEE limits.

    • Conversion of numbers to string format with the best possible precision. The precision of dtoa is always the same or bettter than that of the standard C library functions.

    Because the conversions produced by this library differ in some cases from previous results, the potential exists for incompatibilities in applications that rely on previous results. For example, applications that depend on a specific exact result from previous conversions might need adjustment to accommodate additional precision.

    For additional information about the properties of dtoa conversions, see Section 11.2.2, “Type Conversion in Expression Evaluation”.

    See also Bug#12860, Bug#21497, Bug#26788, Bug#24541, Bug#34015.

  • Important Change: MySQL Cluster: Packaging: Beginning with this release, standard MySQL 6.0 binaries are no longer built with support for the NDBCLUSTER storage engine, and the NDBCLUSTER code included in 6.0 mainline sources is no longer guaranteed to be maintained or supported. Those using MySQL Cluster in MySQL 6.0.4 and earlier MySQL 6.0 mainline releases should upgrade to MySQL Cluster NDB 6.2.15 or a later MySQL Cluster NDB 6.2 or 6.3 release. (Bug#36193)

  • Important Change: Added a ROUTINE_TYPE column to the INFORMATION_SCHEMA.PARAMETERS table, to make it possible to distinguish like-named parameters of stored routines and stored functions having the same names. See Section 19.27, “The INFORMATION_SCHEMA PARAMETERS Table”, for more information. (Bug#33106)

  • Replication: Introduced the slave_exec_mode system variable to control whether idempotent or strict mode is used for replication conflict resolution. Idempotent mode suppresses duplicate-key, no-key-found, and some other errors, and is needed for circular replication, multi-master replication, and some other complex replication setups when using MySQL Cluster. Strict mode is the default. (Bug#31609)

  • Replication: When running the server with --binlog-format=MIXED or --binlog-format=STATEMENT, a query that referred to a system variable used the slave's value when replayed on the slave. This meant that, if the value of a system variable was inserted into a table, the slave differed from the master. Now, statements that refer to a system variable are marked as “unsafe”, which means that:


    See also Bug#34732.

  • In the INFORMATION_SCHEMA database, the FALCON_DATABASE_IO table was renamed to FALCON_TABLESPACE_IO. (Bug#35490)

  • For boolean options, the option-processing library now prints additional information in the --help message: If the option is enabled by default, the message says so and indicates that the --skip form of the option disables the option. This affects all compiled MySQL programs that use the library. (Bug#35224)

  • The PROCESS privilege now is required to start or stop the InnoDB monitor tables (see Section, “SHOW ENGINE INNODB STATUS and the InnoDB Monitors”). Previously, no privilege was required. (Bug#34053)

  • For binary .tar.gz packages, mysqld and other binaries now are compiled with debugging symbols included to enable easier use with a debugger. If you do not need debugging symbols and are short on disk space, you can use strip to remove the symbols from the binaries. (Bug#33252)

  • mysqldump information at the top of the output now shows the same information as mysqldump invoked with the -V option, namely the mysqldump version number, the MySQL server version, and the distribution. (Bug#32350)

  • Several undocumented C API functions were removed: mysql_manager_close(), mysql_manager_command(), mysql_manager_connect(), mysql_manager_fetch_line(), mysql_manager_init(), mysql_disable_reads_from_master(), mysql_disable_rpl_parse(), mysql_enable_reads_from_master(), mysql_enable_rpl_parse(), mysql_master_query(), mysql_master_send_query(), mysql_reads_from_master_enabled(), mysql_rpl_parse_enabled(), mysql_rpl_probe(), mysql_rpl_query_type(), mysql_set_master(), mysql_slave_query(), and mysql_slave_send_query(). (Bug#31952, Bug#31954)

  • Formerly, when the MySQL server crashed, the generated stack dump was numeric and required external tools to properly resolve the names of functions. This is not very helpful to users having a limited knowledge of debugging techniques. In addition, the generated stack trace contained only the names of functions and was formatted differently for each platform due to different stack layouts.

    Now it is possible to take advantage of newer versions of the GNU C Library provide a set of functions to obtain and manipulate stack traces from within the program. On systems that use the ELF binary format, the stack trace contains important information such as the shared object where the call was generated, an offset into the function, and the actual return address. Having the function name also makes possible the name demangling of C++ functions.

    The library generates meaningful stack traces on the following platforms: i386, x86_64, PowerPC, IA64, Alpha, and S390. On other platforms, a numeric stack trace is still produced, and the use of the resolve_stack_dump utility is still required. (Bug#31891)

  • mysqltest now has mkdir and rmdir commands for creating and removing directories. (Bug#31004)

  • The LAST_EXECUTED column of the INFORMATION_SCHEMA.EVENTS table now indicates when the event started executing rather than when it finished executing. As a result, the ENDS column is never less than LAST_EXECUTED. (Bug#29830)

  • The mysql_odbc_escape_string() C API function has been removed. It has multi-byte character escaping issues, doesn't honor the NO_BACKSLASH_ESCAPES SQL mode and is not needed anymore by Connector/ODBC as of 3.51.17. (Bug#29592)

  • The server uses less memory when loading privileges containing table grants. (Patch provided by Google.) (Bug#25175)

  • Added the Uptime_since_flush_status status variable, which indicates the number of seconds since the most recent FLUSH STATUS statement. (Community contribution by Jeremy Cole) (Bug#24822)

  • Added the SHOW PROFILES and SHOW PROFILE statements to display statement profile data, and the accompanying INFORMATION_SCHEMA.PROFILING table. Profiling is controlled via the profiling and profiling_history_size session variables. see Section, “SHOW PROFILES Syntax”, and Section 19.28, “The INFORMATION_SCHEMA PROFILING Table”. (Community contribution by Jeremy Cole)

    The profiling feature is enabled via the --enable-community-features and --enable-profiling options to configure. These options are enabled by default; to disable them, use --disable-community-features and --disable-profiling. (Bug#24795)

  • Added the SHA2() function, which calculates the SHA-2 family of hash functions (SHA-224, SHA-256, SHA-384, and SHA-512). (Contributed by Bill Karwin) (Bug#13174)

  • The new read-only global system variables report_host, report_password, report_port, and report_user system variables provide runtime access to the values of the corresponding --report-host, --report-password, --report-port, and --report-user options.

  • Formerly it was possible to specify an innodb_flush_method value of fdatasync to obtain the default flush behavior of using fdatasync() for flushing. This is no longer possible because it can be confusing that a value of fdatasync causes use of fsync() rather than fdatasync().

  • The use of InnoDB hash indexes now can be controlled by setting the new innodb_adaptive_hash_index system variable at server startup. By default, this variable is enabled. See Section, “Adaptive Hash Indexes”.

  • The argument for the --do-test and --skip-test options is now interpreted as a Perl regular expression if there is a pattern metacharacter in the argument value. This allows more flexible specification of which tests to perform or skip.

  • The Instance Manager (mysqlmanager) has been discontinued and is no longer provided in MySQL releases.

  • For Falcon, supernodes have been added to index pages. Supernodes are an array of 16 vectors into each index page to keys that are fully expanded with noprefix compression. This allows the page to be searched quicker using a binary search of supernode keys followed by the normal sequential search. Without enabling supernodes, the whole page has to be searched sequentially.

  • Two new statements, BACKUP DATABASE and RESTORE, have been added for backup and restore operations. See Section 6.3, “Using MySQL Backup”.

Bugs fixed:

  • Performance: InnoDB adaptive hash latches could be held too long during filesort operations, resulting in a server crash. Now the hash latch is released when a query on InnoDB tables performs a filesort. This eliminates the crash and may provide significant performance improvements on systems on which many queries using filesorts with temporary tables are being performed. (Bug#32149)

  • Important Change: Security Fix: It was possible to circumvent privileges through the creation of MyISAM tables employing the DATA DIRECTORY and INDEX DIRECTORY options to overwrite existing table files in the MySQL data directory. Use of the MySQL data directory in DATA DIRECTORY and INDEX DIRECTORY is now disallowed. This is now also true of these options when used with partitioned tables and individual partitions of such tables.


    Additional fixes were made in MySQL 6.0.6.

    (Bug#32167, CVE-2008-2079)

    See also Bug#39277.

  • Security Fix: A client that connects to a malicious server could be tricked by the server into sending files from the client host to the server. This occurs because the libmysqlclient client library would respond to a FETCH LOCAL FILE request from the server even if the request is sent for statements from the client other than LOAD DATA LOCAL INFILE. The client library has been modified to respond to a FETCH LOCAL FILE request from the server only if is is sent in response to a LOAD DATA LOCAL INFILE statement from the client.

    The client library now also checks whether CLIENT_LOCAL_FILE is set and refuses to send a local file if not.


    Binary distributions ship with the local-infile capability enabled. Applications that do not use this functionality should disable it to be safe.


  • Important Change: Security Enhancement: On Windows Vista and Windows Server 2008, a user without administrative privileges does not have write permissions to the Program Files directory where MySQL and the associated data files are normally installed. Using data files located in the standard Program Files installation directory could therefore cause MySQL to fail, or lead to potential security issues in an installed instance.

    To address the problem, on Windows XP, Windows Vista and Windows Server 2008, the datafiles and data file configuration are now set to the Microsoft recommended AppData folder. The AppData folder is typically located within the user's home directory.


    When upgrading an existing 5.1.23 or 6.0.4 installation of MySQL you must take a backup of your data and configuration file (my.ini before installing the new version. To migrate your data, either extract the data and re-import (using mysqldump, then upgrade and re-import using mysql), or back up your data, upgrade to the new version, and copy your existing data files from your old datadir directory to the new directory located within AppData.

    Failure to back up your data and follow these procedures may lead to data loss.


  • Security Enhancement: It was possible to force an error message of excessive length which could lead to a buffer overflow. This has been made no longer possible as a security precaution. (Bug#32707)

  • Incompatible Change: In MySQL 5.1.23, the last_errno and last_error members of the NET structure in mysql_com.h were renamed to client_last_errno and client_last_error. This was found to cause problems for connectors that use the internal NET structure for error handling. The change has been reverted. (Bug#34655)

    See also Bug#12713.

  • Incompatible Change: The parser accepted illegal syntax in a FOREIGN KEY clause:

    • Multiple MATCH clauses.

    • Multiple ON DELETE clauses.

    • Multiple ON UPDATE clauses.

    • MATCH clauses specified after ON UPDATE or ON DELETE. In case of multiple redundant clauses, this leads to confusion, and implementation-dependent results.

    These illegal syntaxes are now properly rejected. Existing applications that used them will require adjustment. (Bug#34455)

  • Incompatible Change: It was possible to use FRAC_SECOND as a synonym for MICROSECOND with DATE_ADD(), DATE_SUB(), and INTERVAL; now, using FRAC_SECOND with anything other than TIMESTAMPADD() or TIMESTAMPDIFF() produces a syntax error.

    It is now possible (and preferable) to use MICROSECOND with TIMESTAMPADD() and TIMESTAMPDIFF(), and FRAC_SECOND is now deprecated. (Bug#33834)

  • Incompatible Change: The UPDATE statement allowed NULL to be assigned to NOT NULL columns (the implicit default value for the column data type was assigned). This was changed so that on error occurs.

    This change was reverted, because the original report was determined not to be a bug: Assigning NULL to a NOT NULL column in an UPDATE statement should produce an error only in strict SQL mode and set the column to the implicit default with a warning otherwise, which was the original behavior. See Section 10.1.4, “Data Type Default Values”, and Bug#39265. (Bug#33699)

  • Incompatible Change: It is no longer possible to create CSV tables with NULL columns. However, for backwards compatibility, you can continue to use such tables that were created in previous MySQL releases. (Bug#32050)

  • Incompatible Change: For packages that are built within their own prefix (for example, /usr/local/mysql) the plugin directory will be lib/plugin. For packages that are built to be installed into a system-wide prefix (such as RPM packages with a prefix of /usr), the plugin directory will be lib/mysql/plugin to ensure a clean /usr/lib hierarchy. In both cases, the $pkglibdir configuration setting is used at build time to set the plugin directory.

    The current plugin directory location is available as the value of the plugin_dir system variable as before, but the mysql_config script now has a --plugindir option that can be used externally to the server by third-party plugin writers to obtain the default plugin directory path name and configure their installation directory appropriately. (Bug#31736)

  • Incompatible Change: Inserting a row with a NULL value for a DATETIME column results in a CSV file that the storage engine cannot read.

    All CSV tables now need to be defined with each column marked as NOT NULL. An error is raised if you try to create a CSV table with columns that are not defined with NOT NULL. (Bug#31473, Bug#32817)

  • Incompatible Change: The utf8_general_ci and ucs2_general_ci collations did not sort the letter "U+00DF SHARP S" equal to 's'.

    As a result of this fix, any indexes on columns that use these collations (but only columns that use SHARP S) must be rebuilt when upgrading to 6.0.5 or higher. To do this, use ALTER TABLE to drop and re-add the indexes, or use mysqldump to dump the affected tables and mysql to reload the dump file. (Bug#27877)

    See also Bug#37046.

  • Incompatible Change: Several changes were made to the processing of multiple-table DELETE statements:

    • Statements could not perform cross-database deletes unless the tables were referred to without using aliases. This limitation has been lifted and table aliases now are allowed.

    • Previously, alias declarations could be given for tables elsewhere than in the table_references part of the syntax. This could lead to ambiguous statements that have unexpected results such as deleting rows from the wrong table. Example:

      DELETE FROM t1 AS a2 USING t1 AS a1 INNER JOIN t2 AS a2;

      Now alias declarations can be declared only in the table_references part. Elsewhere in the statement, alias references are allowed but not alias declarations.

    • Alias resolution was improved so that it is no longer possible to have inconsistent or ambiguous aliases for tables.

    Statements containing alias constructs that are no longer allowed must be rewritten. (Bug#27525)

    See also Bug#30234.

  • Important Change: Partitioning: The following statements did not function correctly with corrupted or crashed tables and have been disabled:





    ALTER TABLE ... REBUILD PARTITION is unaffected by this change and continues to be available. This statement and ALTER TABLE ... REORGANIZE PARTITION may be used to analyze and optimize partitioned tables, since these operations cause the partition files to be rebuilt. (Bug#20129)

    See also Bug#39434.

  • Important Change: Replication: When the master crashed during an update on a transactional table while in autocommit mode, the slave failed. This fix causes every transaction (including autocommit transactions) to be recorded in the binlog as starting with a BEGIN and ending with a COMMIT or ROLLBACK. (Bug#26395)

  • Important Change: InnoDB free space information is now shown in the Data_free column of SHOW TABLE STATUS and in the DATA_FREE column of the INFORMATION_SCHEMA.TABLES table. (Bug#32440)

    See also Bug#11379.

  • Important Change: The server handled truncation of values having excess trailing spaces into CHAR, VARCHAR, and TEXT columns in different ways. This behavior has now been made consistent for columns of all three of these types, and now follows the existing behavior of VARCHAR columns in this regard; that is, a Note is always issued whenever such truncation occurs.

    This change does not affect columns of these three types when using a binary encoding; BLOB columns are also unaffected by the change, since they always use a binary encoding. (Bug#30059)

  • Important Change: An AFTER UPDATE trigger was not invoked when the UPDATE did not make any changes to the table for which the trigger was defined. Now AFTER UPDATE triggers behave the same in this regard as do BEFORE UPDATE triggers, which are invoked whether the UPDATE makes any changes in the table or not. (Bug#23771)

  • Replication: Important Note: Network timeouts between the master and the slave could result in corruption of the relay log. This fix rectifies a long-standing replication issue when using unreliable networks, including replication over wide area networks such as the Internet. If you experience reliability issues and see many You have an error in your SQL syntax errors on replication slaves, we strongly recommend that you upgrade to a MySQL version which includes this fix. (Bug#26489)

  • MySQL Cluster: When all data and SQL nodes in the cluster were shut down abnormally (that is, other than by using STOP in the cluster management client), ndb_mgm used excessive amounts of CPU. (Bug#33237)

  • MySQL Cluster: There was a short interval during the startup process prior to the beginning of heartbeat detection such that, were an API or management node to reboot or a network failure to occur, data nodes could not detect this, with the result that there could be a lingering connection. (Bug#28445)

  • Partitioning: In some cases, matching rows from a partitioned MyISAM using a BIT column as the primary key were not found by queries. (Bug#34358)

  • Partitioning: Enabling innodb_file_per_table produced problems with partitioning and tablespace operations on partitioned InnoDB tables, in some cases leading to corrupt partitions or causing the server to crash. (Bug#33429)

  • Partitioning: A table defined using PARTITION BY KEY and having a BIT column referenced in the partitioning key did not behave correctly; some rows could be inserted into the wrong partition, causing wrong results to be returned from queries. (Bug#33379)

  • Partitioning: It was possible to partition a table to which a foreign key referred. (Bug#32948)

  • Partitioning: When ALTER TABLE DROP PARTITION was executed on a table on which there was a trigger, the statement failed with an error. This occurred even if the trigger did not reference any tables. (Bug#32943)

  • Partitioning: A query of the form SELECT col1 FROM table GROUP BY (SELECT col2 FROM table LIMIT 1); against a partitioned table having a SET column crashed the server. (Bug#32772)

  • Partitioning: SHOW CREATE TABLE misreported the value of AUTO_INCREMENT for partitioned tables using either of the InnoDB or ARCHIVE storage engines. (Bug#32247)

  • Partitioning: Selecting from INFORMATION_SCHEMA.PARTITIONS while partition management statements (for example, ALTER TABLE ... ADD PARTITION) were executing caused the server to crash. (Bug#32178)

  • Partitioning: An error in the internal function mysql_unpack_partition() led to a fatal error in subsequent calls to open_table_from_share(). (Bug#32158)

  • Partitioning: Currently, all partitions of a partitioned table must use the same storage engine. One may optinally specify the storage engine on a per-partition basis; however, where this is the done, the storage engine must be the same as used by the table as a whole. ALTER TABLE did not enforce these rules correctly, the result being that incaccurate error messages were shown when trying to use the statement to change the storage engine used by an individual partition or partitions. (Bug#31931)

  • Partitioning: ORDER BY ... DESC did not always work correctly when selecting from partitioned tables. (Bug#31890)

    See also Bug#31001.

  • Partitioning: ALTER TABLE ... COALESCE PARTITION on a table partitioned by [LINEAR] HASH or [LINEAR] KEY caused the server to crash. (Bug#30822)

  • Partitioning: When the range access method was used on a partitioned Falcon table, the entire index was scanned. For partitioned tables using other storage engines, a related issue caused an ordered range scan to return some rows twice. (Bug#30573, Bug#33257, Bug#33555)

  • Partitioning: LIKE queries on tables partitioned by KEY could return incomplete results. The problem was observed with the Falcon storage engine, but could affect third-party storage engines as well. (Bug#30480)

    See also Bug#29320, Bug#29493, Bug#30563.

  • Partitioning: Using the DATA DIRECTORY and INDEX DIRECTORY options for partitions with CREATE TABLE or ALTER TABLE statements appeared to work on Windows, although they are not supported by MySQL on Windows systems, and subsequent attempts to use the tables referenced caused errors. Now these options are disabled on Windows, and attempting to use them generates a warning. (Bug#30459)

  • Partitioning: It was not possible to insert the greatest possible value for a given data type into a partitioned table. For example, consider a table defined as shown here:


    The largest possible value for a BIGINT UNSIGNED column is 18446744073709551615, but the statement INSERT INTO t VALUES (18446744073709551615); would fail, even though the same statement succeeded were t not a partitioned table.

    In other words, MAXVALUE was treated as being equal to the greatest possible value, rather than as a least upper bound. (Bug#29258)

  • Replication: Replicating a Falcon table that contained a TEXT or BLOB column would fail during a DELETE operation with the error HA_ERR_END_OF_FILE. (Bug#36468)

  • Replication: When using row-based replication, a slave could crash at startup because it received a row-based replication event that InnoDB could not handle due to an incorrect test of the query string provided by MySQL, which was NULL for row-based replication events. (Bug#35226)

  • Replication: insert_id was not written to the binary log for inserts into BLACKHOLE tables. (Bug#35178)

  • Replication: When using statement-based replication and a DELETE, UPDATE, or INSERT ... SELECT statement using a LIMIT clause is encountered, a warning that the statement is not safe to replicate in statement mode is now issued; when using MIXED mode, the statement is now replicated using the row-based format. (Bug#34768)

  • Replication: mysqlbinlog did not output the values of auto_increment_increment and auto_increment_offset when both were equal to their default values (for both of these variables, the default is 1). This meant that a binary log recorded by a client using the defaults for both variables and then replayed on another client using its own values for either or both of these variables produced erroneous results. (Bug#34732)

    See also Bug#31168.

  • Replication: A CHANGE MASTER TO statement with no MASTER_HEARTBEAT_PERIOD option failed to reset the heartbeat period to its default value. (Bug#34686)

  • Replication: SHOW SLAVE STATUS failed when slave I/O was about to terminate. (Bug#34305)

  • Replication: The character sets and collations used for constant identifiers in stored procedures were not replicated correctly. (Bug#34289)

  • Replication: mysqlbinlog from a 5.1 or later MySQL distribution could not read binary logs generated by a 4.1 server when the logs contained LOAD DATA INFILE statements. (Bug#34141)

    This regression was introduced by Bug#32407.

  • Replication: A CREATE USER, DROP USER, or RENAME USER statement that fails on the master, or that is a duplicate of any of these statements, is no longer written to the binlog; previously, either of these occurrences could cause the slave to fail.


    See also Bug#29749.

  • Replication: SHOW BINLOG EVENTS could fail when the binlog contained one or more events whose size was close to the value of max_allowed_packet. (Bug#33413)

  • Replication: mysqlbinlog failed to release all of its memory after terminating abnormally. (Bug#33247)

  • Replication: When a stored routine or trigger, running on a master that used MySQL 5.0 or MySQL 5.1.11 or earlier, performed an insert on an AUTO_INCREMENT column, the insert_id value was not replicated correctly to a slave running MySQL 5.1.12 or later (including any MySQL 6.0 release). (Bug#33029)

    See also Bug#19630.

  • Replication: The error message generated due to lack of a default value for an extra column was not sufficiently informative. (Bug#32971)

  • Replication: When a user variable was used inside an INSERT statement, the corresponding binlog event was not written to the binlog correctly. (Bug#32580)

  • Replication: When using row-based replication, deletes from a table with a foreign key constraint failed on the slave. (Bug#32468)

  • Replication: The --base64-output option for mysqlbinlog was not honored for all types of events. This interfered in some cases with performing point-in-time recovery. (Bug#32407)

  • Replication: SQL statements containing comments using -- syntax were not replayable by mysqlbinlog, even though such statements replicated correctly. (Bug#32205)

  • Replication: When using row-based replication from a master running MySQL 6.0.3 or earlier to a slave running 6.0.4 or later, updates of integer columns failed on the slave with Error in Unknown event: row application failed. (Bug#31583)

    This regression was introduced by Bug#21842.

  • Replication: Replicating write, update, or delete events from a master running MySQL 5.1.15 or earlier to a slave running 5.1.16 or later caused the slave to crash. (Bug#31581)

  • Replication: When using row-based replication, the slave stopped when attempting to delete nonexistent rows from a slave table without a primary key. In addition, no error was reported when this occurred. (Bug#31552)

  • Replication: Errors due to server ID conflicts were reported only in the slave's error log; now these errors are also shown in the Server_IO_State column in the output of SHOW SLAVE STATUS. (Bug#31316)

  • Replication: STOP SLAVE did not stop connection attempts properly. If the IO slave thread was attempting to connect, STOP SLAVE waited for the attempt to finish, sometimes for a long period of time, rather than stopping the slave immediately. (Bug#31024)

    See also Bug#30932.

  • Replication: Issuing a DROP VIEW statement caused replication to fail if the view did not actually exist. (Bug#30998)

  • Replication: Replication of LOAD DATA INFILE could fail when read_buffer_size was larger than max_allowed_packet. (Bug#30435)

  • Replication: Replication crashed with the NDB storage engine when mysqld was started with --character-set-server=ucs2. (Bug#29562)

  • Replication: The effects of scheduled events were not always correctly reproduced on the slave when using row-based replication. (Bug#29020)

  • Replication: Setting server_id did not update its value for the current session. (Bug#28908)

  • Replication: Some older servers wrote events to the binary log using different numbering from what is currently used, even though the file format number in the file is the same. Slaves running MySQL 5.1.18 and later could not read these binary logs properly. Binary logs from these older versions now are recognized and event numbers are mapped to the current numbering so that they can be interpreted properly. (Bug#27779, Bug#32434)

    This regression was introduced by Bug#22583.

  • Replication: MASTER_POS_WAIT() did not return NULL when the server was not a slave. (Bug#26622)

  • Replication: The nonspecific error message Wrong parameters to function register_slave resulted when START SLAVE failed to register on the master due to excess length of any the slave server options --report-host, --report-user, or --report-password. An error message specific to each of these options is now returned in such cases. The new error messages are:

    • Failed to register slave: too long 'report-host'

    • Failed to register slave: too long 'report-user'

    • Failed to register slave; too long 'report-password'


    See also Bug#19328.

  • Replication: PURGE BINARY LOGS TO and PURGE BINARY LOGS BEFORE did not handle missing binary log files correctly or in the same way. Now for both of these statements, if any files listed in the .index file are missing from the file system, the statement fails with an error. (Bug#18199, Bug#18453)

  • API: When the language option was not set correctly, API programs calling mysql_server_init() crashed. This issue was observed only on Windows platforms. (Bug#31868)

  • Corrected a typecast involving bool on Mac OS X 10.5 (Leopard), which evaluated differently from earlier Mac OS X versions. (Bug#38217)

  • Queries could return different results depending on whether the join buffer was or was not used. (Bug#37131)

  • BACKUP DATABASE did not correctly determine dependency ordering of backed-up objects, which could cause a RESTORE operation to fail. (Bug#36531)

  • Concurrent LOAD DATA INFILE statements inserting data into Falcon tables could crash the server. (Bug#35982)

  • Following a server crash, recovery of Falcon tables containing BLOB or TEXT columns could lose data. (Bug#35688)

  • Manually replacing a binary log file with a directory having the same name caused an error that was not handled correctly. (Bug#35675)

  • Using LOAD DATA INFILE with a view could crash the server. (Bug#35469)

  • Selecting from INFORMATION_SCHEMA.REFERENTIAL_CONSTRAINTS could cause a server crash. (Bug#35406)

    See also Bug#35108.

  • For a TEMPORARY table, DELETE with no WHERE clause could fail when preceded by DELETE statements with a WHERE clause. (Bug#35392)

  • In some cases, when too many clients tried to connect to the server, the proper SQLSTATE code was not returned. (Bug#35289)

  • Memory-allocation failures for attempts to set key_buffer_size to large values could result in a server crash. (Bug#35272)

  • Queries could return different results depending on whether ORDER BY columns were indexed. (Bug#35206)

  • When a view containing a reference to DUAL was created, the reference was removed when the definition was stored, causing some queries against the view to fail with invalid SQL syntax errors. (Bug#35193)

  • SELECT ... FROM INFORMATION_SCHEMA.REFERENTIAL_CONSTRAINTS caused the server to crash if the table referenced by a foreign key had been dropped. This issue was observed on Windows platforms only. (Bug#35108)

    See also Bug#35406.

  • Debugging symbols were missing for some executables in Windows binary distributions. (Bug#35104)

  • Nonconnection threads were being counted in the value of the Max_used_connections status variable. (Bug#35074)

  • Two different threads could obtain the same record number for concurrent inserts into the same Falcon table. (Bug#34990)

  • A query that performed a ref_or_null join where the second table used a key having one or columns that could be NULL and had a column value that was NULL caused the server to crash. (Bug#34945)

    This regression was introduced by Bug#12144.

  • For some queries, the optimizer used an ordered index scan for GROUP BY or DISTINCT when it was supposed to use a loose index scan, leading to incorrect results. (Bug#34928)

  • Creating a foreign key on an InnoDB table that was created with an explicit AUTO_INCREMENT value caused that value to be reset to 1. (Bug#34920)

  • mysqldump failed to return an error code when using the --master-data option without binary logging being enabled on the server. (Bug#34909)

  • Under some circumstances, the value of mysql_insert_id() following a SELECT ... INSERT statement could return an incorrect value. This could happen when the last SELECT ... INSERT did not involve an AUTO_INCREMENT column, but the value of mysql_insert_id() was changed by some previous statements. (Bug#34889)

  • Logging to the progress tables used by BACKUP DATABASE and RESTORE caused a server crash. (Bug#34858)

  • Table and database names were mixed up in some places of the subquery transformation procedure. This could affect debugging trace output and further extensions of that procedure. (Bug#34830)

  • If fsync() returned ENOLCK, InnoDB could treat this as fatal and cause abnormal server termination. InnoDB now retries the operation. (Bug#34823)

  • CREATE SERVER and ALTER SERVER could crash the server if out-of-memory conditions occurred. (Bug#34790)

  • DROP SERVER does not release memory cached for server structures created by CREATE SERVER, so repeated iterations of these statements resulted in a memory leak. FLUSH PRIVILEGES now releases the memory allocated for CREATE SERVER. (Bug#34789)

  • A malformed URL used for a FEDERATED table's CONNECTION option value in a CREATE TABLE statement was not handled correctly and could crash the server. (Bug#34788)

  • Repeated UPDATE operations on a Falcon table could cause a memory leak. (Bug#34778)

  • Queries such as SELECT ROW(1, 2) IN (SELECT t1.a, 2) FROM t1 GROUP BY t1.a (combining row constructors and subqueries in the FROM clause) could lead to assertion failure or unexpected error messages. (Bug#34763)

  • Using NAME_CONST() with a negative number and an aggregate function caused MySQL to crash. This could also have a negative impact on replication. (Bug#34749)

  • A memory-handling error associated with use of GROUP_CONCAT() in subqueries could result in a server crash. (Bug#34747)

  • For an indexed integer column col_name and a value N that is one greater than the maximum value allowed for the data type of col_name, conditions of the form WHERE col_name < N failed to return rows where the value of col_name is N - 1. (Bug#34731)

  • A server running with the --debug option could attempt to dereference a null pointer when opening tables, resulting in a crash. (Bug#34726)

  • Assigning an “incremental” value to the debug system variable did not add the new value to the current value. For example, if the current debug value was 'T', the statement SET debug = '+P' resulted in a value of 'P' rather than the correct value of 'P:T'. (Bug#34678)

  • For debug builds, reading from INFORMATION_SCHEMA.TABLES or INFORMATION_SCHEMA.COLUMNS could cause assertion failures. This could happen under rare circumstances when INFORMATION_SCHEMA fails to get information about a table (for example, when a connection is killed). (Bug#34656)

  • Executing a TRUNCATE statement on a table having both a foreign key reference and a DELETE trigger crashed the server. (Bug#34643)

  • Some subqueries using an expression that included an aggregate function could fail or in some cases lead to a crash of the server. (Bug#34620)

  • Dangerous pointer arithmetic crashed the server on some systems. (Bug#34598)

  • Creating a view inside a stored procedure could lead to a crash of the MySQL Server. (Bug#34587)

  • Concurrent ALTER TABLE operations on temporary and nontemporary Falcon tables caused the server to hang. (Bug#34567)

    This regression was introduced by Bug#33634.

  • A server crash could occur if INFORMATION_SCHEMA tables built in memory were swapped out to disk during query execution. (Bug#34529)

  • CAST(AVG(arg) AS DECIMAL) produced incorrect results for non-DECIMAL arguments. (Bug#34512)

  • SET GLOBAL falcon_record_chill_threshold and SET GLOBAL falcon_index_chill_threshold did not work. (Bug#34486)

  • The per-thread debugging settings stack was not being deallocated before thread termination, resulting in a stack memory leak. (Bug#34424)

  • Client applications could not connect to the server on Windows Vista because the server was creating an IPv6-only TCP/IP socket. (Bug#34381)

  • Inserting a unique record into a Falcon table, then performing a DELETE on the same record resulted in the error Record has changed since last read. (Bug#34351)

    See also Bug#29151, Bug#35321.

  • Executing an ALTER VIEW statement on a table crashed the server. (Bug#34337)

  • For InnoDB, exporting and importing a table could corrupt TINYBLOB columns, and a subsequent ALTER TABLE could corrupt TINYTEXT columns as well. (Bug#34300)

  • On Windows, client programs generated assertion failures. (Bug#34298)

  • DEFAULT 0 was not allowed for the YEAR data type. (Bug#34274)

  • Under some conditions, a SET GLOBAL innodb_commit_concurrency or SET GLOBAL innodb_autoextend_increment statement could fail. (Bug#34223)

  • mysqldump attempts to set the character_set_results system variable after connecting to the server. This failed for pre-4.1 servers that have no such variable, but mysqldump did not account for this and 1) failed to dump database contents; 2) failed to produce any error message alerting the user to the problem. (Bug#34192)

  • Use of stored functions in the WHERE clause for SHOW OPEN TABLES caused a server crash. (Bug#34166)

  • Compilation failed on Solaris for the ARCHIVE storage engine due to inclusion of getopt.h in the ARCHIVE code. (Bug#34094)

  • CREATE TABLE ... ENGINE=Falcon failed with an unhelpful error message when the Falcon storage engine had failed to allocate the page cache properly on server startup. Now, Falcon is initialized on server startup, and is not loaded if the allocation fails. (Bug#34085)

  • Updates of floating-point columns in FEDERATED tables could produce incorrect results. (Bug#34015)

  • For a FEDERATED table with an index on a nullable column, accessing the table could crash a server, return an incorrect result set, or return ERROR 1030 (HY000): Got error 1430 from storage engine. (Bug#33946)

  • Passing anything other than an integer argument to a LIMIT clause in a prepared statement would fail. (This limitation was introduced to avoid replication problems; for example, replicating the statement with a string argument would cause a parse failure in the slave). Now, arguments to the LIMIT clause are converted to integer values, and these converted values are used when logging the statement. (Bug#33851)

  • An internal buffer in mysql was too short. Overextending it could cause stack problems or segmentation violations on some architectures. (This is not a problem that could be exploited to run arbitrary code.) (Bug#33841)

  • A query using WHERE (column1='string1' AND column2=constant1) OR (column1='string2' AND column2=constant2), where col1 used a binary collation and string1 matched string2 except for case, failed to match any records even when matches were found by a query using the equivalent clause WHERE column2=constant1 OR column2=constant2. (Bug#33833)

  • Large unsigned integers were improperly handled for prepared statements, resulting in truncation or conversion to negative numbers. (Bug#33798)

  • Reuse of prepared statements could cause a memory leak in the embedded server. (Bug#33796)

  • The server crashed when executing a query that had a subquery containing an equality X=Y where Y referred to a named select list expression from the parent select. The server crashed when trying to use the X=Y equality for ref-based access. (Bug#33794)

  • Some queries using a combination of IN, CONCAT(), and an implicit type conversion could return an incorrect result. (Bug#33764)

  • In some cases a query that produced a result set when using ORDER BY ASC did not return any results when this was changed to ORDER BY DESC. (Bug#33758)

  • Disabling concurrent inserts caused some cacheable queries not to be saved in the query cache. (Bug#33756)

  • ORDER BY ... DESC sorts could produce misordered results. (Bug#33697)

  • Use of uninitialized memory for filesort in a subquery caused a server crash. (Bug#33675)

  • The WEIGHT_STRING() function returned incorrect results for column values when earlier column values were NULL. (Bug#33663)

  • The server could crash when REPEAT or another control instruction was used in conjunction with labels and a LEAVE instruction. (Bug#33618)

  • The parser allowed control structures in compound statements to have mismatched beginning and ending labels. (Bug#33618)

  • make_binary_distribution passed the --print-libgcc-file option to the C compiler, but this does not work with the ICC compiler. (Bug#33536)

  • Threads created by the event scheduler were incorrectly counted against the max_connections thread limit, which could lead to client lockout. (Bug#33507)

  • CREATE TABLE ... ENGINE=Falcon failed on kernel 2.4 based Linux systems when using O_DIRECT with an NFS file system. (Bug#33484)

  • Dropping a function after dropping the function's creator could cause the server to crash. (Bug#33464)

  • For the latin2_czech_cs collation, the primary weights for all variants of capital letters U and O were incorrect (were not equal to the corresponding small letters).

    As a result of this bug fix, indexes must be rebuilt for columns that use the latin2_czech_cs collation. See Section 2.11.3, “Checking Whether Table Indexes Must Be Rebuilt”. (Bug#33452)

  • Certain combinations of views, subselects with outer references and stored routines or triggers could cause the server to crash. (Bug#33389)

  • SET GLOBAL myisam_max_sort_file_size=DEFAULT set myisam_max_sort_file_size to an incorrect value. (Bug#33382)

    See also Bug#31177.

  • ENUM- or SET-valued plugin variables could not be set from the command line. (Bug#33358)

  • If the mysql database was named in the BACKUP DATABASE statement, the backup operation hung. (Bug#33355)

  • Loading plugins via command-line options to mysqld could cause an assertion failure. (Bug#33345)

  • SLEEP(0) failed to return on 64-bit Mac OS X due to a bug in pthread_cond_timedwait(). (Bug#33304)

  • CREATE TABLE ... SELECT created tables that for date columns used the obsolete Field_date type instead of Field_newdate. (Bug#33256)

  • For MyISAM tables, CHECK TABLE (non-QUICK) and any form of REPAIR TABLE incorrected treated rows as corrupted under the combination of the following conditions:

    • The table had dynamic row format

    • The table had a CHAR (not VARCHAR) column longer than 127 bytes (for multi-byte character sets this could be less than 127 characters)

    • The table had rows with a signifcant length of more than 127 bytes significant length in that CHAR column (that is, a byte beyond byte position 127 must be a nonspace character)

    This problem affected CHECK TABLE, REPAIR TABLE, OPTIMIZE TABLE, ALTER TABLE. CHECK TABLE reported and marked the table as crashed if any row was present that fulfilled the third condition. The other statements deleted these rows. (Bug#33222)

  • The error message was vague for attempts to drop a Falcon tablespace that contained tables. Now the message Tablespace busy is returned. (Bug#33216)

  • When creating temporary tables within Falcon, the tables are automatically created in the FALCON_TEMPORARY tablespace. If you specify an alternate tablespace to the CREATE TABLE statement a warning will now be issued to that effect. (Bug#33211)

  • Granting the UPDATE privilege on one column of a view caused the server to crash. (Bug#33201)

  • For DECIMAL columns used with the ROUND(X,D) or TRUNCATE(X,D) function with a nonconstant value of D, adding an ORDER BY for the function result produced misordered output. (Bug#33143)

    See also Bug#33402, Bug#30617.

  • Some valid SELECT statements could not be used as views due to incorrect column reference resolution. (Bug#33133)

  • The weight for supplementary Unicode characters should be 0xFFFD, but the WEIGHT_STRING() function returned 0x0DC6 instead. (Bug#33077)

  • The CSV engine did not honor update requests for BLOB columns when the new column value had the same length as the value to be updated. (Bug#33067)

  • After receiving a SIGHUP signal, the server could crash, and user-specified log options were ignored when reopening the logs. (Bug#33065)

  • Repeatedly executing a query with a semi-join subquery could cause a server crash. (Bug#33062)

  • The fix for Bug#11230 and Bug#26215 introduced a significant input-parsing slowdown for the mysql client. This has been corrected. (Bug#33057)

  • When MySQL was built with OpenSSL, the SSL library was not properly initialized with information of which endpoint it was (server or client), causing connection failures. (Bug#33050)

  • Under some circumstances a combination of aggregate functions and GROUP BY in a SELECT query over a view could lead to incorrect calculation of the result type of the aggregate function. This in turn could lead to incorrect results, or to crashes on debug builds of the server. (Bug#33049)

  • It was not possible to set the value of falcon_consistent_read within the local scope. You can now set the global value, using SET GLOBAL, but this affects only the current local scope and all new connections made after the global variable was set. (Bug#33041)

  • The new index condition pushdown optimization could cause a server crash when used with the range access method over an InnoDB table. (Bug#33033)

  • For DISTINCT queries, MySQL 4.0 and 4.1 stopped reading joined tables as soon as the first matching row was found. However, this optimization was lost in MySQL 5.0, which instead read all matching rows. This fix for this regression may result in a major improvement in performance for DISTINCT queries in cases where many rows match. (Bug#32942)

  • Repeated creation and deletion of views within prepared statements could eventually crash the server. (Bug#32890)

    See also Bug#34587.

  • The correct data type for a NULL column resulting from a UNION could be determined incorrectly in some cases: 1) Not correctly inferred as NULL depending on the number of selects; 2) Not inferred correctly as NULL if one select used a subquery. (Bug#32848)

  • For queries containing GROUP_CONCAT(DISTINCT col_list ORDER BY col_list), there was a limitation that the DISTINCT columns had to be the same as ORDER BY columns. Incorrect results could be returned if this was not true. (Bug#32798)

  • Incorrect assertions could cause a server crash for DELETE triggers for transactional tables. (Bug#32790)

  • SHOW EVENTS and selecting from the INFORMATION_SCHEMA.EVENTS table failed if the current database was INFORMATION_SCHEMA. (Bug#32775)

  • In some cases where setting a system variable failed, no error was sent to the client, causing the client to hang. (Bug#32757)

  • Enabling the PAD_CHAR_TO_FULL_LENGTH SQL mode caused privilege-loading operations (such as FLUSH PRIVILEGES) to include trailing spaces from grant table values stored in CHAR columns. Authentication for incoming connections failed as a result. Now privilege loading does not include trailing spaces, regardless of SQL mode. (Bug#32753)

  • Use of the cp932 character set with CAST() in an ORDER BY clause could cause a server crash. (Bug#32726)

  • The SHOW ENGINE INNODB STATUS and SHOW ENGINE INNODB MUTEX statements incorrectly required the SUPER privilege rather than the PROCESS privilege. (Bug#32710)

  • Inserting strings with a common prefix into a table that used the ucs2 character set corrupted the table. (Bug#32705)

  • A subquery using an IS NULL check of a column defined as NOT NULL in a table used in the FROM clause of the outer query produced an invalid result. (Bug#32694)

  • Specifying a nonexistent column for an INSERT DELAYED statement caused a server crash rather than producing an error. (Bug#32676)

  • Tables in the mysql database that stored the current sql_mode value as part of stored program definitions were not updated with newer mode values (NO_ENGINE_SUBSTITUTION, PAD_CHAR_TO_FULL_LENGTH). This causes various problems defining stored programs if those modes were included in the current sql_mode value. (Bug#32633)

  • Use of CLIENT_MULTI_QUERIES caused libmysqld to crash. (Bug#32624)

  • A SELECT ... GROUP BY bit_column query failed with an assertion if the length of the BIT column used for the GROUP BY was not an integer multiple of 8. (Bug#32556)

  • A view created with a string literal for one of the columns picked up the connection character set, but not the collation. Comparison to that field therefore used the default collation for that character set, causing an error if the connection collation was not compatible with the default collation. The problem was caused by text literals in a view being dumped with a character set introducer even when this was not necessary, sometimes leading to a loss of collation information. Now the character set introducer is dumped only if it was included in the original query. (Bug#32538)

    See also Bug#21505.

  • Using SELECT INTO OUTFILE with 8-bit ENCLOSED BY characters led to corrupted data when the data was reloaded using LOAD DATA INFILE. This was because SELECT INTO OUTFILE failed to escape the 8-bit characters. (Bug#32533)

  • For FLUSH TABLES WITH READ LOCK, the server failed to properly detect write-locked tables when running with low-priority updates, resulting in a crash or deadlock. (Bug#32528)

  • Queries using LIKE on tables having indexed CHAR columns using either of the eucjpms or ujis character sets did not return correct results. (Bug#32510)

  • A query of the form SELECT @user_variable := constant AS alias FROM table GROUP BY alias WITH ROLLUP crashed the server. (Bug#32482)

  • Sending several KILL QUERY statements to target a connection running SELECT SLEEP() could freeze the server. (Bug#32436)

  • ssl-cipher values in option files were not being read by libmysqlclient. (Bug#32429)

  • Repeated execution of a query containing a CASE expression and numerous AND and OR relations could crash the server. The root cause of the issue was determined to be that the internal SEL_ARG structure was not properly initialized when created. (Bug#32403)

  • Referencing within a subquery an alias used in the SELECT list of the outer query was incorrectly permitted. (Bug#32400)

  • If a global read lock acquired with FLUSH TABLES WITH READ LOCK was in effect, executing ALTER TABLE could cause a server crash. (Bug#32395)

  • utf16 columns allowed incorrect Unicode characters inserted through conversion from another Unicode character set. (Bug#32393)

  • An ORDER BY query on a view created using a FEDERATED table as a base table caused the server to crash. (Bug#32374)

  • Comparison of a BIGINT NOT NULL column with a constant arithmetic expression that evaluated to NULL mistakenly caused the error Column '...' cannot be null (error 1048). (Bug#32335)

  • Assigning a 65,536-byte string to a TEXT column (which can hold a maximum of 65,535 bytes) resulted in truncation without a warning. Now a truncation warning is generated. (Bug#32282)

  • The LAST_DAY() function returns a DATE value, but internally the value did not have the time fields zeroed and calculations involving the value could return incorrect results. (Bug#32270)

  • MIN() and MAX() could return incorrect results when an index was present if a loose index scan was used. (Bug#32268)

  • Executing a prepared statement associated with a materialized cursor sent to the client a metadata packet with incorrect table and database names. The problem occurred because the server sent the name of the temporary table used by the cursor instead of the table name of the original table.

    The same problem occured when selecting from a view, in which case the name of the table name was sent, rather than the name of the view. (Bug#32265)

  • Memory corruption could occur due to large index map in Range checked for each record status reported by EXPLAIN SELECT. The problem was based in an incorrectly calculated length of the buffer used to store a hexadecimal representation of an index map, which could result in buffer overrun and stack corruption under some circumstances. (Bug#32241)

  • Various test program cleanups were made: 1) mytest and libmysqltest were removed. 2) bug25714 displays an error message when invoked with incorrect arguments or the --help option. 3) mysql_client_test exits cleanly with a proper error status. (Bug#32221)

  • The default grant tables on Windows contained information for host, which should not be there. (Bug#32219)

  • For comparisons of the form date_col OP datetime_const (where OP is =, <, >, <=, or >=), the comparison is done using DATETIME values, per the fix for Bug#27590. However that fix caused any index on date_col not to be used and compromised performance. Now the index is used again. (Bug#32198)

  • DATETIME arguments specified in numeric form were treated by DATE_ADD() as DATE values. (Bug#32180)

  • When configure was run with --with-libevent, libevent was not linked statically with mysqld, preventing mysqld from being run with a debugger. (Bug#32156)

  • Killing a statement could lead to a race condition in the server. (Bug#32148)

  • String-to-double conversion was performed differently when the prepared-statement protocol was used from when it was not. (Bug#32095)

  • With lower_case_table_names set, CREATE TABLE LIKE was treated differently by libmysqld than by the nonembedded server. (Bug#32063)

  • On Windows, mysqltest_embedded.exe did not properly execute the send command. (Bug#32044)

  • Within a subquery, UNION was handled differently than at the top level, which could result in incorrect results or a server crash. (Bug#32036, Bug#32051)

  • HOUR(), MINUTE(), and SECOND() could return nonzero values for DATE arguments. (Bug#31990)

  • A variable named read_only could be declared even though that is a reserved word. (Bug#31947)

  • On Windows, the build process failed with four parallel build threads. (Bug#31929)

  • Changing the SQL mode to cause dates with “zero” parts to be considered invalid (such as '1000-00-00') could result in indexed and nonindexed searches returning different results for a column that contained such dates. (Bug#31928)

  • The server used unnecessarily large amounts of memory when user variables were used as an argument to CONCAT() or CONCAT_WS(). (Bug#31898)

  • Queries testing numeric constants containing leading zeroes against ZEROFILL columns were not evaluated correctly. (Bug#31887)

  • sometimes set up test scenarios in which the same port number was passed to multiple servers, causing one of them to be unable to start. (Bug#31880)

  • Using ORDER BY led to the wrong result when using the ARCHIVE on a table with a BLOB when the table cache was full. The table could also be reported as crashed after the query had completed, even though the table data was intact. (Bug#31833)

  • Name resolution for correlated subqueries and HAVING clauses failed to distinguish which of two was being performed when there was a reference to an outer aliased field. This could result in error messages about a HAVING clause for queries that had no such clause. (Bug#31797)

  • If an error occurred during file creation, the server sometimes did not remove the file, resulting in an unused file in the file system. (Bug#31781)

  • The mysqld crash handler failed on Windows. (Bug#31745)

  • mysqlslap failed to commit after the final record load. (Bug#31704)

  • ucs2 does not work as a client character set, but attempts to use it as such were not rejected. Now character_set_client cannot be set to ucs2. This also affects statements such as SET NAMES and SET CHARACTER SET. (Bug#31615)

  • The server returned the error message Out of memory; restart server and try again when the actual problem was that the sort buffer was too small. Now an appropriate error message is returned in such cases. (Bug#31590)

  • For a table that had been opened with HANDLER and marked for reopening after being closed with FLUSH TABLES, DROP TABLE did not properly discard the handler. (Bug#31397)

  • A table having an index that included a BLOB or TEXT column, and that was originally created with a MySQL server using version 4.1 or earlier, could not be opened by a 5.1 or later server. (Bug#31331)

  • The -, *, and / operators and the functions POW() and EXP() could misbehave when used with floating-point numbers. Previously they might return +INF, -INF, or NaN in cases of numeric overflow (including that caused by division by zero) or when invalid arguments were used. Now NULL is returned in all such cases. (Bug#31236)

  • The mysql_change_user() C API function caused global Com_xxx status variable values to be incorrect. (Bug#31222)

  • When sorting privilege table rows, the server treated escaped wildcard characters (\% and \_) the same as unescaped wildcard characters (% and _), resulting in incorrect row ordering. (Bug#31194)

  • Server variables could not be set to their current values on Linux platforms. (Additional fixes were made in MySQL 6.0.9 and 6.0.10.) (Bug#31177)

    See also Bug#6958.

  • Data in BLOB or GEOMETRY columns could be cropped when performing a UNION query. (Bug#31158)

  • The server crashed in the parser when running out of memory. Memory handling in the parser has been improved to gracefully return an error when out-of-memory conditions occur in the parser. (Bug#31153)

  • MySQL declares a UNIQUE key as a PRIMARY key if it doesn't have NULL columns and is not a partial key, and the PRIMARY key must alway be the first key. However, in some cases, a nonfirst key could be reported as PRIMARY, leading to an assert failure by InnoDB. This is fixed by correcting the key sort order. (Bug#31137)

  • Many nested subqueries in a single query could led to excessive memory consumption and possibly a crash of the server. (Bug#31048)

  • An assertion failure occurred for queries containing two subqueries if both subqueries were evaluated using a semi-join strategy. (Bug#31040)

  • On Windows, SHOW PROCESSLIST could display process entries with a State value of *** DEAD ***. (Bug#30960)

  • ROUND(X,D) or TRUNCATE(X,D) for nonconstant values of D could crash the server if these functions were used in an ORDER BY that was resolved using filesort. (Bug#30889)

  • Resetting the query cache by issuing a SET GLOBAL query_cache_size=0 statement caused the server to crash if it concurrently was saving a new result set to the query cache. (Bug#30887)

  • Manifest problems prevented MySQLInstanceConfig.exe from running on Windows Vista. (Bug#30823)

  • The optimizer incorrectly optimized conditions out of the WHERE clause in some queries involving subqueries and indexed columns. (Bug#30788)

  • If an alias was used to refer to the value returned by a stored function within a subselect, the outer select recognized the alias but failed to retrieve the value assigned to it in the subselect. (Bug#30787)

  • Improper calculation of CASE expression results could lead to value truncation. (Bug#30782)

  • The thread_handling system variable was treated as having a SESSION value and as being settable at runtime. Now it has only a GLOBAL read-only value. (Bug#30651)

  • If the optimizer used a Multi-Range Read access method for index lookups, incorrect results could occur for rows that contained any of the BLOB or TEXT data types. (Bug#30622)

  • Binary logging for a stored procedure differed depending on whether or not execution occurred in a prepared statement. (Bug#30604)

  • When casting a string value to an integer, cases where the input string contained a decimal point and was long enough to overrun the unsigned long long type were not handled correctly. The position of the decimal point was not taken into account which resulted in miscalculated numbers and incorrect truncation to appropriate SQL data type limits. (Bug#30453)

  • With libmysqld, use of prepared statements and the query cache at the same time caused problems. (Bug#30430)

  • For CREATE ... SELECT ... FROM, where the resulting table contained indexes, adding SQL_BUFFER_RESULT to the SELECT part caused index corruption in the table. (Bug#30384)

  • An orphaned PID file from a no-longer-running process could cause mysql.server to wait for that process to exit even though it does not exist. (Bug#30378)

  • The optimizer made incorrect assumptions about the value of the is_member value for user-defined functions, sometimes resulting in incorrect ordering of UDF results. (Bug#30355)

  • The Table_locks_waited waited variable was not incremented in the cases that a lock had to be waited for but the waiting thread was killed or the request was aborted. (Bug#30331)

  • Simultaneous ALTER TABLE statements for BLACKHOLE tables caused 100% CPU use due to locking problems. (Bug#30294)

  • Tables with a GEOMETRY column could be marked as corrupt if you added a non-SPATIAL index on a GEOMETRY column. (Bug#30284)

  • Flushing a merge table between the time it was opened and its child table were actually attached caused the server to crash. (Bug#30273)

    This regression was introduced by Bug#26379.

  • The Com_create_function status variable was not incremented properly. (Bug#30252)

  • For Multi-Range Read scans used to resolve LIMIT queries, failure to close the scan caused file descriptor leaks for MyISAM tables. (Bug#30221)

  • View metadata returned from INFORMATION_SCHEMA.VIEWS was changed by the fix for Bug#11986, causing the information returned in MySQL 5.1 to differ from that returned in 5.0. (Bug#30217)

  • If the server crashed during an ALTER TABLE statement, leaving a temporary file in the database directory, a subsequent DROP DATABASE statement failed due to the presence of the temporary file. (Bug#30152)

  • The parser accepted an INTO clause in nested SELECT statements, which is invalid because such statements must return their results to the outer context. (Bug#30105, Bug#33204)

  • For tables with FLOAT or DOUBLE columns, CHECKSUM TABLE could report different results on master and slave servers. (Bug#30041)

  • mysqld displayed the --enable-pstack option in its help message even if MySQL was configured without --with-pstack. (Bug#29836)

  • The mysql_config command would output CFLAGS values that were incompatible with C++ for the HP-UX platform. (Bug#29645)

  • Views were treated as insertable even if some base table columns with no default value were omitted from the view definition. (This is contrary to the condition for insertability that a view must contain all columns in the base table that do not have a default value.) (Bug#29477)

  • myisamchk always reported the character set for a table as latin1_swedish_ci (8) regardless of the table' actual character set. (Bug#29182)

  • Denormalized double-precision numbers cannot be handled properly by old MIPS pocessors. For IRIX, this is now handled by enabling a mode to use a software workaround. (Bug#29085)

  • When doing a DELETE on a table that involved a JOIN with MyISAM or MERGE tables and the JOIN referred to the same table, the operation could fail reporting ERROR 1030 (HY000): Got error 134 from storage engine. This was because scans on the table contents would change because of rows that had already been deleted. (Bug#28837)

  • SHOW VARIABLES did not correctly display the value of the thread_handling system variable. (Bug#28785)

  • When running the MySQL Instance Configuration Wizard, a race condition could exist that would fail to connect to a newly configured instance. This was because mysqld had not completed the startup process before the next stage of the installation process. (Bug#28628)

  • For upgrading to a new major version using RPM packages (such as 4.1 to 5.0), if the installation procedure found an existing MySQL server running, it could fail to shut down the old server, but also erroneously removed the server's socket file. Now the procedure checks for an existing server package from a different vendor or major MySQL version. In such case, it refuses to install the server and recommends how to safely remove the old packages before installing the new ones. (Bug#28555)

  • mysqlhotcopy silently skipped databases with names consisting of two alphanumeric characters. (Bug#28460)

  • No information was written to the general query log for the COM_STMT_CLOSE, COM_STMT_RESET, and COM_STMT_SEND_LONG_DATA commands. (These occur when a client invokes the mysql_stmt_close(), mysql_stmt_reset() and mysql_stmt_send_long_data() C API functions.) (Bug#28386)

  • Previously, the parser accepted the ODBC { OJ ... LEFT OUTER JOIN ...} syntax for writing left outer joins. The parser now allows { OJ ... } to be used to write other types of joins, such as INNER JOIN or RIGHT OUTER JOIN. This helps with compatibility with some third-party applications, but is not official ODBC syntax. (Bug#28317)

  • The FEDERATED storage engine did not perform identifier quoting for column names that are reserved words when sending statements to the remote server. (Bug#28269)

  • The SQL parser did not accept an empty UNION=() clause. This meant that, when there were no underlying tables specified for a MERGE table, SHOW CREATE TABLE and mysqldump both output statements that could not be executed.

    Now it is possible to execute a CREATE TABLE or ALTER TABLE statement with an empty UNION=() clause. However, SHOW CREATE TABLE and mysqldump do not output the UNION=() clause if there are no underlying tables specified for a MERGE table. This also means it is now possible to remove the underlying tables for a MERGE table using ALTER TABLE ... UNION=(). (Bug#28248)

  • An ORDER BY at the end of a UNION affected individual SELECT statements rather than the overall query result. (Bug#27848)

  • It was possible to exhaust memory by repeatedly running index_merge queries and never performing any FLUSH TABLES statements. (Bug#27732)

  • When utf8 was set as the connection character set, using SPACE() with a non-Unicode column produced an error. (Bug#27580)

    See also Bug#23637.

  • A race condition between killing a statement and the thread executing the statement could lead to a situation such that the binary log contained an event indicating that the statement was killed, whereas the statement actually executed to completion. (Bug#27571)

  • Some queries using the NAME_CONST() function failed to return either a result or an error to the client, causing it to hang. This was due to the fact that there was no check to insure that both arguments to this function were constant expressions. (Bug#27545, Bug#32559)

  • Evaluation of an IN() predicate containing a decimal-valued argument caused a server crash. (Bug#27513, Bug#27362, CVE-2007-2583)

  • With the read_only system variable enabled, CREATE DATABASE and DROP DATABASE were allowed to users who did not have the SUPER privilege. (Bug#27440)

  • The parser rules for the SHOW PROFILE statement were revised to work with older versions of bison. (Bug#27433)

  • resolveip failed to produce correct results for host names that begin with a digit. (Bug#27427)

  • In ORDER BY clauses, mixing aggregate functions and nongrouping columns is not allowed if the ONLY_FULL_GROUP_BY SQL mode is enabled. However, in some cases, no error was thrown because of insufficient checking. (Bug#27219)

  • For the --record_log_pos option, mysqlhotcopy now determines the slave status information from the result of SHOW SLAVE STATUS by using the Relay_Master_Log_File and Exec_Master_Log_Pos values rather than the Master_Log_File and Read_Master_Log_Pos values. This provides a more accurate indication of slave execution relative to the master. (Bug#27101)

  • Memory corruption, a crash of the MySQL server, or both, could take place if a low-level I/O error occurred while an ARCHIVE table was being opened. (Bug#26978)

  • SHOW PROFILE hung if executed before enabling the @@profiling session variable. (Bug#26938)

  • The mysql_insert_id() C API function sometimes returned different results for libmysqld and libmysqlclient. (Bug#26921)

  • Symbolic links on Windows could fail to work. (Bug#26811)

  • mysqld sometimes miscalculated the number of digits required when storing a floating-point number in a CHAR column. This caused the value to be truncated, or (when using a debug build) caused the server to crash. (Bug#26788)

    See also Bug#12860.

  • The default database is no longer changed to NULL (“no database”) if DROP DATABASE for that database failed. (Bug#26704)

  • DROP DATABASE failed for attempts to drop databases with names that contained the legacy #mysql50# name prefix. (Bug#26703)

  • config-win.h unconditionally defined bool as BOOL, causing problems on systems where bool is 1 byte and BOOL is 4 bytes. (Bug#26461)

  • It makes no sense to attempt to use ALTER TABLE ... ORDER BY to order an InnoDB table if there is a user-defined clustered index, because rows are always ordered by the clustered index. Such attempts now are ignored and produce a warning.

    Also, in some cases, InnoDB incorrectly used a secondary index when the clustered index would produce a faster scan. EXPLAIN output now indicates use of the clustered index (for tables that have one) as lines with a type value of index, a key value of PRIMARY, and without Using index in the Extra value. (Bug#26447)

    See also Bug#35850.

  • On Windows, for distributions built with debugging support, mysql could crash if the user typed Control-C. (Bug#26243)

  • When symbolic links were disabled, either with a server startup option or by enabling the NO_DIR_IN_CREATE SQL mode, CREATE TABLE silently ignored the DATA DIRECTORY and INDEX DIRECTORY table options. Now the server issues a warning if symbolic links are disabled when these table options are used. (Bug#25677)

  • CREATE TABLE LIKE did not work when the source table was an INFORMATION_SCHEMA table. (Bug#25629)

  • Attempting to create an index with a prefix on a DECIMAL column appeared to succeed with an inaccurate warning message. Now, this action fails with the error Incorrect prefix key; the used key part isn't a string, the used length is longer than the key part, or the storage engine doesn't support unique prefix keys. (Bug#25426)

  • mysqlcheck -A -r did not correctly identify all tables that needed repairing. (Bug#25347)

  • On Windows, an error in configure.js caused installation of source distributions to fail. (Bug#25340)

  • The Qcache_free_blocks status variable did not display a value of 0 if the query cache was disabled. (Bug#25132)

  • The client library had no way to return an error if no connection had been established. This caused problems such as mysql_library_init() failing silently if no errmsg.sys file was available. (Bug#25097)

  • For Windows 64-bit builds, enabling shared-memory support caused client connections to fail. (Bug#24992)

  • If the expected precision of an arithmetic expression exceeded the maximum precision supported by MySQL, the precision of the result was reduced by an unpredictable or arbitrary amount, rather than to the maximum precision. In some cases, exceeding the maximum supported precision could also lead to a crash of the server. (Bug#24907)

  • mysql did not use its completion table. Also, the table contained few entries. (Bug#24624)

  • Data truncated for column col_num at row row_num warnings were generated for some (constant) values that did not have too high precision. (Bug#24541)

  • If a user installed MySQL Server and set a password for the root user, and then uninstalled and reinstalled MySQL Server to the same location, the user could not use the MySQL Instance Config wizard to configure the server because the uninstall operation left the previous data directory intact. The config wizard assumed that any new install (not an upgrade) would have the default data directory where the root user has no password. The installer now writes a registry key named FoundExistingDataDir. If the installer finds an existing data directory, the key will have a value of 1, otherwise it will have a value of 0. When MySQLInstanceConfig.exe is run, it will attempt to read the key. If it can read the key, and the value is 1 and there is no existing instance of the server (indicating a new installation), the Config Wizard will allow the user to input the old password so the server can be configured. (Bug#24215)

  • Logging of statements to log tables was incorrect for statements that contained utf8-incompatible binary strings. Incompatible sequences are hex-encoded now. (Bug#23924)

  • The MySQL header files contained some duplicate macro definitions that could cause compilation problems. (Bug#23839)

  • A CREATE TRIGGER statement could cause a deadlock or server crash if it referred to a table for which a table lock had been acquired with LOCK TABLES. (Bug#23713)

  • SHOW COLUMNS on a TEMPOARY table caused locking issues. (Bug#23588)

  • For distributions compiled with the bundled libedit library, there were difficulties using the mysql client to enter input for non-ASCII or multi-byte characters. (Bug#23097)

  • perror reported incomplete or inaccurate information. (Bug#23028, Bug#25177)

  • After stopping and starting the event scheduler, disabled events could remain in the execution queue. (Bug#22738)

  • The server produced a confusing error message when attempting to open a table that required a storage engine that was not loaded. (Bug#22708)

  • The parser treated the INTERVAL() function incorrectly, leading to situations where syntax errors could result depending on which side of an arithmetic operator the function appeared. (Bug#22312)

  • For views or stored programs created with an invalid DEFINER value, the error message was confusing (did not tie the problem to the DEFINER clause) and has been improved. (Bug#21854)

  • Warnings for deprecated syntax constructs used in stored routines make sense to report only when the routine is being created, but they were also being reported when the routine was parsed for loading into the execution cache. Now they are reported only at routine creation time. (Bug#21801)

  • On Mac OS X, mysqld did not react to Ctrl-C when run under gdb, even when run with the --gdb option. (Bug#21567)

  • When inserting an extraordinarly large value into a DOUBLE column, the value could be truncated in such a way that the new value cannot be reloaded manually or from the output of mysqldump. (Bug#21497)

  • CREATE ... SELECT did not always set DEFAULT column values in the new table. (Bug#21380)

  • mysql_config output did not include -lmygcc on some platforms when it was needed. (Bug#21158)

  • and were missing from some binary distributions. (Bug#21023, Bug#25486)

  • It was possible to execute CREATE TABLE t1 ... SELECT ... FROM t2 with the CREATE privilege for t1 and SELECT privilege for t2, even in the absence of the INSERT privilege for t1. (Bug#20901)

  • The BENCHMARK() function, invoked with more than 2147483648 iterations (the size of a signed 32-bit integer), terminated prematurely. (Bug#20752)

  • mysqldumpslow returned a confusing error message when no configuration file was found. (Bug#20455)

  • MySQLInstanceConfig.exe could lose the innodb_data_home_dir setting when reconfiguring an instance. (Bug#19797)

  • Issuing an SQL KILL of the active connection caused an error on Mac OS X. (Bug#19723)

  • CREATE TABLE allowed 0 as the default value for a TIMESTAMP column when the server was running in NO_ZERO_DATE mode. (Bug#18834)

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

  • Use of GRANT statements with grant tables from an old version of MySQL could cause a server crash. (Bug#16470)

  • A SET column whose definition specified 64 elements could not be updated using integer values. (Bug#15409)

  • Zero-padding of exponent values was not the same across platforms. (Bug#12860)

  • If a SELECT calls a stored function in a transaction, and a statement within the function fails, that statement should roll back. Furthermore, if ROLLBACK is executed after that, the entire transaction should be rolled back. Before this fix, the failed statement did not roll back when it failed (even though it might ultimately get rolled back by a ROLLBACK later that rolls back the entire transaction). (Bug#12713)

    See also Bug#34655.

  • The grammar for GROUP BY, when used with WITH CUBE or WITH ROLLUP, caused a conflict with the grammar for view definitions that included WITH CHECK OPTION. (Bug#9801)

  • The parser incorrectly allowed SQLSTATE '00000' to be specified for a condition handler. (This is incorrect because the condition must be a failure condition and '00000' indicates success.) (Bug#8759)

  • MySQLInstanceConfig.exe did not save the innodb_data_home_dir value to the my.ini file under certain circumstances. (Bug#6627)

  • RESTORE failed for databases or tables with names that contain certain nonalphanumeric characters, such as spaces. (Bug#3353)

  • Grant table checks failed in libmysqld.

C.1.9. Changes in MySQL 6.0.4 (12 February 2008)

Functionality added or changed:

  • Important Change: Partitioning: Security Fix: It was possible, by creating a partitioned table using the DATA DIRECTORY and INDEX DIRECTORY options to gain privileges on other tables having the same name as the partitioned table. As a result of this fix, any table-level DATA DIRECTORY or INDEX DIRECTORY options are now ignored for partitioned tables. (Bug#32091, CVE-2007-5970)

    See also Bug#29325, Bug#32111.

  • Incompatible Change: The Unicode implementation has been extended to provide support for supplementary characters that lie outside the Basic Multilingual Plane (BMP). Noteworthy features:

    • utf16 and utf32 character sets have been added. These correspond to the UTF-16 and UTF-32 encodings of the Unicode character set, and they both support supplementary characters.

    • The utf8 character set from previous versions of MySQL has been renamed to utf8mb3, to reflect that its encoding uses a maximum of three bytes for multi-byte characters. (Old tables that previously used utf8 will be reported as using utf8mb3 after an in-place upgrade to MySQL 6.0, but otherwise work as before.)

    • The new utf8 character set in MySQL 6.0 is similar to utf8mb3, but its encoding allows up to four bytes per character to enable support for supplementary characters.

    • The ucs2 character set is essentially unchanged except for the inclusion of some newer BMP characters.

    In most respects, upgrading from MySQL 5.1 to 6.0 should present few problems with regard to Unicode usage, although there are some potential areas of incompatibility. Some examples:

    • For the variable-length character data types (VARCHAR and the TEXT types), the maximum length in characters for utf8 columns is less in MySQL 6.0 than previously.

    • For all character data types (CHAR, VARCHAR, and the TEXT types), the maximum number of characters for utf8 columns that can be indexed is less in MySQL 6.0 than previously.

    Consequently, if you want to upgrade tables from the old utf8 (now utf8mb3) to the current utf8, it may be necessary to change some column or index definitions.

    For additional details about the new Unicode character sets and potential incompatibilities, see Section 9.1.9, “Unicode Support”, and Section 9.1.10, “Upgrading from Previous to Current Unicode Support”.

    If you use events, a known issue is that if you upgrade from MySQL 5.1 to 6.0.4 though 6.0.6, the event scheduler will not work, even after you run mysql_upgrade. (This is an issue only for an upgrade, not for a new installation of MySQL 6.0.x.) As of MySQL 6.0.7, mysql_upgrade handles upgrading the system tables properly. If you upgrade to 6.0.4 through 6.0.6, you can work around this upgrading problem by using these instructions:

    1. In MySQL 5.1, before upgrading, create a dump file containing your mysql.event table:

      shell> mysqldump -uroot -p mysql event > event.sql
    2. Stop the server, upgrade to MySQL 6.0, and start the server.

    3. Recreate the mysql.event table using the dump file:

      shell> mysql -uroot -p mysql < event.sql
    4. Run mysql_upgrade to upgrade the other system tables in the mysql database:

      shell> mysql_upgrade -uroot -p
    5. Restart the server. The event scheduler should run normally.

  • Incompatible Change: Because of a change in the format of the Falcon pages stored within Falcon database files, Falcon databases created in MySQL 6.0.4 (or later) are not compatible with previous releases, and existing Falcon databases are incompatible with MySQL 6.0.4 (and later versions. You should dump Falcon databases using mysqldump before upgrading, and then reload them after the upgrade. For more information, see Section 4.5.4, “mysqldump — A Database Backup Program”.

  • MySQL Cluster: Introduced the Ndb_execute_count status variable, which measures the number of round trips made by queries to the NDB kernel.

  • Partitioning: Error messages for partitioning syntax errors have been made more descriptive. (Bug#29368)

  • Cluster Replication: Replication: A replication heartbeat mechanism has been added to facilitate monitoring. This provides an alternative to checking log files, making it possible to detect in real time when a slave has failed.

    Configuration of heartbeats is done via a new MASTER_HEARTBEAT_PERIOD = interval clause for the CHANGE MASTER TO statement (see Section, “CHANGE MASTER TO Syntax”); monitoring can be done by checking the values of the status variables Slave_heartbeat_period and Slave_received_heartbeats (see Section 5.1.7, “Server Status Variables”).

    The addition of replication heartbeats addresses a number of issues:

    (Bug#20435, Bug#29309, Bug#30932)

  • Replication: Replication of the following SQL functions now switches to row-based logging in MIXED mode, and generates a warning in STATEMENT mode:

    See Section, “Mixed Binary Logging Format”, for more information. (Bug#12092, Bug#28086, Bug#30244)

  • The (undocumented) configure script previously included with binary distributions is no longer included. (Bug#35011)

  • The --event-scheduler option without a value disabled the event scheduler. Now it enables the event scheduler. (Bug#31332)

  • mysqldump produces a -- Dump completed on DATE comment at the end of the dump if --comments is given. The date causes dump files for identical data take at different times to appear to be different. The new options --dump-date and --skip-dump-date control whether the date is added to the comment. --skip-dump-date suppresses date printing. The default is --dump-date (include the date in the comment). (Bug#31077)

  • MySQL now can be compiled with gcc 4.2.x. There was a problem involving a conflict with the min() and max() macros in my_global.h. (Bug#28184)

  • Added the --auto-vertical-output option to mysql which causes result sets to be displayed vertically if they are too wide for the current window, and using normal tabular format otherwise. (This applies to statements terminated by ; or \G.) (Bug#26780)

  • It is now possible to set long_query_time in microseconds or to 0. Setting this value to 0 causes all queries to be recorded in the slow query log.

    Currently, fractional values can be used only when logging to files. We plan to provide this functionality for logging to tables when time-related data types are enhanced to support microsecond resolution. (Bug#25412)

  • INFORMATION_SCHEMA implementation changes were made that optimize certain types of queries for INFORMATION_SCHEMA tables so that they execute more quickly. Section 7.2.24, “INFORMATION_SCHEMA Optimization”, provides guidelines on how to take advantage of these optimizations by writing queries that minimize the need for the server to access the file system to obtain the information contained in INFORMATION_SCHEMA tables. By writing queries that enable the server to avoid directory scans or opening table files, you will obtain better performance. (Bug#19588)

  • Three options were added to mysqldump make it easier to generate a dump from a slave server. --dump-slave is similar to --master-data, but the CHANGE MASTER TO statement contains binary log coordinates for the slave's master host, not the slave itself. --apply-slave-statements causes STOP SLAVE and START SLAVE statements to be added before the CHANGE MASTER TO statement and at the end of the output, respectively. --include-master-host-port causes the CHANGE MASTER TO statement to include MASTER_PORT and MASTER_HOST options for the slave's master. (Bug#8368)

  • now supports a --combination option for specifying options to the mysqld server. This option is similar to --mysqld but should be given two or more times. executes multiple test runs, using the options for each instance of --combination in successive runs.

    For test runs specific to a given test suite, an alternative to the use of --combination is to create a combinations file in the suite directory. The file should contain a section of options for each test run.

  • An alternative thread model is available for dealing with the issues that occur with the original one-thread-per-client model when scaling to large numbers of simultaneous connections. This model uses thread pooling:

    • Connection manager threads do not dedicate a thread to each client connection. Instead, the connection is added to the set of existing connection sockets. The server collects input from these sockets and when a complete request has been received from a given client, it is queued for service.

    • The server maintains a pool of service threads to process requests. When a queued request is waiting and there is an available (not busy) service thread in the pool, the request is given to the thread to be handled. After processing the request, the service thread becomes available to process other requests.

      Service threads are created at server startup and exist until the server terminates. A given service thread is not tied to a specific client connection and the requests that it processes over time may originate from different client connections.

    • The pool of service threads has a fixed size, so the amount of memory required for it does not increase as the number of client connections increases.

    For information about choosing one thread model over the other and tuning the parameters that control thread resources, see Section 7.5.7, “How MySQL Uses Threads for Client Connections”.

  • When the server detects MyISAM table corruption, it now writes additional information to the error log, such as the name and line number of the source file, and the list of threads accessing the table. Example: Got an error from thread_id=1, mi_dynrec.c:368. This is useful information to include in bug reports.

  • Two options relating to slow query logging have been added for mysqld. --log-slow-slave-statements causes slow statements executed by a replication slave to be written to the slow query log; min_examined_row_limit can be used to cause queries which examine fewer than the stated number of rows not to be logged.

Bugs fixed:

  • Security Fix: Replication: It was possible for any connected user to issue a BINLOG statement, which could be used to escalate privileges.

    Use of the BINLOG statement now requires the SUPER privilege. (Bug#31611, CVE-2007-6313)

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


    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: Using RENAME TABLE against a table with explicit DATA DIRECTORY and INDEX DIRECTORY options can be used to overwrite system table information by replacing the symbolic link points. the file to which the symlink points.

    MySQL will now return an error when the file to which the symlink points already exists. (Bug#32111, CVE-2007-5969)

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

  • Incompatible Change: The falcon_lock_timeout system variable, which had a value in milliseconds, has been replaced with falcon_lock_wait_timeout, which has a value in seconds. The default value of falcon_lock_wait_timeout is 50 seconds. This has been done for better name and unit consistency with the innodb_lock_wait_timeout system variable. Uses of the old variable should be converted to use the new variable. (Bug#33474, Bug#33072)

  • Incompatible Change: With ONLY_FULL_GROUP_BY SQL mode enabled, queries such as SELECT a FROM t1 HAVING COUNT(*)>2 were not being rejected as they should have been.

    This fix results in the following behavior:

    • There is a check against mixing group and nongroup columns only when ONLY_FULL_GROUP_BY is enabled.

    • This check is done both for the select list and for the HAVING clause if there is one.

    This behavior differs from previous versions as follows:


  • Incompatible Change: SET PASSWORD statements now cause an implicit commit, and thus are prohibited within stored functions and triggers. (Bug#30904)

  • Incompatible Change: The mysql_install_db script could fail to locate some components (including resolveip) during execution if the --basedir option was specified on the command-line or within the my.cnf file. This was due to a conflict when comparing the compiled-in values and the supplied values.

    The --source-install command-line option to the script has been removed and replaced with the --srcdir option. mysql_install_db now locates components either using the compiled-in options, the --basedir option or --srcdir option. (Bug#30759)

  • Incompatible Change: It was possible to create a view having a column whose name consisted of an empty string or space characters only.

    One result of this bug fix is that aliases for columns in the view SELECT statement are checked to ensure that they are legal column names. In particular, the length must be within the maximum column length of 64 characters, not the maximum alias length of 256 characters. This can cause problems for replication or loading dump files. For additional information and workarounds, see Section D.5, “Restrictions on Views”. (Bug#27695)

    See also Bug#31202.

  • Incompatible Change: It was possible for option files to be read twice at program startup, if some of the standard option file locations turned out to be the same directory. Now duplicates are removed from the list of files to be read.

    Also, users could not override system-wide settings using ~/.my.cnf because SYSCONFDIR/my.cnf was read last. The latter file now is read earlier so that ~/.my.cnf can override system-wide settings.

    The fix for this problem had a side effect such that on Unix, MySQL programs looked for options in ~/my.cnf rather than the standard location of ~/.my.cnf. That problem was addressed as Bug#38180. (Bug#20748)

  • Incompatible Change: A number of problems existed in the implementation of MERGE tables that could cause problems. The problems are summarized below:

    • Bug#26379 - Combination of FLUSH TABLE and REPAIR TABLE corrupts a MERGE table. This was caused in a number of situations:

      1. A thread trying to lock a MERGE table performs busy waiting while REPAIR TABLE or a similar table administration task is ongoing on one or more of its MyISAM tables.

      2. A thread trying to lock a MERGE table performs busy waiting until all threads that did REPAIR TABLE or similar table administration tasks on one or more of its MyISAM tables in LOCK TABLES segments do UNLOCK TABLES. The difference against problem #1 is that the busy waiting takes place after the administration task. It is terminated by UNLOCK TABLES only.

      3. Two FLUSH TABLES within a LOCK TABLES segment can invalidate the lock. This does not require a MERGE table. The first FLUSH TABLES can be replaced by any statement that requires other threads to reopen the table. In 5.0 and 5.1 a single FLUSH TABLES can provoke the problem.

    • Bug#26867 - Simultaneously executing LOCK TABLES and REPAIR TABLE on a MERGE table would result in memory/cpu hogging.

      Trying DML on a MERGE table, which has a child locked and repaired by another thread, made an infinite loop in the server.

    • Bug#26377 - Deadlock with MERGE and FLUSH TABLE

      Locking a MERGE table and its children in parent-child order and flushing the child deadlocked the server.

    • Bug#25038 - Waiting TRUNCATE

      Truncating a MERGE child, while the MERGE table was in use, let the truncate fail instead of waiting for the table to become free.

    • Bug#25700 - MERGE base tables get corrupted by OPTIMIZE TABLE, ANALYZE TABLE, or REPAIR TABLE.

      Repairing a child of an open MERGE table corrupted the child. It was necessary to FLUSH the child first.

    • Bug#30275 - MERGE tables: FLUSH TABLES or UNLOCK TABLES causes server to crash.

      Flushing and optimizing locked MERGE children crashed the server.

    • Bug#19627 - temporary merge table locking

      Use of a temporary MERGE table with nontemporary children could corrupt the children.

      Temporary tables are never locked. Creation of tables with nontemporary children of a temporary MERGE table is now prohibited.

    • Bug#27660 - Falcon: MERGE table possible

      It was possible to create a MERGE table with non-MyISAM children.

    • Bug#30273 - MERGE tables: Can't lock file (errno: 155)

      This was a Windows-only bug. Table administration statements sometimes failed with "Can't lock file (errno: 155)".

    The fix introduces the following changes in behavior:

    • This patch changes the behavior of temporary MERGE tables. Temporary MERGE must have temporary children. The old behavior was wrong. A temporary table is not locked. Hence even nontemporary children were not locked. See Bug#19627.

    • You cannot change the union list of a nontemporary MERGE table when LOCK TABLES is in effect. The following does not work:

      ALTER TABLE m1 ... UNION=(t1,t2) ...;

      However, you can do this with a temporary MERGE table.

    • You cannot create a MERGE table with CREATE ... SELECT, neither as a temporary MERGE table, nor as a nontemporary MERGE table. For example, CREATE TABLE m1 ... ENGINE=MRG_MYISAM ... SELECT ...; causes the error message: table is not BASE TABLE.

    (Bug#19627, Bug#25038, Bug#25700, Bug#26377, Bug#26379, Bug#26867, Bug#27660, Bug#30275, Bug#30491)

  • Partitioning: Important Note: An apostrophe or single quote character (') used in the DATA DIRECTORY, INDEX DIRECTORY, or COMMENT for a PARTITION clause caused the server to crash. When used as part of a CREATE TABLE statement, the crash was immediate. When used in an ALTER TABLE statement, the crash did not occur until trying to perform a SELECT or DML statement on the table. In either case, the server could not be completely restarted until the .FRM file corresponding to the newly created or altered table was deleted.


    Upgrading to the current (or later) release solves this problem only for tables that are newly created or altered. Tables created or altered in previous versions of the server to include ' characters in PARTITION options must still be removed by deleting the corresponding .FRM files and re-creating them afterwards.


  • Partitioning: MySQL Cluster: EXPLAIN PARTITIONS reported partition usage by queries on NDB tables according to the standard MySQL hash function than the hash function used in the NDB storage engine. (Bug#29550)

  • Replication: MySQL Cluster: Row-based replication from or to a big-endian machine where the table used the NDB storage engine failed, if the same table on the other machine was either non-NDB or the other machine was little-endian. (Bug#29549, Bug#30790)

    See also Bug#24231, Bug#30024, Bug#30133, Bug#30134.

  • MySQL Cluster: Replication: (Replication): Inconsistencies could occur between the master and the slave when replicating Disk Data tables. (Bug#19259, Bug#19227)

  • MySQL Cluster: An insert or update with combined range and equality constraints failed when run against an NDB table with the error Got unknown error from NDB. An example of such a statement would be UPDATE t1 SET b = 5 WHERE a IN (7,8) OR a >= 10;. (Bug#31874)

  • MySQL Cluster: An error with an if statement in sql/ could potentially lead to an infinite loop in case of failure when working with AUTO_INCREMENT columns in NDB tables. (Bug#31810)

  • MySQL Cluster: The NDB storage engine code was not safe for strict-alias optimization in gcc 4.2.1. (Bug#31761)

  • MySQL Cluster: Following an upgrade, ndb_mgmd would fail with an ArbitrationError. (Bug#31690)

  • MySQL Cluster: It was possible in some cases for a node group to be “lost” due to missed local checkpoints following a system restart. (Bug#31525)

  • MySQL Cluster: A query against a table with TEXT or BLOB columns that would return more than a certain amount of data failed with Got error 4350 'Transaction already aborted' from NDBCLUSTER. (Bug#31482)

    This regression was introduced by Bug#29102.

  • MySQL Cluster: NDB tables having names containing nonalphanumeric characters (such as “ $ ”) were not discovered correctly. (Bug#31470)

  • MySQL Cluster: A node failure during a local checkpoint could lead to a subsequent failure of the cluster during a system restart. (Bug#31257)

  • MySQL Cluster: A cluster restart could sometimes fail due to an issue with table IDs. (Bug#30975)

  • MySQL Cluster: In some cases, the cluster managment server logged entries multiple times following a restart of mgmd. (Bug#29565)

  • MySQL Cluster: ndb_mgm --help did not display any information about the -a option. (Bug#29509)

  • MySQL Cluster: An interpreted program of sufficient size and complexity could cause all cluster data nodes to shut down due to buffer overruns. (Bug#29390)

  • MySQL Cluster: Performing DELETE operations after a data node had been shut down could lead to inconsistent data following a restart of the node. (Bug#26450)

  • MySQL Cluster: UPDATE IGNORE could sometimes fail on NDB tables due to the use of unitialized data when checking for duplicate keys to be ignored. (Bug#25817)

  • MySQL Cluster: The cluster log was formatted inconsistently and contained extraneous newline characters. (Bug#25064)

  • Partitioning: An INSERT into a Falcon table with partitions and an auto-increment column would fail. (Bug#33661)

  • Partitioning: Multiple simultaneous inserts into a partitioned Falcon table could deadlock. (Bug#33480, Bug#33735)

  • Partitioning: Repeated updates of a table that was partitioned by KEY on a TIMESTAMP column eventually crashed the server. (Bug#32067)

  • Partitioning: Selecting from a table partitioned by KEY on a VARCHAR column whose size was greater than 65530 caused the server to crash. (Bug#31705)

  • Partitioning: INSERT DELAYED on a partitioned table crashed the server. The server now rejects the statement with an error. (Bug#31210)

  • Partitioning: Using ALTER TABLE to partition an existing table having an AUTO_INCREMENT column could crash the server. (Bug#30878)

    This regression was introduced by Bug#27405.

  • Partitioning: Falcon cannot drop a table for which there is a pending transaction, but the error message for such attempts was misleading. (Bug#22972)

  • Cluster Replication: Replication: A node failure during replication could lead to buckets out of order; now active subscribers are checked for, rather than empty buckets. (Bug#31701)

  • Replication: When using a transactional storage engine not using statement-based logging, a duplicate key error on the master caused replication to fail. This issue was first observed when using the Falcon storage engine. (Bug#33688)

  • Replication: When updating columns for a row when using a Falcon table, the values for columns that were not updated were replicated as NULL. (Bug#33055)

  • Replication: When dropping a database containing a stored procedure while using row-cased replication, the delete of the stored procedure from the mysql.proc table was recorded in the binary log following the DROP DATABASE statement. To correct this issue, DROP DATABASE now uses statement-based replication. (Bug#32435)

  • Replication: DELETE FROM tbl_name (no WHERE clause) for a Falcon table caused replication to fail on the slave. (Bug#32150)

  • Replication: It was possible for the name of the relay log file to exceed the amount of memory reserved for it, possibly leading to a crash of the server. (Bug#31836)

    See also Bug#28597.

  • Replication: Corruption of log events caused the server to crash on 64-bit Linux systems having 4 GB of memory or more. (Bug#31793)

  • Replication: Trying to replicate an update of a row that was missing on the slave led to a failure on the slave. (Bug#31702)

  • Replication: Falcon tables would fail during replication if ROW-based replication was specified. (Bug#31671)

  • Replication: Table names were displayed as binary “garbage” characters in slave error messages. The issue was observed on 64-bit Windows but may have effected other platforms. (Bug#30854)

  • Replication: One thread could read uninitialized memory from the stack of another thread. This issue was only known to occur in a mysqld process acting as both a master and a slave. (Bug#30752)

  • Replication: A new configuration option, falcon_support_xa has been added. The option specifies whether Falcon should report itself as a two-phase commit storage engine, and therefore take part in XA transactions. (Bug#29371)

  • Replication: It was possible to set SQL_SLAVE_SKIP_COUNTER such that the slave would jump into the middle of an event group, including possibly a transaction. (Bug#28618)

    See also Bug#12691.

  • Replication: Due a previous change in how the default name and location of the binary log file were determined, replication failed following some upgrades. (Bug#28597, Bug#28603)

    See also Bug#31836.

    This regression was introduced by Bug#20166.

  • Replication: Connections from one mysqld server to another failed on Mac OS X, affecting replication and FEDERATED tables. (Bug#26664)

    See also Bug#29083.

  • Replication: Stored procedures having BIT parameters were not replicated correctly. (Bug#26199)

  • Replication: Issuing SHOW SLAVE STATUS as mysqld was shutting down could cause a crash. (Bug#26000)

  • Replication: If a temporary error occured inside an event group on an event that was not the first event of the group, the slave could get caught in an endless loop because the retry counter was reset whenever an event was executed successfully. (Bug#24860)

    See also Bug#12691, Bug#23171.

  • Replication: An UPDATE statement using a stored function that modified a nontransactional table was not logged if it failed. This caused the copy of the nontransactional table on the master have a row that the copy on the slave did not.

    In addition, when an INSERT ... ON DUPLICATE KEY UPDATE statement encountered a duplicate key constraint, but the UPDATE did not actually change any data, the statement was not logged. As a result of this fix, such statements are now treated the same for logging purposes as other UPDATE statements, and so are written to the binary log. (Bug#23333)

    See also Bug#12713.

  • Replication: A replication slave sometimes failed to reconnect because it was unable to run SHOW SLAVE HOSTS. It was not necessary to run this statement on slaves (since the master should track connection IDs), and the execution of this statement by slaves was removed. (Bug#21132)

    See also Bug#13963, Bug#21869.

  • Replication: A replication slave sometimes stopped for changes that were idempotent (that is, such changes should have been considered “safe”), even though it should have simply noted that the change was already done, and continued operation. (Bug#19958)

  • Cluster Replication: A replication slave could return “garbage” data that was not in recognizable row format due to a problem with the internal all_set() method. (Bug#33375)

  • Cluster Replication: Replicating NDB tables with extra VARCHAR columns on the master caused the slave to fail. (Bug#31646)

    See also Bug#29549.

  • Cluster Replication: In some cases, not all tables were properly initialized before the binary log thread was started. (Bug#31618)

  • Cluster API: A buffer overrun in NdbBlob::setValue() caused erroneous results on Mac OS X. (Bug#31284)

  • Setting falcon_consistent_read to a value of 1 or ON resulted in a value of –1 being assigned. (Bug#34331)

  • Compiling MySQL on FreeBSD would fail due to missing definitions for certain network constants. (Bug#34292)

  • The INFORMATION_SCHEMA.FALCON_TRANSACTIONS had two columns named STATE. (Bug#34241)

  • For Falcon, under some circumstances, a rolled back record could appear not to be removed. (Bug#34174)

  • Attempting to set the isolation level to a value not supported by Falcon caused a Falcon assertion failure. (Bug#34164)

  • Falcon did not compile on Mac OS X/Intel or Mac OS X/PPC. (Bug#34095)

  • When inserting very large data sets into table using INSERT INTO ... SELECT FROM on a Falcon table when the value of falcon_page_cache_size is higher than the available memory. Instead of returning an error, mysqld would crash in this instance. (Bug#34086)

  • For Falcon, an initializing transaction created a dependency on a commitNoUpdate transaction releasing transaction dependencies, which caused an assertion failure. (Bug#33759)

  • The output from SHOW CREATE TABLE on a Falcon table would not include the AUTO_INCREMENT value parameters. (Bug#33662)

  • For table creation, Falcon did not handle identifiers with embedded double quotes. (Bug#33657, Bug#33667)

  • Contention between concurrent Falcon transactions could cause some queries to be starved for a long time. (Bug#33634)

  • Incomplete Falcon recovery after server restarts eventually resulted in tablespace corruption. (Bug#33608, Bug#33665)

  • Using falcon_debug_mask to enable debugging messages could lead to some messages not being correctly flushed to the log file. (Bug#33531)

  • Table recovery failed repeatedly after starting the server with a corrupted Falcon tablespace, causing the server to crash. (Bug#33517)

  • After a server restart, Falcon mishandled metadata, resulting in apparent corruption of BLOB data. (Bug#33492)

  • Dropping a tablespace for the Falcon storage engine when the specified tablespace did not exist would silently succeed, instead of generating a suitable error message. (Bug#33212)

  • Multiple concurrent delete operations on a Falcon table were serialized rather than executing concurrently, resulting in poor performance. (Bug#33191)

  • Inserting millions of rows into a Falcon table could cause the insert operation to hang. (Bug#33175)

  • The columns in the INFORMATION_SCHEMA table for FALCON_SERIAL_LOG_INFO, FALCON_TRANSACTIONS, and FALCON_TRANSACTION_SUMMARY contained a reference to the databae of tablespace, but the column information was actually showing instances of the Falcon engine. The tables have been updated to a different structure. (Bug#33141)

  • Using ALTER TABLE to convert a CHAR column using the ucs2 character set to VARBINARY when using a Falcon table would cause a crash. (Bug#33081)

  • Multiple Falcon gopher threads attempting to update the same index could result in failure to add new index entries. (Bug#33080)

  • Falcon tried to delete a record from an empty record locator page, which could cause a server crash. (Bug#33068)

  • Falcon failed to rebuild a Section page during recovery, causing a server crash. (Bug#32921)

  • Using Falcon when accessing multiple versions of the same record, certain records could fail to be retrieved from the record cache, causing an assertion failure. (Bug#32862)

  • Creating an index on a Falcon table with a column using UTF32 that has been converted to UTF8 would cause a server crash. (Bug#32833)

  • Using ALTER TABLE on a Falcon table it would be possible to create two tables with the same name but different case. (Bug#32830)

  • Converting a table from InnoDB to Falcon, where the Falcon table with the same name (but different case) would cause a server crash. (Bug#32829)

  • Concurrent TRUNCATE TABLE operations for Falcon tables caused Falcon to crash. (Bug#32730)

  • mysqld_safe looked for error messages in the wrong location. (Bug#32679)

  • An issue with the NO_ENGINE_SUBSTITUTION sql_mode database can cause the creation of stored routines to fail. If you are having problems with creating stored routines while using this sql_mode value, remove this value from your sql_mode setting. (Bug#32633)

  • Repeatedly creating and dropping Falcon tablespaces failed because the old tablespace was not dropped before the new tablespace file was created. (Bug#32621)

  • Falcon did not properly handle quoted column name or tablespace name identifiers. (Bug#32620)

  • The INTERVAL() function incorrectly handled NULL values in the value list. (Bug#32560)

  • Use of a NULL-returning GROUP BY expression in conjunction with WITH ROLLUP could cause a server crash. (Bug#32558)

    See also Bug#31095.

  • ORDER BY UpdateXML(...) caused the server to crash in queries where UpdateXML() returned NULL. (Bug#32557)

  • Falcon used a fixed index key size which was too small to cope with some Falcon page sizes, leading to a crash. Falcon now supports variable-length index keys according to the supported page sizes. See falcon_page_size. (Bug#32554)

  • The rules for valid column names were being applied differently for base tables and views. (Bug#32496)

  • Falcon options to set the limits of memory usage would not be honored. This could lead to crashes and assertions during normal usage, instead of generating a suitable warning. (Bug#32413)

  • Falcon would incorrectly return the supported repeatable-read level when queried by the Online Backup system, preventing the ability to create a consistent snapshot backup. (Bug#32301)

  • Some uses of user variables in a query could result in a server crash. (Bug#32260)

  • Under certain conditions, the presence of a GROUP BY clause could cause an ORDER BY clause to be ignored. (Bug#32202)

  • On Mac OS X, creating a Falcon table using a new Falcon installation caused a crash. (Bug#32201)

  • Altering a Falcon table to support an auto increment column on a column with existing data and null values would incorrectly update the table and return an incorrect count of the altered rows. (Bug#32194)

  • InnoDB does not support SPATIAL indexes, but could crash when asked to handle one. Now an error is returned. (Bug#32125)

  • The server crashed on optimizations involving a join of INT and MEDIUMINT columns and a system variable in the WHERE clause. (Bug#32103)

  • used the --user option when starting mysqld, which produces warnings if the current user is not root. Now --user is added only for root. (Bug#32078)

  • Inserting, updating and deleting a large number of BLOB records in a Falcon table would take significant amount of time and may prevent shutdown. (Bug#32062)

  • On 64-bit platforms, assignments of values to enumeration-valued storage engine-specific system variables were not validated and could result in unexpected values. (Bug#32034)

  • A DELETE statement with a subquery in the WHERE clause would sometimes ignore an error during subquery evaluation and proceed with the delete operation. (Bug#32030)

  • Using dates in the range '0000-00-01' to '0000-00-99' range in the WHERE clause could result in an incorrect result set. (These dates are not in the supported range for DATE, but different results for a given query could occur depending on position of records containing the dates within a table.) (Bug#32021)

  • User-defined functions are not loaded if the server is started with the --skip-grant-tables option, but the server did not properly handle this case and issued an Out of memory error message instead. (Bug#32020)

  • If a user-defined function was used in a SELECT statement, and an error occurred during UDF initialization, the error did not terminate execution of the SELECT, but rather was converted to a warning. (Bug#32007)

  • In debug builds, testing the result of an IN subquery against NULL caused an assertion failure. (Bug#31884)

  • SHOW CREATE TRIGGER caused a server crash. (Bug#31866)

  • The server crashed after insertion of a negative value into an AUTO_INCREMENT column of an InnoDB table. (Bug#31860)

  • For libmysqld applications, handling of mysql_change_user() calls left some pointers improperly updated, leading to server crashes. (Bug#31850)

  • Comparison results for BETWEEN were different from those for operators like < and > for DATETIME-like values with trailing extra characters such as '2007-10-01 00:00:00 GMT-6'. BETWEEN treated the values as DATETIME, whereas the other operators performed a binary-string comparison. Now they all uniformly use a DATETIME comparison, but generate warnings for values with trailing garbage. (Bug#31800)

  • The server could crash during filesort for ORDER BY based on expressions with INET_NTOA() or OCT() if those functions returned NULL. (Bug#31758)

  • For a fatal error during a filesort in find_all_keys(), the error was returned without the necessary handler uninitialization, causing an assertion failure. (Bug#31742)

  • The examined-rows count was not incremented for const queries. (Bug#31700)

  • The mysql_change_user() C API function was subject to buffer overflow. (Bug#31669)

  • For SELECT ... INTO OUTFILE, if the ENCLOSED BY string is empty and the FIELDS TERMINATED BY string started with a special character (one of n, t, r, b, 0, Z, or N), every occurrence of the character within field values would be duplicated. (Bug#31663)

  • SHOW COLUMNS and DESCRIBE displayed null as the column type for a view with no valid definer. This caused mysqldump to produce a nonreloadable dump file for the view. (Bug#31662)

  • The mysqlbug script did not include the correct values of CFLAGS and CXXFLAGS that were used to configure the distribution. (Bug#31644)

  • For queries for which loose index scan is applicable, the optimizer could choose the wrong execution plan for correlated subqueries. (Bug#31639)

  • Queries that include a comparison of an INFORMATION_SCHEMA table column to NULL caused a server crash. (Bug#31633)

  • EXPLAIN EXTENDED for SELECT from INFORMATION_SCHEMA tables caused an assertion failure. (Bug#31630)

  • A buffer used when setting variables was not dimensioned to accommodate the trailing '\0' byte, so a single-byte buffer overrun was possible. (Bug#31588)

  • For semi-join processing, pullout of functionally dependent tables was not handled transitively. (Bug#31563)

  • HAVING could treat lettercase of table aliases incorrectly if lower_case_table_names was enabled. (Bug#31562)

  • Spurious duplicate-key errors could occur for multiple-row inserts into an InnoDB table that activate a trigger. (Bug#31540)

  • When inserting dates into a DATETIME column with a Falcon, the values would automatically be converted with values between 70 and 99 converted to 1970 to 1999, and values from 00 to 69 converted to 2000 to 2069. These dates are now correctly handled. (Bug#31490)

  • The length of the result from IFNULL() could be calculated incorrectly because the sign of the result was not taken into account. (Bug#31471)

  • Queries that used the ref access method or index-based subquery execution over indexes that have DECIMAL columns could fail with an error Column col_name cannot be null. (Bug#31450)

  • InnoDB now tracks locking and use of tables by MySQL only after a table has been successfully locked on behalf of a transaction. Previously, the locked flag was set and the table in-use counter was updated before checking whether the lock on the table succeeded. A subsequent failure in obtaining a lock on the table led to an inconsistent state as the table was neither locked nor in use. (Bug#31444)

  • SELECT 1 REGEX NULL caused an assertion failure for debug servers. (Bug#31440)

  • INFORMATION_SCHEMA.TABLES was returning incorrect information. (Bug#31381)

  • DROP USER caused an increase in memory usage. (Bug#31347)

  • mysql_install_db failed if the default storage engine was NDB. Now it explicitly uses MyISAM as the storage engine when running mysqld --bootstrap. (Bug#31315)

  • TABLESPACE names within Falcon did not support characters outside the alpha-numeric ASCII character set. (Bug#31311)

  • For InnoDB tables with READ COMMITTED isolation level, semi-consistent reads used for UPDATE statements skipped rows locked by another transaction, rather than waiting for the locks to be released. Consequently, rows that possibly should have been updated were never examined. (Bug#31310)

  • For an almost-full MyISAM table, an insert that failed could leave the table in a corrupt state. (Bug#31305)

  • When dropping Falcon tablespaces the associated tablespace file was not deleted. (Bug#31296)

  • Falcon could crash when the maximum record size was exceeded. (Bug#31286)

  • myisamchk --unpack could corrupt a table that when unpacked has static (fixed-length) row format. (Bug#31277)

  • Building a 64-bit binary with support for the Falcon storage engine using gcc on Solaris could fail. See Section 2.9, “MySQL Installation Using a Source Distribution”, for more information. (Bug#31268, Bug#33126)

  • When a TIMESTAMP with a nonzero time part was converted to a DATE value, no warning was generated. This caused index lookups to assume that this is a valid conversion and was returning rows that match a comparison between a TIMESTAMP value and a DATE keypart. Now a warning is generated so that TIMESTAMP with a nonzero time part will not match DATE values. (Bug#31221)

  • If MAKETIME() returned NULL when used in an ORDER BY that was evaluated using filesort, a server crash could result. (Bug#31160)

  • LAST_INSERT_ID() execution could be handled improperly in subqueries. (Bug#31157)

  • An assertion designed to detect a bug in the ROLLUP implementation would incorrectly be triggered when used in a subquery context with noncacheable statements. (Bug#31156)

  • When creating a TABLESPACE that uses the same name as an existing TABLESPACE, Falcon returned Unknown error -103. MySQL now returns an error stating that the specified tablespace already exists. (Bug#31114)

  • mysqldump failed to handle databases containing a ‘-’ character in the name. (Bug#31113)

  • Starting the server using --read-only and with the Event Scheduler enabled caused it to crash.


    This issue occurred only when the server had been built with certain nonstandard combinations of configure options.


  • Dropping a tablespace and specifying an engine type that does not support tablespaces reported a warning. The response has now been updated to report an error. (Bug#31110)

  • GROUP BY NULL WITH ROLLUP could cause a server crash. (Bug#31095)

    See also Bug#32558.

  • A rule to prefer filesort over an indexed ORDER BY when accessing all rows of a table was being used even if a LIMIT clause was present. (Bug#31094)

  • REGEXP operations could cause a server crash for character sets such as ucs2. Now the arguments are converted to utf8 if possible, to allow correct results to be produced if the resulting strings contain only 8-bit characters. (Bug#31081)

  • Expressions of the form WHERE col NOT IN (col, ...), where the same column was named both times, could cause a server crash in the optimizer. (Bug#31075)

  • Falcon failed to compile on FreeBSD. (Bug#31045)

  • Using ORDER BY with ARCHIVE tables caused a server crash. (Bug#31036)

  • The MOD() function and the % operator crashed the server for a divisor less than 1 with a very long fractional part. (Bug#31019)

  • Using falcon_serial_log_dir to set the location of the Falcon serial log would have no effect. (Bug#31005)

  • The LooseScan subquery optimization strategy could produce duplicate rows in query results. (Bug#30993)

  • A character set introducer followed by a hexadecimal or bit-value literal did not check its argument and could return an ill-formed result for invalid input. (Bug#30986)

  • CHAR(str USING charset) did not check its argument and could return an ill-formed result for invalid input. (Bug#30982)

  • The result from CHAR(str USING ucs2) did not add a leading 0x00 byte for input strings with an odd number of bytes. (Bug#30981)

  • The GeomFromText() function could cause a server crash if the first argument was NULL or the empty string. (Bug#30955)

  • When invoked with constant arguments, STR_TO_DATE() could use a cached value for the format string and return incorrect results. (Bug#30942)

  • GROUP_CONCAT() returned ',' rather than an empty string when the argument column contained only empty strings. (Bug#30897)

  • A server crash could occur if a stored function that contained a DROP TEMPORARY TABLE statement was invoked by a CREATE TEMPORARY TABLE statement that created a table of the same name. (Bug#30882)

  • Calling NAME_CONST() with nonconstant arguments triggered an assertion failure. Nonconstant arguments are now disallowed. (Bug#30832)

  • Running ALTER TABLE ... OPTIMIZE PARTITION on a Falcon table, a 'divide by zero' error would be reported during a server crash. (Bug#30826)

  • For a spatial column with a regular (non-SPATIAL) index, queries failed if the optimizer tried to use the index. (Bug#30825)

  • INFORMATION_SCHEMA.SCHEMATA was returning incorrect information. (Bug#30795)

  • On Windows, the pthread_mutex_trylock() implementation was incorrect. One symptom was that invalidating the query cache could cause a server crash. (Bug#30768)

  • A multiple-table UPDATE involving transactional and nontransactional tables caused an assertion failure. (Bug#30763)

  • Under some circumstances, CREATE TABLE ... SELECT could crash the server or incorrectly report that the table row size was too large. (Bug#30736)

  • Using the MIN() or MAX() function to select one part of a multi-part key could cause a crash when the function result was NULL. (Bug#30715)

  • INFORMATION_SCHEMA.VIEWS.VIEW_DEFINITION was incorrect for views that were defined to select from other INFORMATION_SCHEMA tables. (Bug#30689)

  • Issuing an ALTER SERVER statement to update the settings for a FEDERATED server would cause the mysqld to crash. (Bug#30671)

  • The optimizer could ignore ORDER BY in cases when the result set is ordered by filesort, resulting in rows being returned in incorrect order. (Bug#30666)

  • A different execution plan was displayed for EXPLAIN than would actually have been used for the SELECT because the test of sort keys for ORDER BY did not consider keys mentioned in IGNORE KEYS FOR ORDER BY. (Bug#30665)

  • MyISAM tables could not exceed 4294967295 (2^32 - 1) rows on Windows. (Bug#30638)

  • could not run mysqld with root privileges. (Bug#30630)

  • Using GROUP BY on an expression of the form timestamp_col DIV number caused a server crash due to incorrect calculation of number of decimals. (Bug#30587)

  • The options available to the CHECK TABLE statement were also allowed in OPTIMIZE TABLE and ANALYZE TABLE statements, but caused corruption during their execution. These options were never supported for these statements, and an error is now raised if you try to apply these options to these statements. (Bug#30495)

  • When expanding a * in a USING or NATURAL join, the check for table access for both tables in the join was done using only the grant information of the first table. (Bug#30468)

  • Compared to MySQL 5.1, the 6.0 optimizer failed to use join buffering for certain queries, resulting in slower performance for those queries. (Bug#30363)

  • A table-access check was performed improperly by libmysqld, causing a crash. (Bug#30329)

  • Some valid euc-kr characters having the second byte in the ranges [0x41..0x5A] and [0x61..0x7A] were rejected. (Bug#30315)

  • When loading a dynamic plugin on FreeBSD, the plugin would fail to load. This was due to a build error where the required symbols would be not exported correctly. (Bug#30296)

  • Setting certain values on a table using a spatial index could cause the server to crash. (Bug#30286)

  • It was not possible for client applications to distinguish between auto-set and auto-updated TIMESTAMP column values.

    To rectify this problem, a new ON_UPDATE_NOW_FLAG flag is set by Field_timestamp constructors whenever a column should be set to NOW on UPDATE, and the get_schema_column_record() function now reports whether a timestamp column is set to NOW on UPDATE. In addition, such columns now display on update CURRENT_TIMESTAMP in the Extra column in the output from SHOW COLUMNS. (Bug#30081)

  • Some INFORMATION_SCHEMA tables are intended for internal use, but could be accessed by using SHOW statements. (Bug#30079)

  • On some 64-bit systems, inserting the largest negative value into a BIGINT column resulted in incorrect data. (Bug#30069)

  • mysqlslap did not properly handle multiple result sets from stored procedures. (Bug#29985)

  • Running the sqlbench test suite against Falcon would cause a crash. (Bug#29870)

  • When accessing the statistics in INFORMATION_SCHEMA.FALCON_DATABASE_IO, the information related only to the Falcon database, and not to user tablespaces. The output has been updated to report on all tablespaces, and the DATABASE column has been renamed to TABLESPACE to reflect the fact that these statistics are now reported by tablespace, not by database. (Bug#29823)

  • Whitespace characters other than spaces within XML tags, such as linefeeds or tabs, caused LOAD XML INFILE to skip rows. (Bug#29752)

  • configure did not find nss on some Linux platforms. (Bug#29658)

  • Compilation failed on systems where a native log2() implementation was unavailable. (Bug#29640)

  • Use of the latin2_czech_cs collation caused a server crash. (Bug#29459)

  • Using two simultaneous connections it was possible to create a deadlock situation between two different active transactions on the same Falcon table. There is no way to prevent this, but a new parameter, falcon_lock_timeout can set the timeout for deadlocked transactions. The default timeout is 0 (timeouts are disabled). (Bug#29452)

  • The mysql client program now ignores Unicode byte order mark (BOM) characters at the beginning of input files. Previously, it read them and sent them to the server, resulting in a syntax error.

    Presence of a BOM does not cause mysql to change its default character set. To do that, invoke mysql with an option such as --default-character-set=utf8. (Bug#29323)

  • Inserting information into the same table from multiple threads could cause duplicate key errors. This was related to the changes made to allow compatibility with the InnoDB repeatable-read isolation level. The option, falcon_innodb_compatibility, has been renamed to falcon_consistent_read, but with the opposite effect. The default is for this option to be on. When set to off, the behavior of Falcon is similar to that in InnoDB. (Bug#29151)

  • For transactional tables, an error during a multiple-table DELETE statement did not roll back the statement. (Bug#29136)

  • The log and log_slow_queries system variables were displayed by SHOW VARIABLES but could not be accessed in expressions as @@log and @@log_slow_queries. Also, attempting to set them with SET produced an incorrect Unknown system variable message. Now these variables are treated as synonyms for general_log and slow_query_log, which means that they can be accessed in expressions and their values can be changed with SET. (Bug#29131)

  • When loading large data sets using LOAD DATA INFILE into a Falcon table, the server could crash. (Bug#29081)

  • SHOW VARIABLES did not display the relay_log, relay_log_index, or relay_log_info_file system variables. (Bug#28893)

  • Index hints specified in view definitions were ignored when using the view to select from the base table. (Bug#28702)

  • Views do not have indexes, so index hints do not apply. Use of index hints when selecting from a view is now disallowed. (Bug#28701)

  • After changing the SQL mode to a restrictive value that would make already-inserted dates in a column be considered invalid, searches returned different results depending on whether the column was indexed. (Bug#28687)

  • The result from CHAR() was incorrectly assumed in some contexts to return a single-byte result. (Bug#28550)

  • Using a temporary table within Falcon that is created in a directory where the path contains a mixture of upper and lower letters would fail. (Bug#28541)

  • Under heavy load when updating Falcon tables, a race condition could occur that would ultimately result in a crash. (Bug#28519)

  • The result of a comparison between VARBINARY and BINARY columns differed depending on whether the VARBINARY column was indexed. (Bug#28076)

  • The metadata in some MYSQL_FIELD members could be incorrect when a temporary table was used to evaluate a query. (Bug#27990)

  • ALTER TABLE tbl_name ROW_FORMAT=format_type did not cause the table to be rebuilt. (Bug#27610)

  • Searching a Falcon table that uses DATETIME columns with an index could return incorrect results. (Bug#27426)

  • Removing a partition on a Falcon table when there are two tables with the same name, but different case, would cause a crash during normal shutdown. (Bug#27425)

  • Mixing differently cased tables between MyISAM and Falcon tables would cause a crash. (Bug#27424)

  • The ExtractValue() and UpdateXML() functions performed extremely slowly for large amounts of XML data (greater than 64 KB). These functions now execute approximately 2000 times faster than previously. (Bug#27287)

  • On Windows, writes to the debug log were using freopen() instead of fflush(), resulting in slower performance. (Bug#27099)

  • The MySQL Instance Configuration Wizard would not allow you to choose a service name, even though the criteria for the service name were valid. The code that checks the name has been updated to support the correct criteria of any string less than 256 character and not containing either a forward or backward slash character. (Bug#27013)

  • LOAD DATA INFILE ran very slowly when reading large files into partitioned tables. (Bug#26527)

  • Threads that were calculating the estimated number of records for a range scan did not respond to the KILL statement. That is, if a range join type is possible (even if not selected by the optimizer as a join type of choice and thus not shown by EXPLAIN), the query in the statistics state (shown by the SHOW PROCESSLIST) did not respond to the KILL statement. (Bug#25421)

  • For mysql --show-warnings, warnings were in some cases not displayed. (Bug#25146)

  • Using CREATE UNIQUE INDEX on a Falcon table where rows contain duplicate values could result in pending transactions to the table being deleted. (Bug#22842)

  • Creating a Falcon table with an auto-increment column that is not indexed as the first column in a multi-column index would auto-increment. This behavior was different to the behavior in both MyISAM and InnoDB. Falcon now rejects such tables during creation in the same way InnoDB does. (Bug#22564)

  • For storage engines that do not redefine handler::index_next_same() and are capable of indexes, statements that include a WHERE clause might select incorrect data. (Bug#22351)

  • Creating a new table or dropping a database on a newly created Falcon database or tablespace raised an error. (Bug#22199)

  • Using TRUNCATE on a Falcon table did not reset the auto-increment counters and used an inefficient method of deleting existing data. (Bug#22173)

  • Creating a DATE outside the normal range within a Falcon table would result in a zero DATE value being returned, even though normally invalid values would be stored correctly in other storage engines. (Bug#22168)

  • Selecting information from a Falcon table using a DOUBLE column with an index would produce incorrect results. (Bug#22125)

  • The readline library has been updated to version 5.2. This addresses issues in the mysql client where history and editing within the client would fail to work as expected. (Bug#18431)

  • mysql stripped comments from statements sent to the server. Now the --comments or --skip-comments option can be used to control whether to retain or strip comments. The default is --skip-comments. (Bug#11230, Bug#26215)

  • Executing DISABLE KEYS and ENABLE KEYS on a nonempty table would cause the size of the index file for the table to grow considerable. This was because the DISABLE KEYS operation would only mark the existing index, without deleting the index blocks. The ENABLE KEYS operation would re-create the index, adding new blocks, while the previous index blocks would remain. Existing indexes are now dropped and recreated when the ENABLE KEYS statement is executed. (Bug#4692)

C.1.10. Changes in MySQL 6.0.3 (16 November 2007)

Functionality added or changed:

  • Incompatible Change: Aliases for wildcards (as in SELECT t.* AS 'alias' FROM t) are no longer accepted and result in an error. Previously, such aliases were ignored silently. (Bug#27249)

  • Sinhala collations utf8_sinhala_ci and ucs2_sinhala_ci were added for the utf8 and ucs2 character sets. (Bug#26474)

  • If the value of the --log-warnings option is greater than 1, the server now writes access-denied errors for new connection attempts to the error log (for example, if a client user name or password is incorrect). (Bug#25822)

  • Added the PARAMETERS table to INFORMATION_SCHEMA. The PARAMETERS table provides information about stored function and procedure parameters, and about return values for stored functions.

Bugs fixed:

  • Incompatible Change: DROP TABLE now is allowed only if you have acquired a WRITE lock with LOCK TABLES, or if you hold no locks, or if the table is a TEMPORARY table.

    Previously, if other tables were locked, you could drop a table with a read lock or no lock, which could lead to deadlocks between clients. The new stricter behavior means that some usage scenarios will fail when previously they did not. (Bug#25858)

  • Incompatible Change: GRANT and REVOKE statements now cause an implicit commit, and thus are prohibited within stored functions and triggers. (Bug#21975, Bug#21422, Bug#17244)

  • MySQL Cluster: Adding a new TINYTEXT column to an NDB table which used COLUMN_FORMAT = DYNAMIC, and when binary logging was enabled, caused all cluster mysqld processes to crash. (Bug#30213)

  • MySQL Cluster: After adding a new column of one of the TEXT or BLOB types to an NDB table which used COLUMN_FORMAT = DYNAMIC, it was no longer possible to access or drop the table using SQL. (Bug#30205)

  • The server crashed on optimization of queries that compared an indexed DECIMAL column with a string value. (Bug#32262)

  • The server crashed on optimizations that used the range checked for each record access method. (Bug#32229)

  • When comparing a BLOB value that was null, memory corruption could occur casuing the server to crash. (Bug#32191)

  • Deleting a large number of records could sometimes take a significant amount of time. (Bug#27946)

  • Several buffer-size system variables were either being handled incorrectly for large values (for settings larger than 4GB, they were truncated to values less than 4GB without a warning), or were limited unnecessarily to 4GB even on 64-bit systems. The following changes were made:

    In addition, settings for read_buffer_size and read_rnd_buffer_size are limited to 2GB on all platforms. Larger values are truncated to 2GB with a warning. (Bug#5731, Bug#29419, Bug#29446)

C.1.11. Changes in MySQL 6.0.2 (04 September 2007)

Functionality added or changed:

Bugs fixed:

  • An assertion could be thrown during high number of concurrent updates of BLOB fields. (Bug#30463)

  • When loading large data sets into a Falcon table mysqld could crash. An Out of memory error will now be raised in this situation. (Bug#30251, Bug#30074)

  • Falcon would incorrectly allow creation of two tables with the same name but different case sensitivity, without raising an error, but treat the two tables as the same during further queries. . (Bug#30210)

  • Updating a large table without an index would lock all the records during a transaction and unlock the records individually. (Bug#30124)

  • Creating a tablespace with a unique name but using the same data file as an existing tablespace results in the re-initialization of the tablespace and the loss of the data contained in it. Falcon now reports an error if the data file already exists. (Bug#29511)

  • Using SELECT on a table that uses two INT columns with a single index would fail to return rows that queried both columns and complex comparison operators. (Bug#29319)

  • Falcon could occasionally report a problem with a duplicate key error during INSERT when inserting the same data into a unique column on two or more connections simultaneously. (Bug#29240)

  • Inserting into a table with a unique index simultaneously on two connections in a way that would cause a deadlock would cause MySQL to hang. The deadlock situation is now identified and an error will be raised. (Bug#29206)

  • Wide DECIMAL columns would show rounding errors during SELECT. (Bug#29201)

  • Some Falcon variables were marked as status variables. (Bug#29169)

  • Accessing an INFORMATION_SCHEMA table generated by Falcon, when Falcon has not been enabled would cause mysqld to crash. (Bug#29014)

  • For debug builds, the server crashed when inserting a negated DECIMAL value of maximum precision (65 digits), such as for INSERT INTO ... SELECT -col_val ... (Bug#28810)

  • Accessing data within DECIMAL columns wider than 18 digits would cause a crash. (Bug#28725)

  • mysqld would crash after a high number of ALTER TABLE, INSERT and UPDATEstatements. (Bug#28515, Bug#22154)

  • Unique indexes on VARCHAR columns are not identified correctly. (Bug#28500)

  • Under certain situations the Falcon tables and log could become corrupt and prevent recovery from a crashed version of the files. (Bug#28351)

  • The value for FALCON_SYSTEM_MEMORY_SUMMARY.TOTAL_SPACE in INFORMATION_SCHEMA would be reported incorrectly. (Bug#28197)

  • Searching for rows within a table with some nonwestern character sets would fail to return the right results if the SELECT relied on an index. (Bug#27697)

  • Inserting large numbers of identical columns into a table, followed by a SELECT or UPDATE could cause a hang or crash. (Bug#27277)

  • Loading certain data sets through a direct import could cause index problems and crash. (Bug#26930)

  • DECIMAL columns with large widths did not work, either during INSERT or SELECT. (Bug#26607)

  • DELETE statements could cause a crash when many simultaneous threads are running. (Bug#26475)

  • Falcon would fail to build under Mac OS X/Intel. A preliminary patch is available to allow building under Mac OS X/Intel only (PowerPC support is not yet available). Note that Mac OS X/Intel is still an unsupported platform. (Bug#26466)

  • Queries could fail with a Can't find record in ... error. (Bug#26328)

  • Under certain situations, shutting down MySQL using mysqladmin could cause Falcon to corrupt the database tables and fail to restart properly. (Bug#26296)

  • Searches for accented characters in a UTF8 table fail if an index exists for the column. (Bug#26057)

  • Searches using LIKE on a UTF8 table fail if the search relies an indexed column. (Bug#24921)

  • Searches for data on a partial index for a column using the UTF8 character set would fail. (Bug#24858)

  • Searches for data using exotic collation/character sets fail if the search relies on an indexed column. (Bug#23689)

  • Inserting rows to a table with a unique index where the unique index value is identical on two separate connections would block the second transaction. (Bug#22847)

  • Renaming a database would raise error ERROR 1030 (HY000): Got error 157 from storage engine. (Bug#22182)

  • Large inserts to a table within a single transaction trigger high memory usage and may ultimately crash. (Bug#22169)

  • Renaming tables to or from Falcon tablespaces raised an error. (Bug#22155)

C.1.12. Changes in MySQL 6.0.1 (Not released)

This was an internal release only, and no binaries were published.

C.1.13. Changes in MySQL 6.0.0 (30 April 2007 Alpha)

Functionality added or changed:

  • SELECT ... FOR UPDATE is now supported.

  • Uncommitted record scavenging has been implemented.

  • Performance diagnostics are available through INFORMATION_SCHEMA.

Bugs fixed:

  • Using SELECT ... FOR UPDATE and ROLLBACK could cause mysqld to hang indefinitely. (Bug#28165)

  • Concurrent updates on two different connections could lead to an assertion failure. (Bug#28090)

  • Updating a row within a table that has a unique compound index to a nonunique value would not raise an error. (Bug#27997)

  • Rolling back an inserted row while accessing the same on a different connection would cause a crash. (Bug#27993)

  • Creating a table with a 19 digit DECIMAL column would cause incorrect data to be stored. This is due to current limitation in Falcon where you cannot create a table with a column with greater than 18 digits precision (for example, DECIMAL(18,9)). Creating a column with larger than this specification will fail and raise an error. (Bug#27962)

  • Executing INSERT INTO ... SELECT FROM could cause a crash on large data sets. (Bug#27951)

  • Inserting data into the same table on two different connections with autocommit disabled would cause a crash. (Bug#27895)

  • Creating a Falcon table immediately after creating a new database could cause a crash. (Bug#27768)

  • Executing SELECT ... FOR UPDATE in a second connection on a newly created and populated table could cause a crash. (Bug#27767)

  • Continually updating a BLOB column would cause MySQL server to crash. (Bug#27719)

  • Using a trigger on an UPDATE to a Falcon table when autocommit is disabled would cause MySQL server to crash. (Bug#27574)

  • Interrupting a stored procedure during execution could cause a crash. (Bug#27539)

  • Opening the same database with Falcon tables on a different connection could cause a crash. (Bug#27428)

  • Using ROLLBACK after a DELETE does not restore the deleted row. (Bug#27357)

  • Two simultaneous SELECT ... FOR UPDATE statements with READ COMMITTED isolation level would result in the wrong error message being returned. (Bug#26871)

  • Row insertions to a table with long VARCHAR columns and large compound indexes would cause MySQL to crash. (Bug#26850)

  • Falcon could consume large amounts of memory during a high number of continuous INSERT statements. (Bug#26843)

  • Updating a partitioned table in two sessions simultaneously would cause MySQL to crash. (Bug#26828)

  • Locking between sessions when using SELECT ... FOR UPDATE would not work. (Bug#26826)

  • Tables with UNIQUE key constraints would not be enforced. (Bug#26803)

  • When updating a table with a unique key constraint the constraint would not be enforced. (Bug#26802)

  • Searching for records in a table with a DECIMAL(6,6) column would fail to find the value. (Bug#26469)

  • Rows with a numeric column may fail to find records with zero values. (Bug#26468)

  • Retrieving rows from a table that used an index would sometimes fail to return the row. (Bug#26452)

  • Continue handlers in stored procedures could cause a crash. (Bug#26433)

  • Tables with a long multi-column index may fail to find a record for UPDATE. (Bug#26420)

  • Updating BLOB columns could result in a crash. (Bug#26324)

  • Deleting a large quantity of rows in a single table may result in ERROR 1020. (Bug#26055)

  • A DROP TABLE statement on a table created using CREATE TABLE ... SELECT ... crashed the server. (Bug#25564)

  • Random updates of LONG VARCHAR columns would fail. (Bug#23818)

  • Running SELECT after a changing the table contents does not result in a new data set. (Bug#22181)

  • Using ALTER TABLE with interleaving transactions could cause mysqld to crash. (Bug#22165)

C.2. Changes in Release 5.2.x (Development)

MySQL 5.2 was merged into MySQL 6.0. An overview of which features were added in MySQL 5.2 and MySQL 6.0 can be found here: Section 1.4.1, “What Is New in MySQL 6.0”.

For a full list of changes, please refer to the changelog sections for each individual 5.2.x release.

C.2.1. Changes in MySQL 5.2.5 (08 August 2007)

This is a new Alpha development release, fixing recently discovered bugs.


This Alpha release, as any other pre-production release, should not be installed on production level systems or systems with critical data. It is good practice to back up your data before installing any new version of software. Although MySQL has worked very hard to ensure a high level of quality, protect your data by making a backup as you would for any software beta release. Please refer to our bug database at for more details about the individual bugs fixed in this version.

This section documents all changes and bug fixes that have been applied since the last official MySQL release. If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Network (a commercial MySQL offering). For more details please see

Functionality added or changed:

  • Incompatible Change: The obsolete constructs in the following table have been removed. Use the equivalents shown in the table's second column instead. Existing applications that depend on the obsolete constructs should be converted to make use of the current equivalents as soon as possible.

    @@table_type @@storage_engine
    @@log_bin_trust_routine_creators @@log_bin_trust_function_creators
    TIMESTAMP(N) See Section 11.6, “Date and Time Functions”.
    BACKUP TABLE mysqldump, mysqlhotcopy, or MySQL Administrator
    RESTORE TABLE, LOAD TABLE FROM MASTER mysqldump, mysql, or MySQL Administrator
    --master-xxx options to set replication parameters: --master-host, --master-user, --master-password , --master-port, --master-connect-retry, --master-ssl, --master-ssl-ca, --master-ssl-capath, --master-ssl-cert, --master-ssl-cipher, --master-ssl-key CHANGE MASTER TO
  • MySQL Cluster: It is now possible to control whether fixed-width or variable-width storage is used for a given column of an NDB table by means of the COLUMN_FORMAT specifier as part of the column's definition in a CREATE TABLE or ALTER TABLE statement.

    It is also possible to control whether a given column of an NDB table is stored in memory or on disk, using the STORAGE specifier as part of the column's definition in a CREATE TABLE or ALTER TABLE statement.

    For permitted values and other information about COLUMN_FORMAT and STORAGE, see Section 12.1.14, “CREATE TABLE Syntax”.

  • The INFORMATION_SCHEMA.COLUMNS table now has STORAGE and FORMAT columns. For NDB tables, STORAGE indicates whether a column is stored on disk or memory, and FORMAT indicates the column storage format (FIXED, DYNAMIC, or DEFAULT).

  • The INFORMATION_SCHEMA.STATISTICS table now has an INDEX_COMMENT column to indicate any comment string provided for the column. The SHOW INDEX statement now displays an Index_comment column that provides the same information.

  • The LOAD XML INFILE statement was added. This statement makes it possible to read data directly from XML files into database tables. For more information, see Section 12.2.7, “LOAD XML Syntax”.

Bugs fixed:

  • Use of the latin2_czech_cs collation caused a server crash. (Bug#29459)

C.2.2. Changes in MySQL 5.2.4 (Not released)

This is a new Alpha development release, fixing recently discovered bugs.


This Alpha release, as any other pre-production release, should not be installed on production level systems or systems with critical data. It is good practice to back up your data before installing any new version of software. Although MySQL has worked very hard to ensure a high level of quality, protect your data by making a backup as you would for any software beta release. Please refer to our bug database at for more details about the individual bugs fixed in this version.

This section documents all changes and bug fixes that have been applied since the last official MySQL release. If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Network (a commercial MySQL offering). For more details please see

Functionality added or changed:

  • Incompatible Change: Added the optimizer_use_mrr system variable to enable control over whether Multi-Range Read optimization is used. This replaces the multi_range_count system variable, which has been removed.

  • The syntax for the LOCK TABLES statement has been extended to support transactional table locks that do not commit transactions automatically. Following LOCK TABLES ... IN SHARE MODE or LOCK TABLES ... IN EXCLUSIVE MODE, you can access tables not mentioned in the LOCK TABLES statement. You can now also issue these extended LOCK TABLES statements many times in succession, adding additional tables to the locked set, and without unlocking any tables that were locked previously. When using LOCK TABLES with IN SHARE MODE or IN EXCLUSIVE MODE, tables are not unlocked until the transaction is committed.

    The behavior of LOCK TABLES when not using IN SHARE MODE or IN EXCLUSIVE MODE remains unchanged.

  • A new SQL function, WEIGHT_STRING(), returns the weight string for an input string. The weight string represents the sorting and comparison value of the input string.

  • Added the optimizer_switch system variable to enable control over individual optimizations.

  • The maximum length of table comments was extended from 60 to 2048 characters. The maximum length of column comments was extended from 255 to 1024 characters. Index definitions now can include a comment of up to 1024 characters.

  • Parser performance was improved for identifier scanning and conversion of ASCII string literals.

C.2.3. Changes in MySQL 5.2.3 (15 February 2007)

Bugs fixed:

  • MySQL would crash with an assertion on startup during recovery referring to tc.log. (Bug#26161)

  • A crash would occur when running UPDATE within a loop inside a stored procedure. (Bug#25537)

C.2.4. Changes in MySQL 5.2.2 (Not released)

Bugs fixed:

  • MySQL would fail with an assertion on startup. (Bug#25835)

C.2.5. Changes in MySQL 5.2.1 (Not released Alpha)

Functionality added or changed:

  • Performance improvements: thread bottlenecks have been reduced when a larger number of parallel auto-commit threads executed a trivial query in a hard loop.

Bugs fixed:

C.3. MySQL Enterprise Monitor Change History

This appendix lists the changes to the MySQL Enterprise Monitor, beginning with the most recent release. Each release section covers added or changed functionality, bug fixes, and known issues, if applicable. All bug fixes are referenced by bug number and include a link to the bug database. Bugs are listed in order of resolution. To find a bug quickly, search by bug number.

C.3.1. Changes in MySQL Enterprise Monitor 2.0.6 (Not yet released)

This section documents all changes and bug fixes that have been applied since the release of MySQL Enterprise Monitor, version 2.0.5.

Bugs fixed:

  • An error was generated when an attempt was made to rename a Replication Group to one that had previously been deleted. (Bug#43846)

  • A new topology was not discovered after the previous replication group was renamed. (Bug#43815)

  • On Unix systems, executing the command:

    ./ stop

    did not make sure that mysqld was shutdown before finishing.

    This resulted in a situation such as the following:

    # /opt/mysql/enterprise/monitor- stop
    Using CATALINA_BASE:   /opt/mysql/enterprise/monitor/apache-tomcat
    Using CATALINA_HOME:   /opt/mysql/enterprise/monitor/apache-tomcat
    Using CATALINA_TMPDIR: /opt/mysql/enterprise/monitor/apache-tomcat/temp
    Using JRE_HOME:       /opt/mysql/enterprise/monitor-
    Stopping tomcat service ... [ OK ]
    /opt/mysql/enterprise/monitor- : mysql stopped

    However, running the following command a few minutes later showed that the MySQL server was still running:

    # /opt/mysql/enterprise/monitor- status
    MySQL Network MySQL is running
    MySQL Network Tomcat is not running


  • The MySQL Enterprise Monitor upgrade installer incorrectly replaced the AdvisorScript.jar in <instDir>/apache-tomcat/webapps/ROOT/WEB-INF/lib/ with the default Advisor JAR. (Bug#43773)

  • The agent created the mysql.inventory table with an engine type of InnoDB, instead of MyISAM, when InnoDB was specified as the default engine type in my.cnf. This happened because the agent did not explicitly specify the table engine type to be of MyISAM. (Bug#43551)

  • If a host was not a slave during the initial discovery phase, then it would not be displayed in the Replication tab if it subsequently became a slave.

    This was because after the initial discovery phase, if a host did not have slavestatus present, no subsequent checks were made to check for the host being a slave. It was therefore missed for the purposes of replication discovery and never showed in the Replication tab. (Bug#42997)

C.3.2. Changes in MySQL Enterprise Monitor 2.0.5 (18th March 2009)

This section documents all changes and bug fixes that have been applied since the release of MySQL Enterprise Monitor, version 2.0.4.

Bugs fixed:

  • The FreeBSD 7 Agent was inadvertently a Linux binary.

    shell> file mysqlmonitoragent-
    mysqlmonitoragent- ELF 32-bit LSB executable,
    Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs),


  • Calling the Agent with the option --agent-run-os-tests resulted in a crash. This happened on Linux x86-64 systems. The resultant stack trace was:

    2009-03-04 16:39:42: (critical) chassis.c:1097: could not raise RLIMIT_NOFILE to 8192,
    Invalid argument (22). Current limit still 1024.
    sigar-test-all.c.124 (test_sigar_pid_get):
      pid = 5188
    sigar-test-all.c.106 (test_sigar_mem_get):
    sigar-test-all.c.427 (test_sigar_file_system_list_get): (items = 13)
      fs.dirname = /
      fs.devname = /dev/mapper/vg00-root
      fs.typename = local
      fs.sys-type-name = ext3
      fs.type = 2 = 15481840 = 14116140
      fsusage.used = 1365700
      fsusage.avail = 13329708
      fsusage.files = 1966080
      fsusage.use_percent = 0.100000
      diskusage.reads = 315302
      diskusage.writes = 6318240
      diskusage.write_bytes = 25879511040
      diskusage.read_bytes = 6561092608
      diskusage.queue = 47457530080206
    Segmentation fault

    On some systems no output was shown, other than the message “Segmentation fault”. (Bug#43381)

  • Following a change in the replication configuration, MySQL Enterprise Monitor did not display the new topology correctly. (Bug#43240)

  • When a data collection became invalid, the agent sent NULLs for those collection values. However, the timestamps that it sent with the values were the timestamps from the last valid value that was collected.

    Due to key constraints on the Service Manager side, MySQL Enterprise Monitor disregarded anything sent with duplicate timestamps, thus the NULLs received from the agent were never processed. Some mechanisms, such as replication discovery, depend on the NULLs to identify a situation where data has become invalid. (Bug#43239)

  • MySQL Enterprise Monitor did not add a log entry each time data was purged. The log entry should have noted how many rows of each type of data were purged (historical data, logs, quan data). (Bug#43159)

  • MySQL Enterprise Monitor generated a stack overflow. This was as a result of a bug in Hibernate, which caused Hibernate to enter infinite recursion while trying to load a relationship. (Bug#43107)

  • The “Table Cache Set Too Low For Startup” and “Table Cache Not Optimal” rules were not supported on MySQL 5.1 because the table_cache system variable was deprecated and replaced with table_open_cache. (Bug#42663)

  • Migrated server was not completely deleted.

    In a Monitor that had been updated from 1.3.2 to 2.0.4, with 2 database servers queued for migration, if a server being migrated was deleted, or a migrated server was deleted, this would not be reflected in the user interface or in the license count, until Tomcat was restarted. (Bug#42604)

  • The installer used to upgrade from version 1.3 corrupted passwords containing the “?” character. (Bug#42452)

  • The replication status of a server was displayed as “unknown”. However, the agent logged no errors and the server showed no other event problems. The server status was displayed as “up” and the database connection was also displayed as “up”. (Bug#42407)

  • Sun multi-core processors caused all cores to be reported on the meta information page.

    The larger T-series SPARC processors have 32+ cores. This caused the meta information page in the Dashboard to scroll as it reported each one. (Bug#42355)

  • If an attempt was made to disable a rule using the link next to the rule, the following error message was generated:

    U0002 You must log in to access the requested resource. Go to login page.

    However, clicking on the link did not prompt the user to login again. (Bug#42313)

  • Changing ssh-agent from OpenSSH or specifying a malevolent value of agent-host-id, could inject data into the monitored MySQL Server.

    For example, setting agent-host-id to the value “I'm a test” would result in the following message in the error log:

    2009-01-23 15:45:11: ((error)) agent_mysqld.c:281: mysql_real_query('INSERT INTO
    mysql.inventory  (name, value) VALUES ( 'hostid', 'I'm a test' )') on 'mysql' failed: You
    have an error in your SQL syntax; check the manual that corresponds to your MySQL server
    version for the right syntax to use near 'm a test' )' at line 1 (mysql-errno = 1064)


  • When SHOW GLOBAL STATUS returned a value greater than 214748364, it was sent to the Service Manager as 214748364. (Bug#42245)

  • The Agent failed to identify local sockets as local on Mac OS X 10.4.

    If the Agent was configured to use a Unix domain socket on Mac OS X 10.4, it did not treat the connection as local and failed to provide CPU and memory information to MySQL Enterprise Monitor. This is shown in the log file:

    2009-01-20 18:15:02: (message) network-socket.c:752: is-local family 0 != 1
    2009-01-20 18:15:02: (message) agent_mysqld.c:322: [mysql] mysqld is not local or not
    directly connected

    However, this problem did not happen on Mac OS X 10.5. (Bug#42220)

  • Some graphs on the Graph tab were not updated after the page was refreshed, or Update was clicked.

    The only way to get an updated graph was to change the graph size (in pixels) and then click Update. (Bug#42162)

  • The my.cnf file for the Enterprise Monitor internal database had the following configuration item:

    innodb_autoextend_increment = 50M

    This generated the error:

    16:36:23 [Warning] option 'innodb_autoextend_increment': unsigned value 52428800
    adjusted to 1000

    This variable is interpreted as being specified in MB, so 50M would be 50 TB. Such a high value results in the variable being adjusted to 1000 MB.

    The value in the configuration file should be:

    innodb_autoextend_increment = 50


  • A number of Advisor rules had advice text that had not been translated into Japanese. The Advisors that contained untranslated rules included Performance, Schema and Security. (Bug#42067)

  • The Service Manager did not handle the case where the agent failed to supply a valid master_ip. The Service Manager would then not restart. The logs contained the following:

    2009-01-09 14:39:50,472 ERROR [main:org.springframework.web.context.ContextLoader] Context
    initialization failed
    org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with
    name 'serverConnectionMonitor' defined in ServletContext resource
    [/WEB-INF/applicationContext.xml]: Unsatisfied dependency expressed through constructor
    argument with index 2 of type []: Error creating bean
    with name 'manager' defined in ServletContext resource [/WEB-INF/applicationContext.xml]:
    Invocation of init method failed; nested exception is
    101c6b5b-15eb-49aa-916c-843c51b28d38: mysql.slavestatus.Master_ip


  • Having too many users with strong privileges generated Service Manager errors and events failed to be triggered.

    If there were approximately 1000 users with full privileges and the value of group_concat_max_len was set to 100001, the size of the data that the agent sent to the Service Manager was too large and caused Service Manager errors. Also, the Security event “Account has Strong MySQL privileges” did not trigger. (Bug#41987)

  • Query Analyzer's Query Type filter for SELECT ignored statements starting with parenthesis.

    If you sent a statement through Query Analyzer starting with parenthesis, such as:

    (SELECT 1 FROM dual);

    and then attempted to filter for SELECT queries only, queries starting with parenthesis were not displayed. (Bug#41968)

  • The agent angel process was spawning too soon, which caused a duplicate UUID error.

    g_error() logged a fatal error, and called abort(). This terminated the program. Then the angel respawned with the same UUID, but with a -1 session resync request, which the MEM server denied because the old session was still active. This resulted in a permissions denied error (1142) on the mysql.inventory table.

    2008-12-17 18:58:58: (message) agent_mysqld.c:313: [mysql] mysqld is local and directly connected
    2008-12-17 18:58:58: ((error)) agent_mysqld.c:444: [mysql] mysql_real_query("SELECT value
    FROM mysql.inventory WHERE name = 'uuid'") failed: SELECT command denied to user
    'ent_agent'@'' for table 'inventory' (errno=1142)
    2008-12-17 18:58:58: (debug) chassis.c:282: 15134 returned: 15134
    2008-12-17 18:58:58: (message) chassis.c:304: [angel] PID=15134 died on signal=6 (it used
    0 kBytes max) ... waiting 3min before restart
    2008-12-17 18:59:00: (debug) chassis.c:244: we are the child: 15149
    2008-12-17 18:59:00: (message) chassis.c:259: [angel] we try to keep PID=15149 alive
    2008-12-17 18:59:00: (debug) chassis.c:277: waiting for 15149
    2008-12-17 18:59:00: (message) mysql-proxy 0.7.0 started
    2008-12-17 18:59:00: (message) MySQL Monitor Agent started.


  • master_uuid discovery did not work with MySQL Server versions prior to 5.1. master_uuid did not show in any Agent to Monitor communications, and no log or error messages were generated.

    However, now the bug has been fixed, an Agent monitoring a 5.0 MySQL Server would register the following in its logs:


    Note the presence of master_uuid. (Bug#41525)

  • The master_uuid was not used for replication topology discovery.

    The agent collected master_uuid by reading the file, and then running a SELECT directly against its master. This was to try and read the mysql.inventory table on the master to obtain the instance master_uuid.

    However, this was not being used correctly by the replication topology discovery within the server. (Bug#41519)

  • Queries such as SELECT against the master mysql.inventory was not logged on slave-based agents. This made diagnosing topology discovery issues difficult. (Bug#41518)

  • After an error was generated due to an incorrect password while trying to create a new user, the following error was obtained when subsequently attempting to create a valid new user:

    U0002 You must log in to access the requested resource


  • Agent startup failed on Solaris 10. The error generated was:

    # ./mysql-monitor-agent start
    Bad string
    ERROR! /opt/mysql/enterprise/agent/etc/mysql-monitor-agent.ini has to have a
    [mysql-proxy].pid-file setting

    This was caused by unexpected behavior of the tr command. (Bug#41260)

  • On the Query Analysis page, if a query was clicked the minimum displayed was greater than the average. (Bug#41259)

  • In some circumstances the agent/proxy ran out of file descriptors, causing secondary failures. It could not recover from that state. The relevant part of the log file is shown here:

    2008-11-27 11:11:00: (critical) last message repeated 2 times
    2008-11-27 11:11:00: (critical) job_collect_os.c:411: sigar_cpu_info_list_get() failed
    2008-11-27 11:11:00: (critical) job_collect_os.c:445: sigar_cpu_list_get() failed
    2008-11-27 11:11:00: (critical) job_collect_os.c:411: sigar_cpu_info_list_get() failed
    2008-11-27 11:11:00: (critical) job_collect_os.c:445: sigar_cpu_list_get() failed
    2008-11-27 11:11:00: (critical) job_collect_os.c:411: sigar_cpu_info_list_get() failed
    2008-11-27 11:11:00: (critical) job_collect_os.c:445: sigar_cpu_list_get() failed
    2008-11-27 11:11:00: (critical) job_collect_os.c:411: sigar_cpu_info_list_get() failed
    2008-11-27 11:11:00: (critical) job_collect_os.c:445: sigar_cpu_list_get() failed
    2008-11-27 11:11:30: (critical) network-socket.c.292: socket( failed: Too many open files (24)
    2008-11-27 11:11:30: (critical) proxy-plugin.c.1532: Cannot connect, all backends are down.
    2008-11-27 11:20:22: (critical) last message repeated 4 times
    2008-11-27 11:20:22: (critical) network-io.c:215:
    curl_easy_perform('https://user:password@merlin-dashboard:443/heartbeat') failed:
    SSL connection timeout (curl-error = 'Timeout was reached' (28), os-error = 'Connection refused' (111))


  • If an installation of Service Manager included a backup directory, due to a previous upgrade, and was upgraded using at least Service Manager, then the installer displayed an error message and exited.

    The error message displayed was:

    There has been an error.
    Error renaming /Applications/mysql/enterprise/monitor/apache-tomcat to
    The application will exit now


  • The Agent started without problems and connected to the master. But it was unable to perform a SELECT from the table mysql.inventory in order to obtain server information. (Bug#40933)

  • Canonical Query Text for Select -1 was displayed as SELECT -? instead of SELECT ? on the Query Analyzer tab. (Bug#40435)

  • The agent installer for Solaris 8 x86 32-bit was missing. (Bug#40248)

  • The MySQL Enterprise Monitor Dashboard did not display the subscribed notification group(s) on the Advisor Current Scheduled and Add to Schedule pages. (Bug#36007)

  • The startup scripts supplied with MySQL Network Monitoring and Advisory tool did not supply all of the LSB init.d script options required. A list of the required options can be found at the following website

    The required options missing include status and force-reload. The option status is used by monitoring tools and cluster software such as Red Hat Cluster, to ensure that the service is still running. The force-reload option is an alias for restart. (Bug#29848)

  • Multiple errors showed in the agent log after issuing a SHOW INNODB STATUS statement. The InnoDB Buffer Poolgraph also went blank. (Bug#27372)

C.3.3. Changes in MySQL Enterprise Monitor 2.0.4 (5th February 2009)

This section documents all changes and bug fixes that have been applied since the release of MySQL Enterprise Monitor, version 2.0.3.

Bugs fixed:

  • The Service Agent did not log connections to, and disconnects from, the monitored database.

    This meant it was not possible to check if the Agent was connected to the database by simply looking at the log file. (Bug#42403)

  • The Service Agent failed to create the mysql.inventory table. The logs displayed the following error message:

    (critical) (share/mysql-proxy/quan.lua:711) [proxy] please add SELECT permissions for
    this user on mysql.inventory to enable the QUAN feature, got Table 'mysql.inventory'
    doesn't exist

    This happened even though the Service Agent used the root account. (Bug#42389)

  • After installing Service Agent and then starting it with --version, the incorrect version was displayed. Although was installed, the Service Agent displayed the version number as (Bug#42263)

  • An invalid path was shown in the error message if the upgrade installer failed to find the previous install location.

    The error message is shown below, note that the error message displays a different path to that provided by the user:

    Please specify the directory that contains the previous installation of the MySQL
    Enterprise Monitor Agent
    Installation directory [/home/mysql/mysql/enterprise/agent]: /var/lib/mysql/agent
    Warning: The directory /home/mysql/mysql/enterprise/agent does not contain a a
    previous installation. Please select the right installation directory.
    Press [Enter] to continue :
    Please specify the directory that contains the previous installation of the MySQL
    Enterprise Monitor Agent


  • The agent password error in the Service Manager did not log the originating host, making it impossible to determine the agent that failed to log in:

    ErrorJan 5, 2009 4:56:08 PM<?xml version='1.0'?><exceptions><error><![CDATA[E1702:
    IncorrectPasswordException: [agent]]]></error></exceptions>


  • The Service Manager's JDBC connections did not have sql_mode set to include NO_ENGINE_SUBSTITUTION. This resulted in the failure of Data Definition Language (DDL) if the Service Manager was inadvertently pointed to an incorrect mysqld instance. (Bug#42137)

  • A number of Advisor rules had advice text that had not been translated into Japanese. The Advisors that contained untranslated rules included Performance, Schema and Security. (Bug#42067)

  • Service Agent configuration files had global read privileges on the filesystem. (Bug#41794)

  • When the log files rotated to the maximum allowed by the log4j configuration, the metadata contained in the FileAppender became out of synchronization due to a logic bug. This caused an assertion error on any subsequent request for the logs tab or data. (Bug#41593)

  • SNMP trap messages were sending as the IP address, and there was no feature to allow the user to configure the IP address contained in the SNMP message, which would have been useful for troubleshooting. (Bug#41361)

  • On all available test systems, including SUSE Linux Enterprise Server (SLES) 9 and 10 x86-32, x86-64, IA64, and Ubuntu 6.10 x86-64, the agent memory grew incrementally within ~3 hours to ~25M.

    The agents then switched to the 'red' condition on the dashboard and no more data was reported. The agent processes were still alive.

    This was also present in MySQL Enterprise Monitor version on Suse 7.3, with the glibc2.2 x86 agent.

    There was no load on the monitored servers, and the problem also occurred when the “self-quan” was not configured. (Bug#41244)

  • Although the Monitor tab loaded initially, after a 64-bit MySQL server running a 32-bit MySQL Monitor Agent was clicked, a Null Pointer Exception was generated. (Bug#41164)

  • The Service Agent startup configuration did not seem to work and did not generate a log file. (Bug#40583)

  • An error generated by a rule failed to clear.

    When a rule was created with the os:disk:fs_used data item, if the instance was not a valid mount point then the Service Agent reported the error:

    2008-08-11 17:57:00: (critical) disk-get failed for all: 2

    Note the above instance was for “all”, and similar results occurred for instance “disk”.

    The issue was that upon editing the rule, or even deleting the rule, the agent still showed the above error type. Restarting the agent and the monitoring service failed to remove the error. (Bug#38709)

  • If the “On Save send test trap” checkbox was checked when the Save button was clicked and the locale was set to Japanese, an error occurred. The orange error banner was displayed at the top of the page with the error message in Japanese. (Bug#32069)

C.3.4. Changes in MySQL Enterprise Monitor 2.0.3 (23rd January 2009)

This section documents all changes and bug fixes that have been applied since the release of MySQL Enterprise Monitor, version 2.0.2.

Bugs fixed:

  • The Service Agent failed to connect to the server, and no error message was displayed in the log file.

    However, when the log verbosity level was set to message, the following message was recorded:

    2009-01-12 13:34:43: (warning) agent_mysqld.c:600: agent connecting to mysql-server
    failed: mysql_real_connect(host = '', port = 3306, socket = ''): Lost connection
    to MySQL server at 'reading initial communication packet', system error: 0 (mysql-errno =


  • There was a mismatch between the contents of an SNMP Trap from MySQL Enterprise Monitor and the definition given in the file MONITOR.MIB. (Bug#41912)

  • If a copy was made of a standard rule, the resulting Wiki markup was incorrect, resulting in the display of user-interface text containing HTML markup. (Bug#41375)

  • Allowing the heat chart rules to be set to unscheduled caused the user interface to appear broken. (Bug#41312)

  • When a custom rule requiring disk information was created, for example:

    %disk_reads% > THRESHOLD
    Critical Alert: 9000
    Warning Alert: 3000
    Info Alert: 1000
    [Variable Assignment]
    variables: %disk_reads%
    Data Item: os:disk:disk_reads
    Instance: /

    The following error was written to the file mysql-service-agent.log:

    2007-09-05 17:11:00: (critical) disk-get failed for c0d0p1: 2

    It therefore appeared that the Service Agent was not able to obtain the required information. (Bug#30820)

C.3.5. Changes in MySQL Enterprise Monitor 2.0.2 (14th January 2009)

This section documents all changes and bug fixes that have been applied since the release of MySQL Enterprise Monitor, version 2.0.1.

Bugs fixed:

  • The Complete Setup button was missing from the Setup page you were taken to after the current subscription expired. (Bug#41685)

  • If the host-id of the monitored instance and the host-id of the current agent did not match, the agent generated the following error message:

    Please TRUNCATE TABLE mysql.inventory on this mysql-instance and restart the agent.

    However, it did not suggest using sql_log_bin = 0. This is used for all other actions against this table so that they are not replicated to slaves, each of which has their own copy of this table. (Bug#41673)

  • The Agent did not start up when the monitored server had many databases and tables, and was under heavy load. This was because the trigger_schema query was taking too long on agent start up. (Bug#41555)

  • The Service Agent failed to install on Solaris 10 x86. The following error was generated:

    0% ______________ 50% ______________ 100%
    Warning: Problem running post-install step.
    Installation may not complete correctly
    Error running /usr/local/mysqlagent/bin/mysql-monitor-agent
    --plugins=agent --agent-generate-uuid=true : 2008-12-12 13:06:02: (critical)
    Conversion from character set '646' to 'UTF-8' is not supported
    2008-12-12 13:06:02: (message) shutting down normally


  • The console/stdout appender remained in the log4j configuration, which meant that all the MySQL Enterprise Monitor server logs were duplicated to Catalina's stdout, and thus catalina.out, which was wasteful, especially as that file was not rotated or managed. (Bug#41439)

  • When creating new multiple user accounts, the first attempt worked fine. However, following attempts to create new users did not show the Query Analyzer Options in the Create User popup until the role field was changed. (Bug#41430)

  • When login privileges were required the Service Manager did not redirect the user to the login page. This resulted in error messages being displayed rather than simply redirecting the user to the login page. This problem typically occurred if it was necessary to restart Tomcat. (Bug#41320)

  • The monitor and Solaris Intel update installer quits unexpectedly. The installer exits from the GUI in the Backup of Previous Installation screen, when OpenSolaris is running on top of Sun xVM.

    The console output for both installer versions is given below:

    shell> ./mysqlmonitor-
    X Error of failed request:  BadMatch (invalid parameter attributes)
      Major opcode of failed request:  73 (X_GetImage)
      Serial number of failed request:  21161
      Current serial number in output stream:  21161
    shell> ./mysqlmonitor-
    X Error of failed request:  BadMatch (invalid parameter attributes)
      Major opcode of failed request:  73 (X_GetImage)
      Serial number of failed request:  21148
      Current serial number in output stream:  21148


  • The Rename Group function failed if the new group name was different to the current one only in the case used; for example, if “Merlin” was changed to “MERLIN”.

    The error generated was:

    U0105 This group name is already in use. Enter a different name.


  • The Agent returned an inventory list of all databases and tables. This information was not used by MySQL Enterprise Monitor, other than to populate the inv_databases and inv_tables tables. For large-scale deployments, where there were many databases and tables, this resulted in redundant XML messages being sent from the Agent to the Service Manager. (Bug#33150)

C.3.6. Changes in MySQL Enterprise Monitor 2.0.1 (15th December 2008)

This section documents all changes and bug fixes that have been applied since the release of MySQL Enterprise Monitor, version 2.0.0.

Bugs fixed:

  • Having an installation with over 420 master binlogs resulted in the mysql::status graph not being plotted. (Bug#41314)

  • The MySQL Enterprise Monitor installer generated a segfault on RedHat Fedora 10:

    shell> ./mysqlmonitor-
    Segmentation fault


C.3.7. Changes in MySQL Enterprise Monitor 2.0.0 (11th December 2008)

This section documents all changes and bug fixes that have been applied since the release of MySQL Enterprise Monitor, version 1.3.3.

Functionality added or changed:

  • Important Change: The server-name configuration parameter is deprecated. For compatibility, during an upgrade, the information will be migrated to a displayname configuration parameter within the individual instance configuration files. This configuration parameter is provided only for compatibility, as display name information is now stored within the main repository. Support for displayname is also deprecated and will be removed in a future release.

  • Important Note: The rules “32-Bit Binary Running on 64-Bit AMD Or Intel System” and “Key Buffer Size Greater Than 4 GB” occasionally do not evaluate correctly due to timing issues. This causes them to be displayed with the Severity level of “Unknown”. This is a known issue and will be resolved in future versions of MySQL Enterprise Monitor.

  • Important Note: When you start the Merlin 2.0 agent from the command line on Windows, you get the following error dialog:

    "mysql-proxy.exe - Entry Point Not Found"
    "The procedure entry point libiconv_set_relocation_prefix could not be located in the
    dynamic link library iconv.dll"

    If you click OK the agent works fine after that.

    This only occurs when starting the agent from the command line, and only when there is another version of one of the DLLs that the agent uses somewhere on the current path. This error can be avoided by opening a command prompt, typing SET PATH= to clear the path, and then starting the agent.

  • Important Note: If you are monitoring one instance of MySQL server (mysqld) and then upgrade that MySQL server, the correct version of the MySQL server is not displayed in the Dashboard. This is a known issue that will be fixed in future versions of MySQL Enterprise Monitor.

  • The following has been added to the Tomcat properties file:

         # max connections in the pool for the repository


  • The dashboard could be used to change the agent password to one containing the @ character, or other special characters, which subsequently caused errors. To fix this problem, special characters in passwords are now prevented by the dashboard. The list of disallowed special characters can be found at the following location: (Bug#37172)

  • The Query Analysis page was missing the Refresh dropdown control that the Monitor, Events, and Graphs pages had at the top. (Bug#36831)

  • The User Interface only returned error strings, without any associated error codes. This meant that if the error string was in a language that the user did not understand, it would be very difficult to determine which error actually occurred.

    The User Interface now supports error codes, as well as error strings. This change allows easier testing of multiple locales. (Bug#32131)

  • The wording was changed on the fading popup subscription alert. The text “account” was changed to “subscription”. (Bug#31492)

  • The alert thresholds for the Query Cache Advisor were changed:

     Information Warning Critical
    From 95 85 75
    To 60 50 40


  • The agent log file name has changed from mysql-service-agent.log to mysql-monitor-agent.log. The old log file will be retained during a upgrade install.

Bugs fixed:

  • Starting a new agent against an instance that contained many databases broke up the initial discovery packet, causing collections such as CPU usage and their graphs to fail. See also Bug#33150 and Bug#41314. (Bug#41933)

  • When altering an existing rule you had to add an empty string, "", to any threshold level that was empty. Otherwise, the rule failed to run and the resulting exceptions caused the Events page to be unusable due to duplicate key exceptions. (Bug#41310)

  • After installing the Dashboard the following error was generated in the logs:

    com.opensymphony.xwork2.util.OgnlValueStack  Warning  Dec 5, 2008 10:41:26 AM  Caught
    an Ognl exception while getting property titleAddition


  • The dc_ng_long_now table became very large partly due to an unused column begin_time. (Bug#41093)

  • Although there was a unique constraint on the user name, it was not enforced during first-time setup. This resulted in a stack trace being produced, rather than a more user-friendly error message, if the same name was used for the admin and agent accounts. (Bug#40870)

  • MySQL Enterprise Monitor server had stopped sending up/down SNMP traps. (Bug#40861)

  • The Query Analyzer's Explain Query tab did not have pop up text or a link to the documentation regarding SELECT queries. (Bug#40841)

  • When you tried to import a Trial-level advisor JAR using a Trial user account, one of the following error messages was generated:

    U0009 The uploaded Advisor jar was invalid
    U0161 Please import a Platinum level Advisor .jar to use with this Platinum level product key


  • Meta Info on the Dashboard did not display information for the meta data os_description. (Bug#40830)

  • Attempting to create an alias of statements such as COMMIT, ROLLBACK, BEGIN, resulted in the error:

    Can't find template; group hierarchy is [HTMLFormatting]


  • Trying to upgrade from to failed as there was a missing file. When the update program mysqlmonitor- was run, the file /tmp/com/mysql/merlin/server/version.props could not be found. (Bug#40692)

  • On OS X with Java 1.5, Tomcat crashed on launch with the error:

    Invalid memory access of location 00000007 eip=013df179


  • When the agent was installed using the command line installer and --enableproxy 0 was specified, the installer should have removed quan.lua from the agent-item-files option in the INI file. (Bug#40551)

  • The Agent could not connect to a database with the hostname set to localhost. Doing so resulted in the error:

    (critical) the MySQL server could not be reached at socket '(null)', we will check in 10 seconds


  • The update installer for the 2.0 Monitor did not have an Is SSL support required? checkbox. Therefore, the appropriate SSL connector definition was commented out in the conf/server.xml file. (Bug#40414)

  • The Service Manager installer did not uninstall or wipe out the previous installation if you answered “Yes” to the question:

    The directory you selected already contains a MySQL installation. If you continue installation all data will be lost. Do you wish to continue?” (Bug#40410)

  • If you unchecked the Enable Proxy checkbox on the Query Analysis Configuration screen, the agent's INI file still contained proxy configuration data and was not commented out. (Bug#40272)

  • As different queries were sent through the agent it used increasing amounts of memory. (Bug#40260)

  • The Service Manager installer set the Java Virtual Machine option HeapDumpPath to <install_root>\temp on Windows and /tmp on other platforms. For consistency the HeapDumpPath directory should have been set to <install_root>\tmp on Windows. (Bug#40215)

  • When using the command line agent setup program, a socket file was not accepted for the monitored instance. (Bug#40085)

  • The language option when installing the MySQL Enterprise Monitor in Japanese using the command-line instllaer has been changed from jp to ja. (Bug#40082)

  • When monitoring MySQL 5.1.24 and above, the user used by the agent to connect to the MySQL server for monitoring must have the PROCESS privilege. (Bug#40050)

  • The check box option string “Is SSL support required?”, on the Tomcat Server Option dialog of the Monitor installation, was not correctly translated into Japanese. (Bug#39814)

  • The base application directory for the MySQL Enterprise Dashboard has been updated from http://localhost:18080/merlin to http://localhost:18080/. (Bug#39403)

  • If the Service Manager or the MySQL Server running the Repository crashed, they did not restart automatically. (Bug#39377)

  • If the agent crashed, there was no watchdog, angel or keep-alive mechanism to restart the agent and keep it running. (Bug#39374)

  • If the MySQL client libraries were located in a nonstandard location, the agent installer failed with a “library not found” error. (Bug#39317)

  • For the rule “Server-Enforced Data Integrity Checking Not Strict”, the Recommended Action did not display correctly. It displayed as SET sql_mode=modes, rather than SET [GLOBAL|SESSION] sql_mode=modes. (Bug#39261)

  • A query that was issued through the proxy, and that had an auto-explain performed on that query, did not give the correct response to a subsequent query of SELECT FOUND_ROWS(). (Bug#39223)

  • It was not possible to establish a connection with the Dashboard using the SSL protocol (https://). (Bug#39198)

  • When a 1.3 MySQL Enterprise Monitor installation with many rules scheduled was upgraded to 2.0, the upgraded installation was then found to have only the heat chart rules scheduled. (Bug#39043)

  • The agent installer did not allow a second agent to be installed on Windows. (Bug#38976)

  • The Dashboard incorrectly diplayed that insufficient licenses were available, even though sufficient licenses had been purchased. (Bug#38514)

  • After running the MySQL Service Agent uninstall program, the file /etc/init.d/mysql-service-agent remained present on the server. (Bug#38490)

  • The notice fader continued to display English text after you changed the locale to Japanese. (Bug#38460)

  • The Subscription Expired pop-up window referred to the “Global Preferences” page, instead of the “Global Settings” page. (Bug#38358)

  • An inappropriate time zone was used to parse user-entered date and time strings. (Bug#38323)

  • A sigar network stats error was generated on the Solaris platform:

    # /opt/mysql/enterprise/agent/bin/mysql-service-agent --version
    MySQL Service Agent -, (glib lib=2.8.5, headers=2.8.5)
    SunOS mysqlprd01 5.10 Generic_127127-11 sun4v sparc SUNW,T5240
    2008-07-21 10:07:24: (critical) sigar_net_interface_config_primary_get() failed: 6
    2008-07-21 10:08:00: (critical) sigar_net_interface_config_primary_get() failed: 6
    # /opt/mysql/enterprise/agent/bin/sigar-test-all >/tmp/test.txt
    sigar_net_interface_stat_get(e1000g0:2) failed#


  • After deleting a server from the Settings, Manage Servers tab, at the very bottom of the page the Monitoring x instances on x host values did not reflect the deletion. (Bug#38225)

  • The MySQL Enterprise Monitor alert “INFO Alert - Users Can View All Databases On MySQL Server (v 1.5 *)” from the Security advisor was incorrect. This is because the default server behavior allows users to see databases for which they have privileges, not “all databases on server” as suggested by the alert. (Bug#38052)

  • The “Maximum Connection Limit Nearing Or Reached” advisor did not generate a new Critical Alert event when there was an open info success event. (Bug#37816)

  • The Linux IA64 installer appeared to crash. The installer appeared to crash on RH4_IA64 if called with option "--version":

    <INSTALLER> --version
    mysqlmonitorage(30704): unaligned access to 0x6000000000a8413c, ip=0x2000000003ddd5f0
    mysqlmonitorage(30704): unaligned access to 0x6000000000a84144, ip=0x2000000003ddd5f1
    mysqlmonitorage(30704): unaligned access to 0x6000000000a8414c, ip=0x2000000003ddd600
    mysqlmonitorage(30704): unaligned access to 0x6000000000a84154, ip=0x2000000003ddd601
    MySQL Enterprise Monitor Agent --- Built on 2008-06-25 19:31:53

    However, this warning is harmless and will not impact the operation of the agent. (Bug#37496)

  • If the log-level option in the agent configuration file was set to an unknown level by mistake, the init.d script appeared to enter an infinite loop. (Bug#37108)

  • Malformatted server meta information appeared on the Dashboard; RAM and Disk Space appeared under the CPU category. (Bug#36740)

  • A “rename” link incorrectly appeared next to the Upgrade category on the Manage Rules page. (Bug#36584)

  • In the case where exceptions were passed through to the User Interface, the substituted arguments in the message contained developer-only information. (Bug#36580)

  • Agent Version, Last MySQL Contact, OS Info, CPU Info, and IP Addresses were all blank on the dashboard when the agent for the selected server was not functioning. (Bug#36301)

  • mysql-monitor-agent became confused by the .DS_Store files that are created on Mac OS X. (Bug#36216)

  • The rule “Key Buffer Size Greater Than 4 GB” incorrectly triggered the following alert:

    CRITICAL Alert - Key Buffer Size Greater Than 4 GB

    However, on non-Windows systems, a key buffer size greater than 4 GB is supported. (Bug#36143)

  • Since the repository database for MySQL Enterprise Monitor uses InnoDB there was no way to reduce the size of the data files after an old log/event data purge operation. Further, the purge data operation executed once per day, and had no option to trigger the purge operation manually. (Bug#35971)

  • On the Graphs page, if all graphs were expanded, then the Time Display interval updated, the page was refreshed with the Expand All button displayed, even though all the graphs were already expanded. (Bug#35917, Bug#35133)

  • The Meta Info area of the Monitor page incorrectly reported the operating system version number for the MySQL version. (Bug#35836)

  • The rule “XA Distributed Transaction Support Enabled For InnoDB” incorrectly sent a warning when the binary log was on. (Bug#35786)

  • On the Monitor page, the time displayed for Last MySQL Contact lagged behind that for Last Agent Contact by a large amount. (Bug#35774)

  • MySQL Enterprise Monitor did not update replication settings correctly. After a slave became the master, the Adviser still referred to it as a slave. (Bug#35771)

  • The Adviser email suggested using the --log-queries-not-using-indexes option. However, this option is not available in MySQL Server versions prior to 4.1. (Bug#35770)

  • Thumbnail graphs did not update properly after a time zone change. (Bug#35756)

  • If a system had a global wait_timeout lower than the general activity of the agent, the agent was disconnected. The monitored server then logged an error and incremented Aborted_clients. (Bug#35648)

  • Alerts fired after a blackout period based on data collections that happened during the blackout. (Bug#35617)

  • The translation of the Add Row button on the Rule Definition window was incorrect. (Bug#35495)

  • An uninstallation message asked about removing Apache files, even though Apache is no longer used. (Bug#35154)

  • After updating from a previous version to the latest 1.3 version, the Query Cache Has Sub-Optimal Hit Rate was still displayed in English after setting the locale to Japanese. Note, the rule was translated correctly if the full installer was used. (Bug#35134)

  • The MySQL Enterprise Monitor uninstall dialog box had missing text when using the Japanese locale. (Bug#34982)

  • Running the installer with the --help option caused an incorrect message to be displayed. (Bug#34200)

  • When using the unattended unInstall script on Linux together with the option --env deleteUserData=yes the correct warning text was displayed. However, this text should not be displayed in unattended mode. Further, the option --env deleteUserData=yes was not displayed by the --help output. (Bug#34071)

  • Platinum Unlimited customers sometimes received a warning stating incorrectly that their subscription supported zero hosts. (Bug#34010)

  • Clicking on the resolution notes link for a closed event on the events tab showed incorrect behaviour. The popup initially showed the resolution notes, but when the resolution tab was clicked the notes disappeared and were replaced by an edit box. (Bug#33935)

  • The status on the product information page was not translated when the user locale was set to Japanese. (Bug#32785)

  • When the locale was set to Japanese, the date picker still had English month titles. (Bug#32741)

  • Flashing display of a pop-up used while saving outgoing email settings was caused by problematic initial placement calculations. (Bug#32579)

  • AIX 5.2 Agent did not work on AIX 5.3. (Bug#32414)

  • When the First Time Setup program was run it did not prompt the user to allow importing an Advisor bundle. (Bug#32199)

  • Agent on MacOSX did not read IP addresses for network interfaces correctly, so the monitor displayed empty host IP addresses. (Bug#32188)

  • HTML code in queries was not escaped when reporting replication errors, causing the code to be rendered into the page. (Bug#32186)

  • The First Run pop-up defaulted to English rather than to the locale set in the browser. (Bug#32129)

  • The error dialog box flashed in the upper left corner before being positioned in the center of the screen. This error dialog box now opens in the center of the screen. (Bug#32068)

  • The Events list did not take into account Daylight Time and Standard Time when listing events that happened during 1:00am-1:59am. An event that occurred at 1:10am Standard Time was listed before an event that occurred 50 minutes before it at 1:20am Daylight Time. (Bug#32016)

  • The pop-up for editing log levels failed to load due to bad instantiation data. (Bug#32013)

  • During the repeated hour of Daylight Savings Time (when 2am turns back into 1am), the graphs were not drawing data. Instead, there was a straight line from the point at 1:00 to the second 1:00, which is what happens if there is no data. The repository did, however, have data for this hour. (Bug#31997)

  • Only US English was supported for a locale setting. Other English variants are now available for the locale setting on the General Settings or the User Preferences pages. (Bug#31801)

  • If the user locale was changed the graph cache would continue to display the graph in the last locale until it timed out. (Bug#31680)

  • No init script was installed for the MySQL Network Monitoring Service Manager, and so it did not restart automatically on reboot. (Bug#31676)

  • The graph's displayed time was not the local time of the Dashboard corresponding to the requested time on the monitored server. (Bug#31656)

  • Saving a rule with a name that already existed resulted in a stack trace in the window, instead of a more user-friendly error message. (Bug#30925)

  • The error messages were remapped thereby causing confusion. For example, the following error message:

    E9000: MySQL Enterprise Customer Center is having difficulties fetching your contract information. Please contact for assistance.

    Was remapped to:

    Unable to connect to verify credentials (Bug#30873)

  • A newly added server showed as “down” in the user interface, and could potentially have sent a false alarm notification. (Bug#30735)

  • The information on the Advisors, Check For Updates page did not accurately reflect how many rules and graphs were actually in the database and available to the user. (Bug#29623)

  • The agent did not process SIGHUP. (Bug#29380)

  • Monitor did not have a facility to stop or downgrade an agent collection frequency. (Bug#28589)

  • After an agent installation was updated from to, the version in the Add/Remove Programs menu was incorrectly displayed as, even though the update was successful and the file version of agent.exe was correctly displayed as (Bug#27447)

  • When viewing the Results of an Event in the Events tab of the Dashboard, the Notifications section did not reflect the Notifications settings at the time the Event was triggered, but rather the Notifications settings at the time the Event Results were viewed. (Bug#26349)

  • When the Service Agent was remotely monitoring a MySQL server it incorrectly reported that it could collect operating system information. (Bug#22497)

  • The Account Without Password advisor did not report all users who were without a password, it only reported one. (Bug#15165)

C.4. MySQL Connector/ODBC (MyODBC) Change History

C.4.1. Changes in MySQL Connector/ODBC 5.1.6 (Not yet released)
C.4.2. Changes in MySQL Connector/ODBC 5.1.5 (18 August 2008)
C.4.3. Changes in MySQL Connector/ODBC 5.1.4 (15 April 2008)
C.4.4. Changes in MySQL Connector/ODBC 5.1.3 (26 March 2008)
C.4.5. Changes in MySQL Connector/ODBC 5.1.2 (13 February 2008)
C.4.6. Changes in MySQL Connector/ODBC 5.1.1 (13 December 2007)
C.4.7. Changes in MySQL Connector/ODBC 5.1.0 (10 September 2007)
C.4.8. Changes in MySQL Connector/ODBC 5.0.12 (Never released)
C.4.9. Changes in MySQL Connector/ODBC 5.0.11 (31 January 2007)
C.4.10. Changes in MySQL Connector/ODBC 5.0.10 (14 December 2006)
C.4.11. Changes in MySQL Connector/ODBC 5.0.9 (22 November 2006)
C.4.12. Changes in MySQL Connector/ODBC 5.0.8 (17 November 2006)
C.4.13. Changes in MySQL Connector/ODBC 5.0.7 (08 November 2006)
C.4.14. Changes in MySQL Connector/ODBC 5.0.6 (03 November 2006)
C.4.15. Changes in MySQL Connector/ODBC 5.0.5 (17 October 2006)
C.4.16. Changes in Connector/ODBC 5.0.3 (Connector/ODBC 5.0 Alpha 3) (20 June 2006)
C.4.17. Changes in Connector/ODBC 5.0.2 (Never released)
C.4.18. Changes in Connector/ODBC 5.0.1 (Connector/ODBC 5.0 Alpha 2) (05 June 2006)
C.4.19. Changes in MySQL Connector/ODBC 3.51.27 (20 November 2008)
C.4.20. Changes in MySQL Connector/ODBC 3.51.26 (07 July 2008)
C.4.21. Changes in MySQL Connector/ODBC 3.51.25 (11 April 2008)
C.4.22. Changes in MySQL Connector/ODBC 3.51.24 (14 March 2008)
C.4.23. Changes in MySQL Connector/ODBC 3.51.23 (09 January 2008)
C.4.24. Changes in MySQL Connector/ODBC 3.51.22 (13 November 2007)
C.4.25. Changes in MySQL Connector/ODBC 3.51.21 (08 October 2007)
C.4.26. Changes in MySQL Connector/ODBC 3.51.20 (10 September 2007)
C.4.27. Changes in MySQL Connector/ODBC 3.51.19 (10 August 2007)
C.4.28. Changes in MySQL Connector/ODBC 3.51.18 (08 August 2007)
C.4.29. Changes in MySQL Connector/ODBC 3.51.17 (14 July 2007)
C.4.30. Changes in MySQL Connector/ODBC 3.51.16 (14 June 2007)
C.4.31. Changes in MySQL Connector/ODBC 3.51.15 (07 May 2007)
C.4.32. Changes in MySQL Connector/ODBC 3.51.14 (08 March 2007)
C.4.33. Changes in MySQL Connector/ODBC 3.51.13 (Never released)
C.4.34. Changes in MySQL Connector/ODBC 3.51.12 (11 February 2005)
C.4.35. Changes in MySQL Connector/ODBC 3.51.11 (28 January 2005)

C.4.1. Changes in MySQL Connector/ODBC 5.1.6 (Not yet released)

Bugs fixed:

  • Connector/ODBC failed to build with MySQL 5.1.30 due to incorrect use of the data type bool. (Bug#42120)

  • Calling SQLDescribeCol() with a NULL buffer and nonzero buffer length caused a crash. (Bug#41942)

  • MySQL Connector/ODBC updated some fields with random values, rather than with NULL. (Bug#41256)

  • Calling SQLDriverConnect() with a NULL pointer for the output buffer caused a crash if SQL_DRIVER_NOPROMPT was also specified:

    SQLDriverConnect(dbc, NULL, "DSN=myodbc5", SQL_NTS, NULL, 0, NULL, SQL_DRIVER_NOPROMPT)


  • Setting the ADO Recordset decimal field value to 44.56 resulted in an incorrect value of 445600.0000 being stored when the record set was updated with the Update method. (Bug#39961)

  • The SQLTablesW API gave incorrect results. For example, table name and table type were returned as NULL rather than as the correct values. (Bug#39957)

  • MyODBC would crash when a character set was being used on the server that was not supported in the client, for example cp1251:

    [MySQL][ODBC 5.1 Driver][mysqld-5.0.27-community-nt]Restricted data type attribute violation

    The fix causes MyODBC to return an error message instead of crashing. (Bug#39831)

  • When the SQLTables method was called with NULL passed as the tablename parameter, only one row in the resultset, with table name of NULL was returned, instead of all tables for the given database. (Bug#39561)

  • The SQLGetInfo() function returned 0 for SQL_CATALOG_USAGE information. (Bug#39560)

  • MyODBC Driver 5.1.5 was not able to connect if the connection string parameters contained spaces or tab symbols. For example, if the SERVER parameter was specified as “SERVER= localhost” instead of “SERVER=localhost” the following error message will be displayed:

    [MySQL][ODBC 5.1 Driver] Unknown MySQL server host ' localhost' (11001).


  • The pointer passed to the SQLDriverConnect method to retrieve the output connection string length was one greater than it should have been due to the inclusion of the NULL terminator. (Bug#38949)

  • Data-at-execution parameters were not supported during positioned update. This meant updating a long text field with a cursor update would erroneously set the value to null. This would lead to the error Column 'column_name' cannot be null while updating the database, even when column_name had been assigned a valid nonnull string. (Bug#37649)

  • The SQLDriverConnect method truncated the OutputConnectionString parameter to 52 characters. (Bug#37278)

  • The connection string option Enable Auto-reconnect did not work. When the connection failed, it could not be restored, and the errors generated were the same as if the option had not been selected. (Bug#37179)

  • Insertion of data into a LONGTEXT table field did not work. If such an attempt was made the corresponding field would be found to be empty on examination, or contain random characters. (Bug#36071)

  • No result record was returned for SQLGetTypeInfo for the TIMESTAMP data type. An application would receive the result return code 100 (SQL_NO_DATA_FOUND). (Bug#30626)

  • It was not possible to use Connector/ODBC to connect to a server using SSL. The following error was generated:

    Runtime error '-2147467259 (80004005)':
    [MySQL][ODBC 3.51 Driver]SSL connection error.


  • When the recordSet.Update function was called to update an adLongVarChar field, the field was updated but the recordset was immediately lost. This happened with driver cursors, whether the cursor was opened in optimistic or pessimistic mode.

    When the next update was called the test code would exit with the following error:

    -2147467259 : Query-based update failed because the row to update could not be found.


C.4.2. Changes in MySQL Connector/ODBC 5.1.5 (18 August 2008)

Bugs fixed:

  • ODBC TIMESTAMP string format is not handled properly by the MyODBC driver. When passing a TIMESTAMP or DATE to MyODBC, in the ODBC format: {d <date>} or {ts <timestamp>}, the string that represents this is copied once into the SQL statement, and then added again, as an escaped string. (Bug#37342)

  • The connector failed to prompt for additional information required to create a DSN-less connection from an application such as Microsoft Excel. (Bug#37254)

  • SQLDriverConnect does not return SQL_NO_DATA on cancel. The ODBC documentation specifies that this method should return SQL_NO_DATA when the user cancels the dialog to connect. The connector, however, returns SQL_ERROR. (Bug#36293)

  • Assigning a string longer than 67 characters to the TableType parameter resulted in a buffer overrun when the SQLTables() function was called. (Bug#36275)

  • The ODBC connector randomly uses logon information stored in odbc-profile, or prompts the user for connection information and ignores any settings stored in odbc-profile. (Bug#36203)

  • After having successfully established a connection, a crash occurs when calling SQLProcedures() followed by SQLFreeStmt(), using the ODBC C API. (Bug#36069)

C.4.3. Changes in MySQL Connector/ODBC 5.1.4 (15 April 2008)

Bugs fixed:

  • Wrong result obtained when using sum() on a decimal(8,2) field type. (Bug#35920)

  • The driver installer could not create a new DSN if many other drivers were already installed. (Bug#35776)

  • The SQLColAttribute() function returned SQL_TRUE when querying the SQL_DESC_FIXED_PREC_SCALE (SQL_COLUMN_MONEY) attribute of a DECIMAL column. Previously, the correct value of SQL_FALSE was returned; this is now again the case. (Bug#35581)

  • On Linux, SQLGetDiagRec() returned SQL_SUCCESS in cases when it should have returned SQL_NO_DATA. (Bug#33910)

  • The driver crashes ODBC Administrator on attempting to add a new DSN. (Bug#32057)

C.4.4. Changes in MySQL Connector/ODBC 5.1.3 (26 March 2008)

Platform specific notes:

  • Important Change: You must uninstall previous 5.1.x editions of Connector/ODBC before installing the new version.

  • The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.

  • There is no binary package for Mac OS X on 64-bit PowerPC because Apple does not currently provide a 64-bit PowerPC version of iODBC.

  • The installer for 64-bit Windows installs both the 32-bit and 64-bit driver. Please note that Microsoft does not yet supply a 64-bit bridge from ADO to ODBC.

Bugs fixed:

  • Important Change: In previous versions, the SSL certificate would automatically be verified when used as part of the Connector/ODBC connection. The default mode is now to ignore the verificate of certificates. To enforce verification of the SSL certificate during connection, use the SSLVERIFY DSN parameter, setting the value to 1. (Bug#29955, Bug#34648)

  • Inserting characters to a UTF8 table using surrogate pairs would fail and insert invalid data. (Bug#34672)

  • Installation of Connector/ODBC would fail because it was unable to uninstall a previous installed version. The file being requested would match an older release version than any installed version of the connector. (Bug#34522)

  • Using SqlGetData in combination with SQL_C_WCHAR would return overlapping data. (Bug#34429)

  • Descriptor records were not cleared correctly when calling SQLFreeStmt(SQL_UNBIND). (Bug#34271)

  • The dropdown selection for databases on a server when creating a DSN was too small. The list size now automatically adjusts up to a maximum size of 20 potential databases. (Bug#33918)

  • Microsoft Access would be unable to use DBEngine.RegisterDatabase to create a DSN using the Connector/ODBC driver. (Bug#33825)

  • Connector/ODBC erroneously reported that it supported the CAST() and CONVERT() ODBC functions for parsing values in SQL statements, which could lead to bad SQL generation during a query. (Bug#33808)

  • Using a linked table in Access 2003 where the table has a BIGINT column as the first column in the table, and is configured as the primary key, shows #DELETED for all rows of the table. (Bug#24535)

  • Updating a RecordSet when the query involves a BLOB field would fail. (Bug#19065)

C.4.5. Changes in MySQL Connector/ODBC 5.1.2 (13 February 2008)

MySQL Connector/ODBC 5.1.2-beta, a new version of the ODBC driver for the MySQL database management system, has been released. This release is the second beta (feature-complete) release of the new 5.1 series and is suitable for use with any MySQL server version since MySQL 4.1, including MySQL 5.0, 5.1, and 6.0. (It will not work with 4.0 or earlier releases.)

Keep in mind that this is a beta release, and as with any other pre-production release, caution should be taken when installing on production level systems or systems with critical data.

Platform specific notes:

  • The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.

  • There is no binary package for Mac OS X on 64-bit PowerPC because Apple does not currently provide a 64-bit PowerPC version of iODBC.

  • The installer for 64-bit Windows installs both the 32-bit and 64-bit driver. Please note that Microsoft does not yet supply a 64-bit bridge from ADO to ODBC.

  • Due to differences with the installation process used on Windows and potential registry corruption, it is recommended that uninstall any existing versions of Connector/ODBC 5.1.x before upgrading.

    See also Bug#34571.

Functionality added or changed:

  • Explicit descriptors are implemented. (Bug#32064)

  • A full implementation of SQLForeignKeys based on the information available from INFORMATION_SCHEMA in 5.0 and later versions of the server has been implemented.

  • Changed SQL_ATTR_PARAMSET_SIZE to return an error until support for it is implemented.

  • Disabled MYSQL_OPT_SSL_VERIFY_SERVER_CERT when using an SSL connection.

  • SQLForeignKeys uses INFORMATION_SCHEMA when it is available on the server, which allows more complete information to be returned.

Bugs fixed:

  • The SSLCIPHER option would be incorrectly recorded within the SSL configuration on Windows. (Bug#33897)

  • Within the GUI interface, when connecting to a MySQL server on a nonstandard port, the connection test within the GUI would fail. The issue was related to incorrect parsing of numeric values within the DSN when the option was not configured as the last parameter within the DSN. (Bug#33822)

  • Specifying a nonexistent database name within the GUI dialog would result in an empty list, not an error. (Bug#33615)

  • When deleting rows from a static cursor, the cursor position would be incorrectly reported. (Bug#33388)

  • SQLGetInfo() reported characters for SQL_SPECIAL_CHARACTERS that were not encoded correctly. (Bug#33130)

  • Retrieving data from a BLOB column would fail within SQLGetDatawhen the target data type was SQL_C_WCHAR due to incorrect handling of the character buffer. (Bug#32684)

  • Renaming an existing DSN entry would create a new entry with the new name without deleting the old entry. (Bug#31165)

  • Reading a TEXT column that had been used to store UTF8 data would result in the wrong information being returned during a query. (Bug#28617)

  • SQLForeignKeys would return an empty string for the schema columns instead of NULL. (Bug#19923)

  • When accessing column data, FLAG_COLUMN_SIZE_S32 did not limit the octet length or display size reported for fields, causing problems with Microsoft Visual FoxPro.

    The list of ODBC functions that could have caused failures in Microsoft software when retrieving the length of LONGBLOB or LONGTEXT columns includes:

    • SQLColumns

    • SQLColAttribute

    • SQLColAttributes

    • SQLDescribeCol

    • SQLSpecialColumns (theoretically can have the same problem)

    (Bug#12805, Bug#30890)

  • Dynamic cursors on statements with parameters were not supported. (Bug#11846)

  • Evaluating a simple numeric expression when using the OLEDB for ODBC provider and ADO would return an error, instead of the result. (Bug#10128)

  • Adding or updating a row using SQLSetPos() on a result set with aliased columns would fail. (Bug#6157)

C.4.6. Changes in MySQL Connector/ODBC 5.1.1 (13 December 2007)

MySQL Connector/ODBC 5.1.1-beta, a new version of the ODBC driver for the MySQL database management system, has been released. This release is the first beta (feature-complete) release of the new 5.1 series and is suitable for use with any MySQL server version since MySQL 4.1, including MySQL 5.0, 5.1, and 6.0. (It will not work with 4.0 or earlier releases.)

Keep in mind that this is a beta release, and as with any other pre-production release, caution should be taken when installing on production level systems or systems with critical data.

Includes changes from Connector/ODBC 3.51.21 and 3.51.22.

Built using MySQL 5.0.52.

Platform specific notes:

  • The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.

  • There is no binary package for Mac OS X on 64-bit PowerPC because Apple does not currently provide a 64-bit PowerPC version of iODBC.

  • The installer for 64-bit Windows installs both the 32-bit and 64-bit driver. Please note that Microsoft does not yet supply a 64-bit bridge from ADO to ODBC.

  • Due to differences with the installation process used on Windows and potential registry corruption, it is recommended that uninstall any existing versions of Connector/ODBC 5.1.x before upgrading.

    See also Bug#34571.

Functionality added or changed:

  • Incompatible Change: Replaced myodbc3i (now myodbc-installer) with Connector/ODBC 5.0 version.

  • Incompatible Change: Removed monitor (myodbc3m) and dsn-editor (myodbc3c).

  • Incompatible Change: Disallow SET NAMES in initial statement and in executed statements.

  • A wrapper for the SQLGetPrivateProfileStringW() function, which is required for Unicode support, has been created. This function is missing from the unixODBC driver manager. (Bug#32685)

  • Added MSI installer for Windows 64-bit. (Bug#31510)

  • Implemented support for SQLCancel(). (Bug#15601)

  • Added support for SQL_NUMERIC_STRUCT. (Bug#3028, Bug#24920)

  • Removed nonthreadsafe configuration of the driver. The driver is now always built against the threadsafe version of libmysql.

  • Implemented native Windows setup library

  • Replaced the internal library which handles creation and loading of DSN information. The new library, which was originally a part of Connector/ODBC 5.0, supports Unicode option values.

  • The Windows installer now places files in a subdirectory of the Program Files directory instead of the Windows system directory.

Bugs fixed:

  • The SET NAMES statement has been disabled because it causes problems in the ODBC driver when determining the current client character set. (Bug#32596)

  • SQLDescribeColW returned UTF-8 column as SQL_VARCHAR instead of SQL_WVARCHAR. (Bug#32161)

  • ADO was unable to open record set using dynamic cursor. (Bug#32014)

  • ADO applications would not open a RecordSet that contained a DECIMAL field. (Bug#31720)

  • Memory usage would increase considerably. (Bug#31115)

  • SQL statements are limited to 64KB. (Bug#30983, Bug#30984)

  • SQLSetPos with SQL_DELETE advances dynamic cursor incorrectly. (Bug#29765)

  • Using an ODBC prepared statement with bound columns would produce an empty result set when called immediately after inserting a row into a table. (Bug#29239)

  • ADO Not possible to update a client side cursor. (Bug#27961)

  • Recordset Update() fails when using adUseClient cursor. (Bug#26985)

  • Connector/ODBC would fail to connect to the server if the password contained certain characters, including the semicolon and other punctuation marks. (Bug#16178)

  • Fixed SQL_ATTR_PARAM_BIND_OFFSET, and fixed row offsets to work with updatable cursors.

  • SQLSetConnectAttr() did not clear previous errors, possibly confusing SQLError().

  • SQLError() incorrectly cleared the error information, making it unavailable from subsequent calls to SQLGetDiagRec().

  • NULL pointers passed to SQLGetInfo() could result in a crash.

  • SQL_ODBC_SQL_CONFORMANCE was not handled by SQLGetInfo().

  • SQLCopyDesc() did not correctly copy all records.

  • Diagnostics were not correctly cleared on connection and environment handles.

C.4.7. Changes in MySQL Connector/ODBC 5.1.0 (10 September 2007)

This release is the first of the new 5.1 series and is suitable for use with any MySQL server version since MySQL 4.1, including MySQL 5.0, 5.1, and 6.0. (It will not work with 4.0 or earlier releases.)

Keep in mind that this is a alpha release, and as with any other pre-production release, caution should be taken when installing on production level systems or systems with critical data. Not all of the features planned for the final Connector/ODBC 5.1 release are implemented.

Functionality is based on Connector/ODBC 3.51.20.

Platform specific notes:

  • The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.

  • There is no binary package for Mac OS X on 64-bit PowerPC because Apple does not currently provide a 64-bit PowerPC version of iODBC.

  • There are no installer packages for Microsoft Windows x64 Edition.

  • Due to differences with the installation process used on Windows and potential registry corruption, it is recommended that uninstall any existing versions of Connector/ODBC 5.1.x before upgrading.

    See also Bug#34571.

Functionality added or changed:

  • Added support for Unicode functions (SQLConnectW, etc).

  • Added descriptor support (SQLGetDescField, SQLGetDescRec, etc).

  • Added support for SQL_C_WCHAR.

C.4.8. Changes in MySQL Connector/ODBC 5.0.12 (Never released)


Development on Connector/ODBC 5.0.x has ceased. New features and functionality will be incorporated into Connector/ODBC 5.1. See Section, “Connector/ODBC Roadmap”.

Bugs fixed:

  • Inserting NULL values into a DATETIME column from Access reports an error. (Bug#27896)

  • Tables with TEXT columns would be incorrectly identified, returning an Unknown SQL type - 65535 error. (Bug#20127)

C.4.9. Changes in MySQL Connector/ODBC 5.0.11 (31 January 2007)

Functionality added or changed:

  • Added support for ODBC v2 statement options using attributes.

  • Driver now builds and is partially tested under Linux with the iODBC driver manager.

Bugs fixed:

  • Connection string parsing for DSN-less connections could fail to identify some parameters. (Bug#25316)

  • Updates of MEMO or TEXT columns from within Microsoft Access would fail. (Bug#25263)

  • Transaction support has been added and tested. (Bug#25045)

  • Internal function, my_setpos_delete_ignore() could cause a crash. (Bug#22796)

  • Fixed occasional mis-handling of the SQL_NUMERIC_C type.

  • Fixed the binding of certain integer types.

C.4.10. Changes in MySQL Connector/ODBC 5.0.10 (14 December 2006)

Connector/ODBC 5.0.10 is the sixth BETA release.

Functionality added or changed:

  • Significant performance improvement when retrieving large text fields in pieces using SQLGetData() with a buffer smaller than the whole data. Mainly used in Access when fetching very large text fields. (Bug#24876)

  • Added initial unicode support in data and metadata. (Bug#24837)

  • Added initial support for removing braces when calling stored procedures and retrieving result sets from procedure calls. (Bug#24485)

  • Added loose handling of retrieving some diagnostic data. (Bug#15782)

  • Added wide-string type info for SQLGetTypeInfo().

Bugs fixed:

  • Editing DSN no longer crashes ODBC data source administrator. (Bug#24675)

  • String query parameters are new escaped correctly. (Bug#19078)

C.4.11. Changes in MySQL Connector/ODBC 5.0.9 (22 November 2006)

Connector/ODBC 5.0.9 is the fifth BETA release.

This is an implementation and testing release, and is not designed for use within a production environment.

Functionality added or changed:

  • Added support for column binding as SQL_NUMBERIC_STRUCT.

  • Added recognition of SQL_C_SHORT and SQL_C_TINYINT as C types.

Bugs fixed:

  • Fixed wildcard handling of and listing of catalogs and tables in SQLTables.

  • Added limit of display size when requested via SQLColAttribute/SQL_DESC_DISPLAY_SIZE.

  • Fixed buffer length return for SQLDriverConnect.

  • ODBC v2 behaviour in driver now supports ODBC v3 date/time types (since DriverManager maps them).

  • Catch use of SQL_ATTR_PARAMSET_SIZE and report error until we fully support.

  • Fixed statistics to fail if it couldn't be completed.

  • Corrected retrieval multiple field types bit and blob/text.

  • Fixed SQLGetData to clear the NULL indicator correctly during multiple calls.

C.4.12. Changes in MySQL Connector/ODBC 5.0.8 (17 November 2006)

Connector/ODBC 5.0.8 is the fourth BETA release.

This is an implementation and testing release, and is not designed for use within a production environment.

Functionality added or changed:

  • Also made SQL_DESC_NAME only fill in the name if there was a data pointer given, otherwise just the length.

  • Fixed display size to be length if max length isn’t available.

  • Made distinction between CHAR/BINARY (and VAR versions).

  • Wildcards now support escaped chars and underscore matching (needed to link tables with underscores in access).

Bugs fixed:

  • Fixed binding using SQL_C_LONG.

  • Fixed using wrong pointer for SQL_MAX_DRIVER_CONNECTIONS in SQLGetInfo.

  • Set default return to SQL_SUCCESS if nothing is done for SQLSpecialColumns.

  • Fixed MDiagnostic to use correct v2/v3 error codes.

  • Allow SQLDescribeCol to be called to retrieve the length of the column name, but not the name itself.

  • Length now used when handling bind parameter (needed in particular for SQL_WCHAR) - this enables updating char data in MS Access.

  • Updated retrieval of descriptor fields to use the right pointer types.

  • Fixed hanlding of numeric pointers in SQLColAttribute.

  • Fixed type returned for MYSQL_TYPE_LONG to SQL_INTEGER instead of SQL_TINYINT.

  • Fix size return from SQLDescribeCol.

  • Fixed string length to chars, not bytes, returned by SQLGetDiagRec.

C.4.13. Changes in MySQL Connector/ODBC 5.0.7 (08 November 2006)

Connector/ODBC 5.0.7 is the third BETA release.

This is an implementation and testing release, and is not designed for use within a production environment.

Functionality added or changed:

  • Added support for SQLStatistics to MYODBCShell.

  • Improved trace/log.

Bugs fixed:

  • SQLBindParameter now handles SQL_C_DEFAULT.

  • Corrected incorrect column index within SQLStatistics. Many more tables can now be linked into MS Access.

  • Fixed SQLDescribeCol returning column name length in bytes rather than chars.

C.4.14. Changes in MySQL Connector/ODBC 5.0.6 (03 November 2006)

Connector/ODBC 5.0.6 is the second BETA release.

This is an implementation and testing release, and is not designed for use within a production environment.

Features, limitations and notes on this release

  • Connector/ODBC supports both User and System DSNs.

  • Installation is provided in the form of a standard Microsoft System Installer (MSI).

  • You no longer have to have Connector/ODBC 3.51 installed before installing this version.

Bugs fixed:

  • You no longer have to have Connector/ODBC 3.51 installed before installing this version.

  • Connector/ODBC supports both User and System DSNs.

  • Installation is provided in the form of a standard Microsoft System Installer (MSI).

C.4.15. Changes in MySQL Connector/ODBC 5.0.5 (17 October 2006)

Connector/ODBC 5.0.5 is the first BETA release.

This is an implementation and testing release, and is not designed for use within a production environment.

You no longer have to have Connector/ODBC 3.51 installed before installing this version.

Bugs fixed:

  • You no longer have to have Connector/ODBC 3.51 installed before installing this version.

C.4.16. Changes in Connector/ODBC 5.0.3 (Connector/ODBC 5.0 Alpha 3) (20 June 2006)

This is an implementation and testing release, and is not designed for use within a production environment.

Features, limitations and notes on this release:

  • The following ODBC API functions have been added in this release:

    • SQLBindParameter

    • SQLBindCol

C.4.17. Changes in Connector/ODBC 5.0.2 (Never released)

Connector/ODBC 5.0.2 was an internal implementation and testing release.

C.4.18. Changes in Connector/ODBC 5.0.1 (Connector/ODBC 5.0 Alpha 2) (05 June 2006)

Features, limitations and notes on this release:

  • Connector/ODBC 5.0 is Unicode aware.

  • Connector/ODBC is currently limited to basic applications. ADO applications and Microsoft Office are not supported.

  • Connector/ODBC must be used with a Driver Manager.

  • The following ODBC API functions are implemented:

    • SQLAllocHandle

    • SQLCloseCursor

    • SQLColAttribute

    • SQLColumns

    • SQLConnect

    • SQLCopyDesc

    • SQLDisconnect

    • SQLExecDirect

    • SQLExecute

    • SQLFetch

    • SQLFreeHandle

    • SQLFreeStmt

    • SQLGetConnectAttr

    • SQLGetData

    • SQLGetDescField

    • SQLGetDescRec

    • SQLGetDiagField

    • SQLGetDiagRec

    • SQLGetEnvAttr

    • SQLGetFunctions

    • SQLGetStmtAttr

    • SQLGetTypeInfo

    • SQLNumResultCols

    • SQLPrepare

    • SQLRowcount

    • SQLTables

    The following ODBC API function are implemented, but not yet support all the available attributes/options:

    • SQLSetConnectAttr

    • SQLSetDescField

    • SQLSetDescRec

    • SQLSetEnvAttr

    • SQLSetStmtAttr

C.4.19. Changes in MySQL Connector/ODBC 3.51.27 (20 November 2008)

Bugs fixed:

  • The client program hung when the network connection to the server was interrupted. (Bug#40407)

  • The connection string option Enable Auto-reconnect did not work. When the connection failed, it could not be restored, and the errors generated were the same as if the option had not been selected. (Bug#37179)

  • It was not possible to use Connector/ODBC to connect to a server using SSL. The following error was generated:

    Runtime error '-2147467259 (80004005)':
    [MySQL][ODBC 3.51 Driver]SSL connection error.


C.4.20. Changes in MySQL Connector/ODBC 3.51.26 (07 July 2008)

Functionality added or changed:

  • There is a new connection option, FLAG_NO_BINARY_RESULT. When set this option disables charset 63 for columns with an empty org_table. (Bug#29402)

Bugs fixed:

  • When an ADOConnection is created and attempts to open a schema with ADOConnection.OpenSchema an access violation occurs in myodbc3.dll. (Bug#30770)

  • When SHOW CREATE TABLE was invoked and then the field values read, the result was truncated and unusable if the table had many rows and indexes. (Bug#24131)

C.4.21. Changes in MySQL Connector/ODBC 3.51.25 (11 April 2008)

Bugs fixed:

  • The SQLColAttribute() function returned SQL_TRUE when querying the SQL_DESC_FIXED_PREC_SCALE (SQL_COLUMN_MONEY) attribute of a DECIMAL column. Previously, the correct value of SQL_FALSE was returned; this is now again the case. (Bug#35581)

  • The driver crashes ODBC Administrator on attempting to add a new DSN. (Bug#32057)

  • When accessing column data, FLAG_COLUMN_SIZE_S32 did not limit the octet length or display size reported for fields, causing problems with Microsoft Visual FoxPro.

    The list of ODBC functions that could have caused failures in Microsoft software when retrieving the length of LONGBLOB or LONGTEXT columns includes:

    • SQLColumns

    • SQLColAttribute

    • SQLColAttributes

    • SQLDescribeCol

    • SQLSpecialColumns (theoretically can have the same problem)

    (Bug#12805, Bug#30890)

C.4.22. Changes in MySQL Connector/ODBC 3.51.24 (14 March 2008)

Bugs fixed:

  • Security Enhancement: Accessing a parameer with the type of SQL_C_CHAR, but with a numeric type and a length of zero, the parameter marker would get stropped from the query. In addition, an SQL injection was possible if the parameter value had a nonzero length and was not numeric, the text would be inserted verbatim. (Bug#34575)

  • Important Change: In previous versions, the SSL certificate would automatically be verified when used as part of the Connector/ODBC connection. The default mode is now to ignore the verificate of certificates. To enforce verification of the SSL certificate during connection, use the SSLVERIFY DSN parameter, setting the value to 1. (Bug#29955, Bug#34648)

  • When using ADO, the count of parameters in a query would always return zero. (Bug#33298)

  • Using tables with a single quote or other nonstandard characters in the table or column names through ODBC would fail. (Bug#32989)

  • When using Crystal Reports, table and column names would be truncated to 21 characters, and truncated columns in tables where the truncated name was the duplicated would lead to only a single column being displayed. (Bug#32864)

  • SQLExtendedFetch() and SQLFetchScroll() ignored the rowset size if the Don't cache result DSN option was set. (Bug#32420)

  • When using the ODBC SQL_TXN_READ_COMMITTED option, 'dirty' records would be read from tables as if the option had not been applied. (Bug#31959)

  • When creating a System DSN using the ODBC Administrator on Mac OS X, a User DSN would be created instead. The root cause is a problem with the iODBC driver manager used on Mac OS X. The fix works around this issue.


    ODBC Administrator may still be unable to register a System DSN unless the /Library/ODBC/odbc.ini file has the correct permissions. You should ensure that the file is writable by the admin group.


  • Calling SQLFetch or SQLFetchScroll would return negative data lengths when using SQL_C_WCHAR. (Bug#31220)

  • SQLSetParam() caused memory allocation errors due to driver manager's mapping of deprecated functions (buffer length -1). (Bug#29871)

  • Static cursor was unable to be used through ADO when dynamic cursors were enabled. (Bug#27351)

  • Using connection.Execute to create a record set based on a table without declaring the cmd option as adCmdTable will fail when communicating with versions of MySQL 5.0.37 and higher. The issue is related to the way that SQLSTATE is returned when ADO tries to confirm the existence of the target object. (Bug#27158)

  • Updating a RecordSet when the query involves a BLOB field would fail. (Bug#19065)

  • With some connections to MySQL databases using Connector/ODBC, the connection would mistakenly report 'user cancelled' for accesses to the database information. (Bug#16653)

C.4.23. Changes in MySQL Connector/ODBC 3.51.23 (09 January 2008)

Platform specific notes:

  • The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.

  • There is no binary package for Mac OS X on 64-bit PowerPC because Apple does not currently provide a 64-bit PowerPC version of iODBC.

  • There are no installer packages for Microsoft Windows x64 Edition.

Bugs fixed:

  • Connector/ODBC would incorrectly return SQL_SUCCESS when checking for distributed transaction support. (Bug#32727)

  • When using unixODBC or directly linked applications where the thread level is set to less than 3 (within odbcinst.ini), a thread synchronization issue would lead to an application crash. This was because SQLAllocStmt() and SQLFreeStmt() did not synchronize access to the list of statements associated with a connection. (Bug#32587)

  • Cleaning up environment handles in multithread environments could result in a five (or more) second delay. (Bug#32366)

  • Renaming an existing DSN entry would create a new entry with the new name without deleting the old entry. (Bug#31165)

  • Setting the default database using the DefaultDatabase property of an ADO Connection object would fail with the error Provider does not support this property. The SQLGetInfo() returned the wrong value for SQL_DATABASE_NAME when no database was selected. (Bug#3780)

C.4.24. Changes in MySQL Connector/ODBC 3.51.22 (13 November 2007)

Functionality added or changed:

  • The workaround for this bug was removed due to the fixes in MySQL Server 5.0.48 and 5.1.21.

    This regression was introduced by Bug#10491.

Bugs fixed:

  • The English locale would be used when formatting floating point values. The C locale is now used for these values. (Bug#32294)

  • When accessing information about supported operations, the driver would return incorrect information about the support for UNION. (Bug#32253)

  • Unsigned integer values greater than the maximum value of a signed integer would be handled incorrectly. (Bug#32171)

  • The wrong result was returned by SQLGetData() when the data was an empty string and a zero-sized buffer was specified. (Bug#30958)

  • Added the FLAG_COLUMN_SIZE_S32 option to limit the reported column size to a signed 32-bit integer. This option is automatically enabled for ADO applications to provide a work around for a bug in ADO. (Bug#13776)

C.4.25. Changes in MySQL Connector/ODBC 3.51.21 (08 October 2007)

Bugs fixed:

  • When using a rowset/cursor and add a new row with a number of fields, subsequent rows with fewer fields will include the original fields from the previous row in the final INSERT statement. (Bug#31246)

  • Uninitiated memory could be used when C/ODBC internally calls SQLGetFunctions(). (Bug#31055)

  • The wrong SQL_DESC_LITERAL_PREFIX would be returned for date/time types. (Bug#31009)

  • The wrong COLUMN_SIZE would be returned by SQLGetTypeInfo for the TIME columns (SQL_TYPE_TIME). (Bug#30939)

  • Clicking outside the character set selection box when configuring a new DSN could cause the wrong character set to be selected. (Bug#30568)

  • Not specifying a user in the DSN dialog would raise a warning even though the parameter is optional. (Bug#30499)

  • SQLSetParam() caused memory allocation errors due to driver manager's mapping of deprecated functions (buffer length -1). (Bug#29871)

  • When using ADO, a column marked as AUTO_INCREMENT could incorrectly report that the column allowed NULL values. This was dur to an issue with NULLABLE and IS_NULLABLE return values from the call to SQLColumns(). (Bug#26108)

  • Connector/ODBC would return the wrong the error code when the server disconnects the active connection because the configured wait_timeout has expired. Previously it would return HY000. Connector/ODBC now correctly returns an SQLSTATE of 08S01. (Bug#3456)

C.4.26. Changes in MySQL Connector/ODBC 3.51.20 (10 September 2007)

Bugs fixed:

  • Using FLAG_NO_PROMPT doesn't suppress the dialogs normally handled by SQLDriverConnect. (Bug#30840)

  • The specified length of the user name and authentication parameters to SQLConnect() were not being honored. (Bug#30774)

  • The wrong column size was returned for binary data. (Bug#30547)

  • SQLGetData() will now always return SQL_NO_DATA_FOUND on second call when no data left, even if requested size is 0. (Bug#30520)

  • SQLGetConnectAttr() did not reflect the connection state correctly. (Bug#14639)

  • Removed checkbox in setup dialog for FLAG_FIELD_LENGTH (identified as Don't Optimize Column Width within the GUI dialog), which was removed from the driver in 3.51.18.

C.4.27. Changes in MySQL Connector/ODBC 3.51.19 (10 August 2007)

Connector/ODBC 3.51.19 fixes a specific issue with the 3.51.18 release. For a list of changes in the 3.51.18 release, see Section C.4.28, “Changes in MySQL Connector/ODBC 3.51.18 (08 August 2007)”.

Functionality added or changed:

  • Because of Bug#10491 in the server, character string results were sometimes incorrectly identified as SQL_VARBINARY. Until this server bug is corrected, the driver will identify all variable-length strings as SQL_VARCHAR.

C.4.28. Changes in MySQL Connector/ODBC 3.51.18 (08 August 2007)

Platform specific notes:

  • The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.

  • There is no binary package for Mac OS X on 64-bit PowerPC because Apple does not currently provide a 64-bit PowerPC version of iODBC.

  • Binary packages for Sun Solaris are now available as PKG packages.

  • Binary packages as disk images with installers are now available for Mac OS X.

  • A binary package without an installer is available for Microsoft Windows x64 Edition. There are no installer packages for Microsoft Windows x64 Edition.

Functionality added or changed:

  • Incompatible Change: The FLAG_DEBUG option was removed.

  • When connecting to a specific database when using a DSN, the system tables from the mysql database are no longer also available. Previously, tables from the mysql database (catalog) were listed as SYSTEM TABLES by SQLTables() even when a different catalog was being queried. (Bug#28662)

  • Installed for Mac OS X has been re-instated. The installer registers the driver at a system (not user) level and makes it possible to create both user and system DSNs using the Connector/ODBC driver. The installer also fixes the situation where the necessary drivers would bge installed local to the user, not globally. (Bug#15326, Bug#10444)

  • Connector/ODBC now supports batched statements. In order to enable cached statement support you must switch enable the batched statement option (FLAG_MULTI_STATEMENTS, 67108864, or Allow multiple statements within a GUI configuration). Be aware that batched statements create an increased chance of SQL injection attacks and you must ensure that your application protects against this scenario. (Bug#7445)

  • The SQL_ATTR_ROW_BIND_OFFSET_PTR is now supported for row bind offsets. (Bug#6741)

  • The TRACE and TRACEFILE DSN options have been removed. Use the ODBC driver manager trace options instead.

Bugs fixed:

  • When using a table with multiple TIMESTAMP columns, the final TIMESTAMP column within the table definition would not be updateable. Note that there is still a limitation in MySQL server regarding multiple TIMESTAMP columns . (Bug#9927) (Bug#30081)

  • Fixed an issue where the myodbc3i would update the user ODBC configuration file (~/Library/ODBC/odbcinst.ini) instead of the system /Library/ODBC/odbcinst.ini. This was caused because myodbc3i was not honoring the s and u modifiers for the -d command-line option. (Bug#29964)

  • Getting table metadata (through the SQLColumns() would fail, returning a bad table definition to calling applications. (Bug#29888)

  • DATETIME column types would return FALSE in place of SQL_SUCCESS when requesting the column type information. (Bug#28657)

  • The SQL_COLUMN_TYPE, SQL_COLUMN_DISPLAY and SQL_COLUMN_PRECISION values would be returned incorrectly by SQLColumns(), SQLDescribeCol() and SQLColAttribute() when accessing character columns, especially those generated through concat(). The lengths returned should now conform to the ODBC specification. The FLAG_FIELD_LENGTH option no longer has any affect on the results returned. (Bug#27862)

  • Obtaining the length of a column when using a character set for the connection of utf8 would result in the length being returned incorrectly. (Bug#19345)

  • The SQLColumns() function could return incorrect information about TIMESTAMP columns, indicating that the field was not nullable. (Bug#14414)

  • The SQLColumns() function could return incorrect information about AUTO_INCREMENT columns, indicating that the field was not nullable. (Bug#14407)

  • A binary package without an installer is available for Microsoft Windows x64 Edition. There are no installer packages for Microsoft Windows x64 Edition.

  • There is no binary package for Mac OS X on 64-bit PowerPC because Apple does not currently provide a 64-bit PowerPC version of iODBC.

  • BIT(n) columns are now treated as SQL_BIT data where n = 1 and binary data where n > 1.

  • The wrong value from SQL_DESC_LITERAL_SUFFIX was returned for binary fields.

  • The SQL_DATETIME_SUB column in SQLColumns() was not correctly set for date and time types.

  • The value for SQL_DESC_FIXED_PREC_SCALE was not returned correctly for values in MySQL 5.0 and later.

  • The wrong value for SQL_DESC_TYPE was returned for date and time types.

  • SQLConnect() and SQLDriverConnect() were rewritten to eliminate duplicate code and ensure all options were supported using both connection methods. SQLDriverConnect() now only requires the setup library to be present when the call requires it.

  • The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.

  • Binary packages as disk images with installers are now available for Mac OS X.

  • Binary packages for Sun Solaris are now available as PKG packages.

  • The wrong value for DECIMAL_DIGITS in SQLColumns() was reported for FLOAT and DOUBLE fields, as well as the wrong value for the scale parameter to SQLDescribeCol(), and the SQL_DESC_SCALE attribute from SQLColAttribute().

  • The SQL_DATA_TYPE column in SQLColumns() results did not report the correct value for date and time types.

C.4.29. Changes in MySQL Connector/ODBC 3.51.17 (14 July 2007)

Platform specific notes:

  • The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.

  • There is no binary package for Mac OS X on 64-bit PowerPC because Apple does not currently provide a 64-bit PowerPC version of iODBC.

  • Binary packages for Sun Solaris are now available as PKG packages.

  • Binary packages as disk images with installers are now available for Mac OS X.

  • A binary package without an installer is available for Microsoft Windows x64 Edition. There are no installer packages for Microsoft Windows x64 Edition.

Functionality added or changed:

  • It is now possible to specify a different character set as part of the DSN or connection string. This must be used instead of the SET NAMES statement. You can also configure the character set value from the GUI configuration. (Bug#9498, Bug#6667)

  • Fixed calling convention ptr and wrong free in myodbc3i, and fixed the null terminating (was only one, not two) when writing DSN to string.

  • Dis-allow NULL ptr for null indicator when calling SQLGetData() if value is null. Now returns SQL_ERROR w/state 22002.

  • The setup library has been split into its own RPM package, to allow installing the driver itself with no GUI dependencies.

Bugs fixed:

  • myodbc3i did not correctly format driver info, which could cause the installation to fail. (Bug#29709)

  • Connector/ODBC crashed with Crystal Reports due to a rproblem with SQLProcedures(). (Bug#28316)

  • Fixed a problem where the GUI would crash when configuring or removing a System or User DSN. (Bug#27315)

  • Fixed error handling of out-of-memory and bad connections in catalog functions. This might raise errors in code paths that had ignored them in the past. (Bug#26934)

  • For a stored procedure that returns multiple result sets, Connector/ODBC returned only the first result set. (Bug#16817)

  • Calling SQLGetDiagField with RecNumber 0, DiagIdentifier NOT 0 returned SQL_ERROR, preventing access to diagnostic header fields. (Bug#16224)

  • Added a new DSN option (FLAG_ZERO_DATE_TO_MIN) to retrieve XXXX-00-00 dates as the minimum allowed ODBC date (XXXX-01-01). Added another option (FLAG_MIN_DATE_TO_ZERO) to mirror this but for bound parameters. FLAG_MIN_DATE_TO_ZERO only changes 0000-01-01 to 0000-00-00. (Bug#13766)

  • If there was more than one unique key on a table, the correct fields were not used in handling SQLSetPos(). (Bug#10563)

  • When inserting a large BLOB field, Connector/ODBC would crash due to a memory allocation error. (Bug#10562)

  • The driver was using mysql_odbc_escape_string(), which does not handle the NO_BACKSLASH_ESCAPES SQL mode. Now it uses mysql_real_escape_string(), which does. (Bug#9498)

  • SQLColumns() did not handle many of its parameters correctly, which could lead to incorrect results. The table name argument was not handled as a pattern value, and most arguments were not escaped correctly when they contained nonalphanumeric characters. (Bug#8860)

  • There are no binary packages for Microsoft Windows x64 Edition.

  • There is no binary package for Mac OS X on 64-bit PowerPC because Apple does not currently provide a 64-bit PowerPC version of iODBC.

  • Correctly return error if SQLBindCol is called with an invalid column.

  • Fixed possible crash if SQLBindCol() was not called before SQLSetPos().

  • The Mac OS X binary packages are only provided as tarballs, there is no installer.

  • The binary packages for Sun Solaris are only provided as tarballs, not the PKG format.

  • The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.

C.4.30. Changes in MySQL Connector/ODBC 3.51.16 (14 June 2007)

Functionality added or changed:

  • Connector/ODBC now supports using SSL for communication. This is not yet exposed in the setup GUI, but must be enabled through configuration files or the DSN. (Bug#12918)

Bugs fixed:

  • Calls to SQLNativeSql() could cause stack corruption due to an incorrect pointer cast. (Bug#28758)

  • Using curors on results sets with multi-column keys could select the wrong value. (Bug#28255)

  • SQLForeignKeys does not escape _ and % in the table name arguments. (Bug#27723)

  • When using stored procedures, making a SELECT or second stored procedure call after an initial stored procedure call, the second statement will fail. (Bug#27544)

  • SQLTables() did not distinguish tables from views. (Bug#23031)

  • Data in TEXT columns would fail to be read correctly. (Bug#16917)

  • Specifying strings as parameters using the adBSTR or adVarWChar types, (SQL_WVARCHAR and SQL_WLONGVARCHAR) would be incorrectly quoted. (Bug#16235)

  • SQL_WVARCHAR and SQL_WLONGVARCHAR parameters were not properly quoted and escaped. (Bug#16235)

  • Using BETWEEN with date values, the wrong results could be returned. (Bug#15773)

  • When using the Don't Cache Results (option value 1048576) with Microsoft Access, the connection will fail using DAO/VisualBasic. (Bug#4657)

  • Return values from SQLTables() may be truncated. (Bugs #22797)

C.4.31. Changes in MySQL Connector/ODBC 3.51.15 (07 May 2007)

Bugs fixed:

  • Connector/ODBC would incorrectly claim to support SQLProcedureColumns (by returning true when queri