Appendix D. MySQL Change History

Table of Contents

D.1. Changes in Release 5.5.x (Development)
D.1.1. Changes in MySQL 5.5.7 (Not yet released)
D.1.2. Changes in MySQL 5.5.6 (13 September 2010 Release Candidate)
D.1.3. Changes in MySQL 5.5.5 (06 July 2010)
D.1.4. Changes in MySQL 5.5.4 (09 April 2010)
D.1.5. Changes in MySQL 5.5.3 (24 March 2010 Milestone 3)
D.1.6. Changes in MySQL 5.5.2 (12 February 2010)
D.1.7. Changes in MySQL 5.5.1 (04 January 2010)
D.1.8. Changes in MySQL 5.5.0 (07 December 2009 Milestone 2)
D.2. MySQL Enterprise Monitor Change History
D.2.1. Changes in MySQL Enterprise Monitor 2.1.2 (26 May 2010)
D.2.2. Changes in MySQL Enterprise Monitor 2.1.1 (10 February 2010)
D.2.3. Changes in MySQL Enterprise Monitor 2.1.0 (08 September 2009)
D.3. MySQL Connector/ODBC (MyODBC) Change History
D.3.1. Changes in MySQL Connector/ODBC 5.1.8 (Not yet released)
D.3.2. Changes in MySQL Connector/ODBC 5.1.7 (24 August 2010)
D.3.3. Changes in MySQL Connector/ODBC 5.1.6 (09 November 2009)
D.3.4. Changes in MySQL Connector/ODBC 5.1.5 (18 August 2008)
D.3.5. Changes in MySQL Connector/ODBC 5.1.4 (15 April 2008)
D.3.6. Changes in MySQL Connector/ODBC 5.1.3 (26 March 2008)
D.3.7. Changes in MySQL Connector/ODBC 5.1.2 (13 February 2008)
D.3.8. Changes in MySQL Connector/ODBC 5.1.1 (13 December 2007)
D.3.9. Changes in MySQL Connector/ODBC 5.1.0 (10 September 2007)
D.3.10. Changes in MySQL Connector/ODBC 5.0.12 (Never released)
D.3.11. Changes in MySQL Connector/ODBC 5.0.11 (31 January 2007)
D.3.12. Changes in MySQL Connector/ODBC 5.0.10 (14 December 2006)
D.3.13. Changes in MySQL Connector/ODBC 5.0.9 (22 November 2006)
D.3.14. Changes in MySQL Connector/ODBC 5.0.8 (17 November 2006)
D.3.15. Changes in MySQL Connector/ODBC 5.0.7 (08 November 2006)
D.3.16. Changes in MySQL Connector/ODBC 5.0.6 (03 November 2006)
D.3.17. Changes in MySQL Connector/ODBC 5.0.5 (17 October 2006)
D.3.18. Changes in Connector/ODBC 5.0.3 (Connector/ODBC 5.0 Alpha 3) (20 June 2006)
D.3.19. Changes in Connector/ODBC 5.0.2 (Never released)
D.3.20. Changes in Connector/ODBC 5.0.1 (Connector/ODBC 5.0 Alpha 2) (05 June 2006)
D.3.21. Changes in MySQL Connector/ODBC 3.51.28 (Not yet released)
D.3.22. Changes in MySQL Connector/ODBC 3.51.27 (20 November 2008)
D.3.23. Changes in MySQL Connector/ODBC 3.51.26 (07 July 2008)
D.3.24. Changes in MySQL Connector/ODBC 3.51.25 (11 April 2008)
D.3.25. Changes in MySQL Connector/ODBC 3.51.24 (14 March 2008)
D.3.26. Changes in MySQL Connector/ODBC 3.51.23 (09 January 2008)
D.3.27. Changes in MySQL Connector/ODBC 3.51.22 (13 November 2007)
D.3.28. Changes in MySQL Connector/ODBC 3.51.21 (08 October 2007)
D.3.29. Changes in MySQL Connector/ODBC 3.51.20 (10 September 2007)
D.3.30. Changes in MySQL Connector/ODBC 3.51.19 (10 August 2007)
D.3.31. Changes in MySQL Connector/ODBC 3.51.18 (08 August 2007)
D.3.32. Changes in MySQL Connector/ODBC 3.51.17 (14 July 2007)
D.3.33. Changes in MySQL Connector/ODBC 3.51.16 (14 June 2007)
D.3.34. Changes in MySQL Connector/ODBC 3.51.15 (07 May 2007)
D.3.35. Changes in MySQL Connector/ODBC 3.51.14 (08 March 2007)
D.3.36. Changes in MySQL Connector/ODBC 3.51.13 (Never released)
D.3.37. Changes in MySQL Connector/ODBC 3.51.12 (11 February 2005)
D.3.38. Changes in MySQL Connector/ODBC 3.51.11 (28 January 2005)
D.4. MySQL Connector/NET Change History
D.4.1. Changes in MySQL Connector/NET Version 6.3.x
D.4.2. Changes in MySQL Connector/NET Version 6.2.x
D.4.3. Changes in MySQL Connector/NET Version 6.1.x
D.4.4. Changes in MySQL Connector/NET Version 6.0.x
D.4.5. Changes in MySQL Connector/NET Version 5.3.x
D.4.6. Changes in MySQL Connector/NET Version 5.2.x
D.4.7. Changes in MySQL Connector/NET Version 5.1.x
D.4.8. Changes in MySQL Connector/NET Version 5.0.x
D.4.9. Changes in MySQL Connector/NET Version 1.0.x
D.4.10. Changes in MySQL Connector/NET Version 0.9.0 (30 August 2004)
D.4.11. Changes in MySQL Connector/NET Version 0.76
D.4.12. Changes in MySQL Connector/NET Version 0.75
D.4.13. Changes in MySQL Connector/NET Version 0.74
D.4.14. Changes in MySQL Connector/NET Version 0.71
D.4.15. Changes in MySQL Connector/NET Version 0.70
D.4.16. Changes in MySQL Connector/NET Version 0.68
D.4.17. Changes in MySQL Connector/NET Version 0.65
D.4.18. Changes in MySQL Connector/NET Version 0.60
D.4.19. Changes in MySQL Connector/NET Version 0.50
D.5. MySQL Visual Studio Plugin Change History
D.5.1. Changes in MySQL Visual Studio Plugin 1.0.3 (Not yet released)
D.5.2. Changes in MySQL Visual Studio Plugin 1.0.2 (Not yet released)
D.5.3. Changes in MySQL Visual Studio Plugin 1.0.1 (04 October 2006)
D.5.4. Changes in MySQL Visual Studio Plugin 1.0.0 (04 October 2006)
D.6. MySQL Connector/J Change History
D.6.1. Changes in MySQL Connector/J 5.1.x
D.6.2. Changes in MySQL Connector/J 5.0.x
D.6.3. Changes in MySQL Connector/J 3.1.x
D.6.4. Changes in MySQL Connector/J 3.0.x
D.6.5. Changes in MySQL Connector/J 2.0.x
D.6.6. Changes in MySQL Connector/J 1.2b (04 July 1999)
D.6.7. Changes in MySQL Connector/J 1.2.x and lower
D.7. MySQL Connector/MXJ Change History
D.7.1. Changes in MySQL Connector/MXJ 5.0.11 (24th November 2009)
D.7.2. Changes in MySQL Connector/MXJ 5.0.10 (Never released)
D.7.3. Changes in MySQL Connector/MXJ 5.0.9 (19 August 2008)
D.7.4. Changes in MySQL Connector/MXJ 5.0.8 (06 August 2007)
D.7.5. Changes in MySQL Connector/MXJ 5.0.7 (27 May 2007)
D.7.6. Changes in MySQL Connector/MXJ 5.0.6 (04 May 2007)
D.7.7. Changes in MySQL Connector/MXJ 5.0.5 (14 March 2007)
D.7.8. Changes in MySQL Connector/MXJ 5.0.4 (28 January 2007)
D.7.9. Changes in MySQL Connector/MXJ 5.0.3 (24 June 2006)
D.7.10. Changes in MySQL Connector/MXJ 5.0.2 (15 June 2006)
D.7.11. Changes in MySQL Connector/MXJ 5.0.1 (Never released)
D.7.12. Changes in MySQL Connector/MXJ 5.0.0 (09 December 2005)
D.8. MySQL Connector/C++ Change History
D.8.1. Changes in MySQL Connector/C++ 1.1.x
D.8.2. Changes in MySQL Connector/C++ 1.0.x
D.9. MySQL Proxy Change History
D.9.1. Changes in MySQL Proxy 0.8.1 (13 September 2010)
D.9.2. Changes in MySQL Proxy 0.8.0 (21 January 2010)
D.9.3. Changes in MySQL Proxy 0.7.2 (30 June 2009)
D.9.4. Changes in MySQL Proxy 0.7.1 (15 May 2009)
D.9.5. Changes in MySQL Proxy 0.7.0 (Not Released)
D.9.6. Changes in MySQL Proxy 0.6.1 (06 February 2008)
D.9.7. Changes in MySQL Proxy 0.6.0 (11 September 2007)
D.9.8. Changes in MySQL Proxy 0.5.1 (30 June 2007)
D.9.9. 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 5.5, which is currently MySQL 5.5.8. We offer a version of the Manual for each series of MySQL releases (5.0, 5.1, and so forth). For information about changes in another release series of the MySQL database software, see the corresponding version of this Manual.

We update this section as we add new features in the 5.5 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 (http://dev.mysql.com/downloads/), it means that the version has not yet been released.

The date mentioned with a release version is the date of the last Bazaar ChangeSet 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.

D.1. Changes in Release 5.5.x (Development)

An overview of features added in MySQL 5.5 can be found here: Section 1.5, “What Is New in MySQL 5.5”. For a full list of changes, please refer to the changelog sections for individual 5.5 releases.

For discussion of upgrade issues that you may encounter for upgrades from MySQL 5.1 to MySQL 5.5, see Section 2.13.1.1, “Upgrading from MySQL 5.1 to 5.5”.

For discussion of upgrade issues that you may encounter for upgrades from MySQL 5.4 to MySQL 5.5, see Section 2.13.1.2, “Upgrading from MySQL 5.4 to 5.5”.

D.1.1. Changes in MySQL 5.5.7 (Not yet released)

For this release, the server requires that a new grant table, proxy_priv, be present in the mysql database. If you are upgrading from a previous MySQL release rather than performing a new installation, the server will exit during startup after finding that this table is missing. To create the table, start the server with the --skip-grant-tables option to cause it to skip the normal grant table checks, then run mysql_upgrade. For example:

shell> mysqld --skip-grant-tables &
shell> mysql_upgrade

Then stop the server and restart it normally.

You can specify other options on the mysqld command line if necessary. Alternatively, if your installation is configured so that the server normally reads options from an option file, use the --defaults-file option to specify the file (enter each command on a single line):

shell> mysqld --defaults-file=/usr/local/mysql/etc/my.cnf
         --skip-grant-tables &
shell> mysql_upgrade

With the --skip-grant-tables option, the server does no password or privilege checking, so any client can connect and effectively have all privilges. For additional security, use the --skip-networking option as well to prevent remote clients from connecting.

Functionality added or changed:

  • The unused and undocumented thread_pool_size system variable was removed. (Bug#57338)

  • A new status variable, Handler_read_last, displays the number of requests to read the last key in an index. With ORDER BY, the server will issue a first-key request followed by several next-key requests, whereas with With ORDER BY DESC, the server will issue a last-key request followed by several previous-key requests. (Bug#52312)

Bugs fixed:

  • Performance: InnoDB Storage Engine: The master InnoDB background thread could sometimes cause transient performance drops due to excessive flushing of modified pages. (Bug#56933)

  • Security Fix: The server crashed for assignment of values of types other than Geometry to items of type GeometryCollection (MultiPoint, MultiCurve, MultiSurface). Now the server checks the field type and fails with bad geometry value if it detects incorrect parameters. (Bug#55531)

  • Security Fix: EXPLAIN EXTENDED caused a server crash with some prepared statements. (Bug#54494)

  • Security Fix: In prepared-statement mode, EXPLAIN for a SELECT from a derived table caused a server crash. (Bug#54488)

  • Security Fix: The PolyFromWKB() function could crash the server when improper WKB data was passed to the function. (Bug#51875, CVE-2010-3840)

  • Incompatible Change: Replication: The behavior of INSERT DELAYED statements when using statement-based replication has changed as follows:

    Previously, when using binlog_format=STATEMENT, a warning was issued in the client when executing INSERT DELAYED; now, no warning is issued in such cases.

    Previously, when using binlog_format=STATEMENT, INSERT DELAYED was logged as INSERT DELAYED; now, it is logged as an INSERT, without the DELAYED option.

    However, when binlog_format=STATEMENT, INSERT DELAYED continues to be executed as INSERT (without the DELAYED option). The behavior of INSERT DELAYED remains unchanged when using binlog_format=ROW: INSERT DELAYED generates no warnings, is executed as INSERT DELAYED, and is logged using the row-based format.

    This change also affects binlog_format=MIXED, because INSERT DELAYED is no longer considered unsafe. Now, when the logging format is MIXED, no switch to row-based logging occurs. This means that the statement is logged as a simple INSERT (that is, without the DELAYED option), using the statement-based logging format. (Bug#54579)

  • Incompatible Change: Previously, if you flushed the logs using FLUSH LOGS or mysqladmin flush-logs and mysqld was writing the error log to a file (for example, if it was started with the --log-error option), it renamed the current log file with the suffix -old, then created a new empty log file. This had the problem that a second log-flushing operation thus caused the original error log file to be lost unless you saved it under a different name. For example, you could use the following commands to save the file:

    shell> mysqladmin flush-logs
    shell> mv host_name.err-old backup-directory
    

    To avoid the preceding file-loss problem, renaming no longer occurs. The server merely closes and reopens the log file. To rename the file, you can do so manually before flushing. Then flushing the logs reopens a new file with the original file name. For example, you can rename the file and create a new one using the following commands:

    shell> mv host_name.err host_name.err-old
    shell> mysqladmin flush-logs
    shell> mv host_name.err-old backup-directory
    

    (Bug#29751)

  • InnoDB Storage Engine: Replication: If the master had innodb_file_per_table=OFF, innodb_file_format=Antelope (and innodb_strict_mode=OFF), or both, certain CREATE TABLE options, such as KEY_BLOCK_SIZE, were ignored. This could allow master to avoid raising ER_TOO_BIG_ROWSIZE errors.

    However, the ignored CREATE TABLE options were still written into the binary log, so that, if the slave had innodb_file_per_table=ON and innodb_file_format=Barracuda, it could encounter an ER_TOO_BIG_ROWSIZE error while executing the record from the log, causing the slave SQL thread to abort and replication to fail.

    In the case where the master was running MySQL 5.1 and the slave was MySQL 5.5 (or later), the failure occurred when both master and slave were running with default values for innodb_file_per_table and innodb_file_format. This could cause problems during upgrades.

    To address this issue, the default values for innodb_file_per_table and innodb_file_format are reverted to the MySQL 5.1 default values—that is, OFF and Antelope, respectively. (Bug#56318)

  • InnoDB Storage Engine: The server could crash with a high volume of concurrent LOCK TABLE and UNLOCK TABLES statements. (Bug#57345)

  • InnoDB Storage Engine: InnoDB incorrectly reported an error when a cascading foreign key constraint deleted more than 250 rows. (Bug#57255)

  • InnoDB Storage Engine: The output from the SHOW ENGINE INNODB STATUS command can now be up to 1 MB. Formerly, it was truncated at 64 KB. Monitoring applications that parse can check if output exceeds this new, larger limit by testing the Innodb_truncated_status_writes status variable. (Bug#56922)

  • InnoDB Storage Engine: A SELECT ... FOR UPDATE statement affecting a range of rows in an InnoDB table could cause a crash in the debug version of the server. (Bug#56716)

  • InnoDB Storage Engine: Improved the performance of UPDATE operations on InnoDB tables, when only non-indexed columns are changed. (Bug#56340)

  • InnoDB Storage Engine: When MySQL was restarted after a crash with the option innodb_force_recovery=6, certain queries against InnoDB tables could fail, depending on WHERE or ORDER BY clauses.

    Usually in such a disaster recovery situation, you dump the entire table using a query without these clauses. During advanced troubleshooting, you might use queries with these clauses to diagnose the position of the corrupted data, or to recover data following the corrupted part. (Bug#55832)

  • InnoDB Storage Engine: The CHECK TABLE command could cause a time-consuming verification of the InnoDB adaptive hash index memory structure. Now this extra checking is only performed in binaries built for debugging. (Bug#55716)

  • InnoDB Storage Engine: A heavy workload with a large number of threads could cause a crash in the debug version of the server. (Bug#55699)

  • InnoDB Storage Engine: The server could crash on shutdown, if started with --innodb-use-system-malloc=0. (Bug#55627)

  • InnoDB Storage Engine: If the server crashed during a RENAME TABLE operation on an InnoDB table, subsequent crash recovery could fail. This problem could also affect an ALTER TABLE statement that caused a rename operation internally. (Bug#55027)

  • InnoDB Storage Engine: Setting the PACK_KEYS=0 table option for an InnoDB table prevented new indexes from being added to the table. (Bug#54606)

  • InnoDB Storage Engine: Changed the locking mechanism for the InnoDB data dictionary during ROLLBACK operations, to improve concurrency for REPLACE statements. (Bug#54538)

  • InnoDB Storage Engine: With multiple buffer pools enabled, InnoDB could flush more data from the buffer pool than necessary, causing extra I/O overhead. (Bug#54346)

  • InnoDB Storage Engine: InnoDB transactions could be incorrectly committed during recovery, rather than rolled back, if the server crashed and was restarted after performing ALTER TABLE...ADD PRIMARY KEY on an InnoDB table, or some other operation that involves copying the entire table. (Bug#53756)

  • InnoDB Storage Engine: InnoDB startup messages now include the start and end times for buffer pool initialization, and the total buffer pool size. (Bug#48026)

  • Partitioning: Multi-table UPDATE statements involving a partitioned MyISAM table could cause this table to become corrupted. Not all tables affected by the UPDATE needed to be partitioned for this issue to be observed. (Bug#55458)

  • Partitioning: EXPLAIN PARTITIONS returned bad estimates for range queries on partitioned MyISAM tables. In addition, values in the rows column of EXPLAIN PARTITIONS output did not take partition pruning into account. (Bug#53806, Bug#46754)

  • Replication: SET PASSWORD caused row-based replication to fail between a MySQL 5.1 master and a MySQL 5.5 slave.

    This fix makes it possible to replicate SET PASSWORD correctly, using row-based replication between a master running MySQL 5.1.53 or a later MySQL 5.1 release to a slave running MySQL 5.5.7 or a later MySQL 5.5 release. (Bug#57098)

    See also Bug#55452, Bug#57357.

  • Replication: Backticks used to enclose idenitfiers for savepoints were not preserved in the binary log, which could lead to replication failure when the identifier, stripped of backticks, could be misinterpreted, causing a syntax or other error.

    This could cause problems with MySQL application programs making use of generated savepoint IDs. If, for instance, java.sql.Connection.setSavepoint() is called without any parameters, Connector/J automatically generates a savepoint identifier consisting of a string of hexadecimal digits 0-F encased in backtick (`) characters. If such an ID took the form `NeN` (where N represents a string of the decimal digits 0-9, and e is a literal uppercase or lowercase “E” character). Removing the backticks when writing the identifier into the binary log left behind a substring which the slave MySQL server tried to interpret as a floating point number, rather than as an identifier. The resulting syntax error caused loss of replication. (Bug#55961)

    See also Bug#55962.

  • Replication: When a slave tried to execute a transaction larger than the slave's value for max_binlog_cache_size, it crashed. This was caused by an assertion that the server should roll back only the statement but not the entire transaction when the error ER_TRANS_CACHE_FULL occurred. However, the slave SQL thread always rolled back the entire transaction whenever any error occurred, regardless of the type of error. (Bug#55375)

  • Replication: The error message for ER_SLAVE_HEARTBEAT_VALUE_OUT_OF_RANGE was hard coded in English in sql_yacc.yy, so that it could not be translated in errmsg.txt for other languages.

    Additionally, this same error message was used for three separate error conditions:

    1. When the heartbeat period exceeded the value of slave_net_timeout.

    2. When the heartbeat period was nonnegative but shorter than 1 millisecond.

    3. When the value for the heartbeat period was either negative or greater than the maximum allowed.

    These issues have been addressed as follows:

    • By using three distinct error messages for each of the conditions listed previously.

    • By moving the sources for these error messages into the errmsg-utf8.txt file to facilitate translations into languages other than English.

    (Bug#54144)

  • A buffer overrun could occur when formatting DBL_MAX numbers. (Bug#57209)

  • The server could crash inside memcpy() when reading certain Performance Schema tables. (Bug#56761)

  • Memory leaks detected by Valgrind were corrected. (Bug#56709)

  • It was possible to compile mysqld with Performance Schema support but with a dummy atomic-operations implementation, which caused a server crash. This problem does not affect binary distributions. It is helpful as a safety measure for users who build MySQL from source. (Bug#56521)

  • The server crashed if a table maintenance statement such as ANALYZE TABLE or REPAIR TABLE was executed on a MERGE table and opening and locking a child table failed. For example, this could happen if a child table did not exist or if a lock timeout happened while waiting for a conflicting metadata lock to disappear.

    As a consequence of this bug fix, it is now possible to use CHECK TABLE for log tables without producing an error. (Bug#56422, Bug#56494)

  • Deadlock could occur for heavily concurrent workloads consisting of a mix of DML, DDL, and FLUSH TABLES statements affecting the same set of tables. (Bug#56405)

  • The server could crash during shutdown due to a race condition relating to Performance Schema cleanup. (Bug#56324)

  • ALTER TABLE on a MERGE table could result in deadlock with other connections. (Bug#56292, Bug#57002)

  • The tcmalloc library was missing from binary MySQL packages for Linux. (Bug#56267)

  • An INSERT DELAYED statement for a MERGE table could cause deadlock if it occurred as part of a transaction or under LOCK TABLES, and there was a concurrent DDL or LOCK TABLES ... WRITE statement that tried to lock one of its underlying tables. (Bug#56251)

  • In debug builds, the server raised an assertion for DROP DATABASE in installations that had an outdated or corrupted mysql.proc table. For example, this affected mysql_upgrade when run as part of a MySQL 5.1 to 5.5 upgrade. (Bug#56137)

  • A negative TIME argument to MIN() or MAX() could raise an assertion. (Bug#56120)

  • The ordering for supplementary characters with the utf8mb4_bin, utf16_bin, and utf32_bin collations was incorrect. (Bug#55980)

  • Short (single-letter) command-line options did not work. (Bug#55873)

  • If a query specified a DATE or DATETIME value in a format different from 'YYYY-MM-DD HH:MM:SS', a greater-than-or-equal (>=) condition matched only greater-than values in an indexed TIMESTAMP column. (Bug#55779)

  • If a view was named as the destination table for CREATE TABLE ... SELECT, the server produced a warning whether or not IF NOT EXISTS was used. Now it produces a warning only when IF NOT EXISTS is used, and an error otherwise. (Bug#55777)

  • After the fix for Bug#39653, the shortest available secondary index was used for full table scans. The primary clustered key was used only if no secondary index could be used. However, when the chosen secondary index includes all columns of the table being scanned, it is better to use the primary index because the amount of data to scan is the same but the primary index is clustered. This is now taken into account. (Bug#55656)

  • For Performance Schema, the default number of rwlock classes was increased to 30, and the default number of rwlock and mutex instances was increased to 1 million. These changes were made to account for the volume of data instrumented when the InnoDB storage engine is used (because of the InnoDB buffer pool). (Bug#55576)

  • If there was an active SELECT statement, an error arising during trigger execution could cause a server crash. (Bug#55421)

  • Assignment of InnoDB scalar subquery results to a variable resulted in unexpected S locks in READ COMMITTED transation isolation level. (Bug#55382)

  • Queries involving predicates of the form const NOT BETWEEN not_indexed_column AND indexed_column could return incorrect data due to incorrect handling by the range optimizer. (Bug#54802)

  • With an UPDATE IGNORE statement including a subquery that was evaluated using a temporary table, an error transferring the data from the temporary was ignored, causing an assertion to be raised. (Bug#54543)

  • MIN() or MAX() with a subquery argument could raise a debug assertion for debug builds or return incorrect data for nondebug builds. (Bug#54465)

  • If one session attempted to drop a database containing a table which another session had opened with HANDLER, any instance of ALTER DATABASE, CREATE DATABASE, or DROP DATABASE issued by the latter session produced a deadlock. (Bug#54360)

  • INFORMATION_SCHEMA plugins with no deinit() method resulted in a memory leak. (Bug#54253)

  • Row subqueries producing no rows were not handled as UNKNOWN values in row comparison expressions. (Bug#54190)

  • Setting SETUP_INSTRUMENTS.TIMER = 'NO' caused TIMER_WAIT values for aggregations to be NULL rather than 0. (Bug#53874)

  • The max_length metadata value of MEDIUMBLOB types was reported as 1 byte greater than the correct value. (Bug#53296)

  • If an application using the embedded server called mysql_library_init() a second time after calling mysql_library_init() and mysql_library_end() to start and stop the server, the application crashed when reading option files. (Bug#53251)

  • The fix for Bug#30234 caused the server to reject the DELETE tbl_name.* ... Access compatibility syntax for multiple-table DELETE statements. (Bug#53034)

  • The plugin_ftparser.h and plugin_audit.h include files are part of the public API/ABI, but were not tested by the ABI check. (Bug#52821)

  • An atomic “compare and swap” operation using x86 assembly code (32 bit) could access incorrect data, which would make it work incorrectly and lose the intended atomicity. This would in turn cause the MySQL server to work on inconsistent data structures and return incorrect data. That code part affected only 32-bit builds; the effect has been observed when icc was used to build binaries. With gcc, no incorrect results have been observed during tests, so this fix is a proactive one. Other compilers do not use this assembly code. (Bug#52419)

  • In LOAD DATA INFILE, using a SET clause to set a column equal to itself caused a server crash. (Bug#51850)

  • In some cases, when the left part of a NOT IN subquery predicate was a row and contained NULL values, the query result was incorrect. (Bug#51070)

  • CHECKSUM TABLE for Performance Schema tables could cause a server crash due to uninitialized memory reads. (Bug#50557)

  • For some queries, the optimizer produced incorrect results using the Index Merge access method with InnoDB tables. (Bug#50402)

  • EXPLAIN produced an incorrect rows value for queries evaluated using an index scan and that included LIMIT, GROUP BY, and ORDER BY on a computed column. (Bug#50394)

  • mysql_store_result() and mysql_use_result() are not for use with prepared statements and are not intended to be called following mysql_stmt_execute(), but failed to return an error when invoked that way. (Bug#47485)

  • Using REPAIR TABLE table USE_FRM on a MERGE table caused the server to crash. (Bug#46339)

  • If the global and session debug system variables had the same value, the debug trace file could be closed twice, leading to freeing already freed memory and a server crash. (Bug#46165)

  • Trailing space removal for utf32 strings was done with non-multibyte-safe code, leading to incorrect result length and assertion failure. (Bug#42511)

  • A malformed packet sent by the server when the query cache was in use resulted in lost-connection errors. (Bug#42503)

  • Multiple-statement execution could fail. (Bug#40877)

  • CREATE TABLE failed if a column referred to in an index definition and foreign key definition was in different lettercases in the two definitions. (Bug#39932)

D.1.2. Changes in MySQL 5.5.6 (13 September 2010 Release Candidate)

Functionality added or changed:

  • Incompatible Change: The SHA2() function now returns a character string with the connection character set and collation. Previously, it returned a binary string. This is the same change made for several other encryption functions in MySQL 5.5.3. (Bug#54661)

  • Previously, MySQL-shared-compat RPMs for Linux contained both the current and previous client library versions for the target platform. Thus, the package contents overlapped with MySQL-shared RPMs, which contain only the current client library version. This can result in problems in two cases:

    • When the MySQL-shared RPM is installed but later it is determined that the MySQL-shared-compat RPM is needed (an application is installed that was linked against an older client library). Installing the MySQL-shared-compat RPM results in a conflict because both include the current library version. This can be overcome by using the --force option to RPM, or by first uninstalling the MySQL-shared RPM (which breaks dependencies).

    • When the MySQL-shared-compat RPM is installed, but old applications that require it are removed or upgraded to the current library version. In this case, MySQL-shared-compat cannot be replaced with MySQL-shared as long as current applications are installed. This can be overcome by using the --force option to RPM, which incurs the risk of breaking dependencies.

    Now the MySQL-shared-compat RPMs include only older client library versions and no longer include the current version, so that the MySQL-shared and MySQL-shared-compat RPM contents no longer overlap. The MySQL-shared-compat RPM can be installed even if the MySQL-shared RPM is installed, without producing conflicts related to the current library version. The MySQL-shared-compat RPM can be uninstalled when old applications are removed or upgraded to the current library version, without breaking applications that already use the current library version.

    If you previously installed the MySQL-shared-compat RPM because you needed both the current and previous libraries, you should install both the MySQL-shared and MySQL-shared-compat RPMs now. (Bug#56150)

  • Overhead for the Performance Schema interface was reduced. (Bug#55087)

  • Within stored programs, LIMIT clauses now accept integer-valued routine parameters or local variables as parameters. (Bug#11918)

Bugs fixed:

  • Performance: InnoDB Storage Engine: The setting innodb_change_buffering=all could produce slower performance for some operations than the previous default, innodb_change_buffering=inserts. (Bug#54914)

  • Performance: InnoDB Storage Engine: An EXPLAIN plan for an InnoDB table could vary greatly in the estimated cost for a BETWEEN clause. (Bug#53761)

  • InnoDB Storage Engine: Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039, CVE-2010-3676)

  • Security Fix: Replication: It was possible when using statement-based replication to subvert the MySQL privilege system on a slave with a higher server release version number than that of the master by using version-specific comments in statements run on the master.

    A more detailed explanation follows:

    In MySQL, a version-specific comment is an SQL comment of the form /*!nnnnn sql */ where nnnnn represents a MySQL release version number and sql represents a string of SQL, or a portion of a string of SQL, that should be executed by the MySQL Server only if the server version is at least version n.nn. (For additional information and an example, see Section 8.6, “Comment Syntax”.)

    In MySQL replication, the slave SQL thread executes with the SUPER privilege, regardless of the privileges with which statements are originally executed on the master. Specific to this issue, when using statement-based replication it was possible, when the slave was of a higher MySQL version than the master, to run statements that would have failed on the master due to insufficient privileges, except that these statements were wrapped in version-specific comments where the encoded version was greater than the MySQL server version of the master. However, if the MySQL release version of the slave was equal to or greater than the version encoded in the comment, the same statements could execute on this slave whose MySQL release version was less than the version number used in the comment.

    Suppose that a master running MySQL 5.1.48 replicated to a slave running MySQL 4.1.49, and that a user user1 had privileges to run UPDATE statements on database db1 but no privileges at all on the mysql system database, so that the first of the following two statements succeeded, but the second statement failed, and thus the first statement was written to the binary log, but the second statement was not:

          
    UPDATE db1.tb1 SET db1.tbl1.col1=2;
     
    UPDATE mysql.user SET mysql.user.Super_priv='Y' 
        WHERE mysql.user.User='user1';
    

    However, the text of the second statement could be wrapped in version-specific comments and thus “hidden” within the text of the first statement so that this new version of the first statement succeeded, and was written in its entireity to the binary log. The new statement containing the necessary portions of the statement affecting the “mysql.user” table wrapped within version-specific comments is shown here:

    UPDATE db1.tbl1 /*!514900 ,mysql.user */ 
        SET db1.tbl1.col1=2 /*!514900 ,mysql.user.Super_priv='Y'
        WHERE mysql.user.User='user1'*/;
    

    Thus, a 5.1.48 master would see this statement as identical to the first of the original two statements shown previously (UPDATE db1.tb1 SET db1.tbl1.col1=2). However, the version-specific comments within the statement just shown, when run on the MySQL 5.1.49 slave, were ignored; thus the slave SQL thread would execute the statement, as shown here, with the SUPER privilege, on the slave:

          
    UPDATE db1.tbl1,mysql.user 
        SET db1.tbl1.col1=2,mysql.user.Super_priv='Y'
        WHERE mysql.user.User='user1';
    

    To fix this issue, the ! (exclamation) character is now stripped from comments prior to statements containing them being applied on replication slaves; thus, version-specific comments that are not applied on the master are treated as normal comments on the slave and also not applied there. (Bug#49124)

  • Security Fix: During evaluation of arguments to extreme-value functions (such as LEAST() and GREATEST()), type errors did not propagate properly, causing the server to crash. (Bug#55826, CVE-2010-3833)

  • Security Fix: The server could crash after materializing a derived table that required a temporary table for grouping. (Bug#55568, CVE-2010-3834)

  • Security Fix: A user-variable assignment expression that is evaluated in a logical expression context can be precalculated in a temporary table for GROUP BY. However, when the expression value is used after creation of the temporary table, it was re-evaluated, not read from the table and a server crash resulted. (Bug#55564, CVE-2010-3835)

  • Security Fix: Joins involving a table with a unique SET column could cause a server crash. (Bug#54575, CVE-2010-3677)

  • Security Fix: Pre-evaluation of LIKE predicates during view preparation could cause a server crash. (Bug#54568, CVE-2010-3836)

  • Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477, CVE-2010-3678)

  • Security Fix: GROUP_CONCAT() and WITH ROLLUP together could cause a server crash. (Bug#54476, CVE-2010-3837)

  • Security Fix: Queries could cause a server crash if the GREATEST() or LEAST() function had a mixed list of numeric and LONGBLOB arguments, and the result of such a function was processed using an intermediate temporary table. (Bug#54461, CVE-2010-3838)

  • Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393, CVE-2010-3679)

  • Security Fix: After ALTER TABLE was used on a temporary transactional table locked by LOCK TABLES, any later attempts to execute LOCK TABLES or UNLOCK TABLES caused a server crash. (Bug#54117)

  • Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044, CVE-2010-3680)

  • Security Fix: Queries with nested joins could cause an infinite loop in the server when used from stored procedures and prepared statements. (Bug#53544, CVE-2010-3839)

  • Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711, CVE-2010-3682)

  • Incompatible Change: Replication: As of MySQL 5.5.6, handling of CREATE TABLE IF NOT EXISTS ... SELECT statements has been changed for the case that the destination table already exists:

    • Previously, for CREATE TABLE IF NOT EXISTS ... SELECT, MySQL produced a warning that the table exists, but inserted the rows and wrote the statement to the binary log anyway. By contrast, CREATE TABLE ... SELECT (without IF NOT EXISTS) failed with an error, but MySQL inserted no rows and did not write the statement to the binary log.

    • MySQL now handles both statements the same way when the destination table exists, in that neither statement inserts rows or is written to the binary log. The difference between them is that MySQL produces a warning when IF NOT EXISTS is present and an error when it is not.

    This change in handling of IF NOT EXISTS results in an incompatibility for statement-based replication from a MySQL 5.1 master with the original behavior and a MySQL 5.5 slave with the new behavior. Suppose that CREATE TABLE IF NOT EXISTS ... SELECT is executed on the master and the destination table exists. The result is that rows are inserted on the master but not on the slave. (Row-based replication does not have this problem.)

    To address this issue, statement-based binary logging for CREATE TABLE IF NOT EXISTS ... SELECT is changed in MySQL 5.1 as of 5.1.51:

    This change provides forward compatibility for statement-based replication from MySQL 5.1 to 5.5 because when the destination table exists, the rows will be inserted on both the master and slave. To take advantage of this compatibility measure, the 5.1 server must be at least 5.1.51 and the 5.5 server must be at least 5.5.6.

    To upgrade an existing 5.1-to-5.5 replication scenario, upgrade the master first to 5.1.51 or higher. Note that this differs from the usual replication upgrade advice of upgrading the slave first.

    A workaround for applications that wish to achieve the original effect (rows inserted regardless of whether the destination table exists) is to use CREATE TABLE IF NOT EXISTS and INSERT ... SELECT statements rather than CREATE TABLE IF NOT EXISTS ... SELECT statements.

    Along with the change just described, the following related change was made: Previously, if an existing view was named as the destination table for CREATE TABLE IF NOT EXISTS ... SELECT, rows were inserted into the underlying base table and the statement was written to the binary log. As of MySQL 5.1.51 and 5.5.6, nothing is inserted or logged. (Bug#47442, Bug#47132, Bug#48814, Bug#49494)

  • Incompatible Change: Several changes were made to Performance Schema tables:

    • The SETUP_OBJECTS table was removed.

    • The PROCESSLIST table was renamed to THREADS.

    • The EVENTS_WAITS_SUMMARY_BY_EVENT_NAME table was renamed to EVENTS_WAITS_SUMMARY_GLOBAL_BY_EVENT_NAME.

    (Bug#55416)

  • Incompatible Change: Handling of warnings and errors during stored program execution was problematic:

    • If one statement generated several warnings or errors, only the handler for the first was activated, even if another might be more appropriate.

    • Warning or error information could be lost.

    (Bug#36185, Bug#5889, Bug#9857, Bug#23032)

  • Incompatible Change: If the server was started with character_set_server set to utf16, it crashed during full-text stopword initialization. Now the stopword file is loaded and searched using latin1 if character_set_server is ucs2, utf16, or utf32. If any table was created with FULLTEXT indexes while the server character set was ucs2, utf16, or utf32, it should be repaired using this statement:

    REPAIR TABLE tbl_name QUICK;
    

    (Bug#32391)

  • Important Change: Replication: The LOAD DATA INFILE statement is now considered unsafe for statement-based replication. When using statement-based logging mode, the statement now produces a warning; when using mixed-format logging, the statement is made using the row-based format. (Bug#34283)

  • InnoDB Storage Engine: An assertion was raised if (1) an InnoDB table was created using CREATE TABLE ... SELECT where the query used an INFORMATION_SCHEMA table and a view existed in the database; or (2) any statement that modified an InnoDB table had a subquery referencing an INFORMATION_SCHEMA table. (Bug#55973)

  • InnoDB Storage Engine: The InnoDB storage engine was not included in the default installation when using the configure script. (Bug#55547)

  • InnoDB Storage Engine: For an InnoDB table with an auto-increment column, the server could crash if the first statement that references the table after a server restart is a SHOW CREATE TABLE statement. (Bug#55277)

  • InnoDB Storage Engine: The mysql_config tool would not output the requirement for the aio library for mysqld-libs. (Bug#55215)

  • InnoDB Storage Engine: Some memory used for InnoDB asynchronous I/O was not freed at shutdown. (Bug#54764)

  • InnoDB Storage Engine: Implementation of the 64-bit dulint structure in InnoDB was not optimized for 64-bit processors, resulting in excessive storage and reduced performance. (Bug#54728)

  • InnoDB Storage Engine: The output from the SHOW ENGINE INNODB STATUS command now includes information about “spin rounds” for RW-locks (both shared and exclusive locks). (Bug#54726)

  • InnoDB Storage Engine: An ALTER TABLE statement could convert an InnoDB compressed table (with row_format=compressed) back to an uncompressed table (with row_format=compact). (Bug#54679)

  • InnoDB Storage Engine: InnoDB could issue an incorrect message on startup, if tables were created under the setting innodb_file_per_table=ON. The message was of the form InnoDB: Warning: allocated tablespace n, old maximum was 0 and is no longer displayed during restarts after you have upgraded the MySQL server and created at least one InnoDB table with innodb_file_per_table=ON. If you continue to encounter this message, you might have corruption in your shared tablespace; if so, back up and reload your data. (Bug#54658)

  • InnoDB Storage Engine: The database server could crash when renaming a table that had active transactions. (This issue only affected the database server when built for debugging.) (Bug#54453)

  • InnoDB Storage Engine: The server could crash during the recovery phase of startup, if it previously crashed while inserting BLOB or other large columns that use off-page storage into an InnoDB table created with ROW_FORMAT=REDUNDANT or ROW_FORMAT=COMPACT. (Bug#54408)

  • InnoDB Storage Engine: For an InnoDB table created with ROW_FORMAT=COMPRESSED or ROW_FORMAT=DYNAMIC, a query using the READ UNCOMMITTED isolation level could cause the server to stop with an assertion error, if BLOB or other large columns that use off-page storage were being inserted at the same time. (Bug#54358)

  • InnoDB Storage Engine: Fast index creation in the InnoDB Plugin could fail, leaving the new secondary index corrupted. (Bug#54330)

  • InnoDB Storage Engine: If a session executing TRUNCATE TABLE on an InnoDB table was killed during open_tables(), an assertion could be raised. (Bug#53757)

  • InnoDB Storage Engine: Misimplementation of the os_fast_mutex_trylock() function in InnoDB resulted in unnecessary blocking and reduced performance. (Bug#53204)

  • InnoDB Storage Engine: InnoDB could not create tables that used the utf32 character set. (Bug#52199)

  • InnoDB Storage Engine: Performing large numbers of RENAME TABLE statements caused excessive memory use. (Bug#47991)

  • InnoDB Storage Engine: The mechanism that checks if there is enough space for redo logs was improved, reducing the chance of encountering this message: ERROR: the age of the last checkpoint is x, which exceeds the log group capacity y. (Bug#39168)

  • InnoDB Storage Engine: Improved performance and scalability on Windows systems, especially for Windows Vista and higher. Re-enabled the use of atomic instructions on Windows systems. For Windows Vista and higher, reduced the number of event handles used. To compile on Windows systems now requires Windows SDK v6.0 or later; either upgrade to Visual Studio 2008 or 2010, or for Visual Studio 2005, install Windows SDK Update for Windows Vista. (Bug#22268)

  • Partitioning: With innodb_thread_concurrency = 1, ALTER TABLE ... REORGANIZE PARTITION and SELECT could deadlock. There were unreleased latches in the ALTER TABLE ... REORGANIZE PARTITION thread which were needed by the SELECT thread to be able to continue. (Bug#54747)

  • Partitioning: An ALTER TABLE ... ADD PARTITION statement run concurrently with a read lock caused spurious ER_TABLE_EXISTS and ER_NO_SUCH_TABLE errors on subsequent attempts. (Bug#53676)

    See also Bug#53770.

  • Partitioning: UPDATE and INSERT statements affecting partitioned tables performed poorly when using row-based replication. (Bug#52517)

  • Partitioning: INSERT ON DUPLICATE KEY UPDATE statements performed poorly on tables having many partitions. This was because the handler function for reading a row from a specific index was not optimized in the partitioning handler. (Bug#52455)

  • Partitioning: ALTER TABLE ... TRUNCATE PARTITION, when called concurrently with transactional DML on the table, was executed immediately and did not wait for the concurrent transaction to release locks. As a result, the ALTER TABLE statement was written into the binary log before the DML statement, which led to replication failures when using row-based logging. (Bug#49907)

    See also Bug#42643.

  • Partitioning: When the storage engine used to create a partitioned table was disabled, attempting to drop the table caused the server to crash. (Bug#46086)

  • Replication: When using the row-based logging format, a failed CREATE TABLE ... SELECT statement was written to the binary log, causing replication to break if the failed statement was later re-run on the master. In such cases, a DROP TABLE ... IF EXIST statement is now logged in the event that a CREATE TABLE ... SELECT fails. (Bug#55625)

  • Replication: When using the row-based logging format, a SET PASSWORD statement was written to the binary log twice. (Bug#55452)

  • Replication: When closing temporary tables, after the session connection was already closed, if the writing of the implicit DROP TABLE statement into the binary log failed, it was possible for the resulting error to be mishandled, triggering an assertion. (Bug#55387)

  • Replication: Executing SHOW BINLOG EVENTS increased the value of max_allowed_packet applying to the session that executed the statement. (Bug#55322)

  • Replication: Setting binlog_format = ROW then creating and then dropping a temporary table led an assertion. (Bug#54925)

  • Replication: When using mixed-format replication, changes made to a non-transactional temporary table within a transaction were not written into the binary log when the transaction was rolled back. This could lead to a failure in replication if the temporary table was used again afterwards. (Bug#54872)

    See also Bug#53259.

  • Replication: If binlog_format was explicitly switched from STATEMENT to ROW following the creation of a temporary table, then on disconnection the master failed to write the expected DROP TEMPORARY TABLE statement into the binary log. As a consequence, temporary tables (and their corresponding files) accumulated as this scenario was repeated. (Bug#54842)

    See also Bug#52616.

  • Replication: If the SQL thread was started while the I/O thread was performing rotation of the relay log, the 2 threads could begin to race for the same I/O cache, leading to a crash of the server. (Bug#54509)

    See also Bug#50364.

  • Replication: Two related issues involving temporary tables and transactions were introduced by a fix made in MySQL 5.1.37:

    1. When a temporary table was created or dropped within a transaction, any failed statement that following the CREATE TEMPORARY TABLE or DROP TEMPORARY TABLE statement triggered a rollback, which caused the slave diverge from the master.

    2. When a CREATE TEMPORARY TABLE ... SELECT * FROM ... statement was executed within a transaction in which only tables using transactional storage engines were used and the transaction was rolled back at the end, the changes—including the creation of the temporary table—were not written to the binary log.

    The current fix restores the correct behavior in both of these cases. (Bug#53560)

    This regression was introduced by Bug#43929.

  • Replication: The value of binlog_direct_non_transactional_updates had no effect on statements mixing transactional tables and nontransactional tables, or mixing temporary tables and nontransactional tables.

    As part of the fix for this issue, updates to temporary tables are now handled as transactional or nontransactional according to their storage engine types. (In effect, the current fix reverts a change made previously as part of the fix for Bug#53259.)

    In addition, unsafe mixed statements (that is, statements which access transactional table as well nontransactional or temporary tables, and write to any of them) are now handled as transactional when the statement-based logging format is in use. (Bug#53452)

    See also Bug#51894.

  • Replication: When binlog_format=STATEMENT, any statement that is flagged as being unsafe, possibly causing the slave to go out of sync, generates a warning. This warning is written to the server log, the warning count is returned to the client in the server's response, and the warnings are accessible through SHOW WARNINGS.

    The current bug affects only the counts for warnings to the client and that are visible through SHOW WARNINGS; it does not affect which warnings are written to the log. The current issue came about because the fix for an earlier issue caused warnings for substatements to be cleared whenever a new substatement was started. However, this suppressed warnings for unsafe statements in some cases. Now, such warnings are no longer cleared. (Bug#50312)

    This regression was introduced by Bug#36649.

  • Replication: Replication could break if a transaction involving both transactional and nontransactional tables was rolled back to a savepoint. It broke if a concurrent connection tried to drop a transactional table which was locked after the savepoint was set. This DROP TABLE completed when ROLLBACK TO SAVEPOINT was executed because the lock on the table was dropped by the transaction. When the slave later tried to apply the binary log events, it would fail because the table had already been dropped. (Bug#50124)

  • Replication: When CURRENT_USER() or CURRENT_USER was used to supply the name and host of the affected user or of the definer in any of the statements DROP USER, RENAME USER, GRANT, REVOKE, and ALTER EVENT, the reference to CURRENT_USER() or CURRENT_USER was not expanded when written to the binary log. This resulted in CURRENT_USER() or CURRENT_USER being expanded to the user and host of the slave SQL thread on the slave, thus breaking replication. Now CURRENT_USER() and CURRENT_USER are expanded prior to being written to the binary log in such cases, so that the correct user and host are referenced on both the master and the slave. (Bug#48321)

  • After an RPM installation mysqld would be started with the root, rather than the mysql user. (Bug#56574)

  • The embedded server raised an assertion when it attempted to load plugins. (Bug#56085)

  • FORMAT() did not respect the decimal point character if the locale was changed and always returned an ASCII value. (Bug#55912)

  • CMake would produce bad dependencies for the sql/lex_hash.h file during configuration. (Bug#55842)

  • mysql_upgrade did not handle the --ssl option properly. (Bug#55672)

  • Using MIN() or MAX() on a column containing the maximum TIME value caused a server crash. (Bug#55648)

  • Incorrect handling of user variable assignments as subexpressions could lead to incorrect results or server crashes. (Bug#55615)

  • The default compiler options used for Mac OS X 10.5 would be set incorrectly. (Bug#55601)

  • The server was not checking for errors generated during the execution of Item::val_xxx() methods when copying data to a group, order, or distinct temp table's row. (Bug#55580)

  • ORDER BY clauses that included user variable expressions could cause a debug assertion to be raised. (Bug#55565)

  • SHOW CREATE TRIGGER took a stronger metadata lock than required. This caused the statement to be blocked unnecessarily. For example, LOCK TABLES ... WRITE in one session blocked SHOW CREATE TRIGGER in another session.

    Also, a SHOW CREATE TRIGGER statement issued inside a transaction did not release its metadata locks at the end of statement execution. Consequently, SHOW CREATE TRIGGER was able to block other sessions from accessing the table (for example, using ALTER TABLE). (Bug#55498)

  • A single-table DELETE ordered by a column that had a hash-type index could raise an assertion or cause a server crash. (Bug#55472)

  • A call to mysql_library_init() following a call to mysql_library_end() caused a client crash. (Bug#55345)

  • A statement that was aborted by KILL QUERY while it waited on a metadata lock could raise an assertion in debug builds, or send OK to the client instead of ER_QUERY_INTERRUPTED in regular builds. (Bug#55223)

  • GROUP BY operations used max_sort_length inconsistently. (Bug#55188)

  • The Windows MSI installer would fail to preserve custom settings, such as the configured data directory, during installation. (Bug#55169)

  • InnoDB produced no warning at startup about illegal innodb_file_format_check values. (Bug#55095)

  • IF() with a subquery argument could raise a debug assertion for debug builds under some circumstances. (Bug#55077)

  • Building MySQL on Solaris 8 x86 failed when using Sun Studio due to gcc inline assembly code. (Bug#55061)

  • When upgrading an existing install with an RPM on Linux, the MySQL server might not have been restarted properly. This was due to a naming conflict when upgrading from a community named RPM. Previous installations are now correctly removed, and the MySQL init script are recreated and then start the MySQL server as normal. (Bug#55015)

  • The thread_concurrency system variable was unavailable on non-Solaris systems. (Bug#55001)

  • mysqld_safe contained a syntax error that prevented it from restarting the server. (Bug#54991)

  • If audit plugins were installed that were interested in MYSQL_AUDIT_GENERAL_CLASS events and the general query log was disabled, failed INSTALL PLUGIN or UNINSTALL PLUGIN statements caused a server crash. (Bug#54989)

  • Some functions did not calculate their max_length metadata value correctly. (Bug#54916)

  • A SHOW CREATE TABLE statement issued inside a transaction did not release its metadata locks at the end of statement execution. Consequently, SHOW CREATE TABLE was able to block other sessions from accessing the table (for example, using ALTER TABLE). (Bug#54905)

  • INFORMATION_SCHEMA.ENGINES and SHOW ENGINES described MyISAM as the default storage engine, but this is not true as of MySQL 5.5.5. (Bug#54832)

  • The MERGE storage engine tried to use memory mapping on the underlying MyISAM tables even on platforms that do not support it and even when myisam_use_mmap was disabled. This led to a hang for INSERT INTO ... SELECT FROM statements that selected from a MyISAM table into a MERGE table that contained the same MyISAM table. (Bug#54811, Bug#50788)

  • Incorrect error handling could result in an OPTIMIZE TABLE crash. (Bug#54783)

  • Performance Schema event collection for a thread could “leak” from one connection to another if the thread was used for one connection, then cached, then reused for another connection. (Bug#54782)

  • In debug builds, an assertion could be raised when the server tried to send an OK packet to the client after having failed to detect errors during processing of the WHERE condition of an UPDATE statement. (Bug#54734)

  • In a slave SQL thread or Event Scheduler thread, the SLEEP() function could not sleep more than five seconds. (Bug#54729)

  • SET sql_select_limit = 0 did not work. (Bug#54682)

  • Assignments of the PASSWORD() or OLD_PASSWORD() function to a user variable did not preserve the character set of the function return value. (Bug#54668)

  • A signal-handler redefinition for SIGUSR1 was removed. The redefinition could cause the server to encounter a kernel deadlock on Solaris when there are many active threads. Other POSIX platforms might also be affected. (Bug#54667)

  • Queries that named view columns in a GROUP BY clause could cause a server crash. (Bug#54515)

  • Performance Schema displayed spurious startup error messages when the server was run in bootstrap mode. (Bug#54467)

  • For distributions built with cmake rather than the GNU autotools, mysql lacked pager support. (Bug#54466)

  • The server failed to disregard sort order for some zero-length tuples, leading to an assertion failure. (Bug#54459)

  • Errors during processing of WHERE conditions in HANDLER ... READ statements were not detected, so the handler code still tried to send EOF to the client, raising an assertion. (Bug#54401)

  • If a session tried to drop a database containing a table opened with HANDLER in another session, any DATABASE statement (CREATE, DROP, ALTER) executed by that session produced a deadlock. (Bug#54360)

  • Deadlocks involving INSERT DELAYED statements were not detected. The server could crash if the delayed handler thread was killed due to a conflicting shared metadata lock. (Bug#54332)

  • For distributions built with cmake rather than the GNU autotools, some scripts were built without the execute bit set. (Bug#54129)

  • After ALTER TABLE was used on a temporary transactional table locked by LOCK TABLES, any later attempts to execute LOCK TABLES or UNLOCK TABLES caused a server crash. (Bug#54117)

  • INSERT IGNORE INTO ... SELECT statements could cause a debug assertion to be raised. (Bug#54106)

  • SHOW CREATE EVENT released all metadata locks held by the current transaction. This invalidated any existing savepoints and raised an assertion if ROLLBACK TO SAVEPOINT was executed. (Bug#54105)

  • A client could supply data in chunks to a prepared statement parameter other than of type TEXT or BLOB using the mysql_stmt_send_long_data() C API function (or COM_STMT_SEND_LONG_DATA command). This led to a crash because other data types are not valid for long data. (Bug#54041)

  • mysql_secure_installation did not properly identify local accounts and could incorrectly remove nonlocal root accounts. (Bug#54004)

  • A client with automatic reconnection enabled saw the error message Lost connection to MySQL server during query if the connection was lost between the mysql_stmt_prepare() and mysql_stmt_execute() C API functions. However, mysql_stmt_errno() returned 0, not the corresponding error number 2013. (Bug#53899)

  • INFORMATION_SCHEMA.COLUMNS reported incorrect precision for BIGINT UNSIGNED columns. (Bug#53814)

  • The patch for Bug#36569 caused performance regressions and incorrect execution of some UPDATE statments. (Bug#53737, Bug#53742)

  • Missing Performance Schema tables were not reported in the error log at server startup. (Bug#53617)

  • mysql_upgrade could incorrectly remove TRIGGER privileges. (Bug#53613)

  • SHOW ENGINE PERFORMANCE_SCHEMA STATUS underreported the amount of memory allocated by Performance Schema. (Bug#53566)

  • Portability problems in SHOW STATUS could lead to incorrect results on some platforms. (Bug#53493)

  • Builds of MySQL generated a large number of warnings. (Bug#53445)

  • Performance Schema header files were not installed in the correct directory. (Bug#53255)

  • The server could crash when processing subqueries with empty results. (Bug#53236)

  • With lower_case_table_names set to a nonzero value, searches for table or database names in INFORMATION_SCHEMA tables could produce incorrect results. (Bug#53095)

  • Use of uint in typelib.h caused compilation problems in Windows. This was changed to unsigned int. (Bug#52959)

  • The mysql-debug.pdb supplied with releases did not match the corresponding mysqld.exe. (Bug#52850)

  • The PERFORMANCE_SCHEMA database was not correctly created and populated on Windows. (Bug#52809)

  • The large_pages system variable was tied to the --large-files command-line option, not the --large-pages option. (Bug#52716)

  • Attempts to access a nonexistent table in the performance_schema database resulted in a misleading error message. (Bug#52586)

  • The ABI check for MySQL failed to compile with gcc 4.5. (Bug#52514)

  • Performance Schema could enter an infinite loop if required to create a large number of mutex instances. (Bug#52502)

  • mysql_secure_installation sometimes failed to locate the mysql client. (Bug#52274)

  • Some queries involving GROUP BY and a function that returned DATE raised a debug assertion. (Bug#52159)

  • If a symbolic link was used in a file path name, the Performance Schema did not resolve all file io events to the same name. (Bug#52134)

  • PARTITION BY KEY on a utf32 ENUM column raised a debugging assertion. (Bug#52121)

  • A pending FLUSH TABLES tbl_list WITH READ LOCK statement unnecessarily aborted transactions. (Bug#52117)

  • FLUSH TABLES WITH READ LOCK in one session and FLUSH TABLES tbl_list WITH READ LOCK in another session were mutually exclusive.

    This bug fix involved several changes to the states displayed by SHOW PROCESSLIST:

    • Table lock was replaced with Waiting for table level lock.

    • Waiting for table was replaced with Waiting for table flush.

    • New states: Waiting for global metadata lock, Waiting for schema metadata lock, Waiting for stored function metadata lock, Waiting for stored procedure metadata lock, Waiting for table metadata lock.

    (Bug#52044)

  • Reading a ucs2 data file with LOAD DATA INFILE was subject to three problems. 1) Incorrect parsing of the file as ucs2 data, resulting in incorrect length of the parsed string. This is fixed by truncating the invalid trailing bytes (incomplete multibyte characters) when reading from the file. 2) Reads from a proper ucs2 file did not recognize newline characters. This is fixed by first checking whether a byte is a newline (or any other special character) before reading it as a part of a multibyte character. 3) When using user variables to hold column data, the character set of the user variable was set incorrectly to the database charset. This is fixed by setting it to the character set specified in the LOAD DATA INFILE statement, if any. (Bug#51876)

  • XA START had a race condition that could cause a server crash. (Bug#51855)

  • The results of some ORDER BY ... DESC queries were sorted incorrectly. (Bug#51431)

  • Index Merge between three indexes could return incorrect results. (Bug#50389)

  • MIN() and MAX() returned incorrect results for DATE columns if the set of values included '0000-00-00'. (Bug#49771)

  • Searches in INFORMATION_SCHEMA tables for rows matching a nonexistent database produced an error instead of an empty query result. (Bug#49542)

  • DROP DATABASE failed if there was a TEMPORARY table with the same name as a non-TEMPORARY table in the database. (Bug#48067)

  • An assertion occurred in ha_myisammrg.cc line 1137:

      DBUG_ASSERT(this->file->children_attached);
    
    

    The problem was found while running RQG tests and the assertion occurred during REPAIR, OPTIMIZE, and ANALYZE operations. (Bug#47633)

  • The optimize method of the ARCHIVE storage engine did not preserve the FRM embedded in the ARZ file when rewriting the ARZ file for optimization. This meant an ARCHIVE table that had been optimized could not be discovered.

    The ARCHIVE engine stores the FRM in the ARZ file so it can be transferred from machine to machine without also needing to copy the FRM file. The engine subsequently restores the embedded FRM during discovery. (Bug#45377)

  • With character_set_connection set to utf16 or utf32, CREATE TABLE t1 AS SELECT HEX() ... caused a server crash. (Bug#45263)

  • The my_like_range_xxx() functions returned badly formed maximum strings for Asian character sets, which caused problems for storage engines. (Bug#45012)

  • A debugging assertion could be raised after a write failure to a closed socket. (Bug#42496)

  • Enumeration plugin variables were subject to a type casting error, causing inconsistent results between different platforms. (Bug#42144)

  • Sort-index_merge for join tables other than the first table used excessive memory. (Bug#41660)

  • DROP TABLE held a lock during unlink() file system operations, causing performance problems if unlink() took a long time. (Bug#41158)

  • Rows inserted in a table by one session were not immediately visible to another session that queried the table, even if the insert had committed. (Bug#37521)

  • Statements of the form UPDATE ... WHERE ... ORDER BY used a filesort even when not required. (Bug#36569)

    See also Bug#53737, Bug#53742.

  • Reading from a temporary MERGE table, with two non-temporary child MyISAM tables, resulted in the error:

    ERROR 1168 (HY000): Unable to open underlying table which is differently 
    defined or of non-MyISAM type or doesn't exist
    

    (Bug#36171)

  • safemalloc was excessively slow under certain conditions and has been removed. The --skip-safemalloc server option has also been removed, and the --with-debug=full configuration option is no different from --with-debug. (Bug#34043)

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

  • Problems in the atomic operations implementation could lead to server crashes. (Bug#22320, Bug#52261)

D.1.3. Changes in MySQL 5.5.5 (06 July 2010)

icc Notes:

  • This is the final release of MySQL 5.5 for which Generic Linux MySQL binary packages built with the icc compiler on x86 and x86_64 will be offered. These were previously produced as an alternative to our main packages built using gcc, as they provided noticeable performance benefits. In recent times the performance differences have diminished and build and runtime problems have surfaced, thus it is no longer viable to continue producing them.

    We continue to use the icc compiler to produce our distribution-specific RPM packages on ia64.

InnoDB Notes:

  • InnoDB has been upgraded to version 1.1.1. This version is considered of “early adopter” quality.

    InnoDB is now the default storage engine, rather than MyISAM, in the regular and enterprise versions of MySQL. This change has the following consequences:

    • Existing tables are not affected by this change, only new tables that are created.

    • Some of the InnoDB option settings also change, so that the default configuration represents the best practices for InnoDB functionality, reliability, and file management: innodb_file_format=Barracuda rather than Antelope, innodb_strict_mode=ON rather than OFF, and innodb_file_per_table=ON rather than OFF.

    • The system tables remain in MyISAM format.

    • MyISAM remains the default storage engine for the embedded version of MySQL.

    Follow these steps to ensure a smooth transition:

    • Familiarize yourself with the new default setting for the InnoDB file-per-table option, which creates a separate .ibd file for each user table. Adapt any backup procedure to include these files. For details, see Section 13.6.2, “Using Per-Table Tablespaces”.

    • Test the installation and operation for any applications that you run on the database server, to determine if they use any features specific to MyISAM that cause problems during installation (when the tables are created) or at runtime (when MyISAM-specific features might fail, or reliance on MyISAM settings for performance might become apparent). The InnoDBstrict” mode might also alert you to problems while setting up tables for an application.

    • As a preliminary test for individual tables rather than an entire application, you can use the statement ALTER TABLE table_name ENGINE=INNODB; to convert an existing table to use the InnoDB storage engine, and then run compatibility and performance tests.

    • Where necessary, add ENGINE=MYISAM clauses to CREATE TABLE statements, for tables that use features specific to MyISAM, such as full-text search.

    • Benchmark the most important queries, to check whether you need to make changes to the table indexes.

    • Measure the performance of applications under typical load, to check whether you need to change any additional InnoDB configuration settings.

    • As a last resort, if a database server is devoted entirely to applications that can only run with MyISAM tables, you could add a default-storage-engine line in the configuration file, or a --default-storage-engine option in the database server startup command, to re-enable MyISAM as the default storage engine for that server. For details about setting the default storage engine, see Section 13.3, “Setting the Storage Engine”.

Functionality added or changed:

  • Incompatible Change: All numeric operators and functions on integer, floating-point and DECIMAL values now throw an “out of range” error (ER_DATA_OUT_OF_RANGE) rather than returning an incorrect value or NULL, when the result is out of the supported range for the corresponding data type. See Section 10.6, “Out-of-Range and Overflow Handling”. (Bug#8433)

  • InnoDB Storage Engine: The INFORMATION_SCHEMA.INNODB_TRX table now includes a number of new fields that duplicate information from the SHOW ENGINE INNODB STATUS output. You no longer need to parse that output to get complete transaction information. (Bug#53336)

  • InnoDB Storage Engine: InnoDB stores redo log records in a hash table during recovery. On 64-bit systems, this hash table was 1/8 of the buffer pool size. To reduce memory usage, the dimension of the hash table was reduced to 1/64 of the buffer pool size (or 1/128 on 32-bit systems). (Bug#53122)

  • Previously, the innodb_file_format_check system variable served a dual purpose. Setting it at server startup would keep InnoDB from starting if any tables used a more recent file format than supported by the current level of InnoDB. If InnoDB could start, the same system variable was set to the “highest” file format value used by any InnoDB table in the database. Thus, its value could change from the value you specified.

    Now, checking and recording the file format tag are handled using separate variables. innodb_file_format_check can be set to 1 or 0 at server startup to enable or disable whether InnoDB checks the file format tag in the system tablespace. If the tag is checked and is higher than that supported by the current version of InnoDB, an error occurs and InnoDB does not start. If the tag is not higher, InnoDB sets the value of innodb_file_format_max to the file format tag.

    For background information about InnoDB file-format management, see Section 13.7.4, “InnoDB File Format Management”. (Bug#49792, Bug#53654)

  • The Rows_examined value in slow query log rows now is nonzero for UPDATE and DELETE statements that modify rows. (Bug#49756)

  • The deprecated mysql_fix_privilege_tables script has been removed. (Bug#42589)

  • There is a new system variable, skip_name_resolve, that is set from the value of the --skip-name-resolve server option. This provides a way to determine at runtime whether the server uses name resolution for client connections. (Bug#37168)

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

  • It is now possible to build MySQL on all platforms using CMake instead of the GNU autotools. (Prior to MySQL 5.5.5, CMake support was limited to Windows.) For instructions on using CMake to build MySQL, see http://forge.mysql.com/wiki/CMake.

Bugs fixed:

  • Performance: InnoDB Storage Engine: Deadlock detection could be a bottleneck in InnoDB processing, if many transactions attempted to update the same row simultaneously. The algorithm has been improved to enhance performance and scalability, in the InnoDB Plugin for MySQL 5.1, and in InnoDB 1.1 for MySQL 5.5. (Bug#49047)

  • Performance: While looking for the shortest index for a covering index scan, the optimizer did not consider the full row length for a clustered primary key, as in InnoDB. Secondary covering indexes will now be preferred, making full table scans less likely. (Bug#39653)

    See also Bug#55656.

  • Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007, CVE-2010-3681)

  • Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST.

    In MySQL 5.0 and above, this permitted an authenticated user with SELECT privileges on one table to obtain the field definitions of any table in all other databases and potentially of other MySQL instances accessible from the server's file system.

    Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one table could delete or read content from any other table in all databases on this server, and potentially of other MySQL instances accessible from the server's file system. (Bug#53371, CVE-2010-1848)

  • Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown, which could be exploited by an authenticated user to inject malicious code. (Bug#53237, CVE-2010-1850)

  • Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client/server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512, CVE-2010-3683)

  • Security Fix: Privilege checking for UNINSTALL PLUGIN was incorrect. (Bug#51770, CVE-2010-1621)

  • Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum size of one packet. (Bug#50974, CVE-2010-1849)

  • Incompatible Change: TRUNCATE TABLE did not take an exclusive lock on a table if truncation was done by deleting all rows in the table. For InnoDB tables, this could break proper isolation because InnoDB ended up aborting some granted locks when truncating a table. Now an exclusive metadata lock is taken before TRUNCATE TABLE can proceed. This guarantees that no other transaction is using the table.

    Incompatible change: Truncation using delete no longer fails if sql_safe_updates is enabled (this was an undocumented side effect). (Bug#42643)

  • Incompatible Change: After SET TRANSACTION ISOLATION LEVEL to set the isolation level for the next transaction, the session value of the tx_isolation system variable could appear to change after completion of statements within the transaction to the transaction isolation level. Now the current transaction isolation level is now established at transaction start. If there was a SET TRANSACTION ISOLATION LEVEL statement, the value is taken from it. Otherwise, the session tx_isolation value is used. A change in the session value while a transaction is active is still allowed, but no longer affects the current transaction isolation level. This is an incompatible change. A change in the session isolation level made while there is no active transaction overrides a SET TRANSACTION ISOLATION LEVEL statement, if there was any. (Bug#20837)

  • Important Change: Replication: It was possible to set sql_log_bin with session scope inside a transaction or subquery. (Bug#53437)

  • Important Change: Replication: When changing binlog_format or binlog_direct_non_transactional_updates, permissions were not checked prior to checking the scope and context of the variable being changed.

    As a result of this fix, an error is no longer reported when—in the context of a transaction or a stored function—you try to set a value for a session variable that is the same as its previous value, or for a variable whose scope is global only. (Bug#51277)

  • Important Change: Replication: When invoked, CHANGE MASTER TO and SET GLOBAL sql_slave_skip_counter now cause information to be written to the error log about the slave's state prior to execution of the statement. For CHANGE MASTER TO, this information includes the previous values for MASTER_HOST, MASTER_PORT, MASTER_LOG_FILE, and MASTER_LOG_POS. For SET GLOBAL sql_slave_skip_counter, this information includes the previous values of sql_slave_skip_counter, the group relay log name, and the group relay log position. (Bug#43406, Bug#43407)

  • Important Change: When using fast ALTER TABLE, different internal ordering of indexes in the MySQL optimizer and the InnoDB storage engine could cause error messages about possibly mixed up .frm files and incorrect index use. (Bug#47622)

  • InnoDB Storage Engine: Replication: TRUNCATE TABLE performed on a temporary table using the InnoDB storage engine was logged even when using row-based mode. (Bug#51251)

  • InnoDB Storage Engine: Replication: Reading from a table that used a self-logging storage engine and updating a table that used a transactional engine (such as InnoDB) generated changes that were written to the binary log using statement format which could make slaves diverge. However, when using mixed logging format, such changes should be written to the binary log using row format. (This issue did not occur when reading from tables using a self-logging engine and updating MyISAM tables, as this was already handled by checking for combinations of non-transactional and transactional engines.) Now such statements are classified as unsafe, and in mixed mode, cause a switch to row-based logging. (Bug#49019)

  • InnoDB Storage Engine: The server could crash during shutdown, if started with the option --innodb_use_sys_malloc=0. (Bug#54453)

  • InnoDB Storage Engine: The server could crash with a message InnoDB: Assertion failure in thread nnnn, typically during shutdown on a Windows system. (Bug#53947)

  • InnoDB Storage Engine: Some combinations of SELECT and SELECT FOR UPDATE statements could fail with errors about locks, or incorrectly release a row lock during a semi-consistent read operation. (Bug#53674)

  • InnoDB Storage Engine: Adding a unique key on multiple columns, where one of the columns is null, could mistakenly report duplicate key errors. (Bug#53290)

  • InnoDB Storage Engine: Fixed a checksum error reported for compressed tables when the --innodb_checksums option is enabled. Although the message stated that the table was corrupted, the table is actually fine after the fix. (Bug#53248)

  • InnoDB Storage Engine: When reporting a foreign key constraint violation during INSERT, InnoDB could display uninitialized data for the DB_TRX_ID and DB_ROLL_PTR system columns. (Bug#53202)

  • InnoDB Storage Engine: The values of innodb_buffer_pool_pages_total and innodb_buffer_pool_pages_misc in the information_schema.global_status table could be computed incorrectly. (Bug#52983)

  • InnoDB Storage Engine: InnoDB page splitting could enter an infinite loop for compressed tables. (Bug#52964)

  • InnoDB Storage Engine: An overly strict assertion could fail during the purge of delete-marked records in DYNAMIC or COMPRESSED InnoDB tables that contain column prefix indexes. (Bug#52746)

  • InnoDB Storage Engine: InnoDB attempted to choose off-page storage without ensuring that there was an “off-page storage” flag in the record header. To correct this, in DYNAMIC and COMPRESSED formats, InnoDB stores locally any non-BLOB columns having a maximum length not exceeding 256 bytes. This is because there is no room for the “external storage” flag when the maximum length is 255 bytes or less. This restriction trivially holds in REDUNDANT and COMPACT formats, because there InnoDB always stores locally columns having a length up to local_len = 788 bytes. (Bug#52745)

  • InnoDB Storage Engine: Connections waiting for an InnoDB row lock ignored KILL until the row lock wait ended. Now, KILL during lock wait results in “query interrupted” instead of “lock wait timeout exceeded”. The corresponding transaction is rolled back. (Bug#51920)

  • InnoDB Storage Engine: InnoDB checks to see whether a row could possibly exceed the maximum size if all columns are fully used. This produced Row size too large errors for some tables that could be created with the built-in InnoDB from older MySQL versions. Now the check is only done when innodb_strict_mode is enabled or if the table is dynamic or compressed. (Bug#50495)

  • InnoDB Storage Engine: Multi-statement execution could fail with an error about foreign key constraints. This problem could affect calls to mysql_query() and mysql_real_query(), and CALL statements that invoke stored procedures. (Bug#48024)

  • InnoDB Storage Engine: A mismatch between index information maintained within the .frm files and the corresponding information in the InnoDB system tablespace could produce this error: [ERROR] Index index of table has n columns unique inside InnoDB, but MySQL is asking statistics for m columns. Have you mixed up .frm files from different installations? (Bug#44571)

  • Partitioning: Replication: Attempting to execute LOAD DATA on a partitioned MyISAM table while using statement-based logging mode caused the master to hang or crash. (Bug#51851)

  • Partitioning: Replication: The NO_DIR_IN_CREATE server SQL mode was not enforced when defining subpartitions. In certain cases, this could lead to failures on replication slaves. (Bug#42954)

  • Partitioning: Rows inserted into a table created using a PARTITION BY LIST COLUMNS option referencing multiple columns could be inserted into the wrong partition. (Bug#52815)

  • Partitioning: Partition pruning on RANGE partitioned tables did not always work correctly; the last partition was not excluded if the range was beyond it (when not using MAXVALUE). Now the last partition is not included if the partitioning function value is not within the range. (Bug#51830)

  • Partitioning: Attempting to partition a table using a DECIMAL column caused the server to crash; this not supported and is now specifically not permitted. (Bug#51347)

  • Partitioning: ALTER TABLE statements that cause table partitions to be renamed or dropped (such as ALTER TABLE ... ADD PARTITION, ALTER TABLE ... DROP PARTITION, and ALTER TABLE ... REORGANIZE PARTITION) — when run concurrently with queries against the INFORMATION_SCHEMA.PARTITIONS table — could fail, cause the affected partitioned tables to become unusable, or both. This was due to the fact that the INFORMATION_SCHEMA database ignored the name lock imposed by the ALTER TABLE statement on the partitions affected. In particular, this led to problems with InnoDB tables, because InnoDB would accept the rename operation, but put it in a background queue, so that subsequent rename operations failed when InnoDB was unable to find the correct partition. Now, INFORMATION_SCHEMA honors name locks imposed by ongoing ALTER TABLE statements that cause partitions to be renamed or dropped. (Bug#50561)

    See also Bug#47343, Bug#45808.

  • Partitioning: The insert_id server system variable was not reset following an insert that failed on a partitioned MyISAM table having an AUTO_INCREMENT column. (Bug#50392)

  • Partitioning: Foreign keys are not supported on partitioned tables. However, it was possible using an ALTER TABLE statement to set a foreign key on a partitioned table; it was also possible to partition a table with a single foreign key. (Bug#50104)

  • Partitioning: It was possible to execute a CREATE TEMPORARY TABLE tmp LIKE pt statement, where pt is a partitioned table, even though partitioned temporary tables are not permitted, which caused the server to crash. Now a check is performed to prevent such statements from being executed. (Bug#49477)

  • Partitioning: When attempting to perform DDL on a partitioned table and the table's .par file could not be found, the server returned the inaccurate error message Out of memory; restart server and try again (needed 2 bytes). Now in such cases, the server returns the error Failed to initialize partitions from .par file. (Bug#49161)

  • Partitioning: GROUP BY queries performed poorly for some partitioned tables. This was due to the block size not being set for partitioned tables, thus the keys per block was not correct, which could cause such queries to be optimized incorrectly. (Bug#48229)

    See also Bug#37252.

  • Partitioning: REPAIR TABLE failed for partitioned ARCHIVE tables. (Bug#46565)

  • Replication: When using unique keys on NULL columns in row-based replication, the slave sometimes chose the wrong row when performing an update. This happened because a table having a unique key on such a column could have multiple rows containing NULL for the column used by the unique key, and the slave merely picked the first row containing NULL in that column. (Bug#53893)

  • Replication: When a CREATE TEMPORARY TABLE ... SELECT statement was executed within a transaction that updated only transactional engines and was later rolled back (for example, due to a deadlock) the changes—including the creation of the temporary table—were not written to the binary log, which caused subsequent updates to this table to fail on the slave. (Bug#53421)

  • Replication: When using the statement-based logging format, statements that used CONNECTION_ID() were always kept in the transaction cache; consequently, nontransactional changes that should have been flushed before the transaction were kept in the transaction cache. (Bug#53075)

    This regression was introduced by Bug#51894.

  • Replication: In some cases, attempting to update a column with a value of an incompatible type resulted in a mismatch between master and slave because the column value was set to its implicit default value on the master (as expected), but the same column on the slave was set to NULL. (Bug#52868)

  • Replication: ACK packets in semisynchronous replication were not checked for length and malformed packets could cause a server crash. (Bug#52748)

  • Replication: When temporary tables were in use, switching the binary logging format from STATEMENT to ROW did not take effect until all temporary tables were dropped. (The existence of temporary tables should prevent switching the format only from ROW to STATEMENT from taking effect, not the reverse.) (Bug#52616)

  • Replication: A buffer overrun in the handling of DATE column values could cause mysqlbinlog to fail when reading back logs containing certain combinations of DML on a table having a DATE column followed by dropping the table. (Bug#52202)

  • Replication: The failure of a REVOKE statement was logged with the wrong error code, causing replication slaves to stop even when the failure was expected on the master. (Bug#51987)

  • Replication: Issuing any DML on a temporary table temp followed by DROP TEMPORARY TABLE temp, both within the same transaction, caused replication to fail.

    The fix introduces a change to statement-based binary logging with respect to temporary tables. Within a transaction, changes to temporary tables are saved to the transaction cache and written to the binary log when the transaction commits. Otherwise, out-of-order logging of events could occur. This means that temporary tables are treated similar to transactional tables for purposes of caching and logging. This affects assessment of statements as safe or unsafe and the associated error message was changed from:

    Unsafe statement written to the binary log using statement format
    since BINLOG_FORMAT = STATEMENT. Statements that read from both
    transactional and non-transactional tables and write to any of them
    are unsafe.
    

    To:

    Unsafe statement written to the binary log using statement format
    since BINLOG_FORMAT = STATEMENT. Statements that read from both
    transactional (or a temporary table of any engine type) and
    non-transactional tables and write to any of them are unsafe.
    

    (Bug#51894)

    See also Bug#51291, Bug#53075, Bug#53259, Bug#53452, Bug#54872.

    This regression was introduced by Bug#46364.

  • Replication: The flag stating whether a user value was signed or unsigned (unsigned_flag) could sometimes change between the time that the user value was recorded for logging purposes and the time that the value was actually written to the binary log, which could lead to inconsistency. Now unsigned_flag is copied when the user variable value is copied, and the copy of unsigned_flag is then used for logging. (Bug#51426)

    See also Bug#49562.

  • Replication: Enabling binlog_direct_non_transactional_updates causes nontransactional changes to be written to the binary log upon committing the statement. However, even when not enabled, the addition of this variable introduced a number of undesired changes in behavior:

    1. When using ROW or MIXED logging mode: Nontransactional changes executed within a transaction prior to any transactional changes were written to the statement cache, but those following any transactional changes were written to the transactional cache instead, causing these (later) nontransactional changes to be lost.

    2. When using ROW or MIXED logging mode: When rolling back a transaction, any nontransactional changes that might be in the transaction cache were disregarded and truncated along with the transactional changes.

    3. When using STATEMENT logging mode: A statement that combined transactional and nontransactional changes prior to any other transactional changes within the transaction, but failed, was kept in the transactional cache until the transaction ended, rather than being written to the binary log at the instant of failure (and not deferred to the end of the transaction).

    These problems have been handled as follows:

    • The setting for binlog_direct_non_transactional_updates no longer has any effect when the value of binlog_format is either ROW or MIXED. This addresses the first two issues previously listed.

    • When using statement-based logging with binlog_direct_non_transactional_updates set to ON, any statement combining transactional and nontransactional changes within the same transaction is now stored in the transaction cache, whether it succeeds or not, and regardless of its order of execution among any transactional statements within that transaction. This means that such a statement is now written to the binary log only on transaction commit or rollback.

    (Bug#51291)

    This regression was introduced by Bug#46364.

  • Replication: When using temporary tables the binary log needs to insert a pseudo-thread ID for threads that are using temporary tables, each time a switch happens between two threads, both of which are using temporary tables. However, if a thread issued a failing statement before exit, its ID was not recorded in the binary log, and this in turn caused the ID for the next thread that tried to do something with a temporary table not to be logged as well. Subsequent replays of the binary log failed with the error Table ... doesn't exist. (Bug#51226)

  • Replication: If the master was using sql_mode='TRADITIONAL', duplicate key errors were not sent to the slave, which received 0 rather than the expected error code. This caused replication to fail even when such an error was expected. (Bug#51055)

  • Replication: DDL statements that lock tables (such as ALTER TABLE, CREATE INDEX, and CREATE TRIGGER) caused spurious ER_BINLOG_ROW_MODE_AND_STMT_ENGINE or ER_BINLOG_STMT_MODE_AND_ROW_ENGINE errors, even though they did not insert rows into any tables.

    Note

    The error ER_BINLOG_ROW_MODE_AND_STMT_ENGINE is generated when binlog_format=ROW and a statement modifies a table restricted to statement-based logging; ER_BINLOG_STMT_MODE_AND_ROW_ENGINE is generated when binlog_format=STATEMENT and a statement modifies a table restricted to row-based logging.

    (Bug#50479)

    This regression was introduced by Bug#39934.

  • Replication: When run with the --database option, mysqlbinlog printed ROLLBACK statements but did not print any corresponding SAVEPOINT statements. (Bug#50407)

  • Replication: When a CREATE EVENT statement was followed by an additional statement and the statements were executed together as a single statement, the CREATE EVENT statement was padded with “garbage” characters when written to the binary log, which led to a syntax error when trying to read back from the log. (Bug#50095)

  • Replication: When using a non-transactional table on the master with autocommit disabled, no COMMIT was recorded in the binary log following a statement affecting this table. If the slave's copy of the table used a transactional storage engine, the result on the slave was as though a transaction had been started, but never completed. (Bug#49522)

    See also Bug#29288.

  • The make_binary_distribution target to make could fail on some platforms because the lines generated were too long for the shell. (Bug#54590)

  • Inconsistent checking of the relationship between SHOW statements and INFORMATION_SCHEMA queries caused such queries to fail sometimes. (Bug#54422)

  • A crash occurred if a table that was locked with LOCK TABLES was listed twice in a DROP TABLE statement. (Bug#54282)

  • ALTER TABLE for views is not legal but did not produce an error. (If you need to rename a view, use RENAME TABLE.) (Bug#53976)

  • Valgrind warnings resulting from passing incomplete DATETIME values to the TIMESTAMP() function were corrected. (Bug#53942)

  • Builds of the embedded mysqld would fail due to a missing element of the struct NET. (Bug#53908, Bug#53912)

  • The definition of the MY_INIT macro in my_sys.h included an extraneous semicolon, which could cause compilation failure. (Bug#53906)

  • Queries that used MIN() or MAX() on indexed columns could be optimized incorrectly. (Bug#53859)

  • UPDATE on an InnoDB table modifying the same index that was used to satisfy the WHERE condition could trigger a debug assertion under some circumstances. (Bug#53830)

  • MySQL incorrectly processed ALTER DATABASE `#mysql50#<special>` UPGRADE DATA DIRECTORY NAME where <special> was ., .., or a sequence starting with ./ or ../. It used the server data directory (that contains other regular databases) as the database directory. (Bug#53804, CVE-2010-2008)

  • OPTIMIZE TABLE could be run on a table in use by a transaction in a different session, causing repeatable read to break. (Bug#53798)

  • InnoDB crashed when replacing duplicates in a table after a fast ALTER TABLE added a unique index. (Bug#53592)

  • For InnoDB tables, the error handler for a fast CREATE INDEX did not reset the error state of the transaction before attempting to undo a failed operation, resulting in a crash. (Bug#53591)

  • For single-table DELETE statements that used quick select and index scan simultaneously caused a server crash or assertion failure. (Bug#53450)

  • Certain path names passed to LOAD_FILE() could cause a server crash. (Bug#53417)

  • If the completion_type session variable was changed after a stored procedure or prepared statement had been cached, the change had no effect on subsequent executions of the procedure or statement. (Bug#53346)

  • The AND CHAIN option for COMMIT and ROLLBACK failed to preserve the current transaction isolation level. Setting completion_type to 1 also failed to do so. (Bug#53343)

  • Incorrect results could be returned for LEFT JOIN of InnoDB tables with an impossible WHERE condition. (Bug#53334)

  • The Lock_time value in the slow query log was negative for stored routines. (Bug#53191)

  • Setting the innodb_change_buffering system variable to DEFAULT produced an incorrect result. (Bug#53165)

  • mysqldump and SELECT ... INTO OUTFILE truncated long BLOB and TEXT values to 766 bytes. (Bug#53088)

  • On some systems, such as Mac OS X, the sockaddr_in and sockaddr_in6 structures contain a non-standard field (sin_len / sin6_len) that must be set but was not. This resulted in hostname lookup failure. (Bug#52923)

  • In the debug version of the server, the FreeState() function could in some circumstances be called twice, leading to an assertion failure. (Bug#52884)

  • Concurrent SHOW COLUMNS statements could cause a server crash. (Bug#52856)

  • With a non-latin1 ASCII-based current character set, the server inappropriately converted DATETIME values to strings. This resulted in the optimizer not using indexes on such columns. (Bug#52849)

  • mysqld_safe set plugin_dir using a default path name rather than a path depending on basedir. (Bug#52737)

  • Semi-consistent read was implemented for InnoDB to address Bug#3300. Semi-consistent reads do not block when a nonmatching record is already locked by some other transaction. If the record is not locked, a lock is acquired, but is released if the record does not match the WHERE condition. However, semi-consistent read was attempted even for UPDATE statements having a WHERE condition of the form pk_col1=constant1, ..., pk_colN=constantN. Some code that was designed with the assumption that semi-consistent read would be only attempted on table scans, failed. (Bug#52663)

  • Setting @@GLOBAL.debug to an empty string failed to clear the current debug settings. (Bug#52629)

  • SHOW CREATE TABLE was blocked if the table was write locked by another session. (Bug#52593)

  • The length and max_length metadata values were incorrect for columns with the TEXT family of data types that used multibyte character sets This bug was introduced in MySQL 5.5.3. (Bug#52520)

  • mysql_upgrade attempted to work with stored routines before they were available. (Bug#52444)

  • The check_table_is_closed() debugging function did not protect access to the MyISAM open tables list, with the result that server crashes could occur during table drop or rename operations. (Bug#52432)

  • Spurious duplicate-key errors occurred for multiple-column indexes on columns with the BINARY data type. (Bug#52430)

  • EXPLAIN EXTENDED crashed trying to resolve references to freed temporary table columns for GROUP_CONCAT() ORDER BY arguments. (Bug#52397)

  • During installing of MySQL server using the MSI package on Windows, the default-character-set option would be included in the default configuration template file. This would cause the MySQL server to fail to start properly. (Bug#52380)

  • Two sessions trying to set the global event_scheduler system variable to OFF resulted in one of them hanging waiting for the event scheduler to stop. (Bug#52367)

  • There was a race condition between flags used for signaling that a query was killed, which led to error-reporting and lock-acquisition problems. (Bug#52356)

  • For a concurrent load of 16 or more connections containing many LOCK TABLES WRITE statements for the same table, server throughput was significantly lower for MySQL 5.5.3 and 5.5.4 than for earlier versions (10%–40% lower depending on concurrency). (Bug#52289)

  • Operations on geometry data types failed on some systems for builds compiled with Sun Studio. (Bug#52208)

  • The optimizer could attempt to evaluate the WHERE clause before any rows had been read, resulting in a server crash. (Bug#52177)

  • Cast operations on NULL DECIMAL values could cause server crashes or Valgrind warnings. (Bug#52168)

  • An assertion was raised as a result of a NULL string being passed to the dtoa code. (Bug#52165)

  • A memory leak occurred due to missing deallocation of the comparators array (a member of the Arg_comparator class). (Bug#52124)

  • For debug builds, creating a view containing a subquery that might require collation adjustment caused an assertion to be raised. For example, this could occur if some items had different collations but the result collation could be adjusted to the one of them. (Bug#52120)

  • Aggregate functions could incorrectly return NULL in outer join queries. (Bug#52051)

  • For outer joins, the optimizer could fail to properly calculate table dependencies. (Bug#52005)

  • A COUNT(DISTINCT) query on a view could cause a server crash. (Bug#51980)

  • For LDML-defined collations, some data structures were not initialized properly to enable UPPER() and LOWER() to work correctly. (Bug#51976)

  • On Windows, LOAD_FILE() could cause a crash for some pathnames. (Bug#51893)

  • Invalid memory reads occurred for HANDLER ... READ NEXT after a failed HANDLER ... READ FIRST. (Bug#51877)

  • After TRUNCATE TABLE of a MyISAM table, subsequent queries could crash the server if myisam_use_mmap was enabled. (Bug#51868)

  • If myisam_sort_buffer_size was set to a small value, table repair for MyISAM tables with FULLTEXT indexes could crash the server. (Bug#51866)

  • Stored routine DDL statements were written to the binary log using statement-based format regardless of the current logging format. (Bug#51839)

  • A problem with equality propagation optimization for prepared statements and stored procedures caused a server crash upon re-execution of the prepared statement or stored procedure. (Bug#51650)

    See also Bug#8115, Bug#8849.

  • The optimizer performed an incorrect join type when COALESCE() appeared within an IN() operation. (Bug#51598)

  • Locking involving the LOCK_plugin, LOCK_global_system_variables, and LOCK_status mutexes could deadlock. (Bug#51591)

  • Executing a LOAD XML INFILE statement could sometimes lead to a crash of the MySQL Server. (Bug#51571)

  • The server crashed when the optimizer attempted to determine constant tables but a table storage engine did not support exact record count. (Bug#51494)

  • The server could crash populating the INFORMATION_SCHEMA.PROCESSLIST table due to lack of mutex protection. (Bug#51377)

  • Use of HANDLER statements with tables that had spatial indexes caused a server crash. (Bug#51357)

  • With an XA transaction active, SET autocommit = 1 could cause side effects such as memory corruption or a server crash. (Bug#51342)

  • Corrupt MyISAM tables were automatically repaired even when myisam_recover_options was set to OFF. (Bug#51327)

  • Following a bulk insert into a MyISAM table, if MyISAM failed to build indexes using repair by sort, data file corruption could occur. (Bug#51307)

  • CHECKSUM TABLE could compute the checksum for BIT columns incorrectly. (Bug#51304)

  • ALTER TABLE on InnoDB tables (including partitioned tables) acquired exclusive locks on rows of the table being altered. If there was a concurrent transaction that did locking reads from this table, this sometimes led to a deadlock that was not detected by the metadata lock subsystem or by InnoDB (and was reported only after exceeding innodb_lock_wait_timeout). (Bug#51263)

  • A HAVING clause on a joined table in some cases failed to eliminate rows which should have been excluded from the result set. (Bug#51242)

  • Two sessions trying to set the global event_scheduler system variable to different values could deadlock. (Bug#51160)

  • InnoDB fast index creation could incorrectly use a table copy in some cases. (Bug#50946)

  • The Loose Index Scan optimization method assumed that it could depend on the partitioning engine to maintain interval endpoint information, as if it were a storage engine. (Bug#50939)

  • The type inference used for view columns caused some columns in views to be handled as the wrong type, as compared to the same columns in base tables. DATE columns in base tables were treated as TIME columns in views, and base table TIME columns as view DATETIME columns. (Bug#50918)

  • A syntactically invalid trigger could cause the server to crash when trying to list triggers. (Bug#50755)

  • Previously, the server held a global mutex while performing file operations such as deleting an .frm or data file, or reading table metadata from an .frm file or index statistics from a data file. Now the mutex is not held for these operations. Instead, the server uses metadata locks. (Bug#50589, Bug#51557, Bug#49463)

  • User-defined variables of type REAL that contained NULL were handled improperly when assigned to a column of another type. (Bug#50511)

  • Setting --secure-file-priv to the empty string left the value unaffected. (Bug#50373)

  • Calculation of intervals for Event Scheduler events was not portable. (Bug#50087)

  • The YEAR values 2000 and 0000 could be treated as equal. (Bug#49910)

  • Performing a single in-place ALTER TABLE containing ADD INDEX and DROP INDEX options that used the same index name could result in a corrupt table definition file. Now such ALTER TABLE statements are no longer performed in place. (Bug#49838)

  • mysql_upgrade did not detect when CSV log tables incorrectly contained columns that could be NULL. Now these columns are altered to be NOT NULL. (Bug#49823)

  • support-files/mysql.spec.sh had unnecessary Perl dependencies. (Bug#49723)

  • Selecting from INFORMATION_SCHEMA.ROUTINES or INFORMATION_SCHEMA.PARAMETERS resulted in a memory leak. (Bug#48729)

  • In MySQL 5.1, READ COMMITTED was changed to use less locking due to the availability of row based binary logging (see the Note under READ COMMITTED at Section 12.3.6, “SET TRANSACTION Syntax”). However, READ UNCOMMITTED did not have the same change, so it was using more locks than the higher isolation level, which is unexpected. This was changed so that READ UNCOMMITTED now also uses the lesser amount of locking and has the same restrictions for binary logging. (Bug#48607)

  • On Intel x86 machines, the optimizer could choose different execution plans for a query depending on the compiler version and optimization flags used to build the server binary. (Bug#48537)

  • A trigger could change the behavior of assigning NULL to a NOT NULL column. (Bug#48525)

  • The server crashed when it could not determine the best execution plan for queries involving outer joins with nondeterministic ON clauses such as the ones containing the RAND() function, a user-defined function, or a NOT DETERMINISTIC stored function. (Bug#48483)

  • EXPLAIN could cause a server crash for some queries with subqueries. (Bug#48419)

  • The MERGE engine failed to open a child table from a different database if the child table or database name contained characters that were the subject of table name to filename encoding.

    Further, the MERGE engine did not properly open a child table from the same database if the child table name contained characters such as '/', '#'. (Bug#48265)

  • On Windows, the server failed to find a description for Event ID 100. (Bug#48042)

  • A query that read from a derived table (of the form SELECT ... FROM (SELECT ...)) produced incorrect results when the following conditions were present:

    • The table subquery contained a derived query ((SELECT ... ) AS column).

    • The derived query could potentially produce zero rows or a single NULL (that is, no rows matched, or the query used an aggregate function such as SUM() running over zero rows).

    • The table subquery joined at least two tables.

    • The join condition involved an index.

    (Bug#47904)

  • The optimization to read MIN() or MAX() values from an index did not properly handle comparisons with NULL values. This could produce incorrect results for MIN() or MAX()when the WHERE clause tested a NOT NULL column for NULL. (Bug#47762)

  • Killing a query during the optimization phase of a subquery could cause a server crash. (Bug#47761)

  • Using REPLACE to update a previously inserted negative value in an AUTO_INCREMENT coumn in an InnoDB table caused the table auto-increment value to be updated to 2147483647. (Bug#47720)

  • The query shown by EXPLAIN EXTENDED plus SHOW WARNINGS could produce results different from the original query. (Bug#47669)

  • MyISAM could write uninitialized data to new index pages. Now zeros are written to unused bytes in the pages. (Bug#47598)

  • OPTIMIZE TABLE for an InnoDB table could raise an assertion if another session issued a concurrent DROP TABLE. (Bug#47459)

  • For updates to InnoDB tables, TIMESTAMP columns could be updated even when no values actually changed. (Bug#47453)

  • Setting myisam_repair_threads larger than 1 could result in the cardinality for all indexes of a MyISAM table being set to 1 after parallel index repair. (Bug#47444)

  • mysqld_safe did not always pass --open-files-limit through to mysqld. mysqld_safe did not treat dashes and underscores as equivalent in option names. (Bug#47095)

  • For events of MYSQL_AUDIT_GENERAL_CLASS, the event subclass was not passed to audit plugins even though the server passed the subclass to the plugin handler. The subclass is now available through the following changes:

    • The struct mysql_event_general structure has a new event_subclass member.

    • The new member changes the interface, so the audit plugin interface version, MYSQL_AUDIT_INTERFACE_VERSION, has been incremented from 0x0100 to 0x0200. Plugins that require access to the new member must be recompiled to use version 0x0200 or higher.

    The example plugin in the plugin/audit_null directory has been modified to count events of each subclass, based on the event_subclass value. See Section 22.2.5.2, “Writing Audit Plugins”. (Bug#47059)

  • When the transaction isolation level was REPEATABLE READ and binary logging used statement or mixed format, SELECT statements with subqueries referencing InnoDB tables unnecessarily acquired shared locks on rows in these tables. (Bug#46947)

  • In debug builds, if the listed columns in the view definition of the table used in an INSERT ... SELECT statement mismatched, an assertion was raised in the query cache invalidation code following the failing statement. (Bug#46615)

  • For the COMMIT and ROLLBACK statements, the AND CHAIN and RELEASE modifiers should be mutually exclusive, but the parser allowed both to be specified. (Bug#46527)

  • If the server is started with --skip-grant-tables, plugin loading and unloading should be prohibited, but the server failed to reject INSTALL PLUGIN and UNINSTALL PLUGIN statements. (Bug#46261)

  • gcc 4.4.0 could fail to compile dtoa.c. (Bug#45882)

  • ALTER TABLE ... ADD COLUMN for a table with multiple foreign keys caused a server crash. (Bug#45052)

  • Manual pages for a few little-used programs were missing from RPM packages. (Bug#44370)

  • Using an initial command with mysql_options(..., MYSQL_INIT_COMMAND, ...) that generated multiple result sets (such as a stored procedure or a multi-statement command) left the connection unusable. (Bug#42373)

  • The server could crash with an out of memory error when trying to parse a query that was too long to fit in memory. Now the parser rejects such queries with an ER_OUT_OF_RESOURCES error. (Bug#42064)

  • InnoDB could fail to create a unique index on NULL columns. (Bug#41904)

  • For a query that selected from a view and used an alias for the view, the metadata used the alias name rather than the view name in the MYSQL_FIELD.table member. (Bug#41788)

  • mysql_upgrade did not create temporary files properly. (Bug#41057)

  • It was possible for DROP TABLE of one MyISAM table to remove the data and index files of a different MyISAM table. (Bug#40980)

  • If the arguments to a CONCAT() call included a local routine variable, selecting the return value into a user variable could produce an incorrect result. (Bug#40625)

  • Column names displayed from the PARTITION_EXPRESSION column of the INFORMATION_SCHEMA.PARTITIONS table did not include escape characters as necessary. (Bug#39338)

  • When SET TRANSACTION ISOLATION LEVEL was used to set the isolation level for the next transaction, the level could persist for subsequent transactions. (Bug#39170)

  • When using UNINSTALL PLUGIN to remove a loaded plugin, open tables and connections caused mysqld to hang until the open connections had been closed. (Bug#39053)

  • Valgrind warnings in the InnoDB compare_record() function were corrected. (Bug#38999)

  • The optimizer sometimes used filesort for ORDER BY when it should have used an index. (Bug#38745)

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

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

  • The test for readline during configuration failed when trying to build MySQL in a directory other than the source tree root. (Bug#35250)

  • mysqld could fail during execution when using SSL. (Bug#34236)

  • A query on a FEDERATED table in which the data was ordered by a TEXT column returned incorrect results. For example, a query such as the following would result in incorrect results if column column1 was a TEXT column:

    SELECT * FROM table1 ORDER BY column1;
    

    (Bug#32426)

  • MySQL Makefiles relied on GNU extensions. (Bug#30708)

  • The parser allocated too much memory for a query containing multiple statements. (Bug#27863)

  • The behavior of the RPM installation for both new installations and upgrade installations has changed.

    During a new installation, the server boot scripts are installed, but the MySQL server is not started at the end of the installation, since the status of the system during an unattended installation is not known.

    During an upgrade installation using the RPM packages, if the server is running when the upgrade occurs, the server is stopped, the upgrade occurs, and server is restarted. If the server is not already running when the RPM upgrade occurs, the server is not started at the end of the installation.

    The boot scripts for MySQL are installed in the appropriate directories in /etc, so the MySQL server will be restarted automatically at the next machine reboot. (Bug#27072)

  • ROW_COUNT() returned a meaningful value only for some DML statements. Now it returns a value as follows:

    • DDL statements: 0. This applies to statements such as CREATE TABLE or DROP TABLE.

    • DML statements other than SELECT: The number of affected rows. This applies to statements such as UPDATE, INSERT, or DELETE (as before), but now also to statements such as ALTER TABLE and LOAD DATA INFILE.

    • SELECT: -1 if the statement returns a result set, or the number of rows “affected” if it does not. For example, for SELECT * FROM t1, ROW_COUNT() returns -1. For SELECT * FROM t1 INTO OUTFILE 'file_name', ROW_COUNT() returns the number of rows written to the file.

    • SIGNAL statements: 0.

    (Bug#21818)

D.1.4. Changes in MySQL 5.5.4 (09 April 2010)

InnoDB Notes:

Functionality added or changed:

  • InnoDB Storage Engine: InnoDB now has a innodb_use_native_aio system variable that can be disabled at startup if there is a problem with the asynchronous I/O subsystem in the OS. This variable applies to Linux systems only, where the MySQL server now has a dependency on the libaio library.

Bugs fixed:

  • Performance: InnoDB Storage Engine: The redo scan during InnoDB recovery used excessive CPU. The efficiency of this scan was improved, significantly speeding up crash recovery. (Bug#49535, Bug#29847)

  • Performance: InnoDB Storage Engine: InnoDB page-freeing operations were made faster for compressed blocks, speeding up ALTER TABLE, DROP TABLE, and other operations on compressed tables that free compressed blocks. One symptom of the older behavior could be 100% CPU use during these operations. (Bug#35077)

  • InnoDB Storage Engine: The AIX implementation of readdir_r() caused InnoDB errors. (Bug#50691)

  • InnoDB Storage Engine: The limit of 1023 concurrent data-modifying transactions has been raised. The limit is now 128 * 1023 concurrent transactions that generate undo records. You can remove any workarounds that require changing the proper structure of your transactions, such as committing more frequently or delaying DML operations to the end of a transaction. See Section 13.7.7.19, “Better Scalability with Multiple Rollback Segments”. (Bug#26590)

  • A unique index on a column prefix could not be upgraded to a primary index even if there was no primary index already defined. (Bug#51378)

  • InnoDB did not reset table AUTO_INCREMENT values to the last used values after a server restart. (Bug#49032)

  • When using the EXAMPLE storage engine, when the engine had been built as a plugin (instead of built-in), and DTrace probes had been enabled during the build, loading the storage engine library would fail due to a missing object table entry.

D.1.5. Changes in MySQL 5.5.3 (24 March 2010 Milestone 3)

Performance Schema Notes:

  • MySQL Server now includes Performance Schema, a feature for monitoring server execution at a low level. It is implemented using the PERFORMANCE_SCHEMA storage engine and the performance_schema database. Performance Schema focuses primarily on performance data. This differs from INFORMATION_SCHEMA, which serves for inspection of metadata. For more information, see Chapter 20, MySQL Performance Schema.

    Performance Schema support is included in binary MySQL distributions. It is disabled by default. To enable it, start the server with the --performance_schema option.

    To create the performance_schema database if you are upgrading from an earlier release, run mysql_upgrade and restart the server. See Section 4.4.7, “mysql_upgrade — Check Tables for MySQL Upgrade”.

InnoDB Notes:

  • This release includes InnoDB 1.0.6. This version is considered of Release Candidate (RC) quality.

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: The following obsolete constructs have been removed. Where alternatives are shown, applications should be updated to use them.

    • The log_bin_trust_routine_creators system variable (use log_bin_trust_function_creators).

    • The myisam_max_extra_sort_file_size system variable.

    • The record_buffer system variable (use read_buffer_size).

    • The sql_log_update system variable.

    • The table_type system variable (use storage_engine).

    • The FRAC_SECOND modifier for the TIMESTAMPADD() function.

    • The TYPE table option to specify the storage engine for CREATE TABLE or ALTER TABLE (use ENGINE).

    • The SHOW TABLE TYPES SQL statement (use SHOW ENGINES).

    • The SHOW INNODB STATUS and SHOW MUTEX STATUS SQL statements (use SHOW ENGINE INNODB STATUS SHOW ENGINE INNODB MUTEX).

    • The SHOW PLUGIN SQL statement (use SHOW PLUGINS).

    • The LOAD TABLE ... FROM MASTER and LOAD DATA FROM MASTER SQL statements (use mysqldump or mysqlhotcopy to dump tables and mysql to reload dump files).

    • The BACKUP TABLE and RESTORE TABLE SQL statements (use mysqldump or mysqlhotcopy to dump tables and mysql to reload dump files).

    • TIMESTAMP(N) data type: The ability to specify a display width of N (use without N).

    • The --default-character-set and --default-collation server options (use --character-set-server and --collation-server).

    • The --delay-key-write-for-all-tables server option (use --delay-key-write=ALL).

    • The --enable-locking and --skip-locking server options (use --external-locking and --skip-external-locking).

    • The --log-bin-trust-routine-creators server option (use --log-bin-trust-function-creators).

    • The --log-long-format server option.

    • The --log-update server option.

    • The --master-xxx server options to set replication parameters (use the CHANGE MASTER TO statement instead): --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.

    • The --safe-show-database server option.

    • The --skip-symlink and --use-symbolic-links server options (use --skip-symbolic-links and --symbolic-links).

    • The --sql-bin-update-same server option.

    • The --warnings server option (use --log-warnings).

    • The --no-named-commands option for mysql (use --skip-named-commands

    • The --no-pager option for mysql (use --skip-pager).

    • The --no-tee option for mysql (use --skip-tee).

    • The --position option for mysqlbinlog (use --start-position).

    • The --all option for mysqldump (use --create-options).

    • The --first-slave option for mysqldump (use --lock-all-tables).

    • The --config-file option for mysqld_multi (use --defaults-extra-file).

    • The --set-variable=var_name=value and -O var_name=value general-purpose options for setting program variables (use --var_name=value).

    (Bug#48048)

    See also Bug#47974, Bug#56408.

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

  • Incompatible Change: Implicit conversion of a number or temporal value to string now produces a value that has a character set and collation determined by the character_set_connection and collation_connection system variables. (These variables commonly are set with SET NAMES. For information about connection character sets, see Section 9.1.4, “Connection Character Sets and Collations”.)

    This means that such a conversion results in a character (nonbinary) string (a CHAR, VARCHAR, or LONGTEXT value), except in the case that the connection character set is set to binary. In that case, the conversion result is a binary string (a BINARY, VARBINARY, or LONGBLOB value).

    Previously, an implicit conversion always produced a binary string, regardless of the connection character set. Such implicit conversions to string typically occur for functions that are passed numeric or temporal values when string values are more usual, and thus could have effects beyond the type of the converted value. Consider the expression CONCAT(1, 'abc'). The numeric argument 1 was converted to the binary string '1' and the concatenation of that value with the nonbinary string 'abc' produced the binary string '1abc'.

    This change in conversion behavior affects several functions that expect string arguments because a numeric or temporal argument converted to a string now results in a character rather than binary string argument:

    These functions remain unaffected:

    • CHAR() without a USING clause still returns VARBINARY.

    • Functions that previously returned utf8 strings still do so. Examples include CHARSET() and COLLATION().

    Encryption and compression functions that expect string arguments and previously returned binary strings are affected depending on the content of the return value:

  • Incompatible Change: Several changes were made to processing of server system variables and command-line options to make their treatment more consistent.

    General changes:

    • The help message text displayed by mysqld --verbose --help now consistently uses dashes to show the names of options and system variables that can be set at server startup. Previously, the message used both dashes and underscores (generally with dashes for options and underscores for system variables). For example, the help message now displays --log-output and --general-log, whereas previously it displayed --log-output and --general_log.

      This is a display-only change. The permissible syntax for setting options and variables remains unchanged:

      • At server startup, you can specify options and variables on the command line or in option files using either dashes or underscores.

      • For those system variables that can be set at runtime (for example, using SET), you must specify them using underscores.

    • There are fewer session-only system variables. These variables now have a global value: autocommit, foreign_key_checks, profiling, sql_auto_is_null, sql_big_selects, sql_buffer_result, sql_log_bin, sql_log_off, sql_notes, sql_quote_show_create, sql_safe_updates, sql_warnings, unique_checks.

      For those variables, you can now set the global value to change the value from which the session value is initialized for new sessions.

      The following list shows the variables that remain session-only. They apply only in the context of a specific session so that a global value is of no use: debug_sync, error_count, identity, insert_id, last_insert_id, pseudo_thread_id, rand_seed1, rand_seed2, timestamp, warning_count.

    • All system variables are accessible at runtime using @@ syntax (@@GLOBAL.var_name, @@SESSION.var_name, @@var_name). Previously, this syntax produced an error for some variables.

    • All system variables are included as appropriate in the output from SHOW {GLOBAL, SESSION} VARIABLES and the INFORMATION_SCHEMA.GLOBAL_VARIABLES and INFORMATION_SCHEMA.SESSION_VARIABLES tables. Previously, some variables were not displayed.

    • As appropriate” in the preceding item means that SHOW GLOBAL VARIABLES and INFORMATION_SCHEMA.GLOBAL_VARIABLES no longer include session-only system variables. Previously, these included the global value of a variable if it had one, and the session value if not. (SHOW SESSION VARIABLES still includes global-only variables.)

    • The server now enforces type checking for assignments to system variables, so it is more consistent and strict about rejecting invalid values.

    • For attempts to assign a negative value to an unsigned system variable, the server truncates the value to the minimum permitted value. Previously, there was sometimes wraparound to a large positive value.

    • Some system variables (typically those that control memory or disk allocation) are permitted to take only values that are a multiple of a given block size, and assigning a value not a block size multiple causes truncation to the nearest multiple. (For example, net_buffer_length must be a multiple of 1024. Assigning 16384 results in a value of 16384, whereas assigning 16383 results in a value of 15360.) A warning now occurs when adjustment of the specified value takes place. Previously, adjustment was silent.

    • More system variables can be assigned the value DEFAULT to set them to their default value. Previously, this syntax produced an error in some cases.

    • All variables that have a SET data type value can be set to an integer value that is treated like a bit mask. Previously, this did not work for some SET-type variables.

    • The default value for several system variables no longer differs between 32-bit and 64-bit builds. Previously, the values differed by about 100 bytes for some variables.

    • There are no longer any write-only system variables. For example, SELECT @@rand_seed1 returns 0, not Variable 'rand_seed1' can only be set, not read.

    Variable-specific changes:

    See also Bug#34437, Bug#34635.

  • Incompatible Change: FLUSH TABLES has a new variant, FLUSH TABLES tbl_list WITH READ LOCK. This variant enables tables to be flushed and locked in a single operation. It provides a workaround for the restriction (due to work done for Bug#989) that FLUSH TABLES is not permitted when there is an active LOCK TABLES ... READ.

    See also Bug#42465.

  • 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 better 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, “Type Conversion in Expression Evaluation”.

    See also Bug#12860, Bug#21497, Bug#26788, Bug#24541, Bug#34015.

  • 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 utf8mb4 character set has been added. This is similar to utf8, 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 to MySQL 5.5 should present few problems with regard to Unicode usage, although there are some potential areas of incompatibility. These are the primary areas of concern:

    • For the variable-length character data types (VARCHAR and the TEXT types), the maximum length in characters is less for utf8mb4 columns than for utf8 columns.

    • For all character data types (CHAR, VARCHAR, and the TEXT types), the maximum number of characters that can be indexed is less for utf8mb4 columns than for utf8 columns.

    Consequently, if you want to upgrade tables from utf8 to utf8mb4 to take advantage of supplementary-character support, 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.10, “Unicode Support”, and Section 9.1.11, “Upgrading from Previous to Current Unicode Support”.

  • Incompatible Change: Several columns were added to the INFORMATION_SCHEMA.ROUTINES table to provide information about the RETURNS clause data type for stored functions: DATA_TYPE, CHARACTER_MAXIMUM_LENGTH, CHARACTER_OCTET_LENGTH, NUMERIC_PRECISION, NUMERIC_SCALE, CHARACTER_SET_NAME, and COLLATION_NAME.

    This change produces an incompatibility for applications that depend on column order in the ROUTINES table because the new columns appear between the ROUTINE_TYPE and DTD_IDENTIFIER columns. Such applications may need to be adjusted to account for the new columns.

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

  • Important Change: The --skip-thread-priority option is now deprecated 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)

  • Cluster Replication: Replication: MySQL Replication now supports attribute promotion and demotion for row-based replication between columns of different but similar types on the master and the slave. For example, it is possible to promote an INT column on the master to a BIGINT column on the slave, and to demote a TEXT column to a VARCHAR column.

    The implementation of type demotion distinguishes between lossy and non-lossy type conversions, and their use on the slave can be controlled by setting the slave_type_conversions global server system variable.

    For more information, see Row-based replication: attribute promotion and demotion. (Bug#47163, Bug#46584)

  • Replication: For replication based on row-based and mix-format binary logging, it is now safe to mix transactional and nontransactional statements within a transaction. The nontransactional statements are logged immediately rather than waiting until the transaction ends, ensuring that their results are logged and replicated correctly regardless of the result of the transaction.

  • mysqltest has a new --max-connections option to set a higher number of maximum permitted server connections than the default 128. This option can also be passed using mysql-test-run.pl. (Bug#51135)

  • mysql-test-run.pl has a new --portbase option and a corresponding MTR_PORT_BASE environment variable for setting the port range, as an alternative to the existing --build-thread option. (Bug#50182)

  • SHOW PROFILE CPU has been ported to Windows. Thanks to Alex Budovski for the patch. (Bug#50057)

  • mysql-test-run.pl has a new --gprof option that runs the server through the gprof profiler, much the same way the currently supported --gcov option runs it through gcov. (Bug#49345)

  • mysqltest has a new lowercase_result command that converts the output of the next statement to lowercase. This is useful for test cases where the lettercase may vary between platforms. (Bug#48863)

  • mysqltest has a new remove_files_wildcard command that removes files matching a pattern from a directory. (Bug#39774)

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

  • 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 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 not permitted in subqueries (including subqueries in the FROM clause, and SELECT statements in unions other than the first SELECT. (Bug#35020)

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

  • TRUNCATE TABLE now is permitted for a table for which a WRITE lock has been acquired with LOCK TABLES. (Bug#20667)

    See also Bug#46452.

  • FLUSH LOGS now takes an optional log_type value so that FLUSH log_type LOGS can be used to flush only a specified log type. These log_type options are permitted:

    • BINARY closes and reopens the binary log files.

    • ENGINE closes and reopens any flushable logs for installed storage engines.

    • ERROR closes and reopens the error log file.

    • GENERAL closes and reopens the general query log file.

    • RELAY closes and reopens the relay log files.

    • SLOW closes and reopens the slow query log file.

    Thanks to Eric Bergen for the patch to implement this feature. (Bug#14104)

  • Previously, prepared CALL statements could be used through 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 using 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 21.9.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 IPv6 connections to the local host, using the address ::1. For example:

    shell> mysql -h ::1
    

    The address ::1 can be specified in account names in statements such as CREATE USER, GRANT, and REVOKE. For example:

    mysql> CREATE USER 'bill'@'::1' IDENTIFIED BY 'secret';
    mysql> GRANT SELECT ON mydb.* TO 'bill'@'::1';
    

    The default set of accounts created during MySQL installation now includes an account for 'root'@'::1'.

    See Section 5.4.3, “Specifying Account Names”, and Section 2.12.2, “Securing the Initial MySQL Accounts”. (Bug#8836)

  • Three options were added to mysqldump make it easier to generate a dump from a slave server:

    (Bug#8368)

  • mysqladmin now permits the password value to be omitted following the password command. In this case, mysqladmin prompts for the password value, which enables you to avoid specifying the password on the command line. Omitting the password value should be done only if password is the final command on the mysqladmin command line. Otherwise, the next argument is taken as the password. (Bug#5724)

  • The optimizer_switch system variable has a new engine_condition_pushdown flag to control whether storage engine condition pushdown optimization is used. The engine_condition_pushdown system variable now is deprecated.

  • The server now provides a pluggable audit interface that enables information about server operations to be reported to interested parties. Audit plugins may register with the audit interface to receive notification about server operations. When an auditable event occurs within the server, the server determines whether notification is needed. For each registered audit plugin, the server checks the event against those event classes in which the plugin is interested and passes the event to the plugin if there is a match. For more information, see Section 22.2.3.3, “Audit Plugins”.

  • Some conversions between Japanese character sets are more efficient.

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

  • The TABLESPACES table has been added to INFORMATION_SCHEMA for tracking tablespace details.

  • Added the PARAMETERS table to INFORMATION_SCHEMA. The PARAMETERS table provides information about stored procedure and function parameters, and about return values for stored functions.

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

Bugs fixed:

  • Performance: Replication: When writing events to the binary log, transactional events (that is, events that operate on transactional tables) are written to a thread-specific transaction cache, which is then written to the binary log on commit. To handle nontransactional events, there was a lock taken on the binary log (when entering the function MYSQL_BIN_LOG::write()), even when the event was written to the transaction cache instead of the binary log, causing a major bottleneck in replication performance. (Bug#42757)

  • Security Fix: The server crashed if an account with the CREATE ROUTINE privilege but not the EXECUTE privilege attempted to create a stored procedure. (Bug#44798)

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

  • Incompatible Change: Replication: The --binlog_format system variable can no longer be set inside a transaction. In other words, the binary logging format can no longer be changed while a transaction is in progress. (Bug#47863)

  • Incompatible Change: For debug builds, wttempts to execute RESET statements within a transaction that had acquired metadata locks led to an assertion failure.

    As a result of this bug fix, RESET statements now cause an implicit commit. (Bug#51336)

  • Incompatible Change: A deadlock occurred for this sequence of events: Session 1 locked a table using LOCK TABLES; Session 2 dropped the database containing the table; Session 1 created any database.

    A consequence of this bug fix is that CREATE DATABASE is not permitted within a session that has an active LOCK TABLES statement. (Bug#49988)

  • Incompatible Change: For application compatibility reasons, when sql_auto_is_null is 1, MySQL converts auto_inc_col IS NULL to auto_inc_col = LAST_INSERT_ID(). However, this was being done regardless of whether the predicate was alone or at the top level. Now it occurs only when it is a single top-level predicate.

    In conjunction with this bug fix, the default value of the sql_auto_is_null system variable has been changed from 1 to 0, which may cause incompatibilities with existing applications. (Bug#41371)

  • 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: The parser accepted an INTO clause in nested SELECT statements, which is invalid because such statements must return their results to the outer context. This syntax is no longer permitted. (Bug#33204)

  • Incompatible Change: The Locked thread state was equivalent to the Table lock state and has been removed. It no longer appears in SHOW PROCESSLIST output. (Bug#28870)

  • Incompatible Change: Several changes were made to alias resolution in multiple-table DELETE statements so that it is no longer possible to have inconsistent or ambiguous table aliases.

    • In MySQL 5.1.23, alias declarations outside the table_references part of the statement were disallowed for the USING variant of multiple-table DELETE syntax, to reduce the possibility of ambiguous aliases that could lead to ambiguous statements that have unexpected results such as deleting rows from the wrong table.

      Now alias declarations outside table_references are disallowed for all multiple-table DELETE statements. Alias declarations are permitted only in the table_references part.

      Incorrect:

      DELETE FROM t1 AS a2 USING t1 AS a1 INNER JOIN t2 AS a2;
      DELETE t1 AS a2 FROM t1 AS a1 INNER JOIN t2 AS a2;
      

      Correct:

      DELETE FROM t1 USING t1 AS a1 INNER JOIN t2 AS a2;
      DELETE t1 FROM t1 AS a1 INNER JOIN t2 AS a2;
      
    • Previously, for alias references in the list of tables from which to delete rows in a multiple-table delete, the default database is used unless one is specified explicitly. For example, if the default database is db1, the following statement does not work because the unqualified alias reference a2 is interpreted as having a database of db1:

      DELETE a1, a2 FROM db1.t1 AS a1 INNER JOIN db2.t2 AS a2
      WHERE a1.id=a2.id;
      

      To correctly match an alias that refers to a table outside the default database, you must explicitly qualify the reference with the name of the proper database:

      DELETE a1, db2.a2 FROM db1.t1 AS a1 INNER JOIN db2.t2 AS a2
      WHERE a1.id=a2.id;
      

      Now alias resolution does not require qualification and alias references should not be qualified with the database name. Qualified names are interpreted as referring to tables, not aliases.

    Statements containing alias constructs that are no longer permitted must be rewritten. (Bug#27525)

    See also Bug#30234.

  • Incompatible Change: DROP TABLE now is permitted 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: 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:

    (Bug#989, Bug#39675)

  • Important Change: Replication: For an engine that supported only row-based replication, replication stopped with an error when executing row events.

    For information about changes in how the binary logging format is determined in relation to statement type and storage engine logging capabilities, see Section 5.2.4.3, “Mixed Binary Logging Format”.

    As part of the fix for this issue, the EXAMPLE storage engine is now changed so that it supports statement-based logging only. Previously, it supported row-based logging only. (Bug#39934)

  • Important Change: The IPv6 loopback address ::1 was interpeted as a hostname rather than a numeric IP address.

    In addition, the IPv6-enabled server on Windows interpeted the hostname localhost as ::1 only, which failed to match the default 'root'@'127.0.0.1' account in the mysql.user privilege table.

    Note

    As a result of this fix, a 'root'@'::1' account is added to the mysql.user table as one of the default accounts created during MySQL installation.

    (Bug#43006)

    See also Bug#38247, Bug#45283, Bug#45584, Bug#45606.

  • InnoDB Storage Engine: Replication: Column length information generated by InnoDB did not match that generated by MyISAM, which caused invalid metadata to be written to the binary log when trying to replicate BIT columns. (Bug#49618)

  • InnoDB Storage Engine: SHOW INNODB STATUS could display incorrect information about deadlocks, when the deadlock detection routine stops early (to avoid excessive CPU usage). (Bug#49001)

  • InnoDB Storage Engine: Concurrent execution of ALTER TABLE for InnoDB table and a transaction that tried to read and then update the table could result in a deadlock between table-level locks and InnoDB row locks, which was detected only after the innodb_lock_wait_timeout timeout occurred. (Bug#37346)

  • Partitioning: When using a debug build of MySQL, if a query against a partitioned table having an index on one or more DOUBLE columns used that index, the server failed with an assertion. (Bug#45816)

  • Partitioning: The first time that a query against the INFORMATION_SCHEMA.TABLES table for partitioned tables using the ARCHIVE engine was run, it returned invalid data. If the server had been restarted since such a table had been created, or if the table had never actually been opened, its DATA_LENGTH was reported as 0 bytes. (The second and subsequent attempts to issue the same query returned the expected result.) (Bug#44622)

  • Partitioning: ALTER TABLE on a partitioned table caused unnecessary deadlocks. (Bug#43867)

    See also Bug#46654.

  • Partitioning: Attempting to drop a partitioned table from one connection while waiting for the completion of an ALTER TABLE that had been issued from a different connection, and that changed the storage engine used by the table, could cause the server to crash. (Bug#42438)

  • Partitioning: After attempting to create a duplicate index on a partitioned table (and having the attempt fail as expected), a subsequent attempt to create a new index on the table caused the server to hang. (Bug#40181)

  • Partitioning: When used on a partitioned table, ALTER TABLE produced the wrong error message when the name of a nonexistent storage engine was used in the ENGINE clause. (Bug#35765)

  • 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: Portions of the partitioning code were refactored in response to potential regression issues uncovered while working on the fix for Bug#31210. (Bug#32115)

    See also Bug#40281.

  • Replication: When using the row-based or mixed replication format with a debug build of the MySQL server, inserts into columns using the UTF32 character set on the master caused the slave to crash. (Bug#51787)

    See also Bug#51716.

  • Replication: When using the row-based or mixed replication format, column values using the UTF16 character set on the master were padded incorrectly on the slave. (Bug#51716)

    See also Bug#51787.

  • Replication: An issue internal to the code, first seen in Bug#49132 but not completely resolved in the fix for that bug, was removed. This should prevent similar issues to those in the previous bug with binlog_format changes following DDL statements.

    For developers working with the MySQL Server code: the public class variable THD::current_stmt_binlog_row_based was supposed to have been removed as part of the fix for Bug#39934, but was still present in the code. If a developer later tried to use this variable, it could cause the previous issues to re-occur, and possibly new ones to arise. The variable has now been removed; the previously added class functions THD::is_current_stmt_binlog_format_row(), THD::set_current_stmt_binlog_format_row(), and THD::clear_current_stmt_binlog_format_row() should be used instead. (Bug#51021)

  • Replication: Adding an index to a table on the master caused the slave to stop logging slow queries to the slow query log. (Bug#50620)

  • Replication: If a CHANGE MASTER TO statement set MASTER_HEARTBEAT_PERIOD to 30 or higher, Slave_received_heartbeats did not increase on the slave. This caused the slave to reconnect before the time indicated by slave_net_timeout had elapsed.

    This issue affected big-endian 64-bit platforms such as Solaris/SPARC. (Bug#50296)

  • Replication: The error message given when trying to replicate (using statement-based mode) insertions into an AUTO_INCREMENT column by a stored function or a trigger was improved. (Bug#50192)

  • Replication: The server could deadlock when FLUSH LOGS was executed concurrently with DML statements. To fix this problem, nontransactional changes are now always flushed before transactional changes. (Bug#50038)

  • Replication: Metadata for GEOMETRY fields was not properly stored by the slave in its definitions of tables. (Bug#49836)

    See also Bug#48776.

  • Replication: Statement-based replication of user variables having numeric data types did not always work correctly. (Bug#49562)

  • Replication: When using the semi-synchronous replication plugin on Windows, the wait time calculated when the master was waiting for reply from the slave was incorrect. In addition, when the wait time was less than the current time, the master did not wait for a reply at all.

    This issue was caused by the fact that a different internal function was used to get current time by the plugin on Windows as opposed to other platforms, and this function was not correctly implemented. Now the Windows version of the plugin uses the same function as other platforms for this purpose. (Bug#49557)

  • Replication: Due to a change in the format of the information used by the slave to connect to the master, which could cause to reject connection attempts to older masters by newer slaves. (Bug#49259)

    This regression was introduced by Bug#13963.

  • Replication: When using row-based logging, a failing INSERT...SELECT statement on a nontransactional table was not flagged correctly, such that, if a rollback was requested and no other nontransactional table had been updated, nothing was written to the binary log. (Bug#47175)

    See also Bug#40278.

  • Replication: When using row-based replication, the incomplete logging of a group of events involving both transaction and nontransactional tables could cause STOP SLAVE to hang. (Bug#45940)

    See also Bug#319, Bug#38205.

  • Replication: There were two related issues concerning handling of unsafe statements and setting of the binary logging format when there were open temporary tables on the master, and the existing replication format was row-based or mixed:

    1. When using binlog_format=ROW, and an unsafe statement was executed while there were open temporary tables on the master, the statement SET @@session.binlog_format = MIXED failed with the error Cannot switch out of the row-based binary log format when the session has open temporary tables.

    2. When using binlog_format=MIXED, and an unsafe statement was executed while there were open temporary tables on the master, the statement SET @@session.binlog_format = STATEMENT caused any subsequent DML statements to be written to the binary log using the row-based format instead of the statement-based format.

    (Bug#45855, Bug#45856)

  • Replication: Statements that updated AUTO_INCREMENT columns in multiple tables were logged using the row-based format when --binlog_format was set to MIXED, but did not cause an Unsafe statement warning to be generated when --binlog_format was set to STATEMENT. (Bug#45827)

    See also Bug#39934.

  • Replication: Even though INSERT DELAYED statements are unsafe for statement-based replication, they caused the statement only to be logged in row format when the binary logging format was MIXED, but did not cause a warning to be generated when the binary logging format was STATEMENT. (Bug#45825)

  • Replication: When using MIXED binary logging format, statements containing a LIMIT clause and occurring in stored routines were not written to the log as row events. (Bug#45785)

  • Replication: When using statement-based replication, database-level character sets were not always honored by the replication SQL thread. This could cause data inserted on the master using LOAD DATA to be replicated using the wrong character set.

    Note

    This was not an issue when using row-based replication.

    (Bug#45516)

  • Replication: STOP SLAVE did not flush the relay log or the master.info or relay-log.info files, which could lead to corruption if the server crashed. (Bug#44188)

  • Replication: Large transactions and statements could corrupt the binary log if the size of the cache (as set by max_binlog_cache_size) was not large enough to store the changes.

    Now, for transactions that do not fit into the cache, the statement is not logged, and the statement generates an error instead.

    For nontransactional changes that do not fit into the cache, the statement is also not logged—an incident event is logged after committing or rolling back any pending transaction, and the statement then raises an error.

    Note

    If a failure occurs before the incident event is written the binary log, the slave does not stop, and the master does not report any errors.

    (Bug#43929)

    See also Bug#37148.

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

  • 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 no longer permitted, 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: 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: A slave compiled using --with-libevent and run with --thread-handling=pool-of-threads could sometimes crash. (Bug#36929)

  • 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: A CHANGE MASTER TO statement with no MASTER_HEARTBEAT_PERIOD option failed to reset the heartbeat period to its default value. (Bug#34686)

  • Replication: As part of the fix for this issue, the Rpl_recovery_rank column, which had appeared in the output of SHOW SLAVE HOSTS in some MySQL releases, was removed because the corresponding server variable rpl_recovery_rank (now deprecated) was never actually used. (Bug#13963)

    See also Bug#21132, Bug#21869.

  • mysqld_safe did not pass the correct default value of plugin_dir to mysqld. (Bug#51938)

  • mysqld_multi failed due to a syntax error in the script. (Bug#51468)

  • ALTER TABLE on a MERGE table that has been locked using LOCK TABLES ... WRITE incorrectly produced an ER_TABLE_NOT_LOCKED_FOR_WRITE error. (Bug#51240)

  • The mysql could default to the ascii character set, which is not a valid character set choice for MySQL. The latin1 character set will now be used when an ASCII environment has been identified. (Bug#51166)

  • On some Unix/Linux platforms, an error during build from source could be produced, referring to a missing LT_INIT program. This is due to versions of libtool 2.1 and earlier. (Bug#51009)

  • Referring to a subquery result in a HAVING clause could produce incorrect results. (Bug#50995)

  • Use of filesort plus the join cache normally is preferred to a full index scan. But it was used even if the index is clustered, in which case, the clustered index scan can be faster. (Bug#50843)

  • For debug builds, SHOW BINARY LOGS caused an assertion to be raised if binary logging was not enabled. (Bug#50780)

  • The server did not recognize that the stored procedure cache became invalid if a view was created or modified within a procedure, resulting in a crash. (Bug#50624)

  • Incorrect handling of BIT columns in temporary tables could lead to spurious duplicate-key errors. (Bug#50591)

  • The second or subsequent invocation of a stored procedure containing DROP TRIGGER could cause a server crash. (Bug#50423)

  • The return value for calls to put information into the stored routine cache were not consistently checked, causing an assertion to be raised. (Bug#50412)

  • Full-text queries that used the truncation operator (*) could enter an infinite loop. (Bug#50351)

  • For debug builds, an assertion was incorrectly raised in the optimizer when matching ORDER BY expressions. (Bug#50335)

  • Queries optimized with GROUP_MIN_MAX did not clean up KEYREAD optimizations properly, causing subsequent queries to return incomplete rows. (Bug#49902)

  • mysql --show-warnings crashed if the server connection was lost. (Bug#49646)

  • For string-valued system variables containing multibyte characters, the byte length was used in contexts where the character length was more appropriate. (Bug#49645)

  • SHOW VARIABLES did not correctly display string-valued system variables that contained \0 characters. (Bug#49644)

  • MySQL program option-processing code incorrectly displayed some options when printing ambiguous-option errors. (Bug#49640)

  • For dynamic format MyISAM tables containing LONGTEXT columns, a bulk INSERT ... ON DUPLICATE KEY UPDATE or bulk REPLACE could cause corruption. (Bug#49628)

  • Setting binlog_format to DEFAULT assigned a value different from the default. (Bug#49540)

  • For debug builds, with sql_safe_updates enabled, a multiple-table UPDATE with the IGNORE modifier could raise an assertion. (Bug#49534)

  • EXPLAIN EXTENDED crashed trying to print column names for a subquery in the FROM clause when the table had gone out of scope. (Bug#49487)

  • For InnoDB tables, the test for using an index for ORDER BY sorting did not distinguish between primary keys and secondary indexes and expected primary key values to be concatenated to index values the way they are to secondary key values. (Bug#49324)

  • mysqltest no longer lets you execute an SQL statement on a connection after doing a send command, unless you do a reap first. This was previously accepted but could produce unpredictable results. (Bug#49269)

  • Valgrind warnings for several logging messages were corrected. (Bug#49130)

  • For debug builds on Windows, warnings about incorrect use of debugging directives were written to the error log. The directives were rewritten to eliminate these messages. (Bug#49025)

  • Plugins in a binary release could not be installed into a debug version of the server. (Bug#49022)

  • On POSIX systems, calls to select() with a file descriptor set larger than FD_SETSIZE resulted in unpredictable I/O errors; for example, when a large number of tables required repair. (Bug#48929)

  • A dependent subquery containing COUNT(DISTINCT col_name)) could be evaluated incorrectly. (Bug#48920)

  • If a stored function contained a RETURN statement with an ENUM value in the ucs2 character set, SHOW CREATE FUNCTION and SELECT DTD_IDENTIFIER FROM INFORMATION_SCHEMA.ROUTINES returned incorrect values. (Bug#48766)

  • An ARZ file missing from the database directory caused the server to crash. (Bug#48757)

  • Running SHOW CREATE TABLE on a view v1 that contained a function which accessed another view v2 could trigger a infinite loop if the view (v2) referenced within the function caused a warning to be raised while being opened. (Bug#48449)

  • Invalid memory reads could occur following a query that referenced a MyISAM tale multiple times with a write lock. (Bug#48438)

  • For debug builds, creating a view containing a row constructor caused an assertion to be raised. (Bug#48294)

  • An aliasing violation in the C API could lead to a crash. (Bug#48284)

  • Slow CALL statements were not always logged to the slow query log because execution time for multiple-statement stored procedures was assessed incorrectly. (Bug#47905)

  • For debug builds, killing a SELECT retrieving from a view that was processing a function caused an assertion to be raised. (Bug#47736)

  • Failure to open a view with a nonexistent DEFINER was improperly handled and the server would crash later attempting to lock the view. (Bug#47734)

  • If a prepared statement used both a MERGE table and a stored function or trigger, execution sometimes failed with a No such table error. (Bug#47648)

  • CREATE VIEW raised an assertion if a temporary table existed with the same name as the view. (Bug#47635)

  • If a temporary table was created with the same name as a view referenced in a stored routine, routine execution could raise an assertion. (Bug#47313)

  • Selecting from the process list in the embedded server caused a crash. (Bug#47304)

    See also Bug#43733.

  • Programs did not exit if the option file specfied by --defaults-file was not found. (Bug#47216)

  • Attempts to print octal numbers with my_vsnprintf() could cause a crash. (Bug#47212)

  • Corrected a potential problem of unintended overwriting of files when the MY_DONT_OVERWRITE_FILE flag was used. (Bug#47126)

  • Deadlock occurred if one session was running a multiple-statement transaction that involved a single partitioned table and another session attempted to alter the table. (Bug#46654)

  • Valgrind warnings about memory allocation overruns for handling CREATE FUNCTION statements for UDFs were corrected. (Bug#46570)

  • The server could crash attempting to flush privileges after receipt of a SIGHUP signal. (Bug#46495)

  • If INSERT INTO tbl_name invoked a stored function that modified tbl_name, the server crashed. (Bug#46374)

  • For queries that used GROUP_CONCAT(DISTINCT ...), the value of max_heap_table_size was used for memory allocation, which could be excessive. Now the minimum of max_heap_table_size and tmp_table_size is used. (Bug#46018)

  • Improperly closing tables when INSERT DELAYED needed to reopen tables could cause an assertion failure. (Bug#45949)

    See also Bug#18484.

  • Grouping by a subquery in a query with a DISTINCT aggregate function led to incorrect and unordered grouping values. (Bug#45640)

  • For an IPv6-enabled MySQL server, privileges specified using standard IPv4 addresses for hosts were not matched (only IPv4-mapped addresses were handled correctly).

    As part of the fix for this bug, a new build option --disable-ipv6 has been introduced. Compiling MySQL with this option causes all IPv6-specific code in the server to be ignored.

    Important

    If the server has been compiled using --disable-ipv6, it is not able to resolve hostnames correctly when run in an IPv6 environment.

    (Bug#45606)

    See also Bug#38247, Bug#43006, Bug#45283, Bug#45584.

  • The hostname cache failed to work correctly. (Bug#45584)

    See also Bug#38247, Bug#43006, Bug#45283, Bug#45606.

  • A Windows Installation using the GUI installer would fail with:

    MySQL Server 5.1 Setup Wizard ended prematurely
    
    The wizard was interrupted before MySQL Server 5.1. could be completely installed.
    
    Your system has not been modified. To complete installation at another time, please run
    setup again.
    
    Click Finish to exit the wizard

    This was due to an step in the MSI installer that could fail to execute correctly on some environments. (Bug#45418)

  • Propagation of a large unsigned numeric constant in WHERE expressions could lead to incorrect results. This also affected EXPLAIN EXTENDED, which printed incorrect numeric constants in such transformed WHERE expressions. (Bug#45360)

  • There was no timeout for attempts to acquire metadata locks (for example, a DROP TABLE attempt for a table that was open in another transaction would not time out).

    To handle such situations, there is now a lock_wait_timeout system variable that specifies the timeout in seconds for attempts to acquire metadata locks. The permitted values range from 1 to 3153600 (1 year). The default is 3153600.

    This timeout applies to all statements that use metadata locks. These include DML and DDL operations on tables, views, stored procedures, and stored functions, as well as LOCK TABLES, FLUSH TABLES WITH READ LOCK, and HANDLER statements.

    The timeout value applies separately for each metadata lock attempt. A given statement can require more than one lock, so it is possible for the statement to block for longer than the lock_wait_timeout value before reporting a timeout error. When lock timeout occurs, ER_LOCK_WAIT_TIMEOUT is reported.

    lock_wait_timeout does not apply to delayed inserts, which always execute with a timeout of 1 year. This is done to avoid unnecessary timeouts because a session that issues a delayed insert receives no notification of delayed insert timeouts.

    In addition, the unused table_lock_wait_timeout system variable was removed. (Bug#45225)

  • Valgrind warnings about uninitialized variables in optimizer code were corrected. (Bug#45195)

  • Killing a delayed-insert thread could cause a server crash. (Bug#45067)

  • Execution of FLUSH TABLES or FLUSH TABLES WITH READ LOCK concurrently with LOCK TABLES resulted in deadlock. (Bug#45066)

  • The mysql_real_connect() C API function only attempted to connect to the first IP address returned for a hostname. This could be a problem if a hostname mapped to multiple IP address and the server was not bound to the first one returned. Now mysql_real_connect() attempts to connect to all IPv4 or IPv6 addresses that a domain name maps to. (Bug#45017)

    See also Bug#47757.

  • For plugins that did not have command-line options other than the ones to select the plugin itself, those options were not displayed in the mysqld help message. (Bug#44797)

  • Some plugins configured as mandatory could be disabled at server startup. (Bug#44691)

  • InnoDB took a shared row lock when executing SELECT statements inside a stored function as a part of a transaction using REPEATABLE READ. This prevented other transactions from updating the row. (Bug#44613)

  • MySQL Server permitted 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))
    ENGINE=MERGE UNION(v1, v2);
    
    #Reading from the merge table lead to a crash
    SELECT * FROM merge;

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

  • A natural join of INFORMATION_SCHEMA tables could cause an assertion failure. (Bug#43834)

  • When used in conjunction with LOCK TABLES, FLUSH TABLE tbl_list waited for all tables with old versions to clear from the table definition list, rather than only the named tables. (Bug#43685)

  • HANDLER statements are now not permitted if a table lock has been acquired with LOCK TABLES. (Bug#43272)

  • In the embedded server, stack overflow checks for recursive stored procedure calls did not work and stack overflow could occur. (Bug#43201)

  • The server could crash if an attempt to open a MERGE table child MyISAM table failed. (Bug#42862)

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

  • Due to work done for Bug#989, FLUSH TABLES is not permitted when there is an active LOCK TABLES ... READ. This caused a problem with mysqlhotcopy, which used that sequence of statements. mysqlhotcopy now uses FLUSH TABLES tbl_list WITH READ LOCK to flush and lock tables. If mysqlhotcopy is used with a server older than MySQL 5.5.3 that does not support this statement, it has a new option --old_server that causes it to use the previous statement sequence. (Bug#42465)

  • Setting key_buffer_size to a negative value could lead to very large allocations. Now an error occurs. (Bug#42103)

  • An assertion failure could occur if OPTIMIZE TABLE was started on an InnoDB table and the table was altered to a different storage engine during the optimization operation. (Bug#42074)

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

  • The patch for Bug#10374 broke named-pipe and shared-memory connections on Windows. (Bug#41860)

  • Purging the stored routine cache could take a long time and render the server unresponsive. (Bug#41804)

  • Command-line options for enumeration-type plugin variables were not honored. (Bug#41010)

  • System variables could be set to invalid values. (Bug#40988)

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

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

  • mysqld_safe did not treat dashes and underscores as equivalent in option names. Thanks to Erik Ljungstrom for the patch to fix this bug. (Bug#40368)

  • SHOW CREATE VIEW returned invalid SQL if the definition contained a SELECT 'string' statement where the string was longer than the maximum length of a column name, due to the fact that this text was also used as an alias (in the AS clause).

    Because not all names retrieved from arbitrary SELECT statements can be used as view column names due to length and format restrictions, the server now checks the conformity of automatically generated column names and rewrites according to a predefined format any names that are not acceptable as view column names before storing the final view definition on disk.

    In such cases, the name is now rewritten as Name_exp_pos, where pos is the position of the column. To avoid this conversion scheme, define explicit, valid names for view columns using the column_list clause of the CREATE VIEW statement.

    As part of this fix, aliases are now generated only for top-level statements. (Bug#40277)

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

  • Plugin shutdown could lead to an assertion failure caused by using an already destroyed mutex in the metadata locking subsystem. (Bug#39674)

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

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

  • flush_cache_records() did not correctly check for errors that should cause statement execution to stop, leading to a server crash. (Bug#39022)

  • InnoDB logged an error repeatedly trying to load a page into the buffer pool, filling the error log and using excessive disk space. Now the number of attempts is limited to 100, after which the operation aborts with a message. (Bug#38901)

  • Valgrind warnings that occurred for SHOW TABLE STATUS with InnoDB tables were silenced. (Bug#38479)

  • An IPv6-enabled MySQL server did not resolve the IP addresses of incoming connections correctly, with the result that a connection that attempted to match any privilege table entries using fully-qualified domain names for hostnames or hostnames using wildcards were dropped. (Bug#38247)

    See also Bug#43006, Bug#45283, Bug#45584, Bug#45606.

  • For CREATE TABLE ... LIKE with a MERGE source table that included a UNION clause, that clause was omitted from the definition of the destination table. (Bug#37371)

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

  • The parser incorrectly permitted 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)

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

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

  • mysql_stmt_prepare() did not reset the list of messages (those messages available using SHOW WARNINGS). (Bug#36004)

  • A global read lock obtained with FLUSH TABLES WITH READ LOCK did not prevent sessions from creating tables. (Bug#35935)

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

  • When building MySQL when using a different target directory (for example using the VPATH environment variable), the build of the embedded readline component would fail. (Bug#35250)

  • String-valued system variables could be assigned literal values, but could not be assigned values using expressions. Now expressions are legal. (Bug#34883, Bug#46314)

  • The sql_mode system variable could be assigned the illegal value of '?'. (Bug#34834)

  • Some system variables could not be assigned the value DEFAULT to assign their default value. (Bug#34829, Bug#34878)

  • Compiling MySQL on FreeBSD would fail due to missing definitions for certain network constants. (Bug#34292)

  • Creation of a temporary BLOB or TEXT column could create a column with the wrong maximum length. (Bug#33969)

  • INSERT INTO ... VALUES(DEFAULT) failed to insert the correct value for ENUM columns. For MyISAM tables, an empty value was inserted. For CSV tables, the table became corrupt. (Bug#33717)

  • When read_only was enabled, the server incorrectly prevented data modifications to TEMPORARY tables belonging to transactional storage engines such as InnoDB. (Bug#33669)

  • Constant expressions in WHERE, HAVING, or ON clauses were not cached, but were evaluated for each row. This caused a slowdown of query execution, especially if constant user-defined functions or stored functions were used. (Bug#33546)

  • Plugins could find the unqualified form of their system variables but not the qualified form. For example, a plugin p with a system variable sv could find sv but not p_sv. (Bug#32902)

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

  • Concurrent statements using a stored function and DROP FUNCTION for that function could break statement-based replication. (Bug#30977)

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

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

  • If an operation had an InnoDB table, and two triggers, AFTER UPDATE and AFTER INSERT, competing for different resources (such as two distinct MyISAM tables), the triggers were unable to execute concurrently. In addition, INSERT and UPDATE statements for the InnoDB table were unable to run concurrently. (Bug#26141)

  • Some system variables displayed by SHOW VARIABLES could not be selected using SELECT @@{GLOBAL,SESSION}.var_name. (Bug#25430)

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

  • Previously, the server handled character data types for a stored routine parameter, local routine variable created with DECLARE, or stored function return value as follows: 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, which in this context specifies the binary collation of the character set.) If there was no CHARACTER SET attribute, the database character set and its default collation were used.

    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)

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

  • A statement that caused a circular wait among statements did not return a deadlock error. Now the server detects deadlock and returns ER_LOCK_DEADLOCK. (Bug#22876)

  • CREATE TABLE ... LIKE did not always produce an error is the source table column defaults were illegal for the current version of MySQL. (This could occur if the table was created using an older server that was less restrictive about legal default values.) (Bug#22090)

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

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

  • The value of sql_slave_skip_counter was empty when displayed by SHOW VARIABLES or INFORMATION_SCHEMA.GLOBAL_VARIABLES. (Bug#20413, Bug#37187)

  • For INSERT DELAYED statements issued for a table while an ALTER TABLE operation on the table was in progress, the server could return a spurious Server shutdown in progress error. (Bug#18484)

    See also Bug#45949.

  • 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 character set was not being properly initialized for CAST() with a type such as CHAR(2) BINARY, which resulted in incorrect results or a server crash. (Bug#17903)

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

  • Zero-padding of exponent values was not the same across platforms. (Bug#12860)

  • 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#11714, Bug#35578, Bug#38696)

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

  • perror did not work for errors described in the sql/share/errmsg.txt file. (Bug#10143)

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

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

  • Labels in stored routines did not work if the character set was not latin1. (Bug#7088)

  • Previously, for some Asian CJK character sets, the UPPER() and LOWER() functions worked only for basic Latin letters (A-Z, a-z). The affected character sets are ujis, sjis, gb2312, cp932, eucjpms, big5, euckr, and gbk.

    Now UPPER() and LOWER() perform case conversion correctly for all characters in these character sets, with the exception that if a character set contains a character in only one lettercase, conversion to the other lettercase cannot be done.

D.1.6. Changes in MySQL 5.5.2 (12 February 2010)

InnoDB Notes:

  • This release includes InnoDB 1.0.6. This version is considered of Release Candidate (RC) quality.

Functionality added or changed:

  • Replication: Introduced the binlog_direct_non_transactional_updates system variable. Enabling this variable causes updates using the statement-based logging format to tables using nontransactional engines to be written directly to the binary log, rather than to the transaction cache.

    Before enabling this variable, be certain that you have no dependencies between transactional and nontransactional tables. A statement that both selects from an InnoDB table and inserts into a MyISAM table is an example of such a dependency. For more information, see Section 16.1.3.4, “Binary Log Options and Variables”. (Bug#46364)

    See also Bug#28976, Bug#40116.

Bugs fixed:

  • Performance: Partitioning: When used on partitioned tables, the records_in_range handler call checked more partitions than necessary. The fix for this issue reduces the number of unpruned partitions checked for statistics in partition range checking, which has resulted in some partition operations being performed up to 2-10 times faster than before this change was made, when testing with tables having 1024 partitions. (Bug#48846)

    See also Bug#37252, Bug#47261.

  • Performance: The method for comparing INFORMATION_SCHEMA names and database names was nonoptimal and an improvement was made: When the database name length is already known, a length check is made first and content comparison skipped if the lengths are unequal. (Bug#49501)

  • Performance: The MD5() and SHA1() functions had excessive overhead for short strings. (Bug#49491)

  • Security Fix: For servers built with yaSSL, a preauthorization buffer overflow could cause memory corruption or a server crash. We thank Evgeny Legerov from Intevydis for providing us with a proof-of-concept script that permitted us to reproduce this bug. (Bug#50227, CVE-2009-4484)

  • Incompatible Change: In plugin.h, the MYSQL_REPLICATION_PLUGIN symbol was out of synchrony with its value in MySQL 6.0 because the lower-valued MYSQL_AUDIT_PLUGIN was not present. To correct this, MYSQL_AUDIT_PLUGIN has been added in MySQL 5.5, changing the value of MYSQL_REPLICATION_PLUGIN from 5 to 6. Attempts to load the audit plugin produce an error occurs because only the MYSQL_AUDIT_PLUGIN symbol was added, not the audit plugin itself. This error will go away when the audit plugin is added to MySQL 5.5 (in 5.5.3). Replication plugins from earlier 5.5.x releases must be recompiled against the current release before they will work with the current release. (Bug#49894)

  • Important Change: Replication: The RAND() function is now marked as unsafe for statement-based replication. Using this function now generates a warning when binlog_format=STATEMENT and causes the format to switch to row-based logging when binlog_format=MIXED.

    This change is being introduced because, when RAND() was logged in statement mode, the seed was also written to the binary log, so the replication slave generated the same sequence of random numbers as was generated on the master. While this could make replication work in some cases, the order of affected rows was still not guaranteed when this function was used in statements that could update multiple rows, such as UPDATE or INSERT ... SELECT; if the master and the slave retrieved rows in different order, they began to diverge. (Bug#49222)

  • Partitioning: InnoDB Storage Engine: When an ALTER TABLE ... REORGANIZE PARTITION statement on an InnoDB table failed due to innodb_lock_wait_timeout expiring while waiting for a lock, InnoDB did not clean up any temporary files or tables which it had created. Attempting to reissue the ALTER TABLE statement following the timeout could lead to storage engine errors, or possibly a crash of the server. (Bug#47343)

  • InnoDB Storage Engine: Creating or dropping a table with 1023 transactions active caused an assertion failure. (Bug#49238)

  • InnoDB Storage Engine: If innodb_force_recovery was set to 4 or higher, the server could crash when opening an InnoDB table containing an auto-increment column. MySQL versions 5.1.31 and later were affected. (Bug#46193)

  • Replication: FLUSH LOGS could in some circumstances crash the server. This occurred because the I/O thread could concurrently access the relay log I/O cache while another thread was performing the FLUSH LOGS, which closes and reopens the relay log and, while doing so, initializes (or re-initializes) its I/O cache. This could cause problems if some other thread (in this case, the I/O thread) is accessing it at the same time.

    Now the thread performing the FLUSH LOGS takes a lock on the relay log before actually flushing it. (Bug#50364)

    See also Bug#53657.

  • Replication: With semisynchronous replication, memory allocated for handling transactions could be freed while still in use, resulting in a server crash. (Bug#50157)

  • Replication: In some cases, inserting into a table with many columns could cause the binary log to become corrupted. (Bug#50018)

    See also Bug#42749.

  • Replication: When using row-based replication, setting a BIT or CHAR column of a MyISAM table to NULL, then trying to delete from the table, caused the slave to fail with the error Can't find record in table. (Bug#49481, Bug#49482)

  • Replication: A LOAD DATA INFILE statement that loaded data into a table having a column name that had to be escaped (such as `key` INT) caused replication to fail when logging in mixed or statement mode. In such cases, the master wrote the LOAD DATA event into the binary log without escaping the column names. (Bug#49479)

    See also Bug#47927.

  • Replication: When logging in row-based mode, DDL statements are actually logged as statements; however, statements that affected temporary tables and followed DDL statements failed to reset the binary log format to ROW, with the result that these statements were logged using the statement-based format. Now the state of binlog_format is restored after a DDL statement has been written to the binary log. (Bug#49132)

  • Replication: Spatial data types caused row-based replication to crash. (Bug#48776)

  • Replication: When using row-based logging, the statement CREATE TABLE t IF NOT EXIST ... SELECT was logged as CREATE TEMPORARY TABLE t IF NOT EXIST ... SELECT when t already existed as a temporary table. This was caused by the fact that the temporary table was opened and the results of the SELECT were inserted into it when a temporary table existed and had the same name.

    Now, when this statement is executed, t is created as a base table, the results of the SELECT are inserted into it—even if there already exists a temporary table having the same name—and the statement is logged correctly. (Bug#47418)

    See also Bug#47442.

  • Replication: Due to a change in the size of event representations in the binary log, when replicating from a MySQL 4.1 master to a slave running MySQL 5.0.60 or later, the START SLAVE UNTIL statement did not function correctly, stopping at the wrong position in the log. Now the slave detects that the master is using the older version of the binary log format, and corrects for the difference in event size, so that the slave stops in the correct position. (Bug#47142)

  • Replication: Manually removing entries from the binary log index file on a replication master could cause the server to repeatedly send the same binary log file to slaves. (Bug#28421)

  • The SSL certificates in the test suite were about to expire. They have been updated with expiration dates in the year 2015. (Bug#50642)

  • SPATIAL indexes were permitted on columns with non-spatial data types, resulting in a server crash for subsequent table inserts. (Bug#50574)

  • Index prefixes could be specified with a length greater than the associated column, resulting in a server crash for subsequent table inserts. (Bug#50542)

  • Use of loose index scan optimization for an aggregate function with DISTINCT (for example, COUNT(DISTINCT)) could produce incorrect results. (Bug#50539)

  • The printstack function does not exist on Solaris 8 or earlier, which would lead to a compilation failure. (Bug#50409)

  • A user could see tables in INFORMATION_SCHEMA.TABLES without appropriate privileges for them. (Bug#50276)

  • Debug output for join structures was garbled. (Bug#50271)

  • The server crashed when an InnoDB background thread attempted to write a message containing a partitioned table name to the error log. (Bug#50201)

  • Within a stored routine, selecting the result of CONCAT_WS() with a routine parameter argument into a user variable could return incorrect results. (Bug#50096)

  • The filesort sorting method applied to a CHAR(0) column could lead to a server crash. (Bug#49897)

  • EXPLAIN EXTENDED UNION ... ORDER BY caused a crash when the ORDER BY referred to a nonconstant or full-text function or a subquery. (Bug#49734)

  • Some prepared statements could raise an assertion when re-executed. (Bug#49570)

  • sql_buffer_result had an effect on non-SELECT statements, contrary to the documentation. (Bug#49552)

  • In some cases a subquery need not be evaluated because it returns only aggregate values that can be calculated from table metadata. This sometimes was not handled by the enclosing subquery, resulting in a server crash. (Bug#49512)

  • Mixing full-text searches and row expressions caused a crash. (Bug#49445)

  • mysql-test-run.pl now recognizes the MTR_TESTCASE_TIMEOUT, MTR_SUITE_TIMEOUT, MTR_SHUTDOWN_TIMEOUT, and MTR_START_TIMEOUT environment variables. If they are set, their values are used to set the --testcase-timeout, --suite-timeout, --shutdown-timeout, and --start-timeout options, respectively. (Bug#49210)

  • Several strmake() calls had an incorrect length argument (too large by one). (Bug#48983)

  • On Fedora 12, strmov() did not guarantee correct operation for overlapping source and destination buffer. Calls were fixed to use an overlap-safe version instead. (Bug#48866)

  • With one thread waiting for a lock on a table, if another thread dropped the table and created a new table with the same name and structure, the first thread would not notice that the table had been re-created and would try to used cached metadata that belonged to the old table but had been freed. (Bug#48157)

  • If an invocation of a stored procedure failed in the table-open stage, subsequent invocations that did not fail in that stage could cause a crash. (Bug#47649)

  • A crash occurred when a user variable that was assigned to a subquery result was used as a result field in a SELECT statement with aggregate functions. (Bug#47371)

  • When the mysql client was invoked with the --vertical option, it ignored the --skip-column-names option. (Bug#47147)

  • The optimizer could continue to execute a query after a storage engine reported an error, leading to a server crash. (Bug#46175)

  • If EXPLAIN encountered an error in the query, a memory leak occurred. (Bug#45989)

  • A race condition on the privilege hash tables permitted one thread to try to delete elements that had already been deleted by another thread. A consequence was that SET PASSWORD or FLUSH PRIVILEGES could cause a crash. (Bug#35589, Bug#35591)

  • 1) In rare cases, if a thread was interrupted during a FLUSH PRIVILEGES operation, a debug assertion occurred later due to improper diagnostics area setup. 2) A KILL operation could cause a console error message referring to a diagnostic area state without first ensuring that the state existed. (Bug#33982)

  • ALTER TABLE with both DROP COLUMN and ADD COLUMN clauses could crash or lock up the server. (Bug#31145)

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

D.1.7. Changes in MySQL 5.5.1 (04 January 2010)

When the publishing process for MySQL 5.5.1-m2 was already running, the MySQL team was informed about a security problem in the SSL connect area (a possibility to crash the server). The problem is caused by a buffer overflow in the yaSSL library. MySQL Servers using OpenSSL are not affected; it can only occur when SSL (using yaSSL) is enabled.

This problem is still under detailed investigation with the various versions, configurations, and platforms. When that has finished, the problem will be fixed as soon as possible, and new binaries for the affected versions will be released. However, building and testing these binaries in the various configurations on the various platforms will take some time.

The bug is tracked with CVE ID CVE-2009-4484. We repeat the general security hint: If it is not absolutely necessary that external machines can connect to your database instance, we recommend that the server's connection port be blocked by a firewall to prevent any such illegitimate accesses.

InnoDB Notes:

RPM Notes:

  • The version information in RPM package files has been changed:

    • The “level” field of a MySQL version number is now also included in the RPM version and in the package file name.

    • The RPM “release” value now starts to count from 1, not 0.

    For example, the generic x86 server RPM file of 5.5.1-m2 is named MySQL-server-5.5.1_m2-1.glibc23.i386.rpm. This improves consistency with other formats that also include the level (for this version: “m2”) in the file name. For example, the tar.gz filename is mysql-5.5.1-m2-linux-i686-glibc23.tar.gz. The different separator, underscore '_' for RPM, is required by the syntax of RPM.

Functionality added or changed:

  • Partitioning: The UNIX_TIMESTAMP() function is now supported in partitioning expressions using TIMESTAMP columns. For example, it now possible to create a partitioned table such as this one:

    CREATE TABLE t (c TIMESTAMP) 
    PARTITION BY RANGE ( UNIX_TIMESTAMP(c) ) (
        PARTITION p0 VALUES LESS THAN (631148400),
        PARTITION p1 VALUES LESS THAN (946681200),
        PARTITION p2 VALUES LESS THAN (MAXVALUE)
    );
    

    All other expressions involving TIMESTAMP values are now rejected with an error when attempting to create a new partitioned table or to alter an existing partitioned table.

    When accessing an existing partitioned table having a timezone-dependent partitioning function (where the table was using a previous version of MySQL), a warning rather than an error is issued. In such cases, you should fix the table. One way of doing this is to alter the table's partitioning expression so that it uses UNIX_TIMESTAMP(). (Bug#42849)

Bugs fixed:

  • Performance: When the query cache is fragmented, the size of the free block lists in the memory bins grows, which causes query cache invalidation to become slow. There is now a 50ms timeout for a SELECT statement waiting for the query cache lock. If the timeout expires, the statement executes without using the query cache. (Bug#39253)

    See also Bug#21074.

  • Incompatible Change: Replication: The file names for the semisynchronous plugins were prefixed with lib, unlike file names for other plugins. The file names no longer have a lib prefix.

    This change introduces an incompatibility if the plugins had been installed using the previous names. To handle this, uninstall the older version before installing the newer version. For example, use these statements for the master side plugins on Unix:

    mysql> UNINSTALL PLUGIN rpl_semi_sync_master;
    mysql> INSTALL PLUGIN rpl_semi_sync_master SONAME 'semisync_master.so';
    

    If you do not uninstall the older version first, attempting to install the newer version results in an error:

    mysql> INSTALL PLUGIN rpl_semi_sync_master SONAME 'semisync_master.so';
    ERROR 1125 (HY000): Function 'rpl_semi_sync_master' already exists
    

    For the slave side, similar statements apply:

    mysql> UNINSTALL PLUGIN rpl_semi_sync_slave;
    mysql> INSTALL PLUGIN rpl_semi_sync_slave SONAME 'semisync_slave.so';
    
  • Important Change: Replication: The following functions have been marked unsafe for statement-based replication:

    None of the functions just listed are guaranteed to replicate correctly when using the statement-based format, because they can produce different results on the master and the slave. The use of any of these functions while binlog_format is set to STATEMENT is logged with the warning, Statement is not safe to log in statement format. When binlog_format is set to MIXED, the binary logging format is automatically switched to the row-based format whenever one of these functions is used. (Bug#47995)

  • InnoDB Storage Engine: When compiling on Windows, an error in the CMake definitions for InnoDB would cause the engine to be built incorrectly. (Bug#49502)

  • Partitioning: When SHOW CREATE TABLE was invoked for a table that had been created using the COLUMNS keyword or the TO_SECONDS() function, the output contained the wrong MySQL version number in the conditional comments. (Bug#49591)

  • Partitioning: A query that searched on a ucs2 column failed if the table was partitioned. (Bug#48737)

  • Partitioning: In some cases, it was not possible to add a new column to a table that had subpartitions. (Bug#48276)

  • Partitioning: SELECT COUNT(*) from a partitioned table failed when using the ONLY_FULL_GROUP_BY SQL mode. (Bug#46923)

    This regression was introduced by Bug#45807.

  • Partitioning: SUBPARTITION BY KEY failed with DEFAULT CHARSET=utf8. (Bug#45904)

  • Replication: When using row-based logging, TRUNCATE TABLE was written to the binary log even if the affected table was temporary, causing replication to fail. (Bug#48350)

  • Replication: A flaw in the implementation of the purging of binary logs could result in orphaned files being left behind in the following circumstances:

    • If the server failed or was killed while purging binary logs.

      If the server failed or was killed after creating of a new binary log when the new log file was opened for the first time.

    In addition, if the slave was not connected during the purge operation, it was possible for a log file that was in use to be removed; this could lead data loss and possible inconsistencies between the master and slave. (Bug#45292)

  • Replication: When using the STATEMENT or MIXED logging format, the statements LOAD DATA CONCURRENT LOCAL INFILE and LOAD DATA CONCURRENT INFILE were logged as LOAD DATA LOCAL INFILE and LOAD DATA LOCAL INFILE, respectively (in other words, the CONCURRENT keyword was omitted). As a result, when using replication with either of these logging modes, queries on the slaves were blocked by the replication SQL thread while trying to execute the affected statements. (Bug#34628)

  • Cluster Replication: When expire_logs_days was set, the thread performing the purge of the log files could deadlock, causing all binary log operations to stop. (Bug#49536)

  • For debug builds on Windows, SAFEMALLOC was defined inconsistently, leading to mismatches when using my_malloc() and my_free(). (Bug#49811)

  • The mysql.server script had incorrect shutdown logic. (Bug#49772)

  • The push_warning_printf() function was being called with an invalid error level MYSQL_ERROR::WARN_LEVEL_ERROR, causing an assertion failure. To fix the problem, MYSQL_ERROR::WARN_LEVEL_ERROR has been replaced by MYSQL_ERROR::WARN_LEVEL_WARN. (Bug#49638)

  • The result of comparison between nullable BIGINT and INT columns was inconsistent. (Bug#49517)

  • A Valgrind error in make_cond_for_table_from_pred() was corrected. Thanks to Sergey Petrunya for the patch to fix this bug. (Bug#49506)

  • Incorrect cache initialization prevented storage of converted constant values and could produce incorrect comparison results. (Bug#49489)

  • Comparisons involving YEAR values could produce incorrect results. (Bug#49480)

    See also Bug#43668.

  • Valgrind warnings for CHECKSUM TABLE were corrected. (Bug#49465)

  • Specifying an index algorithm (such as BTREE) for SPATIAL or FULLTEXT indexes caused a server crash. These index types do not support algorithm specification, and it is not longer permitted to do so. (Bug#49250)

  • The optimizer sometimes incorrectly handled conditions of the form WHERE col_name='const1' AND col_name='const2'. (Bug#49199)

  • Execution of DECODE() and ENCODE() could be inefficient because multiple executions within a single statement reinitialized the random generator multiple times even with constant parameters. (Bug#49141)

  • With binary logging enabled, REVOKE ... ON {PROCEDURE|FUNCTION} FROM ... could cause a crash. (Bug#49119)

  • The LIKE operator did not work correctly when using an index for a ucs2 column. (Bug#49028)

  • check_key_in_view() was missing a DBUG_RETURN in one code branch, causing a crash in debug builds. (Bug#48995)

  • If a query involving a table was terminated with KILL, a subsequent SHOW CREATE TABLE for that table caused a server crash. (Bug#48985)

  • Privileges for stored routines were ignored for mixed-case routine names. (Bug#48872)

    See also Bug#41049.

  • Building MySQL on Fedora Core 12 64-bit failed, due to errors in comp_err. (Bug#48864)

  • Concurrent ALTER TABLE operations on an InnoDB table could raise an assertion. (Bug#48782)

  • Incomplete reset of internal TABLE structures could cause a crash with eq_ref table access in subqueries. (Bug#48709)

  • During query execution, ranges could be merged incorrectly for OR operations and return an incorrect result. (Bug#48665)

  • The InnoDB Table Monitor reported the FLOAT and DOUBLE data types incorrectly. (Bug#48526)

  • Re-execution of a prepared statement could cause a server crash. (Bug#48508)

  • With row-based binary logging, the server crashed for statements of the form CREATE TABLE IF NOT EXISTS existing_view LIKE temporary_table. This occurred because the server handled the existing view as a table when logging the statement. (Bug#48506)

  • The error message for ER_UPDATE_INFO was subject to buffer overflow or truncation. (Bug#48500)

  • DISTINCT was ignored for queries with GROUP BY WITH ROLLUP and only const tables. (Bug#48475)

  • Loose index scan was inappropriately chosen for some WHERE conditions. (Bug#48472)

  • The server could crash and corrupt the tablespace if the InnoDB tablespace was configured with too small a value, or if many CREATE TEMPORARY TABLE statements were executed and the temporary file directory filled up with innodb_file_per_table enabled. (Bug#48469)

  • Parts of the range optimizer could be initialized incorrectly, resulting in Valgrind errors. (Bug#48459)

  • A bad typecast could cause query execution to allocate large amounts of memory. (Bug#48458)

  • SHOW BINLOG EVENTS could fail with a error: Wrong offset or I/O error. (Bug#48357)

  • Valgrind warnings related to binary logging of LOAD DATA INFILE statements were corrected. (Bug#48340)

  • On Windows, InnoDB could not be built as a statically linked library. (Bug#48317)

  • mysql_secure_installation did not work on Solaris. (Bug#48086)

  • When running mysql_secure_installation, the command would fail if the root password contained multiple spaces, \, # or quote characters. (Bug#48031)

  • MATCH IN BOOLEAN MODE searches could return too many results inside a subquery. (Bug#47930)

  • User-defined collations with an ID less then 256 were not initialized correctly when loaded and caused a server crash. (Bug#47756)

  • If a session held a global read lock acquired with FLUSH TABLES WITH READ LOCK, a lock for one table acquired with LOCK TABLES, and issued an INSERT DELAYED statement for another table, deadlock could occur. (Bug#47682)

  • The mysql client status command displayed an incorrect value for the server character set. (Bug#47671)

  • Connecting to a 4.1.x server from a 5.1.x or higher mysql client resulted in a memory-free error when disconnecting. (Bug#47655)

  • Queries containing GROUP BY ... WITH ROLLUP that did not use indexes could return incorrect results. (Bug#47650)

  • Assignment of a system variable sharing the same base name as a declared stored program variable in the same context could lead to a crash. (Bug#47627)

  • On Solaris, no stack trace was printed to the error log after a crash. (Bug#47391)

  • The first execution of STOP SLAVE UNTIL stopped too early. (Bug#47210)

  • The innodb_file_format_check system variable could not be set at runtime to DEFAULT or to the value of a user-defined variable. (Bug#47167)

  • After a binary upgrade to MySQL 5.1 from a MySQL 5.0 installation that contains ARCHIVE tables, accessing those tables caused the server to crash, even if you had run mysql_upgrade or CHECK TABLE ... FOR UPGRADE.

    To work around this problem, use mysqldump to dump all ARCHIVE tables before upgrading, and reload them into MySQL 5.1 after upgrading. The same problem occurs for binary downgrades from MySQL 5.1 to 5.0. (Bug#47012)

  • The IGNORE clause on a DELETE statement masked an SQL statement error that occurred during trigger processing. (Bug#46425)

  • Valgrind errors for InnoDB were corrected. (Bug#45992, Bug#46656)

  • The return value was not checked for some my_hash_insert() calls. (Bug#45613)

  • It was possible for init_available_charsets() not to initialize correctly. (Bug#45058)

  • GROUP BY on a constant (single-row) InnoDB table joined to other tables caused a server crash. (Bug#44886)

  • For a VARCHAR(N) column, ORDER BY BINARY(col_name) sorted using only the first N bytes of the column, even though column values could be longer than N bytes if they contained multibyte characters. (Bug#44131)

  • For YEAR(2) values, MIN(), MAX(), and comparisons could yield incorrect results. (Bug#43668)

  • Comparison with NULL values sometimes did not produce a correct result. (Bug#42760)

  • In debug builds, killing a LOAD XML INFILE statement raised an assertion.

    Implemented in the course of fixing this bug, mysqltest has a new send_eval command that combines the functionality of the existing send and eval commands. (Bug#42520)

  • The server could crash when attempting to access a non-conformant mysql.proc system table. For example, the server could crash when invoking stored procedure-related statements after an upgrade from MySQL 5.0 to 5.1 without running mysql_upgrade. (Bug#41726)

  • The mysql_upgrade command would create three additional fields to the mysql.proc table (character_set_client, collation_connection, and db_collation), but did not populate the fields with correct values. This would lead to error messages reported during stored procedure execution. (Bug#41569)

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

  • When compressed MyISAM files were opened, they were always memory mapped, sometimes causing memory-swapping problems. To deal with this, a new system variable, myisam_mmap_size, was added to limit the amount of memory used for memory mapping of MyISAM files. (Bug#37408)

  • When running mysql_secure_installation on Windows, the command would fail to load a required module, Term::ReadKey, which was required for correct operation. (Bug#35106)

  • If the --log-bin server option was set to a directory name with a trailing component separator character, the basename of the binary log files was empty so that the created files were named .000001 and .index. The same thing occurred with the --log-bin-index, --relay-log, and --relay-log-index options. Now the server reports and error and exits. (Bug#34739)

  • If a comparison involved a constant value that required type conversion, the converted value might not be cached, resulting in repeated conversion and poorer performance. (Bug#34384)

  • Using the SHOW ENGINE INNODB STATUS statement when using partitions in InnoDB tables caused Invalid (old?) table or database name errors to be logged. (Bug#32430)

  • Output from mysql --html did not encode the <, >, or & characters. (Bug#27884)

  • Under heavy load with a large query cache, invalidating part of the cache could cause the server to freeze (that is, to be unable to service other operations until the invalidation was complete). (Bug#21074)

    See also Bug#39253.

  • On some Windows systems, InnoDB could report Operating system error number 995 in a file operation due to transient driver or hardware problems. InnoDB now retries the operation and adds Retry attempt is made to the error message. (Bug#3139)

D.1.8. Changes in MySQL 5.5.0 (07 December 2009 Milestone 2)

Previously, MySQL development proceeded by including a large set of features and moving them over many versions within a release series through several stages of maturity (Alpha, Beta, and so forth). This development model had a disadvantage in that problems with only part of the code could hinder timely release of the whole. As you might have found when testing MySQL Server 6.0, alpha quality code could jeopardize the stability of the entire release. (One consequence of this was that MySQL Server 6.0 has been withdrawn for now.)

MySQL development now uses a milestone model. The move to this model provides for more frequent milestone releases, with each milestone proceeding through a small number of releases having a focus on a specific subset of thoroughly tested features. Following the releases for one milestone, development proceeds with the next milestone; that is, another small number of releases that focuses on the next small set of features, also thoroughly tested.

MySQL 5.5.0-m2 is the first release for Milestone 2. The new features of this milestone may be considered to be initially of beta quality. For subsequent Milestone 2 releases, we plan to use increasing version numbers (5.5.1 and higher) while continuing to employ the “-m2” suffix. For Milestone 3, we plan to change the suffix to “-m3”. Version designators with “-alpha” or “-beta” suffixes are no used.

You may notice that the MySQL 5.5.0 release is designated as Milestone 2 rather than Milestone 1. This is because MySQL 5.4 was actually designated as Milestone 1, although we had not yet begun referring to milestone numbers as part of version numbers at the time.

InnoDB Notes:

Functionality added or changed:

  • Incompatible Change: MySQL Server now includes a plugin services interface that complements the plugin API. The services interface enables server functionality to be exposed as a “service” that plugins can access through a function-call interface. The libmysqlservices library provides access to the available services and dynamic plugins now must be linked against this library (use the -lmysqlservices flag). For an example showing what Makefile.am should look like, see Section 22.2.6, “MySQL Services for Plugins”. (Bug#48461)

  • Incompatible Change: Several changes have been made regarding the language and character set of error messages:

    • The --language option for specifying the directory for the error message file is now deprecated. The new --lc-messages-dir and --lc-messages options should be used instead, and --language is handled as an alias for --lc-messages-dir.

    • The language system variable has been removed and replaced with the new lc_messages_dir and lc_messages system variables. lc_messages_dir has only a global value and is read only. lc_messages has global and session values and can be modified at runtime, so the error message language can be changed while the server is running, and individual clients each can have a different error message language by changing their session lc_messages value to a different locale name.

    • Error messages previously were constructed in a mix of character sets. This issue is resolved by constructing error messages internally within the server using UTF-8 and returning them to the client in the character set specified by the character_set_results system variable. The content of error messages therefore may in some cases differ from the messags returned previously.

    For more information, see Section 9.2, “Setting the Error Message Language”, and Section 9.1.6, “Character Set for Error Messages”.

    See also Bug#46218, Bug#46236.

  • Partitioning: New PARTITION BY RANGE COLUMNS(column_list) and PARTITION BY LIST COLUMNS(column_list) options are added for the CREATE TABLE and ALTER TABLE statements.

    A major benefit of RANGE COLUMNS and LIST COLUMNS partitioning is that they make it possible to define ranges or lists based on column values that use string, date, or datetime values.

    These new extensions also broaden the scope of partition pruning to provide better coverage for queries using comparisons on multiple columns in the WHERE clause, some examples being WHERE a = 1 AND b < 10 and WHERE a = 1 AND b = 10 AND c < 10.

    For more information, see Section 17.2.1, “RANGE Partitioning”, Section 17.2.2, “LIST Partitioning”, and Section 17.4, “Partition Pruning”.

  • Partitioning: A new ALTER TABLE option, TRUNCATE PARTITION, makes it possible to delete rows from one or more selected partitions only. Unlike the case with ALTER TABLE ... DROP PARTITION, ALTER TABLE ... TRUNCATE PARTITION merely deletes all rows from the specified partition or partitions, and does not change the definition of the table.

  • Partitioning: It is now possible to assign indexes on partitioned MyISAM tables to key caches using the CACHE INDEX and to preload such indexes into the cache using LOAD INDEX INTO CACHE statements. Cache assignment and preloading of indexes for such tables can be performed for one, several, or all partitions of the table.

    This functionality is supported for only those partitioned tables that employ the MyISAM storage engine.

  • Replication: The 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 synchronize the relay log to disk after every N events. Setting its value to 0 permits the operating system to handle synchronization 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.

    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 master.info and relay.info files.

    In each case, setting the variable to a nonzero integer value N causes the slave to synchronize the corresponding file to disk after every N events. Setting its value to 0 permits the operating system to handle synchronization 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.

    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.

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

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

  • Replication: Because SHOW BINLOG EVENTS cannot be used to read events from relay log files, a new SHOW RELAYLOG EVENTS statement has been added for this purpose. (Bug#28777)

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

    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 12.5.2.1, “CHANGE MASTER TO Syntax”.

    In conjunction with the introduction of IGNORE_SERVER_IDS, SHOW SLAVE STATUS has two new fields. Replicate_Ignore_Server_Ids displays information about ignored servers. Master_Server_Id displays the server_id value from the master. (Bug#25998)

    See also Bug#27808.

  • 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 using a new MASTER_HEARTBEAT_PERIOD = interval clause for the CHANGE MASTER TO statement (see Section 12.5.2.1, “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.6, “Server Status Variables”).

    The addition of replication heartbeats addresses a number of issues:

    (Bug#20435, Bug#29309, Bug#30932)

  • Replication: 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 acknowledges that it has received and logged the events for the transaction. Semisynchronous replication is implemented through an optional plugin component. See Section 16.3.8, “Semisynchronous Replication”.

  • On Linux (and perhaps other systems), the performance of MySQL Server can be improved by using a different malloc() implementation, developed by Google and called tcmalloc. The gain is noticeable with a higher number of simultaneous users. To support use of this library, the following changes have been made:

    • The server is linked against the default malloc() provided by the respective platform.

    • Binary distributions for Linux include libtcmalloc_minimal.so (a shared library that can be linked against at runtime) in pkglibdir (that is, the same directory within the package where server plugins and similar object files are located). The version of tcmalloc included with MySQL comes from google-perftools 1.4.

      If you want to try tcmalloc but are using a binary distribution for a non-Linux platform or a source distribution, you can install Google's tcmalloc. Some distributions provide it in a google-perftools package or with a similar name, or you can download it from Google at http://code.google.com/p/google-perftools/ and compile it yourself.

    • mysqld_safe now supports a --malloc-lib option that enables administrators to specify that mysqld should use tcmalloc.

    The --malloc-lib option works by modifying the LD_PRELOAD environment value to affect dynamic linking to enable the loader to find the memory-allocation library when mysqld runs:

    • If the option is not given, or is given without a value (--malloc-lib=), LD_PRELOAD is not modified and no attempt is made to use tcmalloc.

    • If the option is given as --malloc-lib=tcmalloc, mysqld_safe looks for a tcmalloc library in /usr/lib and then in the MySQL pkglibdir location (for example, /usr/local/mysql/lib or whatever is appropriate). If tmalloc is found, its path name is added to the beginning of the LD_PRELOAD value for mysqld. If tcmalloc is not found, mysqld_safe aborts with an error.

    • If the option is given as --malloc-lib=/path/to/some/library, that full path is added to the beginning of the LD_PRELOAD value. If the full path points to a nonexistent or unreadable file, mysqld_safe aborts with an error.

    • For cases where mysqld_safe adds a path name to LD_PRELOAD, it adds the path to the beginning of any existing value the variable already has.

    As a result of the preceding changes, Linux users can use the libtcmalloc_minimal.so now included in binary packages by adding these lines to the my.cnf file:

    [mysqld_safe]
    malloc-lib=tcmalloc
    

    Those lines also suffice for users on any platform who have installed a tcmalloc package in /usr/lib. To use a specific tcmalloc library, specify its full path name. Example:

    [mysqld_safe]
    malloc-lib=/opt/lib/libtcmalloc_minimal.so
    

    (Bug#47549)

  • The InnoDB buffer pool is divided into two sublists: A new sublist containing blocks that are heavily used by queries, and an old sublist containing less-used blocks and from which candidates for eviction are taken. In the default operation of the buffer pool, a block when read in is loaded at the midpoint and then moved immediately to the head of the new sublist as soon as an access occurs. In the case of a table scan (such as performed for a mysqldump operation), each block read by the scan ends up moving to the head of the new sublist because multiple rows are accessed from each block. This occurs even for a one-time scan, where the blocks are not otherwise used by other queries. Blocks may also be loaded by the read-ahead background thread and then moved to the head of the new sublist by a single access. These effects can be disadvantageous because they push blocks that are in heavy use by other queries out of the new sublist to the old sublist where they become subject to eviction.

    InnoDB now provides two system variables that enable LRU algorithm tuning:

    • innodb_old_blocks_pct

      Specifies the approximate percentage of the buffer pool used for the old block sublist. The range of values is 5 to 95. The default value is 37 (that is, 3/8 of the pool).

    • innodb_old_blocks_time

      Specifies how long in milliseconds (ms) a block inserted into the old sublist must stay there after its first access before it can be moved to the new sublist. The default value is 0: A block inserted into the old sublist moves immediately to the new sublist the first time it is accessed, no matter how soon after insertion the access occurs. If the value is greater than 0, blocks remain in the old sublist until an access occurs at least that many ms after the first access. For example, a value of 1000 causes blocks to stay in the old sublist for 1 second after the first access before they become eligible to move to the new sublist. See Section 7.9.1, “The InnoDB Buffer Pool”

    For additional information, see Section 7.9.1, “The InnoDB Buffer Pool”. (Bug#45015)

  • Two status variables have been added to SHOW STATUS output. Innodb_buffer_pool_read_ahead and Innodb_buffer_pool_read_ahead_evicted indicate the number of pages read in by the InnoDB read-ahead background thread, and the number of such pages evicted without ever being accessed, respectively. Also, the status variables Innodb_buffer_pool_read_ahead_rnd and Innodb_buffer_pool_read_ahead_seq status variables have been removed. (Bug#42885)

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

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

  • Previously, mysqldump would not dump the INFORMATION_SCHEMA database and ignored it if it was named on the command line. Now, mysqldump will dump INFORMATION_SCHEMA if it is named on the command line. Currently, this requires that the --skip-lock-tables (or --skip-opt) option be given. (Bug#33762)

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

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

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

  • The TRADITIONAL SQL mode now includes NO_ENGINE_SUBSTITUTION. (Bug#21099)

  • MySQL now implements the SQL standard SIGNAL and RESIGNAL statements. See Section 12.7.8, “SIGNAL and RESIGNAL. (Bug#11661)

  • The undocumented, deprecated, and not useful SHOW COLUMN TYPES statement has been removed. (Bug#5299)

  • The FORMAT() function now supports an optional third parameter that enables a locale to be specified to be used for the result number's decimal point, thousands separator, and grouping between separators. Permissible locale values are the same as the legal values for the lc_time_names system variable (see Section 9.7, “MySQL Server Locale Support”). For example, the result from FORMAT(1234567.89,2,'de_DE') is 1.234.567,89. If no locale is specified, the default is 'en_US'.

  • The Greek locale 'el_GR' is now a permissible value for the lc_time_names system variable.

  • Previously, in the absence of other information, the MySQL client programs mysql, mysqladmin, mysqlcheck, mysqlimport, and mysqlshow used the compiled-in default character set, usually latin1.

    Now these clients can autodetect which character set to use based on the operating system setting, such as the value of the LANG or LC_ALL locale environment language on Unix system or the code page setting on Windows systems. For systems on which the locale is available from the OS, the client uses it to set the default character set rather than using the compiled-in default. Thus, users can configure the locale in their environment for use by MySQL clients. For example, setting LANG to ru_RU.KOI8-R causes the koi8r character set to be used. The OS character set is mapped to the closest MySQL character set if there is no exact match. If the client does not support the matching character set, it uses the compiled-in default. (For example, ucs2 is not supported as a connection character set.)

    An implication of this change is that if your environment is configured to use a non-latin1 locale, MySQL client programs will use a different connection character set than previously, as though you had issued an implicit SET NAMES statement.

    Third-party applications that wish to use character set autodetection based on the OS setting can use the following mysql_options() call before connecting to the server:

    mysql_options(mysql,
                  MYSQL_SET_CHARSET_NAME,
                  MYSQL_AUTODETECT_CHARSET_NAME);
    

    See Section 9.1.4, “Connection Character Sets and Collations”.

  • mysql_upgrade now has an --upgrade-system-tables option that causes only the system tables to be upgraded. With this option, data upgrades are not performed.

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

  • 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 mysql-test-run.pl support a --debug-sync-timeout option to enable the facility and set the default synchronization point timeout.

  • Added the TO_SECONDS() function, which converts a date or datetime value to a number of seconds since the year 0.

  • Parser performance was improved for identifier scanning and conversion of ASCII string literals.

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

  • Performance: The server unnecessarily acquired a query cache mutex even with the query cache disabled, resulting in a small performance decrement which could show up as threads often in state “invalidating query cache entries (table)”, particularly on a replication slave with row-based replication. Now if the server is started with query_cache_type set to 0, it does not acquire the query cache mutex. This has the implication that the query cache cannot be enabled at runtime. (Bug#38551)

  • Performance: The InnoDB adaptive hash latch is released (if held) for several potentially long-running operations. This improves throughput for other queries if the current query is removing a temporary table, changing a temporary table from memory to disk, using CREATE TABLE ... SELECT, or performing a MyISAM repair on a table used within a transaction. (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 no longer permitted. This is now also true of these options when used with partitioned tables and individual partitions of such tables. (Bug#32167, CVE-2008-2079)

    See also Bug#39277.

  • Security Fix: MySQL clients linked against OpenSSL can be tricked not to check server certificates. (Bug#47320, CVE-2009-4028)

  • Security Fix: The server crashed if an account without the proper privileges attempted to create a stored procedure. (Bug#44658)

  • 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 permissible values, such as tx_isolation. (Bug#34828)

  • Incompatible Change: In binary installations of MySQL, the supplied binary-configure script would start and configure MySQL, even when command help was requested with the --help command-line option. The --help, if provided, will no longer start and install the server. (Bug#30954)

  • Incompatible Change: Access privileges for several statements are more accurately checked:

    (Bug#27145)

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

  • 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 permitting 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 12.5.2.1, “CHANGE MASTER TO Syntax”. (Bug#12190)

  • 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: An ALTER TABLE ... ADD PARTITION statement that caused open_files_limit to be exceeded led to a crash of the MySQL server. (Bug#46922)

    See also Bug#47343.

  • Partitioning: When performing an INSERT ... SELECT into a partitioned table, read_buffer_size bytes of memory were allocated for every partition in the target table, resulting in consumption of large amounts of memory when the table had many partitions (more than 100).

    This fix changes the method used to estimate the buffer size required for each partition and limits the total buffer size to a maximum of approximately 10 times read_buffer_size. (Bug#45840)

  • Partitioning: The cardinality of indexes on partitioned tables was calculated using the first partition in the table, which could result in suboptimal query execution plans being chosen. Now the partition having the most records is used instead, which should result in better use of indexes and thus improved performance of queries against partitioned tables in many if not most cases. (Bug#44059)

  • Partitioning: Truncating a partitioned MyISAM table did not reset the AUTO_INCREMENT value. (Bug#35111)

  • 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: When using statement-based or mixed-format replication, the database name was not written to the binary log when executing a LOAD DATA statement. This caused problems when the table being loaded belonged to a database other than the current database; data could be loaded into the wrong table (if a table having the same name existed in the current database) or replication could fail (if no table having that name existed in the current database). Now a table referenced in a LOAD DATA statement is always logged using its fully qualified name when the database to which it belongs is not the current database. (Bug#48297)

  • Replication: When a session was closed on the master, temporary tables belonging to that session were logged with the wrong database names when either of the following conditions was true:

    1. The length of the name of the database to which the temporary table belonged was greater than the length of the current database name.

    2. The current database was not set.

    (Bug#48216)

    See also Bug#46861, Bug#48297.

  • Replication: When using row-based replication, changes to nontransactional tables that occurred early in a transaction were not immediately flushed upon committing a statement. This behavior could break consistency since changes made to nontransactional tables become immediately visible to other connections. (Bug#47678)

    See also Bug#47287, Bug#46864, Bug#43929, Bug#46129.

  • Replication: When mysqlbinlog --verbose was used to read a binary log that had been recorded using the row-based format, the output for events that updated some but not all columns of tables was not correct. (Bug#47323)

  • Replication: Performing ALTER TABLE ... DISABLE KEYS on a slave table caused row-based replication to fail. (Bug#47312)

  • Replication: When using the row-based format to replicate a transaction involving both transactional and nontransactional engines, which contained a DML statement affecting multiple rows, the statement failed; if this transaction was followed by a COMMIT, the master and the slave could diverge, because the statement was correctly rolled back on the master, but was applied on the slave. (Bug#47287)

    See also Bug#46864.

  • Replication: BEGIN statements were not included in the output of mysqlbinlog. (Bug#46998)

  • Replication: A problem with the BINLOG statement in the output of mysqlbinlog could break replication; statements could be logged with the server ID stored within events by the BINLOG statement rather than the ID of the running server. With this fix, the server ID of the server executing the statements can no longer be overridden by the server ID stored in the binary log's format description statement. (Bug#46640)

    This regression was introduced by Bug#32407.

  • Replication: When using row-based replication, DROP TEMPORARY TABLE IF EXISTS was written to the binary log if the table named in the statement did not exist, even though a DROP TEMPORARY TABLE statement should never be logged in row-based logging mode, whether the table exists or not. (Bug#46572)

  • Replication: Concurrent transactions that inserted rows into a table with an AUTO_INCREMENT column could break statement-based or mixed-format replication error 1062 Duplicate entry '...' for key 'PRIMARY' on the slave. This was especially likely to happen when one of the transactions activated a trigger that inserted rows into the table with the AUTO_INCREMENT column, although other conditions could also cause the issue to manifest. (Bug#45677)

  • Replication: The internal function get_master_version_and_clock() (defined in sql/slave.cc) ignored errors and passed directly when queries failed, or when queries succeeded but the result retrieved was empty. Now this function tries to reconnect the master if a query fails due to transient network problems, and to fail otherwise. The I/O thread now prints a warning if the same system variables do not exist on master (in the event the master is a very old version of MySQL, compared to the slave.) (Bug#45214)

  • 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, Bug#47741, Bug#48091.

  • Replication: By default, all statements executed by the mysql_upgrade program on the master are written to the binary log, then replicated to the slave. In some cases, this can result in problems; for example, it attempted to alter log tables on replicated databases (this failed due to logging being enabled).

    As part of this fix, a mysql_upgrade option, --write-binlog, is added. Its inverse, --skip-write-binlog, can be used to disable binary logging while the upgrade is in progress. (Bug#43579)

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

    (Bug#43075)

  • Replication: When the logging format was set without binary logging being enabled, the server failed to start. Now in such cases, the server starts successfully, binlog_format is set, and a warning is logged instead of an error. (Bug#42928)

  • Replication: On the master, if a binary log event is larger than max_allowed_packet, the error message ER_MASTER_FATAL_ERROR_READING_BINLOG is sent to a slave when it requests a dump from the master, thus leading the I/O thread to stop. On a slave, the I/O thread stops when receiving a packet larger than max_allowed_packet.

    In both cases, however, there was no Last_IO_Error reported, which made it difficult to determine why the slave had stopped in such cases. Now, Last_IO_Error is reported when max_allowed_packet is exceeded, and provides the reason for which the slave I/O thread stopped. (Bug#42914)

    See also Bug#14068, Bug#47200, Bug#47303.

  • Replication: When using statement-based replication and the transaction isolation level was set to READ COMMITTED or a less strict level, InnoDB returned an error even if the statement in question was filtered out according to the --binlog-do-db or --binlog-ignore-db rules in effect at the time. (Bug#42829)

  • 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.7, “Server SQL Modes”. (Bug#38173)

    See also Bug#38262, Bug#43992.

  • 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: FLUSH LOGS did not close and reopen the binary log index file. (Bug#34582)

    See also Bug#48738.

  • Replication: An error message relating to permissions required for SHOW SLAVE STATUS was confusing. (Bug#34227)

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

    See also Bug#46640, Bug#34777.

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

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

    See also Bug#48632.

  • Replication: Valgrind revealed an issue with mysqld that as corrected: memory corruption in replication slaves when switching databases. (Bug#19022)

  • API: The fix for Bug#24507 could lead in some cases to client application failures due to a race condition. Now the server waits for the “dummy” thread to return before exiting, thus making sure that only one thread can initialize the POSIX threads library. (Bug#42850)

  • Certain INTERVAL expressions could cause a crash on 64-bit systems. (Bug#48739)

  • Following a literal, the COLLATE clause was mishandled such that different results could be produced depending on whether an index was used. (Bug#48447)

  • SUM() artificially increased the precision of a DECIMAL argument, which was truncated when a temporary table was created to hold the results. (Bug#48370)

    See also Bug#45261.

  • GRANT and REVOKE crashed if a user name was specified as CURRENT_USER(). (Bug#48319)

  • If an outer query was invalid, a subquery might not even be set up. EXPLAIN EXTENDED did not expect this and caused a crash by trying to dereference improperly set up information. (Bug#48295)

  • A query containing a view using temporary tables and multiple tables in the FROM clause and PROCEDURE ANALYSE() caused a server crash.

    As a result of this bug fix, PROCEDURE ANALYSE() is legal only in a top-level SELECT. (Bug#48293)

    See also Bug#46184.

  • Error handling was missing for SELECT statements containing subqueries in the WHERE clause and that assigned a SELECT result to a user variable. The server could crash as a result. (Bug#48291)

  • An assertion could fail if the optimizer used a SPATIAL index. (Bug#48258, Bug#47019)

  • Memory-allocation failures were handled incorrectly in the InnoDB os_mem_alloc_large() function. (Bug#48237)

  • WHERE clauses with outer_value_list NOT IN subquery were handled incorrectly if the outer value list contained multiple items at least one of which could be NULL. (Bug#48177)

  • Searches using a non-default collation could return different results for a table when partitioning was and was not used. (Bug#48161)

  • A combination of GROUP BY WITH ROLLUP, DISTINCT and the const join type in a query caused a server crash when the optimizer chose to employ a temporary table to resolve DISTINCT. (Bug#48131)

  • The subquery optimizer had a memory leak. (Bug#48060)

  • Server shutdown failed on Windows. (Bug#48047)

  • In some cases, using a null microsecond part in a WHERE condition (for example, WHERE date_time_field <= 'YYYY-MM-DD HH:MM:SS.0000') could lead to incorrect results due to improper DATETIME comparison. (Bug#47963)

  • A build configured using the --without-server option did not compile the yaSSL code, so if --with-ssl was also used, the build failed. (Bug#47957)

  • When a query used a DATE or DATETIME value formatted using any separator characters other than hyphen ('-') and a >= condition matching only the greatest value in an indexed column, the result was empty if an index range scan was employed. (Bug#47925)

  • mysys/mf_keycache.c requires threading, but no test was made for thread support. (Bug#47923)

  • For debug builds, an assertion could fail during the next statement executed for a temporary table after a multiple-table UPDATE involving that table and modified an AUTO_INCREMENT column with a user-supplied value. (Bug#47919)

  • The mysys/mf_strip.c file, which defines the strip_sp() function, has been removed from the MySQL source. The function was no longer used within the main build, and the supplied function was causing symbol errors on Windows builds. (Bug#47857)

  • When building storage engines on Windows it was not possible to specify additional libraries within the CMake file required for the build. An ${engine}_LIBS macro has been included in the files to support these additional storage-engine specific libraries. (Bug#47797)

  • When building a pluggable storage engine on Windows, the engine name could be based on the directory name where the engine was located, rather than the configured storage engine name. (Bug#47795)

  • During cleanup of a stored procedure's internal structures, the flag to ignore the errors for INSERT IGNORE or UPDATE IGNORE was not cleaned up, which could result in a server crash. (Bug#47788)

  • If the first argument to GeomFromWKB() function was a geometry value, the function just returned its value. However, it failed to preserve the argument's null_value flag, which caused an unexpected NULL value to be returned to the caller, resulting in a server crash. (Bug#47780)

  • InnoDB could crash when updating spatial values. (Bug#47777)

  • The pthread_cond_wait() implementations for Windows could deadlock in some rare circumstances. (Bug#47768)

  • The encoding of values for SET system_variable = identifier statements was incorrect, resulting in incorrect error messages. (Bug#47597)

  • On WIndows, when an idle named pipe connection was forcibly closed with a KILL statement or because the server was being shut down, the thread that was closing the connection would hang infinitely. (Bug#47571, Bug#31621)

  • On Mac OS X or Windows, sending a SIGHUP signal to the server or an asynchronous flush (triggered by flush_time) caused the server to crash. (Bug#47525)

  • Debug builds could not be compiled with the Sun Studio compiler. (Bug#47474)

  • Queries of the form SELECT SUM(DISTINCT varchar_key) FROM tbl_name caused a server crash. (Bug#47421)

  • A function call could end without throwing an error or setting the return value. For example, this could happen when an error occurred while calculating the return value. This is fixed by setting the value to NULL when an error occurs during evaluation of an expression. (Bug#47412)

  • mysqladmin debug could crash on 64-bit systems. (Bug#47382)

  • A simple SELECT with implicit grouping could return many rows rather than a single row if the query was ordered by the aggregated column in the select list. (Bug#47280)

  • An assertion could be raised for CREATE TABLE if there was a pending INSERT DELAYED or REPLACE DELAYED for the same table. (Bug#47274)

  • InnoDB raised errors in some cases in a manner not compatible with SIGNAL and RESIGNAL. (Bug#47233)

  • A multiple-table UPDATE involving a natural join and a mergeable view raised an assertion. (Bug#47150)

  • On FreeBSD, memory mapping for MERGE tables could fail if underlying tables were empty. (Bug#47139)

  • Solaris binary packages now are compiled with -g0 rather than -g. (Bug#47137)

  • If an InnoDB table was created with the AUTO_INCREMENT table option to specify an initial auto-increment value, and an index was added in a separate operation later, the auto-increment value was lost (subsequent inserts began at 1 rather than the specified value). (Bug#47125)

  • Incorrect handling of predicates involving NULL by the range optimizer could lead to an infinite loop during query execution. (Bug#47123)

  • EXPLAIN caused a server crash for certain valid queries. (Bug#47106)

  • Repair by sort or parallel repair of MyISAM tables could fail to fail over to repair with key cache. (Bug#47073)

  • InnoDB did not compile on some Solaris systems. (Bug#47058)

  • On WIndows, when a failed I/O operation occurred with return code of ERROR_WORKING_SET_QUOTA, InnoDB intentionally crashed the server. Now InnoDB sleeps for 100ms and retries the failed operation. (Bug#47055)

  • The mysql_config script contained a reference to @innodb_system_libs@ that was not replaced with the corresponding library flags during the build process and ended up in the output of mysql_config --libs. (Bug#47007)

  • The configure option --without-server did not work. (Bug#46980)

  • InnoDB now ignores negative values supplied by a user for an AUTO_INCREMENT column when calculating the next value to store in the data dictionary. Setting AUTO_INCREMENT columns to negative values is undefined behavior and this change should bring the behavior of InnoDB closer to what users expect. (Bug#46965)

  • Failed multiple-table DELETE statements could raise an assertion. (Bug#46958)

  • When MySQL crashed (or a snapshot was taken that simulates a crash), it was possible that internal XA transactions (used to synchronize the binary log and InnoDB) could be left in a PREPARED state, whereas they should be rolled back. This occurred when the server_id value changed before the restart, because that value was used to construct XID values.

    Now the restriction is relaxed that the server_id value be consistent for XID values to be considered valid. The rollback phase should then be able to clean up all pending XA transactions. (Bug#46944)

  • When creating a new instance on Windows using mysqld-nt and the --install parameter, the value of the service would be set incorrectly, resulting in a failure to start the configured service. (Bug#46917)

  • The test suite was missing from RPM packages. (Bug#46834)

  • For InnoDB tables, an unnecessary table rebuild for ALTER TABLE could sometimes occur for metadata-only changes. (Bug#46760)

  • The server could crash for queries with the following elements: 1. An “impossible where” in the outermost SELECT; 2. An aggregate in the outermost SELECT; 3. A correlated subquery with a WHERE clause that includes an outer field reference as a top-level WHERE sargable predicate; (Bug#46749)

  • InnoDB did not compile using gcc 4.1 on PPC systems. (Bug#46718)

  • If InnoDB reached its limit on the number of concurrent transactions (1023), it wrote a descriptive message to the error log but returned a misleading error message to the client, or an assertion failure occurred. (Bug#46672)

    See also Bug#18828.

  • A Valgrind error during index creation by InnoDB was corrected. (Bug#46657)

  • Concurrent INSERT INTO ... SELECT statements for an InnoDB table could cause an AUTO_INCREMENT assertion failure. (Bug#46650)

  • The Serbian locale name 'sr_YU' is obsolete. It is still recognized for backward compatibility, but 'sr_RS' now should be used instead. (Bug#46633)

  • On Solaris and HP-UX systems with the environment set to the default C locale, MySQL client programs issued an Unknown OS character set error. (Bug#46619)

  • SHOW CREATE TRIGGER for a MERGE table trigger caused an assertion failure. (Bug#46614)

  • DIV operations that are out of range generated an error Error (Code 1264): Out of range value (correct), but also an error: Error (Code 1041): Out of memory (incorrect). (Bug#46606)

  • If a transaction was rolled back inside InnoDB due to a deadlock or lock wait timeout, and a statement in the transaction had an IGNORE clause, the server could crash at the end of the statement or on shutdown. (Bug#46539)

  • TRUNCATE TABLE for a table that was opened with HANDLER did not close the handler and left it in an inconsistent state that could lead to a server crash. Now TRUNCATE TABLE for a table closes all open handlers for the table. (Bug#46456)

  • Trailing spaces were not ignored for user-defined collations that mapped spaces to a character other than 0x20. (Bug#46448)

    See also Bug#29468.

  • The server crashed if a shutdown occurred while a connection was idle. This happened because of a NULL pointer dereference while logging to the error log. (Bug#46267)

  • Dropping an InnoDB table that used an unknown collation (created on a different server, for example) caused a server crash. (Bug#46256)

  • The GPL and commercial license headers had different sizes, so that error log, backtrace, core dump, and cluster trace file line numbers could be off by one if they were not checked against the version of the source used for the build. (For example, checking a GPL build backtrace against commercial sources.) (Bug#46216)

  • A query containing a subquery in the FROM clause and PROCEDURE ANALYSE() caused a server crash. (Bug#46184)

    See also Bug#48293.

  • After an error such as a table-full condition, INSERT IGNORE could cause an assertion failure for debug builds. (Bug#46075)

  • On 64-bit systems, --skip-innodb did not skip InnoDB startup. (Bug#46043)

  • InnoDB did not disallow creation of an index with the name GEN_CLUST_INDEX, which is used internally. (Bug#46000)

  • CREATE TABLE ... SELECT could cause a server crash if no default database was selected. (Bug#45998)

  • Configuring MySQL for DTrace support resulted in a build failure on Solaris if the directory for the dtrace executable was not in PATH. (Bug#45810)

  • An infinite hang and 100% CPU usage occurred after handler tried to open a merge table.

    If the command mysqladmin shutdown was executed during the hang, the debug server generated the following assert:

    mysqld: table.cc:407: void free_table_share(TABLE_SHARE*): Assertion `share->ref_count ==
    0' failed.
    090610 14:54:04 - mysqld got signal 6 ;
    

    (Bug#45781)

  • During the build of the Red Hat IA64 MySQL server RPM, the system library link order was incorrect. This made the resulting Red Hat IA64 RPM depend on "libc.so.6.1(GLIBC_PRIVATE)(64bit)", thus preventing installation of the package. (Bug#45706)

  • The caseinfo member of the CHARSET_INFO structure was not initialized for user-defined Unicode collations, leading to a server crash. (Bug#45645)

  • Appending values to an ENUM or SET definition is a metadata change for which ALTER TABLE need not rebuild the table, but it was being rebuilt anyway. (Bug#45567)

  • The socket system variable was unavailable on Windows. (Bug#45498)

  • The combination of MIN() or MAX() in the select list with WHERE and GROUP BY clauses could lead to incorrect results. (Bug#45386)

  • Truncation of DECIMAL values could lead to assertion failures; for example, when deducing the type of a table column from a literal DECIMAL value. (Bug#45261)

    See also Bug#48370.

  • Client flags were incorrectly initialized for the embedded server, causing several tests in the jp test suite to fail. (Bug#45159)

  • Concurrent execution of statements requiring a table-level lock and statements requiring a non-table-level write lock for a table could deadlock. (Bug#45143)

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

  • mysqld_safe could fail to find the logger program. (Bug#44736)

  • The have_community_features system variable was renamed to have_profiling.

    Previously, to enable profiling, it was necessary to run configure with the --enable-community-features and --enable-profiling options. Now only --enable-profiling is needed. (Bug#44651)

  • Some Perl scripts in AIX packages contained an incorrect path to the perl executable. (Bug#44643)

  • With InnoDB, renaming a table column and then creating an index on the renamed column caused a server crash to the .frm file and the InnoDB data directory going out of sync. Now InnoDB 1.0.5 returns an error instead: ERROR 1034 (HY000): Incorrect key file for table 'tbl_name'; try to repair it. To work around the problem, create another table with the same structure and copy the original table to it. (Bug#44571)

  • For debug builds, executing a stored procedure as a prepared statement could sometimes cause an assertion failure. (Bug#44521)

  • Using mysql_stmt_execute() to call a stored procedure could cause a server crash. (Bug#44495)

  • InnoDB did not always disallow creating tables containing columns with names that match the names of internal columns, such as DB_ROW_ID, DB_TRX_ID, DB_ROLL_PTR, and DB_MIX_ID. (Bug#44369)

  • An InnoDB error message incorrectly referred to the nonexistent innodb_max_files_open variable rather than to innodb_open_files. (Bug#44338)

  • SELECT ... WHERE ... IN (NULL, ...) was executed using a full table scan, even if the same query without the NULL used an efficient range scan. (Bug#44139)

    See also Bug#18360.

  • InnoDB use of SELECT MAX(autoinc_column) could cause a crash when MySQL data dictionaries went out of sync. (Bug#44030)

  • LOAD DATA INFILE statements were written to the binary log in such a way that parsing problems could occur when re-executing the statement from the log. (Bug#43746)

  • Selecting from the process list in the embedded server caused a crash. (Bug#43733)

    See also Bug#47304.

  • Attempts to enable large_pages with a shared memory segment larger than 4GB caused a server crash. (Bug#43606)

  • For ALTER TABLE, renaming a DATETIME or TIMESTAMP column unnecessarily caused a table copy operation. (Bug#43508)

  • The weekday names for the Romanian lc_time_names locale 'ro_RO' were incorrect. Thanks to Andrei Boros for the patch to fix this bug. (Bug#43207)

  • XA START could cause an assertion failure or server crash when it is called after a unilateral rollback issued by the Resource Manager (both in a regular transaction and after an XA transaction). (Bug#43171)

  • Redefining a trigger could cause an assertion failure. (Bug#43054)

  • The FORCE INDEX FOR ORDER BY index hint was ignored when join buffering was used. (Bug#43029)

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

  • The NUM_FLAG bit of the MYSQL_FIELD.flags member now is set for columns of type MYSQL_TYPE_NEWDECIMAL. (Bug#42980)

  • Incorrect handling of range predicates combined with OR operators could yield incorrect results. (Bug#42846)

  • Failure to treat BIT values as unsigned could lead to unpredictable results. (Bug#42803)

  • For the embedded server on Windows, InnoDB crashed when innodb_file_per_table was enabled and a table name was in full path format. (Bug#42383)

  • SHOW ERRORS returned an empty result set after an attempt to drop a nonexistent table. (Bug#42364)

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

  • Some queries with nested outer joins could lead to crashes or incorrect results because an internal data structure was handled improperly. (Bug#42116)

  • The server used the wrong lock type (always TL_READ instead of TL_READ_NO_INSERT when appropriate) for tables used in subqueries of UPDATE statements. This led in some cases to replication failure because statements were written in the wrong order to the binary log. (Bug#42108)

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

  • In a replication scenario with innodb_locks_unsafe_for_binlog enabled on the slave, where rows were changed only on the slave (not through replication), in some rare cases, many messages of the following form were written to the slave error log: InnoDB: Error: unlock row could not find a 4 mode lock on the record. (Bug#41756)

  • After renaming a user, granting that user privileges could result in the user having additional privileges other than those granted. (Bug#41597)

  • The mysql-stress-test.pl test script was missing from the noinstall packages on Windows. (Bug#41546)

  • With a nonstandard InnoDB page size, some error messages became inaccurate.

    Note

    Changing the page size is not a supported operation and there is no guarantee that InnoDB will function normally with a page size other than 16KB. Problems compiling or running InnoDB may occur. In particular, ROW_FORMAT=COMPRESSED in InnoDB assumes that the page size is at most 16KB and uses 14-bit pointers.

    A version of InnoDB built for one page size cannot use data files or log files from a version built for a different page size.

    (Bug#41490)

  • In some cases, the server did not recognize lettercase differences between GRANT attributes such as table name or user name. For example, a user was able to perform operations on a table with privileges of another user with the same user name but in a different lettercase.

    In consequence of this bug fix, the collation for the Routine_name column of the mysql.proc table is changed from utf8_bin to utf8_general_ci. (Bug#41049)

    See also Bug#48872.

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

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

  • CREATE TABLE failed if a column name in a FOREIGN KEY clause was given in a lettercase different from the corresponding index definition. (Bug#39932)

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

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

  • ALTER TABLE neglected to preserve ROW_FORMAT information from the original table, which could cause subsequent ALTER TABLE and OPTIMIZE TABLE statements to lose the row format for InnoDB tables. (Bug#39200)

  • Simultaneous ANALYZE TABLE operations for an InnoDB tables could be subject to a race condition. (Bug#38996)

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

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

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

  • For certain SELECT statements using ref access, MySQL estimated an incorrect number of rows, which could lead to inefficient query plans. (Bug#38049)

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

  • The MySQL client library mishandled EINPROGRESS errors for connections in nonblocking mode. This could lead to replication failures on hosts capable of resolving both IPv4 and IPv6 network addresses, when trying to resolve localhost. (Bug#37267)

    See also Bug#44344.

  • 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 S with shared locks or as a consistent read, as for INSERT ... SELECT. This reduces lock contention between sessions. (Bug#37232)

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

  • Privileges for SHOW CREATE VIEW were not being checked correctly. (Bug#35996)

  • Different invocations of CHECKSUM TABLE could return different results for a table containing columns with spatial data types. (Bug#35570)

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

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

  • For its warning count, the mysql_info() C API function could print the number of truncated data items rather than the number of warnings. (Bug#34898)

  • Concurrent execution of FLUSH TABLES along with SHOW FUNCTION STATUS or SHOW PROCEDURE STATUS could cause a server crash. (Bug#34895)

  • Executing SHOW MASTER LOGS as a prepared statement without binary logging enabled caused a crash for debug builds. (Bug#34741)

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

  • A COMMENT longer than 64 characters caused CREATE PROCEDURE to fail. (Bug#34197)

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

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

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

  • The LAST_DAY() and MAKEDATE() functions could return NULL, but the result metadata indicated NOT NULL. Thanks to Hiromichi Watari for the patch to fix this bug. (Bug#33629)

  • Instance Manager (mysqlmanager) has been removed, but a reference to it still appeared in the mysql.server script. (Bug#33472)

  • There was a race condition between the event scheduler and the server shutdown thread. (Bug#32771)

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

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

  • For const tables that were optimized away, EXPLAIN EXTENDED displayed them in the FROM clause. Now they are not displayed. If all tables are optimized away, FROM DUAL is displayed. (Bug#30302)

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

  • In mysql, using Control-C to kill the current query resulted in a ERROR 1053 (08S01): Server shutdown in progress" message if the query was waiting for a lock. (Bug#28141)

  • When building MySQL on Windows from source, the WITH_BERKELEY_STORAGE_ENGINE option would fail to configure BDB support correctly. (Bug#27693)

  • The default database is no longer changed to NULL (“no database”) if DROP DATABASE for that database failed. (Bug#26704)

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

  • SELECT COUNT(DISTINCT) was slow compared with SELECT DISTINCT. Now the server can use loose index scan for certain forms of aggregate functions that use DISTINCT. See Section 7.13.10.1, “Loose Index Scan”. (Bug#21849, Bug#38213)

  • Referring to a stored function qualified with the name of one database and tables in another database caused a “table doesn't exist” error. (Bug#18444)

  • A Table ... doesn't exist error could occur for statements that called a function defined in another database. (Bug#17199)

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

D.2.1. Changes in MySQL Enterprise Monitor 2.1.2 (26 May 2010)

This section documents all changes and bug fixes that have been applied since the release of MySQL Enterprise Monitor, version 2.1.1.

Bugs fixed:

  • Security Fix: A number of cross-site request forging issues have been identified and resolved. (Bug#52888, Bug#52910, Bug#52905, Bug#52897)

  • On Windows platforms, the MySQL Enterprise Monitor Agent could show increasing memory usage over time. (Bug#54313)

  • MySQL Enterprise Service Manager would crash during initial startup on Solaris SPARC 64-bit. (Bug#53751)

  • The dialog box during installation of MySQL Enterprise Service Manager has been updated to make the process of installing MySQL Enterprise Service Manager when using an existing MySQL server. (Bug#52839)

  • Scheduling a rule against an instance, and then deleting that instance, would retain the instance within MySQL Enterprise Dashboard, identified as Unknown. (Bug#51095)

  • Deleting a server within MySQL Enterprise Dashboard could cause a foreign key constraint error. (Bug#50927)

  • Deleting a server that had purged all its monitoring data, but still have query analyzer information, would fail. (Bug#50916)

  • The SSL certificates supplied with MySQL Enterprise Service Manager have been updated.

    The certificate shipped with MySQL Enterprise Service Manager is an example certificate that expires after 1 year and that folks should create their own and back it up between MEM service manager updates. For more information on updating the certificate, see Section 15.12.4, “Creating a new SSL KeyStore”. (Bug#50694)

  • Clicking a link to a support issue within the dashboard is now configured to open the issue within a new window. (Bug#50651)

  • The MySQL Enterprise Monitor Agent could report data using an old timestamp, or report information for a server that the MySQL Enterprise Monitor Agent can no longer connect to due to a permissions change. (Bug#50449)

  • Monitoring of a server that had INFORMATION_SCHEMA, and a large number of schemas or tables could upset the gathering of monitoring data. (Bug#47947)

  • If you specify an invalid backend proxy address to MySQL Enterprise Monitor Agent, the agent would fail silently. (Bug#46927)

  • Installation on certain platforms could fail during the generation of a UUID because of a lack of privileges. A separate UUID generation tool, agent-generate-uuid is now used to create the UUID. (Bug#46370)

  • If a customer was using their own SSL certificate, they entered that information in the server.xml file. However, running the upgrade installer caused server.xml, and any custom certificates, to be replaced. (Bug#44525)

  • Starting the agent could lead to an error regarding the ssh-keygen tool and a missing library (libcrypto). (Bug#43125)

D.2.2. Changes in MySQL Enterprise Monitor 2.1.1 (10 February 2010)

This section documents all changes and bug fixes that have been applied since the release of MySQL Enterprise Monitor, version 2.1.0.

Functionality added or changed:

  • The smallest purge log time interval that could be set in the Dashboard was one week. MySQL Enterprise Monitor was changed to enable setting the smallest purge log time interval to one day. (Bug#46822)

  • Certain heat chart rules cannot be unscheduled or disabled, this is because they are required for correct operation of MySQL Enterprise Monitor. Should an attempt be made to unschedule or disable one of these heat chart rules, a suitable message is now displayed, explaining this requirement. (Bug#46535)

  • 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. The agent will now perform a re-synchronization of the inventory if it identifies that the server has gone away and that the monitored MySQL has been upgraded. (Bug#38409)

Bugs fixed:

  • The MySQL Enterprise Monitor Agent could fail to reconnect to a monitored MySQL instance if the agent was started while the MySQL instance was unavailable. (Bug#50797)

  • When installing MySQL Enterprise Monitor Agent on a Linux operating system using the SELinux security environment, the installation would fail if the allow_execstack option had been enabled. (Bug#50515)

  • When purging old data, the purging process could fail to remove all of the data if the inflow of new information was very high. Purging now removes all outdated information at each execution. (Bug#50422)

  • It was possible to updated an existing email notification list with two email addresses in the destination without a required comma between the addresses. Addresses are now validated during the editing phase to ensure that this does not occur. (Bug#50161)

  • The agent could not be installed on Mac OS X Snow Leopard (10.6) due to an incompatibility in the XML libraries used. (Bug#50126)

  • Deleting users within MySQL Enterprise Service Manager could lead to errors in the repository database that would affect further operations involving the deleted user. (Bug#49896)

  • When creating a new instance by copying an existing agent configuration, it is possible to create an orphaned agent. The recommended advice is to TRUNCATE the mysql.inventory table. However, doing this could lead to additional errors and an exception when the scheduled data updates on the now orphaned agent are executed. (Bug#49882)

  • Monitoring a MySQL 4.0 server would fail because MySQL 4.0 did not support table-level character set support. (Bug#49082)

  • RAM statistics for FreeBSD machines would not be reported correctly by MySQL Enterprise Monitor Agent. (Bug#48493)

  • The agent installer for Solaris on x64 would fail due to a library linker issue duing the post-installation phase of the installer. (Bug#48336)

  • Support has been added for SNMPv2 traps in addition to the existing SNMPv1 traps. You can configure the version to use for SNMP traps, see SNMP Traps.

    In addition, support has also been added to send SNMP notifications to two hosts in place of just one host. Notifications are sent to both hosts simultaneously. (Bug#47686, Bug#48955)

  • Support issues can have a Severity from S1 through S4, but can also have a value of “NS” meaning “No Severity Set”. MySQL Enterprise Monitor was not able to parse this, which resulted in errors such as the following:

    2009-09-23 13:53:51,812 ERROR [em-worker-pool-thread-6:monitor.support.DevSpPoller] error
    consuming successful response
    java.lang.IllegalArgumentException: No enum const class
    com.mysql.etools.monitor.support.SpIssue$Severity.NS
    	at java.lang.Enum.valueOf(Enum.java:196)
    ...
    

    (Bug#47562)

  • The pagination of errors within MySQL Enterprise Dashboard for MySQL Enterprise Service Manager logging made it difficult to identify the true source of the error. (Bug#47464)

  • An additional link has been added to the Configure What's New page to link to the relevant documentation. (Bug#47256)

  • MySQL Enterprise Monitor would fail to install on Miracle Linux4. (Bug#47209)

  • Some strings in the What's New tab of MySQL Enterprise Dashboard had not been translated from English to Japanese. (Bug#47203)

  • The diagnostic report file has been updated so that the filename of the report includes the timestamp when the report was generated. (Bug#47164)

  • When the Configuring and troubleshooting this feed link was clicked it opened the help screen in the current browser window, rather than in a new window.

    The link can be found on the What's New tab, at the bottom of the Important Product-Related Announcements section, in the Welcome to the "What's New?" Live Feed! sub-section. (Bug#47145)

  • The links for further information on the What's New feed were invalid. (Bug#47133)

  • When the Help link was clicked in the Dashboard, the following script error was generated:

       row:   32
       char:  5
       error: object expected
       code:  0
       URL:   http://xxx.yyy.com:38080/Help.action
          

    This only happened when using Internet Explorer. (Bug#47065)

  • The times used for queries in Query Analyzer would not match the time set for the user's timezone and browser setting. (Bug#47040)

  • The date format in the configure what's new pop-up on the What's New? tab did not reflect the locale set in the User Preferences page. (Bug#46901)

  • Two links in the Agent installer were incorrect.

    The link https://enterprise.mysql.com/docs/monitor/2.0/en/mem-install.html#mem-agent-rights should have pointed to https://enterprise.mysql.com/docs/monitor/2.1/en/mem-install.html#mem-agent-rights. Also, the link https://enterprise.mysql.com/docs/monitor/2.1/en/mem-query-analysis.html should have pointed to https://enterprise.mysql.com/docs/monitor/2.1/en/mem-query-analyzer.html. (Bug#46812)

  • The REPLACE and CALL statements did not show a rows graph within the statement pop-up graph tab. (Bug#46796)

  • When updating your scription after the subscription has expired, the ability to update your advisor bundle was not available. (Bug#46700)

  • The task message for a given server within the agent would be logged at the incorrect level. Messages are now logged at the message level. (Bug#46681)

  • Pressing cancel on a pop-up would cause a page reload, instead of just closing the pop-up window. (Bug#46604)

  • The cry for help email included a stack trace, however it was displayed on a single line without any line breaks. (Bug#46458)

  • If the Last link was clicked on the Infrastructure logs page, the following error was generated:

    Error Message
    fromIndex(400) > toIndex(31)
          

    (Bug#46229)

  • When using MySQL Enterprise Monitor Agent, if the current configured time went backward (for example, during time correction), the MySQL Enterprise Monitor Agent would stop reporting data and induce a high load on the machine running MySQL Enterprise Monitor Agent (Bug#46052)

  • The Windows installers for MySQL Enterprise Service Manager did not include 64-bit versions of the various binary tools. (Bug#45682)

  • The agent could get into a state where it loop through the resynchronization of the core data, without reporting information to the service manager, causing gaps in the data. (Bug#45382)

  • The IP address of the agent host on FreeBSD 7 systems would not be reported correctly. (Bug#45079)

D.2.3. Changes in MySQL Enterprise Monitor 2.1.0 (08 September 2009)

This section documents all changes and bug fixes that have been applied since the release of MySQL Enterprise Monitor, version 2.0.6.

Functionality added or changed:

  • Incompatible Change: The default proxy port used to relay queries when using the Query Analyzer has been changed from port 4040 to 6446.

  • The Agent did not write its version number to the log on startup or shutdown.

    The information is now available by setting log level “MESSAGE” in the Dashboard. It is also available when running the Agent from the command line with the command mysql-monitor-agent --version. The Agent also now logs its version number on startup if the log level is set to “CRITICAL”. (Bug#45884)

  • The Agent did not have a configurable response size.

    The response size was hard coded to 65K. However, with large inventories, the customer might need to use a larger response size.

    The Agent command line option --agent-max-response-size was added which will set the maximum size (in bytes) of the response the agent will send to the Service Manager. The default is 65536. (Bug#45571)

  • If the Service Manager lost connection to the repository server, it would shut down after 50 attempts to reconnect or if it was unable to reconnect within 180 seconds. This behavior has now been made configurable through parameters in the config.properties file. The parameters are:

    • mysql.max_connect_retries - default is 50.

    • mysql.max_connect_timeout_msec - default is 180 seconds.

    (Bug#45471)

  • There was no way to force the Agent to resynch with the Service Manager. A link has now been added. The link can be found on the Settings, Manage Servers page - click the context menu next to a server, the menu now contains a Refresh item. (Bug#45461)

  • When the Agent debug log was examined, it was found to contain XML returned by the Service Manager that did not contain carriage returns. This made the data difficult to read by a human. The Service Manager has been changed to return formatted XML. (Bug#45460)

  • The version of Enterprise Monitor was not logged on startup.

    Enterprise Monitor was changed to log the Monitor and Advisor version number on startup. See also Bug#45884. (Bug#45459)

  • The ability to customize the text of the email sent for an event was added. The URL to the event can now be added to the email, so that the administrator does not have to search for the action that triggered the email. (Bug#44383)

  • In large installations it can be desirable to locate the repository MySQL Server and the Tomcat server on difference computers to reduce load. However, the script mysqlmonitorctl.sh assumed these were running on the same server.

    The script was therefore changed to accommodate the above requirement.

    The mysqlmonitorctl.sh script now checks for a new configuration file called mysqlmonitorctl.conf. This configuration file is located in a new directory, etc/defaults, relative to the install directory. The configuration file contains 2 variables:

    • START_MYSQL=yes

    • START_TOMCAT=yes

    The script will then start/stop the MySQL Server and Tomcat accordingly. Defaults for both variables in the file are set to “yes”. The update installers will not overwrite this file. (Bug#44379)

  • When Replication was configured to use SSL for encrypting the transfer of the binary log, even though replication worked and the dashboard displayed the replication group correctly, the agent still logged the following message (repeatedly):

    2009-04-06 16:12:00: (critical) job_collect_mysql.c:698: [mysql] (master-uuid)
    mysql_real_connect(hostname:port replication:...) to the slave's master
    failed: Access denied for user 'replication'@'hostname' (using password: YES) (1045)

    (Bug#44200)

  • It was not possible to keep logs for a specific period of more than 52 weeks. The value for purging logs could be set in Settings, Global Settings to values ranging from “Never” to “52 Weeks” using the drop down list boxes.

    The interface has now been changed to additionally offer periods of 18 months and 24 months. (Bug#43793)

  • Events used a GMT timestamp for the event time within email notifications, rather than the local time for the server generating the event.

    MySQL Enterprise Monitor has been changed so that it displays the time using the server's locale and GMT. (Bug#43739)

  • MySQL Enterprise Monitor did not include a graph to show max_used_connections versus max_connections.

    This has now been included with the Silver level advisor bundle. (Bug#43583)

  • A rule has been added named “Server Restarted” to signal a server restart. This has been added as a Heat Chart advisor to the Silver level advisor bundle. The rule has the following options:

    Expression: (%Uptime% < THRESHOLD)
    
    Critical Alert: 600
    Warning Alert: 600
    Info Alert: 600
    
    Variable: %Uptime%
    
    Data Item: mysql.status:Uptime
    
    Instance: local
    
    Default frequency: 5 minutes
    

    (Bug#43243)

  • In the Enterprise Dashboard, it was possible to change the last remaining user with a manager role to having an agent role. This led to a problem whereby when attempting to subsequently login to the Dashboard, this caused redirection to the setup.action page which presents the Create Administrator facility. However, there was no Continue button on this page, so it was not possible to create the administrative account.

    The Dashboard has now been changed so that the currently logged in user is not able to change their role. (Bug#42436)

  • Certain alerts were misleadingly labelled as CRITICAL, and caused people to change settings unnecessarily, thereby adversely affecting their system performace and functionality.

    MySQL Enterprise Monitor was changed as follows:

    Heat Chart Advisor

    • MyISAM Key Cache Has Sub-Optimal Hit Rate. Critical threshold removed, Warning set to 75 and Info set to 85.

    • Query Cache Has Sub-Optimal Hit Rate. Critical threshold removed, Warning set to 40 and Info set to 50.

    • Temporary Tables To Disk Ratio Excessive. Critical threshold removed, others left unchanged.

    Memory Usage Advisor

    • InnoDB Buffer Cache Has Sub-Optimal Hit Rate. Critical threshold removed, others left unchanged.

    • Key Buffer Size May Not Be Optimal For Key Cache. Critical threshold removed, others left unchanged.

    • Key Buffer Size May Not Be Optimal For System RAM. Critical threshold removed, others left unchanged.

    • Table Cache Not Optimal. Critical threshold removed, Warning set to 60 and Info set to 40.

    • Thread Cache Size May Not Be Optimal. Critical threshold removed, Warning set to 75 and Info set to 85.

    Performance Advisor

    • Binary Log Usage Exceeding Disk Cache Memory Limits. Critical threshold removed, Warning set to 50 and Info set to 70.

    • Excessive Disk Temporary Table Usage Detected. Critical threshold removed, others left unchanged.

    • InnoDB Buffer Pool Writes May Be Performance Bottleneck. Critical threshold removed, Warning set to 99 and Info set to 99.5.

    • InnoDB Log Waits May Be Performance Bottleneck. Critical threshold removed, Warning set to 1 and Info set to 0.5.

    (Bug#42089)

  • In the Enterprise Dashboard, the Monitor page did not have detailed server meta information. For example, the hostname, datadir, socket and port information were not displayed.

    The interface has now been changed to include the following. Hostname, datadir, socket, and port information has been added to the server meta information on the monitor page. The port and datadir information has been added to the Settings, Manage Servers page. Socket and datadir information has been added to the edit server pop-up. (Bug#40787)

  • When running multiple instances of the Enterprise Dashboard it could be difficult to determine which instance is currently being logged into.

    This was fixed by adding a name for the server on the login page. The name defaults to the hostname but may be changed in the Settings page. (Bug#40642)

  • The agent should be able to run as a non-root user. However, the startup scripts always started it as root.

    The agent chassis now has a new option --user to drop privileges after being started as root. Note, this does not work when not started as superuser, nor on Windows.

    A new dialog box has also been added to the agent installer. The dialog has the following text: “The agent does not need to run with root user privileges. The agent will switch to the user account provided below when started by the root user.

    The dialog also has a text field to enable the entry of the user account.

    A new parameter was also added to the mysql-monitor-agent.ini file. The parameter has the format user=xxx, where xxx is the user account to be used. (Bug#33778)

  • The Advisor rule “InnoDB Redo Logs Not Sized Correctly” has been renamed to “InnoDB Transaction Logs Not Sized Correctly”. The rule's Problem Description and Advice text have also been updated accordingly. (Bug#33528)

  • You can now configure an individual notification group to be used when sending critical email alerts. You can configure this by selecting the administration checkbox when configuring an individual notification group. For more information, see Section 15.5.5, “Manage Notification Groups”. (Bug#30974)

  • The Event Log now tracks both the Current and Worst states for individual events.

  • To enable communication by MySQL Enterprise Service Manager with the MySQL Enterprise website, you can now configure an HTTP Proxy to be used when accessing the Internet. For more information, see Section 15.5.1, “Global Settings”.

  • The MySQL Enterprise Dashboard now includes a What's New page that incorporates information automatically from the MySQL Enterprise and MySQL Support websites. For more information, see Section 15.6, “The What's New Page”.

Bugs fixed:

  • The installer for MySQL Enterprise Monitor Agent on Linux 64-bit using glibc-2.3 would fail before the installation had completed properly. (Bug#50289)

  • The alert for “Connection Usage Excessive” recommended raising max_connections. However, if the users raised max_connections based only on the advice of the alert, they could potentially exhaust all RAM and SWAP.

    This alert should have made the proviso that max_connections be increased only if sufficient free RAM is available to support the additional connections. The alert should also have recommended checking that all connections are correctly closed, and suggest lowering the wait_timeout or interactive_timeout settings. (Bug#46921)

  • The “Slow Query Log Not Enabled” rule was missing a <value> tag in the <thresholdList> block. This caused a stack trace to be generated when the Service Manager started. (Bug#46899)

  • Table lock contention rules had inconsistent thresholds.

    The rule lock_contention_excessive (part of the Basic subscription) contained the following expression:

    (%Uptime% > 10800) && (((%Table_locks_waited% /
    (%Table_locks_immediate% + %Table_locks_waited%)) * 100) > THRESHOLD)
    
    

    This used thresholds of 1/3/5 (for Info/Warning/Critical).

    However, in the rule table_lock_contention_excessive (part of the Platinum subscription), the same expression existed but with different thresholds:

    (%Uptime% > 10800) && (((%Table_locks_waited% /
    (%Table_locks_immediate% + %Table_locks_waited%)) * 100) > THRESHOLD)
    
    

    In this case the thresholds were 30/60/95. (Bug#46768)

  • MySQL Enterprise Monitor 2.1 advisors for Windows suggested using innodb_flush_method=unbuffered, which is an undocumented value. Only documented values should have been recommended. (Bug#46709)

  • When deleting a server within MySQL Enterprise Dashboard where there was a lot of historical data or a large number of instances being monitored, the deletion process could take some time and affect the loading of all pages within MySQL Enterprise Dashboard The process should no longer affect the performance UI. (Bug#46632)

  • The rule names and other content on the Rules page could be displayed without the necessary formatting and translation. (Bug#46608)

  • You would get a Java NullPointerException message if you omitted to select a server before using Add server to group to add a new server to an existing group. (Bug#46593)

  • Initial setup and registration of MySQL Enterprise Monitor could fail on Mac OS X when communicating with the MySQL Enterprise website. (Bug#46571)

  • The MySQL Enterprise Service Manager would send one email from each agent when agents were no longer able to write information to the repository. You now get one email containing a list of the affected agents. (Bug#46460)

  • The error message shown in the orange dialog when a Rule could not be scheduled showed the Rule's resource key instead of its name. For example:

    U0146 Unable to schedule rule "binary_logging_is_limited.name" due to
    "mysql.MasterStatus.Binlog_Ignore_DB" data not being collected from server
    "net-dev2:13306". It may be an unsupported collection for that server.
    

    (Bug#46442)

  • The length of the MySQL Enterprise Monitor related cookie information caused the web browser to fail with errors such as the following (from Safari 4):

    Bad Request
    
    Your browser sent a request that this server could not understand.
    Size of a request header field exceeds server limit.
    
    Cookie: __utma=183337658.3685800196369993700.1241092024.1248080652.1248188601.199;
    __utmc=183337658; __utmz=183337658.1247859315.194.26.ut......
    

    (Bug#46348)

  • The values reported for the os.mem.swap_page_out and os.mem.swap_page_in could be identified incorrectly as delta, instead of absolute, values. (Bug#46326)

  • When upgrading an agent that uses SSL to connect to MySQL Enterprise Service Manager using a non-standard SSL port (i.e. not 18443), the upgrade would change the SSL port back to the default value. (Bug#46253)

  • When upgrading MySQL Enterprise Service Manager any custom properties set within config.properties would be lost. Changes are now retained during an upgrade. (Bug#46252)

  • When installing MySQL Enterprise Service Manager the disk space requirements could be calcualted incorrectly, which would cause the remainder of the installation to fail. (Bug#46251)

  • Installation of MySQL Enterprise Monitor Agent on Solaris 8 or Solaris 9 using the SPARC platform could fail if the latest patches of the SUNW UTF-8 and iconv libraries were not available. This prevented the installer from operating correctly, although the agent would work correctly. The installer for the agent has now been updated to avoid this issue. (Bug#46235)

  • In the Enterprise Dashboard, the query summary information pop-up on the BrowseQueries page forced a page reload after any hide. This affected both the user pressing the hide button, as well as the links on the Example and Explain tabs that caused the query summary information pop-up to be hidden, and the Query Analyzer config pop-up to be shown instead. (Bug#46230)

  • The Agent had a memory leak. The memory consumption increased by 35MB every five minutes. (Bug#46222)

  • The MySQL server embedded with MySQL Enterprise Service Manager has been updated to MySQL 5.1.37. (Bug#46214)

  • After a Service Manager upgrade, if there were migration errors, the message “Upgrade Status: there were errors in migration (details)” was displayed on the Settings, Manage Servers page. When the details link was clicked the yellow “An Error Occurred” pop-up was briefly displayed before disappearing, making it impossible to determine the details of the error. (Bug#46181)

  • When installing a new Advisor JAR, the contents could overwrite localizations in your current installation. (Bug#46169)

  • The threshold information in email alerts listed the thresholds in a seemingly random order, for example:

    Thresholds
    Warning : 1024
    Info : 512
    Critical : 10240
    
    Thresholds
    Info : 70
    Critical : 5
    Warning : 40
    
    Thresholds
    Critical : 75
    Warning : 85
    Info : 95
    

    (Bug#46143)

  • In the Enterprise Dashboard, the check boxes within the configure what's new panel did not function correctly. When deselecting a check box the accompanying text did not become de-emphasized (“grayed out”) as expected, but only changed when another check box was selected. Further, when the checkbox was subsequently selected, the text did not become emphasized until another check box was selected or deselected. This problem was limited to Internet Explorer 8. (Bug#46104)

  • In the Enterprise Dashboard, selecting all three checkboxes in the Configure Query Analyzer panel generated an error:

    The interval “00:00:00,500” could not be parsed. Intervals must be in hh:mm:ss.msec
    format.

    The error was due to the default value of Auto-Explain Threshold containing a “,” rather than a “.” character. (Bug#46102)

  • The MySQL Enterprise Monitor Agent could return a null value for a valid result set, resulting in incorrect results when using Query Analyzer. (Bug#46095)

  • The Rule “Non-Authorized User Has Server Admin Privileges” in the “Security” Advisor checked for the following:

    Create_user_priv = 'Y'
    File_priv = 'Y'
    Lock_tables_priv = 'Y'
    Reload_priv = 'Y'
    Shutdown_priv = 'Y'
    Super_priv = 'Y
    

    However, it did not include a check for the condition:

    Process_priv = 'Y'
    

    (Bug#46071)

  • The Query Analyzer Statement Pop-up history graphs were inconsistent with the other graphs. In particular:

    • The series colors were not consistent with other graphs.

    • The graph image was right aligned, but the title was left aligned. When the pop-up was expanded, unnecessary space was located on the left.

    • The Y axis did not have a Range Label.

    (Bug#46066)

  • In the Enterprise Dashboard, if a Notification Group was created, and also set to be the “MEM Admin” for cry for help emails, the MEM Admin column showed as "false" in the table overview when the group was saved. However, if the group was then edited and the flag added again, the MEM Admin status was saved. (Bug#46038)

  • Links in emails generated from the Query Analyzer were not linking to the Query Analyzer tab correctly. (Bug#46036)

  • When a query was clicked on the Query Analyzer page, the Explain Query tab displayed a potentially incorrect value for the Auto-Explain Threshold. The Threshold can actually be set to a user configurable value in Configure Query Analyzer, but the pop-up text did not reflect the currently set value, instead displaying a hard-coded default value. (Bug#46035)

  • The Rule “Server Includes A Root User Account” in the “Security” Advisor had a Recommended Action:

    UPDATE user SET user = 'new_name' WHERE user = 'root'; FLUSH PRIVILEGES;

    However, three other rules triggered in the case where “user” was not “root” but had administrative grants. This caused the following alerts to be generated:

    • Non-Authorized User Has DB, Table, Or Index Privileges On All Databases

    • Non-Authorized User Has GRANT Privileges On All Databases

    • Non-Authorized User Has Server Admin Privileges

    (Bug#46023)

  • In the Enterprise Dashboard, on the Settings, Manage Servers page, the menu item Configure Query Analyzer generated an unhandled error message if clicked when using the Silver level subscription. Query Analyzer is not available at this subscription level, and the menu option to configure the analyzer should not be shown on this page. (Bug#46016)

  • If the Agent and monitored server had time settings that were out of sync the Enterprise Dashboard reported the server as “down”. (Bug#45937)

  • On the What's New? page of the Enterprise Dashboard, multiple messages were generated for the same error. This cluttered the user interface. (Bug#45927)

  • In the Enterprise Dashboard, when using the Safari web browser, the graph selection displayed on the Query Analyzer tab was sometimes drawn outside the plot area. (Bug#45926)

  • The Enterprise Monitor log was flooded with ERROR/WARN messages when the Service Manager was retrying for a mysqld connection:

    2009-07-02 16:52:23,440  WARN [http-18080-4:com.mysql.sql] java.lang.Exception: MySQL
    server not running or accepting connections, retrying  30 times or 46 seconds, whichever
    expires first. Exception was: Communications link failure
    Last packet sent to the server was 0 ms ago.
    2009-07-02 16:52:24,455  WARN [Purger:com.mysql.sql] java.lang.Exception: MySQL server not
    running or accepting connections, retrying  46 times or 151 seconds, whichever expires
    first. Exception was: Communications link failure
    Last packet sent to the server was 0 ms ago.
    2009-07-02 16:52:25,471  WARN [http-18080-5:com.mysql.sql] java.lang.Exception: MySQL
    server not running or accepting connections, retrying  28 times or 34 seconds, whichever
    expires first. Exception was: Communications link failure
    Last packet sent to the server was 0 ms ago.
    2009-07-02 16:52:26,377  WARN [http-18080-9:com.mysql.sql] java.lang.Exception: MySQL
    server not running or accepting connections, retrying  33 times or 64 seconds, whichever
    expires first. Exception was: Communications link failure
    Last packet sent to the server was 0 ms ago.

    (Bug#45924)

  • In the Enterprise Dashboard the icon file for event.status.closed was missing. The problem manifested differently in different browsers. In Internet Explorer 8 the UI cell was empty and no text was displayed. In Firefox 3 the text “event.status.closed” was displayed in the cell. (Bug#45872)

  • If the system time zone was different from that set in the Enterprise Dashboard, then there was inconsistency in the way times were displayed on the Query Analyzer page. Some times were displayed in the time zone of the system and some were displayed using the Dashboard time zone setting. (Bug#45858)

  • In Enterprise Dashboard, when a range on the graph in the Graphs tab was selected, the following error message was displayed:

    Error Message
    You do not have permissions to access this resource.
    
    E0211: PermissionDeniedException: []
    com.mysql.merlin.ui.interceptors.AuthenticationInterceptor.intercept(AuthenticationInterce
    ptor.java:109)
    com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java
    :224)
    com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java
    :1)
    com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
    com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221)
    org.apache.struts2.impl.StrutsActionProxy.execute(StrutsActionProxy.java:50)
    org.apache.struts2.dispatcher.Dispatcher.serviceAction(Dispatcher.java:507)
    org.apache.struts2.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:421)
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.ja
    va:235)
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    net.sf.ehcache.constructs.web.filter.GzipFilter.doFilter(GzipFilter.java:81)
    net.sf.ehcache.constructs.web.filter.Filter.doFilter(Filter.java:92)
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.ja
    va:235)
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    com.mysql.util.RequestCounterFilter.doFilter(RequestCounterFilter.java:117)
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.ja
    va:235)
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    com.mysql.merlin.ui.filters.AccessLogFilter.doFilter(AccessLogFilter.java:56)
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.ja
    va:235)
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
    org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
    org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263)
    org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
    org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.jav
    a:584)
    org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
    java.lang.Thread.run(Unknown Source)

    (Bug#45836)

  • If both the View Readme and Launch Monitor in browser check boxes were selected on the last screen of the Monitor installer, the Dashboard was not brought up in a browser until after the window displaying the “readme” information was closed. (Bug#45795)

  • The Agent did not report all the rows from an explain plan where the plan had more than one row. The Dashboard would display information for the first row, but subsequent rows would display NULL. (Bug#45791)

  • Custom collections did not override standard collections.

    If a custom collection file was defined, and collections specified which were the same as the defaults but with some extensions, the custom collection did not appear to be processed and so did not override the default collection. (Bug#45755)

  • When the Service Manager was restarted, or if the Service Manager was turned off for a brief period, and then turned back on, some graphs, such as Database Activity, showed an erroneous spike in traffic. (Bug#45688)

  • Cry for help emails were not sent for events such as the monitored server running out of connections or disk space. In the past these had been sent for any error code < 1026. (Bug#45667)

  • If custom collection files were created for the Agent, and references added to the agent-item-files variable within the mysql-monitor-agent.ini file, on upgrade the following problems occurred:

    1. The agent-item-files variable was overwritten, thereby removing the custom entry.

    2. The custom files were deleted, if they were contained in the share/ directory.

    (Bug#45655)

  • In the Enterprise Dashboard, when closing single or multiple Events the following exception was generated:

    Could not execute JDBC batch update
    org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:71)
    

    (Bug#45627)

  • In the Enterprise Dashboard, the icon displayed for each server on the Settings, Manage Servers page was incorrectly located. This resulted in fewer servers being displayed per page. (Bug#45564)

  • In Enterprise Dashboard, when clicking configure what's new in the What's New? tab, an error occurred. This only happened when using Internet Explorer 8. (Bug#45478)

  • After the initial server installation a user may select OpenSSL native integration with Tomcat. This will modify the apache-tomcat/lib directory. However, subsequently running an upgrade installer overwrote the apache-tomcat/lib directory which had been modified during the OpenSSL native integration. (Bug#45432)

  • The query SELECT * FROM 23lk4kj234; was reported incorrectly in the Query Analyzer. (Bug#45431)

  • When an event was closed a “SUCCESS” SNMP trap was sent, rather than a “CLOSED” SNMP trap. (Bug#45376)

  • When MySQL Enterprise Monitor 1.3 was upgraded directly to 2.1, and having requested SSL in the upgrade dialog, SSL did not work in the upgraded Monitor. (Bug#45339)

  • When an event was closed, the row in the event table where the event entry was located had its checkbox disabled, even though the event now in that row was open. This happened regardless of whether the Close button, or the close link were used to close the event. (Bug#45250)

  • The Notifications list in the Schedules or Edit Schedules pop-ups listed the Notification Groups targets in the order in which they were created, not alphabetic order. (Bug#45169)

  • A small memory leak occurred in the agent when a connection attempt to the dashboard failed. This represented a problem if the agent was unable to connect to the dashboard for a long period of time, as each failure to connect would leak some more memory. (Bug#45164)

  • When disabling Query Analyzer while the two sub-options remain enabled for an individual agent, the analyzer, explain and other options would be logged by the agent as critical errors. Now, only the disabling of Query Analyzer is logged as a critical error. The Example Query and Example Explain options are reported as info errors. (Bug#45041)

  • The Agent attempted to obtain the Query Analyzer configuration before the Monitor server has created it. This resulted in the Agent generating the following critical error in the log:

    2009-05-21 15:59:42: (critical) network-io.c:255: successfully reconnected to dashboard at
    http://agent:merlin@127.0.0.1:18080/heartbeat
    2009-05-21 15:59:47: (critical) agent_mysqld.c:641: successfully connected to database at
    127.0.0.1:13306 as user marcos (with password: YES)
    2009-05-21 15:59:52: (critical) network-io.c:807: starting task 2 for
    mysql::server[8b1294a5-b40b-457c-b8d3-a834848dc1df]
    
    2009-05-21 15:59:52: (critical) job_collect_lua.c:323:
    ...ql/enterprise/agent/share/mysql-proxy/items/quan.lua:505: GETing quan-config from
    http://agent:merlin@127.0.0.1:18080/v2/rest/instance/mysql/StatementAnalysisSupport/8b1294
    a5-b40b-457c-b8d3-a834848dc1df failed with: 404
    8b1294a5-b40b-457c-b8d3-a834848dc1df of type mysql.StatementAnalysisSupport not found
    
    2009-05-21 16:00:00: (critical) (share/mysql-proxy/items/quan.lua:528) setting
    .analyze_queries for 8b1294a5-b40b-457c-b8d3-a834848dc1df to true
    2009-05-21 16:00:00: (critical) (share/mysql-proxy/items/quan.lua:532) setting
    .auto_explain for 8b1294a5-b40b-457c-b8d3-a834848dc1df to true
    2009-05-21 16:00:00: (critical) (share/mysql-proxy/items/quan.lua:536) setting
    .analyze_worst_queries for 8b1294a5-b40b-457c-b8d3-a834848dc1df to true
    2009-05-21 16:00:00: (critical) (share/mysql-proxy/items/quan.lua:540) setting
    .auto_explain_min_exec_time_us for 8b1294a5-b40b-457c-b8d3-a834848dc1df to 500000
    

    (Bug#45016)

  • If a migration from 1.3 to 2.0 was initiated and a new server created during the migration, but then deleted before migration was finished, the new server delete operation failed with an Null Pointer Exception (NPE). (Bug#44991)

  • If you have the environment variable http_proxy set within your environment, when connections from MySQL Enterprise Monitor Agent could be redirected to an external site, instead of sending them to the configured MySQL Enterprise Service Manager. You can disable this behavior by adding the contents of the agent-mgmt-hostname configuration option for MySQL Enterprise Monitor Agent to the no_proxy variable. (Bug#44893)

  • The regular expression used to parse the adaptive hash index section of SHOW INNODB STATUS for the cell size/used and node size did not function correctly for versions of monitored server greater than 5.1.28. This was because the section of the expression dealing with “cells used” was removed as part of Bug#36941. (Bug#44853)

  • The Rule “InnoDB Buffer Cache Hit Rate Not Optimal” in the “Memory Usage” Advisor did not contain an uptime check. This resulted in premature firing of an info event. (Bug#44770)

  • Any JAVA_OPTS configuration changes made in the catalina.sh file, such as -Xmx, -Xms, were overwritten when the upgrade installer was run. These values were used for customizing larger installations. (Bug#44740)

  • In the Advisor “Administration” the Rule “InnoDB Redo Logs Not Sized Correctly” did not fire correctly. The rule contained the expression:

    (%have_innodb% == "YES") && ((%innodb_log_file_size% * %innodb_log_files_in_group%) <
    LEAST(1073741824, (%innodb_buffer_pool_size% / 2)))
    

    This was incorrect and needed to be changed to:

    (%have_innodb% == "YES") && ((%innodb_log_file_size% * %innodb_log_files_in_group%) <=
    LEAST(1073741824, (%innodb_buffer_pool_size% / 2)))
    

    (Bug#44734)

  • If the Service Manager was set up to use an HTTP proxy, all traffic attempted to go through the proxy, including the connection to the mysqld server running the repository. (Bug#44729)

  • The recommendation for the rule Table Cache Not Optimal says:

    Recommended Action
    SET GLOBAL table_cache = (64 + 16);

    But an error was generated on executing that query:

    mysql> SET GLOBAL table_cache = (64 + 16);
    ERROR 1193 (HY000): Unknown system variable 'table_cache'
    
    mysql> select version();
    +------------+
    | version()  |
    +------------+
    | 5.1.31-log |
    +------------+
    1 row in set (0.01 sec)

    (Bug#44602)

  • In Enterprise Dashboard, clicking a query listed on the Query Analyzer page resulted in a delay of around 28 seconds before the pop-up was displayed. (Bug#44601)

  • The frequency shown on the Advanced tab of an Event pop-up was the default frequency for a rule and not the frequency actually scheduled. (Bug#44591)

  • Any changes made to the config.properties file, were overwritten by the upgrade installer. (Bug#44526)

  • If a customer was using their own SSL certificate, they entered that information in the server.xml file. However, running the upgrade installer caused server.xml, and any custom certificates, to be replaced. (Bug#44525)

  • If you edited the server.xml file inside the tomcat/conf/ folder, and changed the Tomcat port, running the upgrade installer did not show you the new port number, but the one you used at the installation time.

    It also did not remember that you had enabled SSL. (Bug#44444)

  • Editing an Advisor and selecting the Use SNMP Traps checkbox led to confusing behavior. Advisors appeared to be incorrectly enabled or disabled. (Bug#44387)

  • The Agent failed to correctly determine the state of the monitored server if the thread-id, extracted from the client-server protocol, is greater than 2^32. In the case with a thread-id greater than 2^32, the agent incorrectly determined that it was monitoring a remote server. High values of thread-id occur when the monitored server has many connections, or if it has been running for an extended period of time. (Bug#44168)

  • The Mac OS X version of the Service Manager uses the system JRE. The system JRE loads the libraries located in /Library/Java/Extensions. As libraries in the extensions directory take precedence over other libraries, this caused conflicts when user extension libraries were installed there, as these would be used by the JRE when running Service Manager, instead of the shipped libraries. This happened when Java-related products were installed such as Connector/J, Spring, and Hibernate.

    This fix stops user-installed extension libraries from being used when the JRE runs the Service Manager, thus giving a “pristine” environment with no library collisions. (Bug#44157)

  • The What's New tab can no longer be hidden, as it now provides important information and updates about MySQL and MySQL Enterprise Monitor. (Bug#44107)

  • In the Enterprise Dashboard, when the frequency for a rule was changed in Advisors, Manage Rules, edit, incorrect thresholds were saved, leading to erroneous alerts. (Bug#44102)

  • MySQL Enterprise Monitor installation sometimes failed, generating the following error:

    Installing
    
    Innitializing User accounts. (4/6)
    
    Error running /opt/mysql/enterprise/monitor/mysql/bin/mysql
    --defaults-file=/opt/mysql/enterprise/monitor/mysql/my.cnf -S
    /opt/mysql/enterprise/monitor/mysql/tmp/mysql.sock -u root -D mysql -e "update user set
    Password = PASSWORD('service_manager') where User = 'root'; update user set User =
    'service_manager' where User = 'root';delete from user where User = '';flush privileges;"
    : ERROR 2002 (HY000): Can't connect to local MySQL server through socket
    '/opt/mysql/enterprise/monitor/mysql/tmp/mysql.sock' (2)

    After displaying this error, the MySQL Enterprise Monitor installer reported that it had “completed”, but the message displayed contained an error message string:

    Report2.SetInstallerVariable.errorsOnSQLStatementsText

    (Bug#44038)

  • In the Enterprise Dashboard, in the Query Analyzer tab, the monitored parameter was not handled correctly during collapse and expansion of the graph. For example, if the graph was monitoring CPU Utilization, and then collapsed and the parameter changed to Database Activity, the monitored parameter reverted to CPU Utilization when the graph was expanded again. (Bug#44029)

  • The upgrade installer overwrote any custom settings stored in WEB-INF/config.properties. For example it set the database host back to localhost. (Bug#44003)

  • Accessing the Query Analyzer tab caused a full table scan to take place on the MySQL Enterprise Monitor database. (Bug#43989)

  • Some SNMP managers could not detect “Application Error” SNMP notifications.

    This happened because some SNMP managers do not follow the protocol correctly. Some use the DisplayString length of 255 as the maximum OctetString, but this is in fact unlimited in SMIv1 and 64k in SMIv2.

    To work around this issue it is possible to override the correct behavior to enable non-comformant SNMP Managers to detect all messages. This is achieved by overriding the OctetString maximum size by setting a MySQL Enterprise Monitor server property. This is done by entering SQL such as the following:

    INSERT INTO map_entries VALUES (1,'2048','snmp.octetstring');
    

    In this example the value 2048 will be the maximum SNMP OctetString size that would sent in any SNMP traps. After setting this property the server will need to be restarted. Note that the value used may need adjusting depending on the behavior of the SNMP manager. (Bug#43970)

  • When updating an Agent from 2.0 to 2.1 the mysql-monitor-agent.ini was incorrectly updated.

    This happened if the Agent was configured to use SSL to connect to the Enterprise Dashboard, on a port other than 18443. The update installer caused any value specified for the port to be changed to 18443. This did not happen if the Agent was not using SSL. (Bug#43900)

  • The Enterprise Dashboard was running abnormally slowly. Clicking on a tab in the Dashboard, or selecting a server from the server tree resulted in a delay of approximately one minute before the results were displayed. (Bug#43866)

  • The Agent failed on Linux 32-bit systems with the following error:

    2009-03-24 16:01:09: (debug) chassis.c:1091: current RLIMIT_NOFILE = 4398046512128 (hard:
    577792033385921489)
    2009-03-24 16:01:09: (debug) chassis.c:1095: trying to set new RLIMIT_NOFILE =
    4398046519296 (hard: 577792033385921489)
    2009-03-24 16:01:09: (critical) chassis.c:1097: could not raise RLIMIT_NOFILE to 8192,
    Invalid argument (22). Current limit still 13811918798715880448.
    2009-03-24 16:01:09: (message) MySQL Monitor Agent 2.0.5.7153 started.
    

    This happened with the following environment:

    $ ./mysql-monitor-agent -V
     mysql-proxy 0.7.0
     glib2: 2.16.3
     libevent: 1.4.6-stable
     proxy: 0.7.0
     monitor: 0.7.0
     MySQL Monitor Agent(agent): 2.0.5.7153
     admin: 0.7.0
    
    $ cat /etc/redhat-release
     Red Hat Enterprise Linux ES release 3 (Taroon Update 5)
    
    $ uname -a
     Linux xxxx 2.4.21-32.0.1.ELsmp #1 SMP Tue May 17 17:52:23 EDT 2005 i686 i686 i386
    GNU/Linux
    

    The same error also occurred on CentOS 5.2 32-bit systems. (Bug#43821)

  • The Replication Group was renamed back to its default name after a new topology was discovered. (Bug#43816)

  • A new topology was not discovered after the previous replication group was renamed. (Bug#43815)

  • On Unix systems, executing the command:

    ./mysqlmonitorctl.sh stop

    did not make sure that mysqld was shutdown before finishing.

    This resulted in a situation such as the following:

    # /opt/mysql/enterprise/monitor-2.0.0.7092/mysqlmonitorctl.sh 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-2.0.0.7092/java
    Stopping tomcat service ... [ OK ]
    /opt/mysql/enterprise/monitor-2.0.0.7092/mysqlmonitorctl.sh : mysql stopped
    

    However, running the following command a few minutes later showed that the MySQL server was still running:

    # /opt/mysql/enterprise/monitor-2.0.0.7092/mysqlmonitorctl.sh status
    MySQL Network MySQL is running
    MySQL Network Tomcat is not running
    

    (Bug#43803)

  • 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 SNMP trap source IP was always set to 127.0.0.1. (Bug#43738)

  • The advisor “Replication - Slave Has Login Accounts With Inappropriate Privileges” contained inappropriate advice information.

    The advice message generated was:

    Server: slave-01
    Time: 2009-03-17 12:00:04 GMT
    Advisor: Replication - Slave Has Login Accounts With Inappropriate Privileges
    
    Problem Description
    Altering and dropping tables on a slave can break replication. Unless the slave also hosts
    non-replicated tables, there is no need for accounts with these privileges.
    
    Advice
    Revoke the global ALTER and DROP privileges from the following accounts on server slave-01
    unless they are absolutely necessary:
    
    user_1@localhost,
    user_2@localhost
    
    Recommended Action
    REVOKE ALTER, DROP ON *.* FROM user_name@host_name;
    FLUSH PRIVILEGES;

    However, the problems with this advice were:

    1. The server was configured read_only so it would not be possible to DROP or ALTER tables unless the user had SUPER privilege.

    2. MySQL grants were replicated from the master and therefore appeared on the slave. Also, read_only ensured the slave could not be changed.

    (Bug#43701)

  • In Enterprise Dashboard, if on the Monitor page the Configure Graphs link was clicked, no changes made, and then the Save button clicked, then the following error was generated:

    U0023 You must provide a non-zero interval

    (Bug#43682)

  • The installer exited with a return code 0, even if an error was detected and reported to the user during the installation.

    .../mysqlmonitor-2.1.0.1015-linux-x86-64bit-installer.bin --mode unattended --installdir
    /data0/merlin/monitoring/2.1.0.1015/host/38080 --tomcatport 38080 --tomcatshutdownport
    38503 --tomcatsslport 38443 --dbport 33300 --usessl 1 --adminuser **user** --adminpassword **pwd**
    Error running /data0/merlin/monitoring/2.1.0.1015/host/38080/mysql/bin/mysql
    --defaults-file=/data0/merlin/monitoring/2.1.0.1015/host/38080/mysql/my.cnf -S
    /data0/merlin/monitoring/2.1.0.1015/qa-merlin/38080/mysql/tmp/mysql.sock -u root -D mysql
    -e "update user set Password = PASSWORD('**pwd**') where User = 'root'; update user set
    User = '**user**' where User = 'root';delete from user where User = '';flush privileges;"
    : ERROR 2002 (HY000): Can't connect to local MySQL server through socket
    '/data0/merlin/monitoring/2.1.0.1015/host/38080/mysql/tmp/mysql.sock' (2)

    (Bug#43676)

  • The Connections graph did not include information from the Thread Cache graph. Connections and Thread Cache were available as separate graphs but it was difficult to compare them. (Bug#43584)

  • If it was desired to look at MySQL Enterprise Monitor graphs for time spans of over 24 hours, you had to change from Interval to From/To mode, and specify a fixed From and To period. This was inconvenient compared to simply specifying a greater interval. (Bug#43564)

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

  • When a trailing space, or tab character, was added at the end of a parameter in the config.properties file, MySQL Enterprise Monitor failed to start and generated the following errors in log:

    ERROR [Thread-1:org.springframework.web.context.ContextLoader] Context initialization
    failed
    ...
    Caused by: java.sql.SQLException: Illegal connection port value '13306'
    ...

    Resolving the problem required detailed log analysis because the configuration file did not show any apparent problems. (Bug#43540)

  • The MySQL Enterprise Monitor installer failed to install correctly due to insufficient disk space, even though the installer calculated there was suffcient disk space for the installation. This was due to the installer having out of date information regarding disk space requirements. (Bug#43538)

  • After removing enough servers to bring the host count back down to the number covered in the subscription, the Subscription Warnings reflected the new number. However, the warning message displayed:

    You are currently monitoring 1 host, however your subscription covers only 1. Your
    subscription needs to be updated to cover at least 0 additional hosts.
    

    Instead of displaying:

    Your subscription is up-to-date
    You have no warnings at this time.
    

    The former message resulted in confusion. (Bug#43163)

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

  • In the Enterprise Dashboard it is only possible to delete monitored servers if they are stopped. Monitored servers can be deleted in Settings, Manage Servers. However, if after stopping the Agent, the Dashboard was not refreshed and the agent was started again, an error was generated saying that the agent was running and could therefore not be deleted. Although correct, this was confusing as the Dashboard showed the Agent as stopped but the delete operation error message showed the Agent as running. (Bug#42983)

  • Heat Chart rules could not be disabled or unscheduled. (Bug#42932)

  • There were four columns added to the SHOW SLAVE STATUS query in MySQL Server 5.1: Last_IO_Errno, Last_IO_Error, Last_SQL_Errno, and Last_SQL_Error.

    However, these were not displayed within the Replication tab. (Bug#42811)

  • Agent IP address was not included in SNMP traps. It was also not possible to set these Agent IP addresses through a configuration, which would have been useful for situations where the Agent could not determine the monitored server IP address, such as when virtual IP addresses were used. (Bug#42703)

  • The Agent would not reconnect to a monitored database if it was started when the monitored server was down. The agent log contained the following error:

    Can't connect to MySQL server on '127.0.0.1' (0) (mysql-errno = 2003)

    The agent only sent OS data to the Dashboard. Further, when the monitored server was later started, no attempts to reconnect were logged.

    The problem could be worked around by restarting the agent when the monitored server was running again. (Bug#42581)

  • The installer used to upgrade from version 1.3 corrupted passwords containing the “?” character. (Bug#42452)

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

  • The username field for new users was populated by the last username used.

    When creating a new user for the second time in Dashboard, the previously created username appeared in the dialog. (Bug#42314)

  • The Agent shut down if the wrong username/password was given in the Service Manager. This happened on a fresh installation, when running the Service Manager through the Proxy. When Complete was clicked to finish the installation the error “Cannot open conection” was displayed. The Agent log also contained the following errors:

    2009-01-20 15:54:16: (critical) <-- received HTTP-status: 401 (failed) for
    'http://agent:mysql@127.0.0.1:8080/Monitor2/heartbeat': password are wrong
    2009-01-20 15:54:16: (critical) shutting down normally
    
    2009-01-20 15:54:19: (critical) <-- received HTTP-status: 401 (failed) for
    'http://agent:mysql@127.0.0.1:8080/Monitor2/heartbeat': password are wrong
    2009-01-20 15:54:19: (critical) shutting down normally
    

    (Bug#42228)

  • 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
    

    (Bug#42096)

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

  • Using a long interval for the long data collection purging (such as 6 weeks), and a short interval for the query analysis purging (such as 1 week) caused the Query Analyzer purge EXPLAIN for the INSERT ... SELECT into the temp_dc_ng_*_now table to perform a full scan on the dc_ng_*_now.end_time index. For example:

    explain SELECT instance_attribute_id, end_time, end_time  FROM dc_ng_long_now JOIN
    inventory_instance_attributes USING  (instance_attribute_id) JOIN inventory_instances
    USING (instance_id) WHERE  dc_ng_long_now.end_time <= 1230814870074 AND
    dc_ng_long_now.instance_attribute_id AND type_id in (8, 9, 7, 6) ORDER BY
    dc_ng_long_now.end_time ASC LIMIT 10000\G
    *************************** 1. row ***************************
               id: 1
      select_type: SIMPLE
            table: dc_ng_long_now
             type: range
    possible_keys: PRIMARY,end_time
              key: end_time
          key_len: 8
              ref: NULL
             rows: 8205369
            Extra: Using where; Using index
    *************************** 2. row ***************************
               id: 1
      select_type: SIMPLE
            table: inventory_instance_attributes
             type: eq_ref
    possible_keys: PRIMARY,instance_id
              key: PRIMARY
          key_len: 4
              ref: mem.dc_ng_long_now.instance_attribute_id
             rows: 1
            Extra:
    *************************** 3. row ***************************
               id: 1
      select_type: SIMPLE
            table: inventory_instances
             type: eq_ref
    possible_keys: PRIMARY,FKD4320F5BBDD9C29B
              key: PRIMARY
          key_len: 4
              ref: mem.inventory_instance_attributes.instance_id
             rows: 1
            Extra: Using where
    3 rows in set (0.55 sec)

    (Bug#42061)

  • OM_REFRESH was not supported by MySQL Proxy, it caused an abort().

    shell>  ./mysql-proxy --proxy-backend-addresses=192.168.250.3:3306
    network-mysqld-proxy.c.3524: COM_(0x07) is not handled
    Aborted (core dumped)
    
    (gdb) bt
    0x00b1b402 in ?? ()
    0x00cbaf30 in raise () from /lib/i686/nosegneg/libc.so.6
    0x00cbc811 in abort () from /lib/i686/nosegneg/libc.so.6
    0x08061efc in IA__g_logv at gmessages.c:497
    0x08061f66 in IA__g_log  at gmessages.c:517
    0x08054645 in proxy_read_query_result  at network-mysqld-proxy.c:3522
    0x0804c5f4 in plugin_call  at network-mysqld.c:977
    0x0804d45a in network_mysqld_con_handle at network-mysqld.c:1520
    0x08057cb9 in event_process_active (base=0x978b260) at event.c:331
    0x08057e64 in event_base_loop (base=0x978b260, flags=0) at event.c:449
    0x08057d1c in event_base_dispatch (event_base=0x978b260) at event.c:351
    0x0804d9d0 in network_mysqld_thread (_srv=0x9789008) at network-mysqld.c:1768
    0x0804b84a in main (argc=1, argv=0xbfc4fe84) at mysql-proxy.c:615

    (Bug#41991)

  • The MySQL Enterprise Monitor file my.cnf specified an initial size of 500M for the central tablespace. However, innodb_file_per_table was used as well, resulting in approximately 500M of space being potentially wasted. (Bug#41967)

  • It was not possible to change any settings related to Query Analyzer unless at least one MySQL server was already being monitored. (Bug#41875)

  • The advisor “User Has Rights To Database That Does Not Exist” generated erroneous alerts.

    If a database was created with an “_” character in the name, and then user privileges granted to this database using the escaped character sequence “\_” to prevent wildcards, then the advisor generates an error stating there is no database for the privilege.

    For example, if the following is carried out on the monitored server:

    CREATE DATABASE test_foo;
    GRANT SELECT ON `test\_foo`.* to testuser@'localhost' identified by 'test';

    then the advisor warns that these users have rights to a database that does not exist:

    ''@'%' on DB test_%,
    'test'@'localhost' on DB test_foo,
    'testuser'@'localhost' on DB test_foo

    (Bug#41717)

  • In the Enterprise Dashboard, when a new server group was clicked in the main tab an error message was generated. On checking the Monitor log there were many error messages related to lock timeouts and having to retry transactions. This problem occurred after enabling purging of the Repository. (Bug#41461)

  • Running the Service Manager on Mac OS X and monitoring two servers with two agents for at least 16 hours caused the Java process to use 2.08 GB of memory. (Bug#41438)

  • 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

    (Bug#41384)

  • SNMP trap messages were sending 127.0.0.1 as the IP address, and there was no feature to enable the user to configure the IP address contained in the SNMP message, which would have been useful for troubleshooting. (Bug#41361)

  • Allowing the heat chart rules to be set to unscheduled caused the user interface to appear broken. (Bug#41312)

  • Data in the agent resource usage graphs (CPU, RAM) stopped after a full install of a new agent monitoring the same database was carried out. Usage history was available across agent versions for all graphs except the agent resource usage graphs. (Bug#41249)

  • Graphs were incorrect for data that did not change. The graphs appeared as if no data had been gathered.

    The Hit Ratios graph had gaps in it where there had not been any activity on the parameters being monitored. For instance, if MyISAM tables were not used, then no Key Cache hit ratio series was plotted, even though the variables were still being collected. (Bug#41232)

  • The generic Linux IA64 glibc2.3 Agent installer was missing from the build. (Bug#41224)

  • When creating a new Database Administrator user in FireFox 2 the following error message was generated:

    U0002 You must log in to access the requested resource.

    This occurred in a new installation using the default administrator account. No Query Analysis permissions were given. However, the operation worked correctly using the Safari web browser. (Bug#41032)

  • The Enterprise Dashboard displayed a blank entry for Disk Space in the Meta Info area. This happened on Open Solaris 2008.05. This problem only occurred when using the ZFS file system. (Bug#40907)

  • The configuration for Query Analyzer that sets the default for all servers (using the Make this the default for all new servers checkbox) could still applied even when the dialog box was canceled. (Bug#40828)

  • The Manage Servers page did not refresh in a manner consistent with other pages. This meant that changes to configuration made by others would not be reflected on the page. Also, changes in the status of the servers were not displayed automatically. (Bug#40792)

  • The agent installer for HP-UX 11.11 would fail to execute correctly. (Bug#40568, Bug#40566, Bug#37508)

  • The graphs for Thread Cache, Connections and Temporary Tables contained incorrect Japanese translations on their Y axis. The Japanese displayed “total connection time (min)” when it should have displayed something else. For example, the Thread Cache graph should have displayed “total/min”. (Bug#40413)

  • If the MySQL Enterprise Monitor Agent was unable to execute an EXPLAIN on a query, it would report an empty SQL query. The agent will now report the query hash value, which can be used to identify the original query by examining the repository. (Bug#40353)

  • The agent installer for Solaris 8 x86 32-bit was missing. (Bug#40248)

  • Even though Query Analysis was disabled through the user interface, the queries that go through the agent were still being collected.

    When Query Analysis was turned back on in the user interface, those queries were then displayed. (Bug#40032)

  • The Enterprise Dashboard did not display OS data if the Agent was changed from remote to local monitoring. (Bug#39954)

  • The agent crashed if ssh-keygen was not present and if a wireless card was being used instead of an Ethernet card.

    This only affected Unix based systems, it did not affect Microsoft Windows. (Bug#39938)

  • On Mac OS X when a server had more than 4GB RAM available the memory advisor was still triggered. This appeared to be due to an overflowing value. (Bug#39757)

  • The Agent received a critical error but did not terminate as expected. The critical error generated was:

    2008-09-23 09:35:02: (critical) agent_mysqld.c:139: mysql_real_query() failed: Can't find
    file: './mysql/inventory.frm' (errno: 13) (errno=1017)
    

    (Bug#39603)

  • Alerts sent from MySQL Enterprise Monitor used the GMT timezone, for example:

    Time: 2008-09-17 19:41:08 GMT

    That was not convenient for users, as their timezones may not have been GMT. (Bug#39504)

  • The Agent running on AIX 5.3 did not report CPU data or RAM size, causing the Enterprise Dashboard to crash with a Null Pointer Exception. (Bug#38001)

  • The MySQL Enterprise Monitor upgrade installer replaced the my.cnf file. This resulted in the loss of any changes that had been made to the configuration file. (Bug#36528)

  • In the Enterprise Dashboard, on the Graphs page, the interface for selecting time intervals was not convenient, and it required multiple clicks to select the desired interval.

    This was fixed by adding a selection of pre-determined time intervals. (Bug#34556)

  • Auto-generated replication group names were not translated into Japanese. (Bug#32155)

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

  • The Enterprise Dashboard could communicate with https://enterprise.mysql.com using the customer username and password to download the license key and advisor bundle. However, it could not make use of a proxy to do so. This was a problem as many corporate firewalls required the use of a proxy for all HTTP and HTTPS traffic.

    The work around of having to manually download license keys and advisor bundles by hand was inconvenient. (Bug#31507)

  • The agent log does not include a specific note of when the monitoring by the agent was started. An entry AgentMonitoringService started is now added to the log. (Bug#30609)

  • When the Agent was started as a service on Windows for the first time, the name in the Task Manager window was MYSQL-~1.EXE. This occurred whether the Agent was started from within the installer or from the Start Menu.

    If the service was restarted, the Agent's name changed to the correct value, mysql-service-agent.exe. (Bug#30166)

  • When configuring a graph, setting a to date to a value prior to the from date, or the from date to a value after the to date will not automatically switch the dates when Update is pressed. (Bug#28473)

  • In the Enterprise Dashboard, the user interface permitted you to close an already closed event. This happened if multiple instances of the Events tab were created. It was possible to close an event with resolution notes in one instance, and then close the same event again with a different set of resolution notes in the other instance. However, on review, the resolution notes and event closure time stamp recorded, were those of the first closure. (Bug#24107)

  • When upgrading a monitored server, the information and configuration of the server would not be updated, leading to rules not being executed or applied correctly. Server's are now re-inventoried according to the specified schedule. For more information, see Remote Server Inventory Schedule. (Bug#24068)

  • The Dynamic Link Library (DLL) libxml2.dll did not contain version resources. This meant version information was not available to be displayed when the file was examined in Windows Explorer. (Bug#23948)

  • It was not possible to rename a notification group. (Bug#22962)

  • Failures by MySQL Enterprise Service Manager to send warning emails are now reported both in the logs and in the MySQL Enterprise Dashboard within the Product Info section of the Settings page. For more information, see Section 15.5.7, “The Product Information Screen”. (Bug#20478)

D.3. MySQL Connector/ODBC (MyODBC) Change History

D.3.1. Changes in MySQL Connector/ODBC 5.1.8 (Not yet released)
D.3.2. Changes in MySQL Connector/ODBC 5.1.7 (24 August 2010)
D.3.3. Changes in MySQL Connector/ODBC 5.1.6 (09 November 2009)
D.3.4. Changes in MySQL Connector/ODBC 5.1.5 (18 August 2008)
D.3.5. Changes in MySQL Connector/ODBC 5.1.4 (15 April 2008)
D.3.6. Changes in MySQL Connector/ODBC 5.1.3 (26 March 2008)
D.3.7. Changes in MySQL Connector/ODBC 5.1.2 (13 February 2008)
D.3.8. Changes in MySQL Connector/ODBC 5.1.1 (13 December 2007)
D.3.9. Changes in MySQL Connector/ODBC 5.1.0 (10 September 2007)
D.3.10. Changes in MySQL Connector/ODBC 5.0.12 (Never released)
D.3.11. Changes in MySQL Connector/ODBC 5.0.11 (31 January 2007)
D.3.12. Changes in MySQL Connector/ODBC 5.0.10 (14 December 2006)
D.3.13. Changes in MySQL Connector/ODBC 5.0.9 (22 November 2006)
D.3.14. Changes in MySQL Connector/ODBC 5.0.8 (17 November 2006)
D.3.15. Changes in MySQL Connector/ODBC 5.0.7 (08 November 2006)
D.3.16. Changes in MySQL Connector/ODBC 5.0.6 (03 November 2006)
D.3.17. Changes in MySQL Connector/ODBC 5.0.5 (17 October 2006)
D.3.18. Changes in Connector/ODBC 5.0.3 (Connector/ODBC 5.0 Alpha 3) (20 June 2006)
D.3.19. Changes in Connector/ODBC 5.0.2 (Never released)
D.3.20. Changes in Connector/ODBC 5.0.1 (Connector/ODBC 5.0 Alpha 2) (05 June 2006)
D.3.21. Changes in MySQL Connector/ODBC 3.51.28 (Not yet released)
D.3.22. Changes in MySQL Connector/ODBC 3.51.27 (20 November 2008)
D.3.23. Changes in MySQL Connector/ODBC 3.51.26 (07 July 2008)
D.3.24. Changes in MySQL Connector/ODBC 3.51.25 (11 April 2008)
D.3.25. Changes in MySQL Connector/ODBC 3.51.24 (14 March 2008)
D.3.26. Changes in MySQL Connector/ODBC 3.51.23 (09 January 2008)
D.3.27. Changes in MySQL Connector/ODBC 3.51.22 (13 November 2007)
D.3.28. Changes in MySQL Connector/ODBC 3.51.21 (08 October 2007)
D.3.29. Changes in MySQL Connector/ODBC 3.51.20 (10 September 2007)
D.3.30. Changes in MySQL Connector/ODBC 3.51.19 (10 August 2007)
D.3.31. Changes in MySQL Connector/ODBC 3.51.18 (08 August 2007)
D.3.32. Changes in MySQL Connector/ODBC 3.51.17 (14 July 2007)
D.3.33. Changes in MySQL Connector/ODBC 3.51.16 (14 June 2007)
D.3.34. Changes in MySQL Connector/ODBC 3.51.15 (07 May 2007)
D.3.35. Changes in MySQL Connector/ODBC 3.51.14 (08 March 2007)
D.3.36. Changes in MySQL Connector/ODBC 3.51.13 (Never released)
D.3.37. Changes in MySQL Connector/ODBC 3.51.12 (11 February 2005)
D.3.38. Changes in MySQL Connector/ODBC 3.51.11 (28 January 2005)

D.3.1. Changes in MySQL Connector/ODBC 5.1.8 (Not yet released)

Functionality added or changed:

  • Documentation in .CHM and .HLP format has been removed from the distribution. (Bug#56232)

Bugs fixed:

  • For some procedure and parameter combinations SQLProcedureColumns() did not work correctly. For example, it could not return records for an existing procedure with correct parameters supplied.

    Further, it returned incorrect data for column 7, TYPE_NAME. For example, it returned VARCHAR(20) instead of VARCHAR. (Bug#57182)

  • The MySQL Connector/ODBC MSI installer did not set the InstallLocation value in the Microsoft Windows registry. (Bug#56978)

  • In bulk upload mode, SQLExecute would return SQL_SUCCESS, even when the uploaded data contained errors, such as primary key duplication, and foreign key violation. (Bug#56804)

  • SQLDescribeCol and SQLColAttribute could not be called before SQLExecute, if the query was parameterized and not all parameters were bound.

    Note, MSDN states that “For performance reasons, an application should not call SQLColAttribute/SQLDescribeCol before executing a statement.” However, it should still be possible to do so if performance reasons are not paramount. (Bug#56717)

  • When SQLNumResultCols() was called between SQLPrepare() and SQLExecute() the driver ran SET @@sql_select_limit=1, which limited the resultset to just one row. (Bug#56677)

  • After installing MySQL Connector/ODBC, the system DSN created could not be configured or deleted. An error dialog was displayed, showing the error message “Invalid attribute string”.

    In this case the problem was due to the fact that the driver could not parse the NULL-separated connection string. (Bug#56233)

  • When attempting to install the latest Connector/ODBC 5.1.6 on Windows using the MSI, with an existing 5.1.x version already installed, the following error was generated:

    Another version of this product is already installed.  Installation of this version
    cannot continue.  To configure or remove the existing version of this product, use
    Add/Remove Programs on the Control Panel.
    

    Also, the version number displayed in the ODBC Data Source Administrator/Drivers tab did not get updated when removing or installing a new version of 5.1.x. (Bug#54314)

D.3.2. Changes in MySQL Connector/ODBC 5.1.7 (24 August 2010)

Functionality added or changed:

  • MySQL Connector/ODBC has been changed to support the CLIENT_INTERACTIVE flag. (Bug#48603)

Bugs fixed:

  • SQLColAttribute(SQL_DESC_PRECISION...) function returned incorrect results for type identifiers that have a negative value:

    #define SQL_LONGVARCHAR       (-1) returned 4294967295
    #define SQL_BINARY            (-2) returned 4294967294
    #define SQL_VARBINARY         (-3) returned 4294967293
    #define SQL_LONGVARBINARY     (-4) returned 4294967292
    #define SQL_BIGINT            (-5) returned 4294967291
    #define SQL_TINYINT           (-6) returned 4294967290
    #define SQL_BIT               (-7) returned 4294967289
    

    They were returned as 32-bit unsigned integer values. This only happened on 64-bit Linux. (Bug#55024)

  • SQLColAttribute for SQL_DESC_OCTET_LENGTH returned length including terminating null byte. It should not have included the null byte. (Bug#54206)

  • The SQLColumns function returned the incorrect transfer octet length into the column BUFFER_LENGTH for DECIMAL type. (Bug#53235)

  • SQLForeignKeys() did not return the correct information. The list of foreign keys in other tables should not have included foreign keys that point to unique constraints in the specified table. (Bug#51422)

  • In contrast to all other ODBC catalog functions SQLTablePrivileges required the user to have SELECT privilege on MySQL schemata, otherwise the function returned with an error:

    SQL Error. Native Code: 1142, SQLState: HY000, Return Code: -1
    [MySQL][ODBC 5.1 Driver][mysqld-5.0.67-community-nt]SELECT command denied to user
    'repadmin'@'localhost' for table 'tables_priv'
    [Error][SQL Error]Error executing SQLTablePrivileges for object cat: myrep, object Name:
    xxxxxxxxxx
    

    (Bug#50195)

  • MySQL Connector/ODBC manually added a LIMIT clause to the end of certain SQL statements, causing errors for statements that contained code that should be positioned after the LIMIT clause. (Bug#49726)

  • If NO_BACKSLASH_ESCAPES mode was used on a server, escaping binary data led to server query parsing errors. (Bug#49029)

  • Bulk upload operations did not work for queries that used parameters. (Bug#48310)

  • Retrieval of the current catalog at the moment when a connection was not ready, such as when the connection had been broken or when not all pending results had been processed, resulted in the application crashing. (Bug#46910)

  • Describing a view or table caused SQLPrepare to prefetch table data. For large tables this created an intolerable performance hit. (Bug#46411)

  • If an application was invoked by the root user, SQLDriverConnect() was not able to use the username and password in the connection string to connect to the database. (Bug#45378)

  • Calling SQLColAttribute on a date column did not set SQL_DESC_DATETIME_INTERVAL_CODE. SQLColAttribute returned SQL_SUCCESS but the integer passed in was not set to SQL_CODE_DATE. (Bug#44576)

  • Conversions for many types were missing from the file driver/info.c. (Bug#43855)

  • The SQLTables() function required approximately two to four minutes to return the list of 400 tables in a database. The SHOW TABLE STATUS query used by SQLTables() was extremely slow for InnoDB tables with a large number of rows because the query was calculating the approximate number of rows in each table. Further, the results could not be cached due to non-deterministic nature of the result set (the row count was re-calculated every time), impacting performance further. (Bug#43664)

  • Executing SQLForeignKeys to get imported foreign keys for tables took an excessively long time. For example, getting imported foreign keys for 252 tables to determine parent/child dependencies took about 3 minutes and 14 seconds for the 5.1.5 driver, whereas it took 3 seconds for the 3.5x.x driver. (Bug#39562)

  • SQLDescribeCol returned incorrect column definitions for SQLTables result. (Bug#37621)

  • When opening ADO.Recordset from Microsoft Access 2003, a run-time error occurred:

    ErrNo: -2147467259 ErrMessage: Data provider or other service returned an E_FAIL status.
    

    (Bug#36996)

  • SQLPrimaryKeysW returned mangled strings for table name, column name and primary key name. (Bug#36441)

  • On Windows, the SOCKET parameter to the DSN was used as the named pipe name to connect to. This was not exposed in the Windows setup GUI. (Bug#34477)

  • MySQL Connector/ODBC returned a value of zero for a column with a non-zero value. This happened when the column had a data type of BIT, and any numeric type was used in SQLBindCol. (Bug#32821)

  • Option for handling bad dates was not available in the GUI. (Bug#30539)

D.3.3. Changes in MySQL Connector/ODBC 5.1.6 (09 November 2009)

Functionality added or changed:

  • In the MySQL Data Source Configuration dialog, an excessive number of tabs were required to navigate to selection of a database. MySQL Connector/ODBC has been changed to make the tab order more practical, thereby enabling faster configuration of a Data Source. (Bug#42905)

Bugs fixed:

  • An error randomly occurred on Windows 2003 Servers (German language Version) serving classic ASP scripts on IIS6 MDAC version 2.8 SP2 on Windows 2003 SP2. The application connected to MySQL Server 5.0.44-log with a charset of UTF-8 Unicode (utf8). The MySQL server was running on Gentoo Linux.

    The script error occurred sporadically on the following line of code:

    SET my_conn = Server.CreateObject("ADODB.Connection")
    my_conn.Open ConnString  <- ERROR
    

    The connection was either a DSN or the explicit connection string:

    Driver={MySQL ODBC 5.1 Driver};SERVER=abc.abc.abc.abc;DATABASE=dbname;UID=uidname;PWD=pwdname;PORT=3306;OPTION=67108864;
    

    The error occurred on connections established using either a DNS or a connection string.

    When IISState and Debug Diagnostic Tool 1.0.0.152 was used to analyse the code, the following crash analysis was generated:

    MYODBC5!UTF16TOUTF32+6In 4640-1242788336.dmp the assembly instruction at
    myodbc5!utf16toutf32+6 in C:\Programme\MySQL\Connector ODBC 5.1\myodbc5.dll from MySQL AB
    has caused an access violation exception (0xC0000005) when trying to read from memory
    location 0x194dd000 on thread 33
    

    (Bug#44971)

  • MySQL Connector/ODBC overwrote the query log. MySQL Connector/ODBC was changed to append the log, rather than overwrite it. (Bug#44965)

  • MySQL Connector/ODBC failed to build with MySQL 5.1.30 due to incorrect use of the data type bool. (Bug#42120)

  • Inserting a new record using SQLSetPos did not correspond to the database name specified in the SELECT statement when querying tables from databases other than the current one.

    SQLSetPos attempted to do the INSERT in the current database, but finished with a SQL_ERROR result and “Table does not exist” message from MySQL Server. (Bug#41946)

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

  • When a column of type DECIMAL containing NULL was accessed, MySQL Connector/ODBC returned a 0 rather than a NULL. (Bug#41081)

  • In Access 97, when linking a table containing a LONGTEXT or TEXT field to a MySQL Connector/ODBC DSN, the fields were shown as TEXT(255) in the table structure. Data was therefore truncated to 255 characters. (Bug#40932)

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

    (Bug#40316)

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

  • Binding SQL_C_BIT to an INTEGER column did not work.

    The sql_get_data() function only worked correctly for BOOLEAN columns that corresponded to SQL_C_BIT buffers. (Bug#39644)

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

    (Bug#39085)

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

    (Bug#29955)

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

    (Bug#26950)

  • Microsoft Access was not able to read BIGINT values properly from a table with just two columns of type BIGINT and VARCHAR. #DELETE appeared instead of the correct values. (Bug#17679)

D.3.4. 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)

D.3.5. 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)

D.3.6. 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 MySQL 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 MySQL 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 MySQL 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 MySQL Connector/ODBC driver. (Bug#33825)

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

D.3.7. 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 MySQL 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 enables 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)

D.3.8. 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 MySQL Connector/ODBC 5.1.x before upgrading.

    See also Bug#34571.

Functionality added or changed:

  • Incompatible Change: Replaced myodbc3i (now myodbc-installer) with MySQL Connector/ODBC 5.0 version.

  • Incompatible Change: Removed monitor (myodbc3m) and dsn-editor (myodbc3c).

  • Incompatible Change: Do not permit 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 MySQL 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)

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

D.3.9. 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 MySQL 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.

D.3.10. Changes in MySQL Connector/ODBC 5.0.12 (Never released)

Note

Development on Connector/ODBC 5.0.x has ceased. New features and functionality will be incorporated into Connector/ODBC 5.1.

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)

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

D.3.12. 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)

D.3.13. 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 using SQLColAttribute/SQL_DESC_DISPLAY_SIZE.

  • Fixed buffer length return for SQLDriverConnect.

  • ODBC v2 behavior 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.

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

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

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

  • MySQL 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 MySQL Connector/ODBC 3.51 installed before installing this version.

Bugs fixed:

  • You no longer have to have MySQL Connector/ODBC 3.51 installed before installing this version.

  • MySQL Connector/ODBC supports both User and System DSNs.

  • Installation is provided in the form of a standard Microsoft System Installer (MSI).

D.3.17. 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 MySQL Connector/ODBC 3.51 installed before installing this version.

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

D.3.19. Changes in Connector/ODBC 5.0.2 (Never released)

Connector/ODBC 5.0.2 was an internal implementation and testing release.

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

D.3.21. Changes in MySQL Connector/ODBC 3.51.28 (Not yet released)

Bugs fixed:

  • SQLColAttribute(...SQL_DESC_CASE_SENSITIVE...) returned SQL_FALSE for binary types and SQL_TRUE for the rest. It should have returned SQL_TRUE for binary types, and SQL_FALSE for the rest. (Bug#54212)

  • SQLColAttribute for SQL_DESC_OCTET_LENGTH returned length including terminating null byte. It should not have included the null byte. (Bug#54206)

  • If NO_BACKSLASH_ESCAPES mode was used on a server, escaping binary data led to server query parsing errors. (Bug#49029)

  • Inserting a new record using SQLSetPos did not correspond to the database name specified in the SELECT statement when querying tables from databases other than the current one.

    SQLSetPos attempted to do the INSERT in the current database, but finished with a SQL_ERROR result and “Table does not exist” message from MySQL Server. (Bug#41946)

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

  • Microsoft Access was not able to read BIGINT values properly from a table with just two columns of type BIGINT and VARCHAR. #DELETE appeared instead of the correct values. (Bug#17679)

D.3.22. 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 MySQL 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.
    

    (Bug#29955)

D.3.23. 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)

D.3.24. 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)

D.3.25. 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 MySQL 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.

    Note

    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.

    (Bug#31495)

  • 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 MySQL Connector/ODBC, the connection would mistakenly report 'user cancelled' for accesses to the database information. (Bug#16653)

D.3.26. 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:

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

D.3.27. 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)

D.3.28. 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 permitted NULL values. This was dur to an issue with NULLABLE and IS_NULLABLE return values from the call to SQLColumns(). (Bug#26108)

  • MySQL 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. MySQL Connector/ODBC now correctly returns an SQLSTATE of 08S01. (Bug#3456)

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

D.3.30. 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 D.3.31, “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.

D.3.31. 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 MySQL 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)

  • MySQL Connector/ODBC now supports batched statements. 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.

D.3.32. 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 enable 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)

  • MySQL 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, MySQL 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 permitted 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, MySQL 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.

D.3.33. Changes in MySQL Connector/ODBC 3.51.16 (14 June 2007)

Functionality added or changed:

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

D.3.34. Changes in MySQL Connector/ODBC 3.51.15 (07 May 2007)

Bugs fixed:

  • MySQL Connector/ODBC would incorrectly claim to support SQLProcedureColumns (by returning true when queried about SQLPROCEDURECOLUMNS with SQLGetFunctions), but this functionality is not supported. (Bug#27591)

  • An incorrect transaction isolation level may not be returned when accessing the connection attributes. (Bug#27589)

  • Adding a new DSN with the myodbc3i utility under AIX would fail. (Bug#27220)

  • When inserting data using bulk statements (through SQLBulkOperations), the indicators for all rows within the insert would not updated correctly. (Bug#24306)

  • Using SQLProcedures does not return the database name within the returned resultset. (Bug#23033)

  • The SQLTransact() function did not support an empty connection handle. (Bug#21588)

  • Using SQLDriverConnect instead of SQLConnect could cause later operations to fail. (Bug#7912)

  • When using blobs and parameter replacement in a statement with WHERE CURSOR OF, the SQL is truncated. (Bug#5853)

  • MySQL Connector/ODBC would return too many foreign key results when accessing tables with similar names. (Bug#4518)

D.3.35. Changes in MySQL Connector/ODBC 3.51.14 (08 March 2007)

Functionality added or changed:

  • Use of SQL_ATTR_CONNECTION_TIMEOUT on the server has now been disabled. If you attempt to set this attribute on your connection the SQL_SUCCESS_WITH_INFO will be returned, with an error number/string of HYC00: Optional feature not supported. (Bug#19823)

  • Added auto is null option to MySQL Connector/ODBC option parameters. (Bug#10910)

  • Added auto-reconnect option to MySQL Connector/ODBC option parameters.

  • Added support for the HENV handlers in SQLEndTran().

Bugs fixed:

  • On 64-bit systems, some types would be incorrectly returned. (Bug#26024)

  • When retrieving TIME columns, C/ODBC would incorrectly interpret the type of the string and could interpret it as a DATE type instead. (Bug#25846)

  • MySQL Connector/ODBC may insert the wrong parameter values when using prepared statements under 64-bit Linux. (Bug#22446)

  • Using MySQL Connector/ODBC, with SQLBindCol and binding the length to the return value from SQL_LEN_DATA_AT_EXEC fails with a memory allocation error. (Bug#20547)

  • Using DataAdapter, MySQL Connector/ODBC may continually consume memory when reading the same records within a loop (Windows Server 2003 SP1/SP2 only). (Bug#20459)

  • When retrieving data from columns that have been compressed using COMPRESS(), the retrieved data would be truncated to 8KB. (Bug#20208)

  • The ODBC driver name and version number were incorrectly reported by the driver. (Bug#19740)

  • A string format exception would be raised when using iODBC, MySQL Connector/ODBC and the embedded MySQL server. (Bug#16535)

  • The SQLDriverConnect() ODBC method did not work with recent MySQL Connector/ODBC releases. (Bug#12393)

D.3.36. Changes in MySQL Connector/ODBC 3.51.13 (Never released)

Connector/ODBC 3.51.13 was an internal implementation and testing release.

D.3.37. Changes in MySQL Connector/ODBC 3.51.12 (11 February 2005)

Functionality added or changed:

  • N/A

Bugs fixed:

  • Using stored procedures with ADO, where the CommandType has been set correctly to adCmdStoredProc, calls to stored procedures would fail. (Bug#15635)

  • File DSNs could not be saved. (Bug#12019)

  • SQLColumns() returned no information for tables that had a column named using a reserved word. (Bug#9539)

D.3.38. Changes in MySQL Connector/ODBC 3.51.11 (28 January 2005)

Bugs fixed:

  • mysql_list_dbcolumns() and insert_fields() were retrieving all rows from a table. Fixed the queries generated by these functions to return no rows. (Bug#8198)

  • SQLGetTypoInfo() returned tinyblob for SQL_VARBINARY and nothing for SQL_BINARY. Fixed to return varbinary for SQL_VARBINARY, binary for SQL_BINARY, and longblob for SQL_LONGVARBINARY. (Bug#8138)

D.4. MySQL Connector/NET Change History

D.4.1. Changes in MySQL Connector/NET Version 6.3.x

D.4.1.1. Changes in MySQL Connector/NET 6.3.5 (12 October 2010 GA)

Second GA release. Fixes bugs since 6.3.4.

Bugs fixed:

  • Setting MySqlCommand.CommandTimeout to 0 had no effect. It should have resulted in an infinite timeout. (Bug#57265)

  • When performing a row-by-row update, only the first row was updated and all other rows were ignored. (Bug#57092)

  • MySQL Connector/NET experienced two problems as follows:

    1. A call to System.Data.Objects.ObjectContext.DatabaseExists() returned false, even if the database existed.

    2. A call to System.Data.Objects.ObjectContext.CreateDatabase() created a database but with a name other than the one specified in the connection string. It then failed to use it when EDM objects were processed.

    (Bug#56859)

  • Setting the Default Command Timeout connection string option had no effect. (Bug#56806)

  • When an output parameter was declared as type MySqlDbType.Bit, it failed to return with the correct value. (Bug#56756)

  • MySqlHelper.ExecuteReader did not include an overload accepting MySqlParameter objects when using a MySqlConnection. However, MySqlHelper did include an overload for MySqlParameter objects when using a string object containing the connection string to the database. (Bug#56755)

  • MySQL Connector/NET 6.1.3 (GA) would not install on a Windows Server 2008 (Web Edition) clean installation. There were two problems:

    • If .NET framework version 4.0 was not installed, installation failed because c:\windows\microsoft.net\v4.0.* did not exist.

    • If .NET 4.0 was subsequently installed, then the following error was generated:

      InstallFiles: File: MySql.Data.Entity.dll,  Directory: ,  Size: 229888
      MSI (s) (E0:AC) [15:20:26:196]: Assembly Error:The assembly is built by a runtime newer
      than the currently loaded runtime, and cannot be loaded.
      MSI (s) (E0:AC) [15:20:26:196]: Note: 1: 1935 2:  3: 0x8013101B 4: IStream 5: Commit 6: 
      MSI (s) (E0:A0) [15:20:26:196]: Note: 1: 1304 2: MySql.Data.Entity.dll 
      Error 1304. Error writing to file: MySql.Data.Entity.dll. Verify that you have access to
      that directory.
      

    (Bug#56580)

D.4.1.2. Changes in MySQL Connector/NET 6.3.4 (01 September 2010 GA)

First GA release. Fixes bugs since 6.3.3.

Bugs fixed:

  • The calculation of lockAge in the Session Provider sometimes generated a System.Data.SqlTypes.SqlNullValueException. (Bug#55701)

  • Attempting to read Double.MinValue from a DOUBLE column in MySQL table generated the following exception:

    System.OverflowException : Value was either too large or too small for a Double.
    
    --OverflowException
    at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo
    numfmt)
    at MySql.Data.Types.MySqlDouble.MySql.Data.Types.IMySqlValue.ReadValue(MySqlPacket
    packet, Int64 length, Boolean nullVal)
    at MySql.Data.MySqlClient.NativeDriver.ReadColumnValue(Int32 index, MySqlField field,
    IMySqlValue valObject)
    at MySql.Data.MySqlClient.ResultSet.ReadColumnData(Boolean outputParms)
    at MySql.Data.MySqlClient.ResultSet.NextRow(CommandBehavior behavior)
    at MySql.Data.MySqlClient.MySqlDataReader.Read()
    

    (Bug#55644)

  • Calling MySqlDataAdapter.Update(DataTable) resulted in an unacceptable performance hit when updating large amounts of data. (Bug#55609)

  • If using MySQL Server 5.0.x it was not possible to alter stored routines in Visual Studio. If the stored routine was clicked, and the context sensitive menu option, Alter Routine, selected, the following error was generated:

    Unable to load object with error: Object reference not
    set to an instance of an object
    

    (Bug#55170)

  • EventLog was not disposed in the SessionState provider. (Bug#52550)

  • When attempting to carry out an operation such as:

    from p in db.Products where p.PostedDate>=DateTime.Now select p;
    

    Where p.PostedDate is a DateTimeOffset, and the underlying column type is a TIMESTAMP, the following exception was generated:

    MySqlException occurred
    Unable to serialize date/time value
    

    MySQL Connector/NET has now been changed so that all TIMESTAMP columns will be surfaced as DateTime. (Bug#52550)

  • Stored procedure enumeration code generated an error if a procedure was used in a dataset that did not return any resultsets. (Bug#50671)

  • The INSERT command was significantly slower with MySQL Connector/NET 6.x compared to 5.x, when compression was enabled. (Bug#48243)

  • Opening a connection in the Visual Studio Server Explorer and choosing to alter an existing routine required another authentication at the server. (Bug#44715)

D.4.1.3. Changes in MySQL Connector/NET 6.3.3 (27 July 2010 beta)

Second Beta release. Fixes bugs since 6.3.2.

Bugs fixed:

  • MySqlDataAdapter.Update() generated concurrency violations for custom stored procedure driven update commands that used UpdateRowSource.FirstReturnedRecord. (Bug#54895)

  • Several calls to datadapter.Update() with intervening changes to DataTable resulted in ConcurrencyException exceptions being generated. (Bug#54863)

  • MySQL Connector/NET generated a null reference exception when TransactionScope was used by multiple threads. (Bug#54681)

  • The icon for the MySQL Web Configuration Tool was not displayed in Visual Studio for Web Application Projects. (Bug#54571)

  • The MySqlHelper object did not have an overloaded version of the ExecuteReader method that accepted a MySqlConnection object. (Bug#54570)

  • If MySqlDataAdapter was used with an INSERT command where the VALUES clause contained an expression with parentheses in it, and set the adapter.UpdateBatchSize parameter to be greater than one, then the call to adpater.Update either generated an exception or failed to batch the commands, executing each insert individually. (Bug#54386)

  • The method MySql.Data.Common.QueryNormalizer.CollapseValueList generated an ArgumentOutOfRangeException. (Bug#54152, Bug#53865)

  • MySQL Connector/NET did not process Thread.Abort() correctly, and failed to cancel queries currently running on the server. (Bug#54012)

  • MySQL Connector/NET 6.3.2 failed to install on Windows Vista. (Bug#53975)

  • Garbage Collector disposal of a MySqlConnection object caused the following exception:

    System.IO.EndOfStreamException: Attempted to read past the end of the stream.
    MySql.Data.MySqlClient.MySqlStream.ReadFully(Stream stream, Byte[] buffer, Int32 offset,
    Int32 count)
    MySql.Data.MySqlClient.MySqlStream.LoadPacket()
    Outer Exception Reading from the stream has failed.
    ...

    (Bug#53457)

  • MySQL Connector/NET did not throw an EndOfStreamException exception when net_write_timeout was exceeded. (Bug#53439)

  • After a timeout exception, if an attempt was made to reuse a connection returned to the connection pool the following exception was generated:

    [MySqlException (0x80004005): There is already an open DataReader associated with this
    Connection which must be closed first.]
       MySql.Data.MySqlClient.MySqlCommand.CheckState() +278
       MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior) +43
       MySql.Data.MySqlClient.MySqlCommand.ExecuteReader() +6
       Controls.SimpleCommand.ExecuteReader(String SQL) in ...:323
       Albums.GetImagesByAlbum(SimpleCommand Cmd, Int32 iAlbum, String Order, String Limit)
    in ...:13
       Forecast.Page_Load(Object sender, EventArgs e) in ...:70
       System.Web.UI.Control.OnLoad(EventArgs e) +99
       System.Web.UI.Control.LoadRecursive() +50
       System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean
    includeStagesAfterAsyncPoint) +627

    (Bug#53357)

  • Membership schema creation failed if the default schema collation was not Latin1. (Bug#53174)

  • The MySQL Connector/NET installation failed due to machine.config files not being present in configuration folders.

    MySQL Connector/NET has been changed to skip over configuration folders that do not contain a machine.config file. (Bug#52352)

  • CHAR(36) columns were not recognized as GUIDs when used in views with entity models. (Bug#52085)

  • When an application was subjected to increased concurrent load, MySQL Connector/NET generated the following error when calling stored procedures:

    A DataTable named \'Procedure Parameters\'
    already belongs to this DataSet.
          

    (Bug#49118)

  • When the connection string option “Connection Reset = True” was used, a connection reset used the previously used encoding for the subsequent authentication operation. This failed, for example, if UCS2 was used to read the last column before the reset. (Bug#47153)

  • When batching was used in MySqlDataAdapter, a connection was not opened automatically in MySqlDataAdapter.Update(). This resulted in an InvalidOperationException exception being generated, with the message text “connection must be valid and open”.

    MySQL Connector/NET has been changed to behave more like SQL Server: if the connection is closed, it is opened for the duration of update operation. (Bug#38411)

  • Database name was emitted into typed datasets. This prevented users using the configured default database. (Bug#33870)

D.4.1.4. Changes in MySQL Connector/NET 6.3.2 (24 May 2010 beta)

First Beta release. Fixes bugs since 6.3.1.

Functionality added or changed:

  • Procedure cacheing had a problem whereby if you created a procedure, dropped it, and recreated it with a different number of parameters an exception was generated.

    MySQL Connector/NET has been changed so that if the procedure is recreated with a different number of parameters, it will still be recognized. (Bug#52562)

  • MySQL Connector/NET has been changed to include MySqlDataReader.GetFieldType(string columnname). Further, MySqlDataReader.GetOrdinal() now includes the name of the column in the exception if the column is not found. (Bug#47467)

Bugs fixed:

  • After an exception, the internal datareader, MySqlCommand.Connection.Reader, was not properly closed (it was not set to null). If another query was subsequently executed on that command object an exception was generated with the message “There is already an open DataReader associated with this Connection which must be closed first.” (Bug#55558)

  • MySQL Connector/NET generated an exception when used to read a TEXT column containing more than 32767 bytes. (Bug#54040)

  • In MySQL Connector/NET, the MySqlConnection.Abort() method contained a try...catch construct, with an empty catch block. This meant that any exception generated at this point would not be caught. (Bug#52769)

  • The procedure cache affected the MySQL Connector/NET performance, reducing it by around 65%. This was due to unnecessary calls of String.Format(), related to debug logging. Even though the logging was disabled the string was still being formatted, resulting in impaired performance. (Bug#52475)

  • If FunctionsReturnString=true was used in the connection string, the decimal separator (according to locale) was not interpreted. (Bug#52187)

  • In MySQL Connector/NET, the LoadCharsetMap() function of the CharSetMap class set the following incorrect mapping:

    mapping.Add("latin1", new CharacterSet("latin1", 1));
    

    This meant that, for example, the Euro sign was not handled correctly.

    The correct mapping should have been:

    mapping.Add("latin1", new CharacterSet("windows-1252", 1));
    

    This is because MySQL's latin1 character set is the same as the windows-cp1252 character set and it extends the official ISO 8859-1 or IANA latin1. (Bug#51927)

  • A non-terminated string in SQL threw a CLR exception rather than a syntax exception. (Bug#51788)

  • When calling ExecuteNonQuery on a command object, the following exception occurred:

    Index and length must refer to a location within the string.
    Parameter name: length
    

    (Bug#51610)

  • MySQL Connector/NET 6.3.1 failed to install. (Bug#51407, Bug#51604)

  • When using table per type inheritance and listing the contents of the parent table, the result of the query was a list of child objects, even though there was no related child record with the same parent Id. (Bug#49850)

D.4.1.5. Changes in MySQL Connector/NET 6.3.1 (02 March 2010 alpha)

Fixes bugs since 6.3.0.

Functionality added or changed:

  • Connector/NET was not compatible with Visual Studio wizards that used square brackets to delimit symbols.

    Connector/NET has been changed to include a new connection string option Sql Server mode that supports use of square brackets to delimit symbols. (Bug#35852)

Bugs fixed:

  • Specifying a connection string where an option had no value generated an error, rather than the value being set to the default. For example, a connection string such as the following would result in an error:

    server=localhost;user=root;compress=;database=test;port=3306;password=123456;
    

    (Bug#51209)

  • The method Command.TrimSemicolons used StringBuilder, and therefore allocated memory for the query even if it did not need to be trimmed. This led to excessive memory consumption when executing a number of large queries. (Bug#51149)

  • MySqlCommand.Parameters.Clear() did not work. (Bug#50444)

  • Binary Columns were not displayed in the Query Builder of Visual Studio. (Bug#50171)

  • When the UpdateBatchSize property was set to a value greater than 1, only the first row was applied to the database. (Bug#50123)

  • When trying to create stored procedures from a SQL script, a MySqlException was thrown when attempting to redefine the DELIMITER:

            MySql.Data.MySqlClient.MySqlException was unhandled
            Message="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 'DELIMITER' at line 1"
            Source="MySql.Data"
            ErrorCode=-2147467259
            Number=1064
            StackTrace:
            à MySql.Data.MySqlClient.MySqlStream.ReadPacket()
            à MySql.Data.MySqlClient.NativeDriver.ReadResult(UInt64& affectedRows, Int64&
            lastInsertId)
            à MySql.Data.MySqlClient.MySqlDataReader.GetResultSet()
            à MySql.Data.MySqlClient.MySqlDataReader.NextResult()
            à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
            à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader()
            à MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()
          à MySql.Data.MySqlClient.MySqlScript.Execute()

    Note: The MySqlScript class has been fixed to support the delimiter statement as it is found in SQL scripts. (Bug#46429)

  • A connection string set in web.config could not be reused after Visual Studio 2008 Professional was shut down. It continued working for the existing controls, but did not work for new controls added. (Bug#41629)

D.4.1.6. Changes in MySQL Connector/NET 6.3.0 (16 February 2010 alpha)

First alpha release of 6.3.

Functionality added or changed:

  • Nested transaction scopes were not supported. MySQL Connector/NET now implements nested transaction scopes. A per-thread stack of scopes is maintained, which is necessary to handle nested scopes with the RequiresNew or Suppress options. (Bug#45098)

  • Support for MySQL Server 4.1 has been removed from MySQL Connector/NET starting with version 6.3.0. The connector will now throw an exception if you try to connect to a server of version less than 5.0.

Bugs fixed:

  • When adding a data set in Visual Studio 2008, the following error was generated:

    Relations couldn't be addded. Column 'REFERENCED_TABLE_CATALOG' does not belong to table.

    This was due to a 'REFERENCED_TABLE_CATALOG' column not being included in the foreign keys collection. (Bug#48974)

  • Attempting to execute a load data local infile on a file where the user did not have write permissions, or the file was open in an editor gave an access denied error. (Bug#48944)

  • The method MySqlDataReader.GetSchemaTable() returned 0 in the NumericPrecision field for decimal and newdecimal columns. (Bug#48171)

D.4.2. Changes in MySQL Connector/NET Version 6.2.x

D.4.2.1. Changes in MySQL Connector/NET 6.2.5 (Not yet released GA)

This release fixes bugs since 6.2.4.

Bugs fixed:

  • Setting MySqlCommand.CommandTimeout to 0 had no effect. It should have resulted in an infinite timeout. (Bug#57265)

  • When performing a row-by-row update, only the first row was updated and all other rows were ignored. (Bug#57092)

  • Setting the Default Command Timeout connection string option had no effect. (Bug#56806)

  • When an output parameter was declared as type MySqlDbType.Bit, it failed to return with the correct value. (Bug#56756)

  • MySqlHelper.ExecuteReader did not include an overload accepting MySqlParameter objects when using a MySqlConnection. However, MySqlHelper did include an overload for MySqlParameter objects when using a string object containing the connection string to the database. (Bug#56755)

D.4.2.2. Changes in MySQL Connector/NET 6.2.4 (30 August 2010 GA)

This release fixes bugs since 6.2.3.

Functionality added or changed:

  • Procedure cacheing had a problem whereby if you created a procedure, dropped it, and recreated it with a different number of parameters an exception was generated.

    MySQL Connector/NET has been changed so that if the procedure is recreated with a different number of parameters, it will still be recognized. (Bug#52562)

Bugs fixed:

  • The calculation of lockAge in the Session Provider sometimes generated a System.Data.SqlTypes.SqlNullValueException. (Bug#55701)

  • Attempting to read Double.MinValue from a DOUBLE column in MySQL table generated the following exception:

    System.OverflowException : Value was either too large or too small for a Double.
    
    --OverflowException
    at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo
    numfmt)
    at MySql.Data.Types.MySqlDouble.MySql.Data.Types.IMySqlValue.ReadValue(MySqlPacket
    packet, Int64 length, Boolean nullVal)
    at MySql.Data.MySqlClient.NativeDriver.ReadColumnValue(Int32 index, MySqlField field,
    IMySqlValue valObject)
    at MySql.Data.MySqlClient.ResultSet.ReadColumnData(Boolean outputParms)
    at MySql.Data.MySqlClient.ResultSet.NextRow(CommandBehavior behavior)
    at MySql.Data.MySqlClient.MySqlDataReader.Read()
    

    (Bug#55644)

  • After an exception, the internal datareader, MySqlCommand.Connection.Reader, was not properly closed (it was not set to null). If another query was subsequently executed on that command object an exception was generated with the message “There is already an open DataReader associated with this Connection which must be closed first.” (Bug#55558)

  • If using MySQL Server 5.0.x it was not possible to alter stored routines in Visual Studio. If the stored routine was clicked, and the context sensitive menu option, Alter Routine, selected, the following error was generated:

    Unable to load object with error: Object reference not
    set to an instance of an object
    

    (Bug#55170)

  • MySqlDataAdapter.Update() generated concurrency violations for custom stored procedure driven update commands that used UpdateRowSource.FirstReturnedRecord. (Bug#54895)

  • Several calls to datadapter.Update() with intervening changes to DataTable resulted in ConcurrencyException exceptions being generated. (Bug#54863)

  • The icon for the MySQL Web Configuration Tool was not displayed in Visual Studio for Web Application Projects. (Bug#54571)

  • The MySqlHelper object did not have an overloaded version of the ExecuteReader method that accepted a MySqlConnection object. (Bug#54570)

  • If MySqlDataAdapter was used with an INSERT command where the VALUES clause contained an expression with parentheses in it, and set the adapter.UpdateBatchSize parameter to be greater than one, then the call to adpater.Update either generated an exception or failed to batch the commands, executing each insert individually. (Bug#54386)

  • The method MySql.Data.Common.QueryNormalizer.CollapseValueList generated an ArgumentOutOfRangeException. (Bug#54152, Bug#53865)

  • MySQL Connector/NET did not process Thread.Abort() correctly, and failed to cancel queries currently running on the server. (Bug#54012)

  • Garbage Collector disposal of a MySqlConnection object caused the following exception:

    System.IO.EndOfStreamException: Attempted to read past the end of the stream.
    MySql.Data.MySqlClient.MySqlStream.ReadFully(Stream stream, Byte[] buffer, Int32 offset,
    Int32 count)
    MySql.Data.MySqlClient.MySqlStream.LoadPacket()
    Outer Exception Reading from the stream has failed.
    ...

    (Bug#53457)

  • MySQL Connector/NET did not throw an EndOfStreamException exception when net_write_timeout was exceeded. (Bug#53439)

  • After a timeout exception, if an attempt was made to reuse a connection returned to the connection pool the following exception was generated:

    [MySqlException (0x80004005): There is already an open DataReader associated with this
    Connection which must be closed first.]
       MySql.Data.MySqlClient.MySqlCommand.CheckState() +278
       MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior) +43
       MySql.Data.MySqlClient.MySqlCommand.ExecuteReader() +6
       Controls.SimpleCommand.ExecuteReader(String SQL) in ...:323
       Albums.GetImagesByAlbum(SimpleCommand Cmd, Int32 iAlbum, String Order, String Limit)
    in ...:13
       Forecast.Page_Load(Object sender, EventArgs e) in ...:70
       System.Web.UI.Control.OnLoad(EventArgs e) +99
       System.Web.UI.Control.LoadRecursive() +50
       System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean
    includeStagesAfterAsyncPoint) +627

    (Bug#53357)

  • Membership schema creation failed if the default schema collation was not Latin1. (Bug#53174)

  • In MySQL Connector/NET, the MySqlConnection.Abort() method contained a try...catch construct, with an empty catch block. This meant that any exception generated at this point would not be caught. (Bug#52769)

  • EventLog was not disposed in the SessionState provider. (Bug#52550)

  • The procedure cache affected the MySQL Connector/NET performance, reducing it by around 65%. This was due to unnecessary calls of String.Format(), related to debug logging. Even though the logging was disabled the string was still being formatted, resulting in impaired performance. (Bug#52475)

  • If FunctionsReturnString=true was used in the connection string, the decimal separator (according to locale) was not interpreted. (Bug#52187)

  • Periodically the session provider threw an SqlNullValueException exception. When this happened, the row within the my_aspnet_Sessions table had locked always set to '1'. The locked status never changed back to '0' and the user experienced the exception on every page, until their browser was closed and reopened (recreating a new sessionID), or the locked value was manually changed to '0'. (Bug#52175)

  • CHAR(36) columns were not recognized as GUIDs when used in views with entity models. (Bug#52085)

  • In MySQL Connector/NET, the LoadCharsetMap() function of the CharSetMap class set the following incorrect mapping:

    mapping.Add("latin1", new CharacterSet("latin1", 1));
    

    This meant that, for example, the Euro sign was not handled correctly.

    The correct mapping should have been:

    mapping.Add("latin1", new CharacterSet("windows-1252", 1));
    

    This is because MySQL's latin1 character set is the same as the windows-cp1252 character set and it extends the official ISO 8859-1 or IANA latin1. (Bug#51927)

  • Stored procedure enumeration code generated an error if a procedure was used in a dataset that did not return any resultsets. (Bug#50671)

  • When an application was subjected to increased concurrent load, MySQL Connector/NET generated the following error when calling stored procedures:

    A DataTable named \'Procedure Parameters\'
    already belongs to this DataSet.
          

    (Bug#49118)

  • The INSERT command was significantly slower with MySQL Connector/NET 6.x compared to 5.x, when compression was enabled. (Bug#48243)

  • When the connection string option “Connection Reset = True” was used, a connection reset used the previously used encoding for the subsequent authentication operation. This failed, for example, if UCS2 was used to read the last column before the reset. (Bug#47153)

  • Opening a connection in the Visual Studio Server Explorer and choosing to alter an existing routine required another authentication at the server. (Bug#44715)

  • When batching was used in MySqlDataAdapter, a connection was not opened automatically in MySqlDataAdapter.Update(). This resulted in an InvalidOperationException exception being generated, with the message text “connection must be valid and open”.

    MySQL Connector/NET has been changed to behave more like SQL Server: if the connection is closed, it is opened for the duration of update operation. (Bug#38411)

  • Database name was emitted into typed datasets. This prevented users using the configured default database. (Bug#33870)

D.4.2.3. Changes in MySQL Connector/NET 6.2.3 (10 April 2010 GA)

This release fixes bugs since 6.2.2.

Functionality added or changed:

  • MySQL Connector/NET has been changed to include MySqlDataReader.GetFieldType(string columnname). Further, MySqlDataReader.GetOrdinal() now includes the name of the column in the exception if the column is not found. (Bug#47467)

Bugs fixed:

  • A non-terminated string in SQL threw a CLR exception rather than a syntax exception. (Bug#51788)

  • When calling ExecuteNonQuery on a command object, the following exception occurred:

    Index and length must refer to a location within the string.
    Parameter name: length
    

    (Bug#51610)

  • Specifying a connection string where an option had no value generated an error, rather than the value being set to the default. For example, a connection string such as the following would result in an error:

    server=localhost;user=root;compress=;database=test;port=3306;password=123456;
    

    (Bug#51209)

  • The method Command.TrimSemicolons used StringBuilder, and therefore allocated memory for the query even if it did not need to be trimmed. This led to excessive memory consumption when executing a number of large queries. (Bug#51149)

  • MySqlCommand.Parameters.Clear() did not work. (Bug#50444)

  • When the MySqlScript.execute() method was called, the following exception was generated:

    InvalidOperationException : The CommandText property has not been properly initialized.

    (Bug#50344)

  • When using the Compact Framework the following exception occurred when attempting to connect to a MySQL Server:

    System.InvalidOperationException was unhandled
      Message="Timeouts are not supported on this stream."
    

    (Bug#50321)

  • Binary Columns were not displayed in the Query Builder of Visual Studio. (Bug#50171)

  • When the UpdateBatchSize property was set to a value greater than 1, only the first row was applied to the database. (Bug#50123)

  • When using table per type inheritance and listing the contents of the parent table, the result of the query was a list of child objects, even though there was no related child record with the same parent Id. (Bug#49850)

  • MySqlDataReader.GetUInt64 returned an incorrect value when reading a BIGINT UNSIGNED column containing a value greater than 2147483647. (Bug#49794)

  • A FormatException was generated when an empty string was returned from a stored function. (Bug#49642)

  • When trying to create stored procedures from a SQL script, a MySqlException was thrown when attempting to redefine the DELIMITER:

            MySql.Data.MySqlClient.MySqlException was unhandled
            Message="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 'DELIMITER' at line 1"
            Source="MySql.Data"
            ErrorCode=-2147467259
            Number=1064
            StackTrace:
            à MySql.Data.MySqlClient.MySqlStream.ReadPacket()
            à MySql.Data.MySqlClient.NativeDriver.ReadResult(UInt64& affectedRows, Int64&
            lastInsertId)
            à MySql.Data.MySqlClient.MySqlDataReader.GetResultSet()
            à MySql.Data.MySqlClient.MySqlDataReader.NextResult()
            à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
            à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader()
            à MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()
          à MySql.Data.MySqlClient.MySqlScript.Execute()

    Note: The MySqlScript class has been fixed to support the delimiter statement as it is found in SQL scripts. (Bug#46429)

  • Calling a User Defined Function using Entity SQL in the Entity Framework caused a NullReferenceException. (Bug#45277)

  • A connection string set in web.config could not be reused after Visual Studio 2008 Professional was shut down. It continued working for the existing controls, but did not work for new controls added. (Bug#41629)

D.4.2.4. Changes in MySQL Connector/NET 6.2.2 (22 December 2009 GA)

First GA release of 6.2. This release fixes bugs since 6.2.1.

Bugs fixed:

  • When adding a data set in Visual Studio 2008, the following error was generated:

    Relations couldn't be addded. Column 'REFERENCED_TABLE_CATALOG' does not belong to table.

    This was due to a 'REFERENCED_TABLE_CATALOG' column not being included in the foreign keys collection. (Bug#48974)

  • Attempting to execute a load data local infile on a file where the user did not have write permissions, or the file was open in an editor gave an access denied error. (Bug#48944)

  • The method MySqlDataReader.GetSchemaTable() returned 0 in the NumericPrecision field for decimal and newdecimal columns. (Bug#48171)

  • MySQL Connector/NET generated an invalid operation exception during a transaction rollback:

    System.InvalidOperationException: Connection must be valid and open to rollback
    transaction
       at MySql.Data.MySqlClient.MySqlTransaction.Rollback()
       at MySql.Data.MySqlClient.MySqlConnection.CloseFully()
       at
    MySql.Data.MySqlClient.MySqlPromotableTransaction.System.Transactions.IPromotableSinglePhaseNotification.Rollback(SinglePhaseEnlistment
    singlePhaseEnlistment)
    ...
    

    (Bug#35330)

  • Connection objects were not garbage collected when not in use. (Bug#31996)

D.4.2.5. Changes in MySQL Connector/NET 6.2.1 (16 November 2009 beta)

This release fixes bugs since 6.2.0.

Functionality added or changed:

  • The MySqlParameter class now has a property named PossibleValues. This property is NULL unless the parameter is created by MySqlCommandBuilder.DeriveParameters. Further, it will be NULL unless the parameter is of type enum or set - in this case it will be a list of strings that are the possible values for the column. This feature is designed as an aid to the developer. (Bug#48586)

  • Prior to MySQL Connector/NET 6.2, MySqlCommand.CommandTimeout included user processing time, that is processing time not related to direct use of the connector. Timeout was implemented through a .NET Timer, that triggered after CommandTimeout seconds.

    MySQL Connector/NET 6.2 introduced timeouts that are aligned with how Microsoft handles SqlCommand.CommandTimeout. This property is the cumulative timeout for all network reads and writes during command execution or processing of the results. A timeout can still occur in the MySqlReader.Read method after the first row is returned, and does not include user processing time, only IO operations.

    Further details on this can be found in the relevant Microsoft documentation.

  • Starting with MySQL Connector/NET 6.2, there is a background job that runs every three minutes and removes connections from pool that have been idle (unused) for more than three minutes. The pool cleanup frees resources on both client and server side. This is because on the client side every connection uses a socket, and on the server side every connection uses a socket and a thread.

    Prior to this change, connections were never removed from the pool, and the pool always contained the peak number of open connections. For example, a web application that peaked at 1000 concurrent database connections would consume 1000 threads and 1000 open sockets at the server, without ever freeing up those resources from the connection pool.

  • MySQL Connector/NET now supports the processing of certificates when connecting to an SSL-enabled MySQL Server. For further information see the connection string option SSL Mode in the section Section 21.2.6, “Connector/NET Connection String Options Reference” and the tutorial Section 21.2.4.7, “Tutorial: Using SSL with MySQL Connector/NET”.

Bugs fixed:

  • Cloning of MySqlCommand was not typesafe. To clone a MySqlCommand it was necessary to do:

            MySqlCommand clone = (MySqlCommand)((ICloneable)comm).Clone();
          

    MySQL Connector/NET was changed so that it was possible to do:

            MySqlCommand clone = comm.Clone();
          

    (Bug#48460)

  • When used, the Encrypt connection string option caused a “Keyword not supported” exception to be generated.

    This option is in fact obsolete, and the option SSL Mode should be used instead. Although the Encrypt option has been fixed so that it does not generate an exception, it will be removed completely in version 6.4. (Bug#48290)

  • When building the MySql.Data project with .NET Framework 3.5 installed, the following build output was displayed:

    Project file contains ToolsVersion="4.0", which is not supported by this version of
    MSBuild. Treating the project as if it had ToolsVersion="3.5".
    

    The project had been created using the .NET Framework 4.0, which was beta, instead of using the 3.5 framework. (Bug#48271)

  • It was not possible to retrieve a value from a MySQL server table, if the value was larger than that supported by the .NET type System.Decimal.

    MySQL Connector/NET was changed to expose the MySqlDecimal type, along with the supporting method GetMySqlDecimal. (Bug#48100)

  • An entity model created from a schema containing a table with a column of type UNSIGNED BIGINT and a view of the table did not behave correctly. When an entity was created and mapped to the view, the column that was of type UNSIGNED BIGINT was displayed as BIGINT. (Bug#47872)

  • MySQL Connector/NET session support did not work with MySQL Server versions prior to 5.0, as the Session Provider used a call to TIMESTAMPDIFF, which was not available on servers prior to 5.0. (Bug#47219)

D.4.2.6. Changes in MySQL Connector/NET 6.2.0 (21 October 2009 alpha)

The first alpha release of 6.2.

Bugs fixed:

  • When using a BINARY(16) column to represent a GUID and having specified “old guids = true” in the connection string, the values were returned correctly until a null value was encountered in that field. After the null value was encountered a format exception was thrown with the following message:

    Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
    

    (Bug#47928)

  • The Session Provider created invalid “session expires” on a random basis.

    This was due to the fact that the Session Provider was incorrectly reading from the root web.config, rather than from the application specific web.config. (Bug#47815)

  • When loading the MySQLClient-mono.sln file included with the Connector/NET source into Mono Develop, the following error occurred:

    /home/tbedford/connector-net-src/6.1/MySQLClient-mono.sln(22):
    Unsupported or unrecognized project:
    '/home/tbedford/connector-net-src/6.1/Installer/Installer.wixproj'
    

    If the file was modified to remove this problem, then attempting to build the solution generated the following error:

    /home/tbedford/connector-net-src/6.1/MySql.Data/Provider/Source/Connection.cs(280,46):
    error CS0115: `MySql.Data.MySqlClient.MySqlConnection.DbProviderFactory' is marked as an
    override but no suitable property found to override
    

    (Bug#47048)

D.4.3. Changes in MySQL Connector/NET Version 6.1.x

D.4.3.1. Changes in MySQL Connector/NET 6.1.6 (Not yet released GA)

This release fixes bugs since 6.1.5.

Bugs fixed:

  • Setting MySqlCommand.CommandTimeout to 0 had no effect. It should have resulted in an infinite timeout. (Bug#57265)

  • When performing a row-by-row update, only the first row was updated and all other rows were ignored. (Bug#57092)

  • Setting the Default Command Timeout connection string option had no effect. (Bug#56806)

  • When an output parameter was declared as type MySqlDbType.Bit, it failed to return with the correct value. (Bug#56756)

  • MySqlHelper.ExecuteReader did not include an overload accepting MySqlParameter objects when using a MySqlConnection. However, MySqlHelper did include an overload for MySqlParameter objects when using a string object containing the connection string to the database. (Bug#56755)

D.4.3.2. Changes in MySQL Connector/NET 6.1.5 (30 August 2010 GA)

This release fixes bugs since 6.1.4.

Bugs fixed:

  • The calculation of lockAge in the Session Provider sometimes generated a System.Data.SqlTypes.SqlNullValueException. (Bug#55701)

  • Attempting to read Double.MinValue from a DOUBLE column in MySQL table generated the following exception:

    System.OverflowException : Value was either too large or too small for a Double.
    
    --OverflowException
    at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo
    numfmt)
    at MySql.Data.Types.MySqlDouble.MySql.Data.Types.IMySqlValue.ReadValue(MySqlPacket
    packet, Int64 length, Boolean nullVal)
    at MySql.Data.MySqlClient.NativeDriver.ReadColumnValue(Int32 index, MySqlField field,
    IMySqlValue valObject)
    at MySql.Data.MySqlClient.ResultSet.ReadColumnData(Boolean outputParms)
    at MySql.Data.MySqlClient.ResultSet.NextRow(CommandBehavior behavior)
    at MySql.Data.MySqlClient.MySqlDataReader.Read()
    

    (Bug#55644)

  • If using MySQL Server 5.0.x it was not possible to alter stored routines in Visual Studio. If the stored routine was clicked, and the context sensitive menu option, Alter Routine, selected, the following error was generated:

    Unable to load object with error: Object reference not
    set to an instance of an object
    

    (Bug#55170)

  • MySqlDataAdapter.Update() generated concurrency violations for custom stored procedure driven update commands that used UpdateRowSource.FirstReturnedRecord. (Bug#54895)

  • Several calls to datadapter.Update() with intervening changes to DataTable resulted in ConcurrencyException exceptions being generated. (Bug#54863)

  • The icon for the MySQL Web Configuration Tool was not displayed in Visual Studio for Web Application Projects. (Bug#54571)

  • The MySqlHelper object did not have an overloaded version of the ExecuteReader method that accepted a MySqlConnection object. (Bug#54570)

  • If MySqlDataAdapter was used with an INSERT command where the VALUES clause contained an expression with parentheses in it, and set the adapter.UpdateBatchSize parameter to be greater than one, then the call to adpater.Update either generated an exception or failed to batch the commands, executing each insert individually. (Bug#54386)

  • The method MySql.Data.Common.QueryNormalizer.CollapseValueList generated an ArgumentOutOfRangeException. (Bug#54152, Bug#53865)

  • Garbage Collector disposal of a MySqlConnection object caused the following exception:

    System.IO.EndOfStreamException: Attempted to read past the end of the stream.
    MySql.Data.MySqlClient.MySqlStream.ReadFully(Stream stream, Byte[] buffer, Int32 offset,
    Int32 count)
    MySql.Data.MySqlClient.MySqlStream.LoadPacket()
    Outer Exception Reading from the stream has failed.
    ...

    (Bug#53457)

  • MySQL Connector/NET did not throw an EndOfStreamException exception when net_write_timeout was exceeded. (Bug#53439)

  • After a timeout exception, if an attempt was made to reuse a connection returned to the connection pool the following exception was generated:

    [MySqlException (0x80004005): There is already an open DataReader associated with this
    Connection which must be closed first.]
       MySql.Data.MySqlClient.MySqlCommand.CheckState() +278
       MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior) +43
       MySql.Data.MySqlClient.MySqlCommand.ExecuteReader() +6
       Controls.SimpleCommand.ExecuteReader(String SQL) in ...:323
       Albums.GetImagesByAlbum(SimpleCommand Cmd, Int32 iAlbum, String Order, String Limit)
    in ...:13
       Forecast.Page_Load(Object sender, EventArgs e) in ...:70
       System.Web.UI.Control.OnLoad(EventArgs e) +99
       System.Web.UI.Control.LoadRecursive() +50
       System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean
    includeStagesAfterAsyncPoint) +627

    (Bug#53357)

  • Membership schema creation failed if the default schema collation was not Latin1. (Bug#53174)

  • EventLog was not disposed in the SessionState provider. (Bug#52550)

  • CHAR(36) columns were not recognized as GUIDs when used in views with entity models. (Bug#52085)

  • Stored procedure enumeration code generated an error if a procedure was used in a dataset that did not return any resultsets. (Bug#50671)

  • When an application was subjected to increased concurrent load, MySQL Connector/NET generated the following error when calling stored procedures:

    A DataTable named \'Procedure Parameters\'
    already belongs to this DataSet.
          

    (Bug#49118)

  • The INSERT command was significantly slower with MySQL Connector/NET 6.x compared to 5.x, when compression was enabled. (Bug#48243)

  • When the connection string option “Connection Reset = True” was used, a connection reset used the previously used encoding for the subsequent authentication operation. This failed, for example, if UCS2 was used to read the last column before the reset. (Bug#47153)

  • Opening a connection in the Visual Studio Server Explorer and choosing to alter an existing routine required another authentication at the server. (Bug#44715)

  • When batching was used in MySqlDataAdapter, a connection was not opened automatically in MySqlDataAdapter.Update(). This resulted in an InvalidOperationException exception being generated, with the message text “connection must be valid and open”.

    MySQL Connector/NET has been changed to behave more like SQL Server: if the connection is closed, it is opened for the duration of update operation. (Bug#38411)

  • Database name was emitted into typed datasets. This prevented users using the configured default database. (Bug#33870)

D.4.3.3. Changes in MySQL Connector/NET 6.1.4 (28 April 2010 GA)

This release fixes bugs since 6.1.3.

Functionality added or changed:

  • Procedure cacheing had a problem whereby if you created a procedure, dropped it, and recreated it with a different number of parameters an exception was generated.

    MySQL Connector/NET has been changed so that if the procedure is recreated with a different number of parameters, it will still be recognized. (Bug#52562)

  • MySQL Connector/NET has been changed to include MySqlDataReader.GetFieldType(string columnname). Further, MySqlDataReader.GetOrdinal() now includes the name of the column in the exception if the column is not found. (Bug#47467)

Bugs fixed:

  • In MySQL Connector/NET, the MySqlConnection.Abort() method contained a try...catch construct, with an empty catch block. This meant that any exception generated at this point would not be caught. (Bug#52769)

  • If FunctionsReturnString=true was used in the connection string, the decimal separator (according to locale) was not interpreted. (Bug#52187)

  • In MySQL Connector/NET, the LoadCharsetMap() function of the CharSetMap class set the following incorrect mapping:

    mapping.Add("latin1", new CharacterSet("latin1", 1));
    

    This meant that, for example, the Euro sign was not handled correctly.

    The correct mapping should have been:

    mapping.Add("latin1", new CharacterSet("windows-1252", 1));
    

    This is because MySQL's latin1 character set is the same as the windows-cp1252 character set and it extends the official ISO 8859-1 or IANA latin1. (Bug#51927)

  • A non-terminated string in SQL threw a CLR exception rather than a syntax exception. (Bug#51788)

  • When calling ExecuteNonQuery on a command object, the following exception occurred:

    Index and length must refer to a location within the string.
    Parameter name: length
    

    (Bug#51610)

  • The method Command.TrimSemicolons used StringBuilder, and therefore allocated memory for the query even if it did not need to be trimmed. This led to excessive memory consumption when executing a number of large queries. (Bug#51149)

  • MySqlCommand.Parameters.Clear() did not work. (Bug#50444)

  • When the MySqlScript.execute() method was called, the following exception was generated:

    InvalidOperationException : The CommandText property has not been properly initialized.

    (Bug#50344)

  • Binary Columns were not displayed in the Query Builder of Visual Studio. (Bug#50171)

  • When the UpdateBatchSize property was set to a value greater than 1, only the first row was applied to the database. (Bug#50123)

  • When using table per type inheritance and listing the contents of the parent table, the result of the query was a list of child objects, even though there was no related child record with the same parent Id. (Bug#49850)

  • MySqlDataReader.GetUInt64 returned an incorrect value when reading a BIGINT UNSIGNED column containing a value greater than 2147483647. (Bug#49794)

  • A FormatException was generated when an empty string was returned from a stored function. (Bug#49642)

  • When adding a data set in Visual Studio 2008, the following error was generated:

    Relations couldn't be addded. Column 'REFERENCED_TABLE_CATALOG' does not belong to table.

    This was due to a 'REFERENCED_TABLE_CATALOG' column not being included in the foreign keys collection. (Bug#48974)

  • Attempting to execute a load data local infile on a file where the user did not have write permissions, or the file was open in an editor gave an access denied error. (Bug#48944)

  • The method MySqlDataReader.GetSchemaTable() returned 0 in the NumericPrecision field for decimal and newdecimal columns. (Bug#48171)

  • When trying to create stored procedures from a SQL script, a MySqlException was thrown when attempting to redefine the DELIMITER:

            MySql.Data.MySqlClient.MySqlException was unhandled
            Message="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 'DELIMITER' at line 1"
            Source="MySql.Data"
            ErrorCode=-2147467259
            Number=1064
            StackTrace:
            à MySql.Data.MySqlClient.MySqlStream.ReadPacket()
            à MySql.Data.MySqlClient.NativeDriver.ReadResult(UInt64& affectedRows, Int64&
            lastInsertId)
            à MySql.Data.MySqlClient.MySqlDataReader.GetResultSet()
            à MySql.Data.MySqlClient.MySqlDataReader.NextResult()
            à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
            à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader()
            à MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()
          à MySql.Data.MySqlClient.MySqlScript.Execute()

    Note: The MySqlScript class has been fixed to support the delimiter statement as it is found in SQL scripts. (Bug#46429)

  • Calling a User Defined Function using Entity SQL in the Entity Framework caused a NullReferenceException. (Bug#45277)

  • A connection string set in web.config could not be reused after Visual Studio 2008 Professional was shut down. It continued working for the existing controls, but did not work for new controls added. (Bug#41629)

D.4.3.4. Changes in MySQL Connector/NET 6.1.3 (16 November 2009 GA)

This release fixes bugs since 6.1.2.

Bugs fixed:

  • Cloning of MySqlCommand was not typesafe. To clone a MySqlCommand it was necessary to do:

            MySqlCommand clone = (MySqlCommand)((ICloneable)comm).Clone();
          

    MySQL Connector/NET was changed so that it was possible to do:

            MySqlCommand clone = comm.Clone();
          

    (Bug#48460)

  • When building the MySql.Data project with .NET Framework 3.5 installed, the following build output was displayed:

    Project file contains ToolsVersion="4.0", which is not supported by this version of
    MSBuild. Treating the project as if it had ToolsVersion="3.5".
    

    The project had been created using the .NET Framework 4.0, which was beta, instead of using the 3.5 framework. (Bug#48271)

  • If MySqlConnection.GetSchema was called for "Indexes" on a table named “b`a`d” as follows:

    DataTable schemaPrimaryKeys = connection.GetSchema(
      "Indexes",
      new string[] { null, schemaName, "b`a`d"});
    

    Then the following exception was generated:

    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 'a`d`' at line 1
    

    (Bug#48101)

  • It was not possible to retrieve a value from a MySQL server table, if the value was larger than that supported by the .NET type System.Decimal.

    MySQL Connector/NET was changed to expose the MySqlDecimal type, along with the supporting method GetMySqlDecimal. (Bug#48100)

  • For some character sets such as UTF-8, a CHAR column would sometimes be incorrectly interpreted as a GUID by MySQL Connector/NET.

    MySQL Connector/NET was changed so that a column would only be interpreted as a GUID if it had a character length of 36, as opposed to a byte length of 36. (Bug#47985)

  • When using a BINARY(16) column to represent a GUID and having specified “old guids = true” in the connection string, the values were returned correctly until a null value was encountered in that field. After the null value was encountered a format exception was thrown with the following message:

    Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
    

    (Bug#47928)

  • An entity model created from a schema containing a table with a column of type UNSIGNED BIGINT and a view of the table did not behave correctly. When an entity was created and mapped to the view, the column that was of type UNSIGNED BIGINT was displayed as BIGINT. (Bug#47872)

  • The Session Provider created invalid “session expires” on a random basis.

    This was due to the fact that the Session Provider was incorrectly reading from the root web.config, rather than from the application specific web.config. (Bug#47815)

  • Attempting to build MySQL Connector/NET 6.1 MySQL.Data from source code on Windows failed with the following error:

    ...\clones\6.1\MySql.Data\Provider\Source\NativeDriver.cs(519,29): error CS0122:
    'MySql.Data.MySqlClient.MySqlPacket.MySqlPacket()' is inaccessible due to its protection level
    

    (Bug#47354)

  • When tables were auto created for the Session State Provider they were set to use the MySQL Server's default collation, rather than the default collation set for the containing database. (Bug#47332)

  • When loading the MySQLClient-mono.sln file included with the Connector/NET source into Mono Develop, the following error occurred:

    /home/tbedford/connector-net-src/6.1/MySQLClient-mono.sln(22):
    Unsupported or unrecognized project:
    '/home/tbedford/connector-net-src/6.1/Installer/Installer.wixproj'
    

    If the file was modified to remove this problem, then attempting to build the solution generated the following error:

    /home/tbedford/connector-net-src/6.1/MySql.Data/Provider/Source/Connection.cs(280,46):
    error CS0115: `MySql.Data.MySqlClient.MySqlConnection.DbProviderFactory' is marked as an
    override but no suitable property found to override
    

    (Bug#47048)

D.4.3.5. Changes in MySQL Connector/NET 6.1.2 (08 September 2009 GA)

This is the first GA release of 6.1.

Bugs fixed:

  • The MySQL Connector/NET Session State Provider truncated session data to 64KB, due to its column types being set to BLOB. (Bug#47339)

  • MySQL Connector/NET generated the following exception when using the Session State provider:

    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 'MINUTEWHERE SessionId =
    'dtmgga55x35oi255nrfrxe45' AND ApplicationId = 1 AND Loc' at line 1 
    Description: An unhandled exception occurred during the execution of the current web
    request. Please review the stack trace for more information about the error and where it
    originated in the code. 
    
    Exception Details: MySql.Data.MySqlClient.MySqlException: 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 'MINUTEWHERE SessionId = 'dtmgga55x35oi255nrfrxe45' AND ApplicationId =
    1 AND Loc' at line 1
          

    (Bug#46939)

  • If an error occurred during connection to a MySQL Server, deserializing the error message from the packet buffer caused a NullReferenceException to be thrown. When the method MySqlPacket::ReadString() attempted to retrieve the error message, the following line of code threw the exception:

            string s = encoding.GetString(bits, (int)buffer.Position, end - (int)buffer.Position);
          

    This was due to the fact that the encoding field had not been initialized correctly. (Bug#46844)

  • Input parameters were missing from Stored Procedures when using them with ADO.NET Data Entities. (Bug#44985)

  • MySQL Connector/NET did not time out correctly. The command timeout was set to 30 secs, but MySQL Connector/NET hung for several hours. (Bug#43761)

D.4.3.6. Changes in MySQL Connector/NET 6.1.1 (20 August 2009 beta)

This is the first Beta release of 6.1.

Bugs fixed:

  • In the MySqlDataReader class the GetSByte function returned a byte value instead of an sbyte value. (Bug#46620)

  • The MySQL Connector/NET Profile Provider, MySql.Web.Profile.MySQLProfileProvider, generated an error when running on Mono. When an attempt was made to save a string in Profile.Name the string was not saved to the my_aspnet_Profiles table. If an attempt was made to force the save with Profile.Save() the following error was generated:

            Server Error in '/mono' Application
    
            --------------------------------------------------------------------------------
    
            The requested feature is not implemented.
            Description: HTTP 500. Error processing request.
    
            Stack Trace: 
    
            System.NotImplementedException: The requested feature is not implemented.
            at MySql.Data.MySqlClient.MySqlConnection.EnlistTransaction
            (System.Transactions.Transaction transaction) [0x00000] 
            at MySql.Data.MySqlClient.MySqlConnection.Open () [0x00000] 
            at MySql.Web.Profile.MySQLProfileProvider.SetPropertyValues
            (System.Configuration.SettingsContext context,
            System.Configuration.SettingsPropertyValueCollection collection) [0x00000] 
            
    
            --------------------------------------------------------------------------------
            Version information: Mono Version: 2.0.50727.1433; ASP.NET Version: 2.0.50727.1433
          

    (Bug#46375)

  • An exception was generated when using TIMESTAMP columns with the Entity Framework. (Bug#46311)

  • MySQL Connector/NET sometimes hung, without generating an exception. This happened if a read from a stream failed returning a 0, causing the code in LoadPacket() to enter an infinite loop. (Bug#46308)

  • When using MySQL Connector/NET 6.0.4 and a MySQL Server 4.1 an exception was generated when trying to execute:

            connection.GetSchema("Columns", ...);
          

    The exception generated was:

            'connection.GetSchema("Columns")' threw an exception of type
            'System.ArgumentException'System.Data.DataTable {System.ArgumentException}
            base{"Input string was not in a correct format.Couldn't store <'Select'> in
            NUMERIC_PRECISION Column.  Expected type is UInt64."}System.Exception
            {System.ArgumentException}
          

    (Bug#46270)

  • The MySQL Connector/NET method StoredProcedure.GetParameters(string) ignored the programmer's setting of the UseProcedureBodies option. This broke any application for which the application's parameter names did not match the parameter names in the Stored Procedure, resulting in an ArgumentException with the message “Parameter 'foo' not found in the collection.” and the following stack trace:

            MySql.Data.dll!MySql.Data.MySqlClient.MySqlParameterCollection.GetParameterFlexible(stri
            ng parameterName = "pStart", bool throwOnNotFound = true) Line 459C#
            MySql.Data.dll!MySql.Data.MySqlClient.StoredProcedure.Resolve() Line 157 + 0x25
            bytesC#
            MySql.Data.dll!MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(System.Data.CommandBeha
            vior behavior = SequentialAccess) Line 405 + 0xb bytesC#
            MySql.Data.dll!MySql.Data.MySqlClient.MySqlCommand.ExecuteDbDataReader(System.Data.Comma
            ndBehavior behavior = SequentialAccess) Line 884 + 0xb bytesC#
            System.Data.dll!System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(System
            .Data.CommandBehavior behavior) + 0xb bytes
            System.Data.dll!System.Data.Common.DbDataAdapter.FillInternal(System.Data.DataSet
            dataset = {System.Data.DataSet}, System.Data.DataTable[] datatables = null, int
            startRecord = 0, int maxRecords = 0, string srcTable = "Table", System.Data.IDbCommand
            command = {MySql.Data.MySqlClient.MySqlCommand}, System.Data.CommandBehavior behavior) +
            0x83 bytes
            System.Data.dll!System.Data.Common.DbDataAdapter.Fill(System.Data.DataSet dataSet, int
            startRecord, int maxRecords, string srcTable, System.Data.IDbCommand command,
            System.Data.CommandBehavior behavior) + 0x120 bytes
            System.Data.dll!System.Data.Common.DbDataAdapter.Fill(System.Data.DataSet dataSet) +
            0x5f bytes
          

    (Bug#46213)

  • Conversion of MySQL TINYINT(1) to boolean failed. (Bug#46205, Bug#46359, Bug#41953)

  • When populating a MySQL database table in Visual Studio using the Table Editor, if a VARCHAR(10) column was changed to a VARCHAR(20) column an exception was generated:

            SystemArgumentException: DataGridViewComboBoxCell value is not valid.
          To replace this default dialog please handle the DataError Event.

    (Bug#46100)

  • The Entity Framework provider was not calling DBSortExpression correctly when the Skip and Take methods were used, such as in the following statement:

            TestModel.tblquarantine.OrderByDescending(q => q.MsgDate).Skip(100).Take(100).ToList();
          

    This resulted in the data being unsorted. (Bug#45723)

  • The MySQL Connector/NET 6.0.4 installer failed with an error. The error message generated was:

            There is a problem with this Windows Installer package. A DLL required for this
            install to complete could not be run. Contact your support personnel or package vendor.
          

    When OK was clicked to acknowledge the error the installer exited. (Bug#45474)

  • Calling the Entity Framework SaveChanges() method of any MySQL ORM Entity with a column type TIME, generated an error message:

    Unknown PrimitiveKind Time

    (Bug#45457)

  • Insert into two tables failed when using the Entity Framework. The exception generated was:

            The value given is not an instance of type 'Edm.Int32'
          

    (Bug#45077)

  • Errors occurred when using the Entity Framework with cultures that used a comma as the decimal separator. This was because the formatting for SINGLE, DOUBLE and DECIMAL values was not handled correctly. (Bug#44455)

  • When attempting to connect to MySQL using the Compact Framework version of MySQL Connector/NET, an IndexOutOfRangeException exception was generated on trying to open the connection. (Bug#43736)

  • When reading data, such as with a MySqlDataAdapter on a MySqlConnection, MySQL Connector/NET could potentially enter an infinite loop in CompressedStream.ReadNextpacket() if compression was enabled. (Bug#43678)

  • An error occurred when building MySQL Connector/NET from source code checked out from the public SVN repository. This happened on Linux using Mono and Nant. The Mono JIT compiler version was 1.2.6.0. The Nant version was 0.85.

    When an attempt was made to build (for example) the MySQL Connector/NET 5.2 branch using the command:

            $ nant -buildfile:Client.build
          

    The following error occurred:

            BUILD FAILED
    
            Error loading buildfile.
            Encoding name 'Windows-1252' not supported.
            Parameter name: name
          

    (Bug#42411)

  • MySQL Connector/NET CHM documentation stated that MySQL Server 3.23 was supported. (Bug#42110)

  • In the case of long network inactivity, especially when connection pooling was used, connections were sometimes dropped, for example, by firewalls.

    Note: The bugfix introduced a new keepalive parameter, which prevents disconnects by sending an empty TCP packet after a specified timeout. (Bug#40684)

  • Calling a Stored Procedure with an output parameter through MySQL Connector/NET resulted in a memory leak. Calling the same Stored Procedure without an output parameter did not result in a memory leak. (Bug#36027)

D.4.3.7. Changes in MySQL Connector/NET 6.1.0 (15 July 2009 alpha)

This is the first Alpha release of 6.1.

Functionality added or changed:

  • Changed GUID type - The backend representation of a guid type has been changed to be CHAR(36). This is so you can use the server UUID() function to populate a GUID table. UUID generates a 36 character string. Developers of older applications can add old guids=true to the connection string and the old BINARY(16) type will be used instead.

  • Support for native output parameters - This is supported when connected to a server that supports native output parameters. This includes servers as of 5.5.3 and 6.0.8.

  • Session State Provider - This enables you to store the state of your website in a MySQL server.

  • Website Configuration Dialog - This is a new wizard that is activated by clicking a button on the toolbar at the top of the Visual Studio Solution Explorer. It works in conjunction with the ASP.Net administration pages, making it easier to activate and set advanced options for the different MySQL web providers included.

D.4.4. Changes in MySQL Connector/NET Version 6.0.x

D.4.4.1. Changes in MySQL Connector/NET 6.0.8 (Not yet released)

Fixes bugs since 6.0.7.

Bugs fixed:

  • Setting MySqlCommand.CommandTimeout to 0 had no effect. It should have resulted in an infinite timeout. (Bug#57265)

  • When performing a row-by-row update, only the first row was updated and all other rows were ignored. (Bug#57092)

  • Setting the Default Command Timeout connection string option had no effect. (Bug#56806)

  • When an output parameter was declared as type MySqlDbType.Bit, it failed to return with the correct value. (Bug#56756)

D.4.4.2. Changes in MySQL Connector/NET 6.0.7 (30 August 2010)

Fixes bugs since 6.0.6.

Bugs fixed:

  • Attempting to read Double.MinValue from a DOUBLE column in MySQL table generated the following exception:

    System.OverflowException : Value was either too large or too small for a Double.
    
    --OverflowException
    at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo
    numfmt)
    at MySql.Data.Types.MySqlDouble.MySql.Data.Types.IMySqlValue.ReadValue(MySqlPacket
    packet, Int64 length, Boolean nullVal)
    at MySql.Data.MySqlClient.NativeDriver.ReadColumnValue(Int32 index, MySqlField field,
    IMySqlValue valObject)
    at MySql.Data.MySqlClient.ResultSet.ReadColumnData(Boolean outputParms)
    at MySql.Data.MySqlClient.ResultSet.NextRow(CommandBehavior behavior)
    at MySql.Data.MySqlClient.MySqlDataReader.Read()
    

    (Bug#55644)

  • MySqlDataAdapter.Update() generated concurrency violations for custom stored procedure driven update commands that used UpdateRowSource.FirstReturnedRecord. (Bug#54895)

  • Several calls to datadapter.Update() with intervening changes to DataTable resulted in ConcurrencyException exceptions being generated. (Bug#54863)

  • The MySqlHelper object did not have an overloaded version of the ExecuteReader method that accepted a MySqlConnection object. (Bug#54570)

  • If MySqlDataAdapter was used with an INSERT command where the VALUES clause contained an expression with parentheses in it, and set the adapter.UpdateBatchSize parameter to be greater than one, then the call to adpater.Update either generated an exception or failed to batch the commands, executing each insert individually. (Bug#54386)

  • The method MySql.Data.Common.QueryNormalizer.CollapseValueList generated an ArgumentOutOfRangeException. (Bug#54152, Bug#53865)

  • Garbage Collector disposal of a MySqlConnection object caused the following exception:

    System.IO.EndOfStreamException: Attempted to read past the end of the stream.
    MySql.Data.MySqlClient.MySqlStream.ReadFully(Stream stream, Byte[] buffer, Int32 offset,
    Int32 count)
    MySql.Data.MySqlClient.MySqlStream.LoadPacket()
    Outer Exception Reading from the stream has failed.
    ...

    (Bug#53457)

  • After a timeout exception, if an attempt was made to reuse a connection returned to the connection pool the following exception was generated:

    [MySqlException (0x80004005): There is already an open DataReader associated with this
    Connection which must be closed first.]
       MySql.Data.MySqlClient.MySqlCommand.CheckState() +278
       MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior) +43
       MySql.Data.MySqlClient.MySqlCommand.ExecuteReader() +6
       Controls.SimpleCommand.ExecuteReader(String SQL) in ...:323
       Albums.GetImagesByAlbum(SimpleCommand Cmd, Int32 iAlbum, String Order, String Limit)
    in ...:13
       Forecast.Page_Load(Object sender, EventArgs e) in ...:70
       System.Web.UI.Control.OnLoad(EventArgs e) +99
       System.Web.UI.Control.LoadRecursive() +50
       System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean
    includeStagesAfterAsyncPoint) +627

    (Bug#53357)

  • Membership schema creation failed if the default schema collation was not Latin1. (Bug#53174)

  • EventLog was not disposed in the SessionState provider. (Bug#52550)

  • Stored procedure enumeration code generated an error if a procedure was used in a dataset that did not return any resultsets. (Bug#50671)

  • When an application was subjected to increased concurrent load, MySQL Connector/NET generated the following error when calling stored procedures:

    A DataTable named \'Procedure Parameters\'
    already belongs to this DataSet.
          

    (Bug#49118)

  • The INSERT command was significantly slower with MySQL Connector/NET 6.x compared to 5.x, when compression was enabled. (Bug#48243)

  • When the connection string option “Connection Reset = True” was used, a connection reset used the previously used encoding for the subsequent authentication operation. This failed, for example, if UCS2 was used to read the last column before the reset. (Bug#47153)

  • Opening a connection in the Visual Studio Server Explorer and choosing to alter an existing routine required another authentication at the server. (Bug#44715)

  • When batching was used in MySqlDataAdapter, a connection was not opened automatically in MySqlDataAdapter.Update(). This resulted in an InvalidOperationException exception being generated, with the message text “connection must be valid and open”.

    MySQL Connector/NET has been changed to behave more like SQL Server: if the connection is closed, it is opened for the duration of update operation. (Bug#38411)

  • Database name was emitted into typed datasets. This prevented users using the configured default database. (Bug#33870)

D.4.4.3. Changes in MySQL Connector/NET 6.0.6 (28 April 2010)

Fixes bugs since 6.0.5.

Functionality added or changed:

  • Procedure cacheing had a problem whereby if you created a procedure, dropped it, and recreated it with a different number of parameters an exception was generated.

    MySQL Connector/NET has been changed so that if the procedure is recreated with a different number of parameters, it will still be recognized. (Bug#52562)

  • MySQL Connector/NET has been changed to include MySqlDataReader.GetFieldType(string columnname). Further, MySqlDataReader.GetOrdinal() now includes the name of the column in the exception if the column is not found. (Bug#47467)

Bugs fixed:

  • If using MySQL Server 5.0.x it was not possible to alter stored routines in Visual Studio. If the stored routine was clicked, and the context sensitive menu option, Alter Routine, selected, the following error was generated:

    Unable to load object with error: Object reference not
    set to an instance of an object
    

    (Bug#55170)

  • In MySQL Connector/NET, the MySqlConnection.Abort() method contained a try...catch construct, with an empty catch block. This meant that any exception generated at this point would not be caught. (Bug#52769)

  • If FunctionsReturnString=true was used in the connection string, the decimal separator (according to locale) was not interpreted. (Bug#52187)

  • In MySQL Connector/NET, the LoadCharsetMap() function of the CharSetMap class set the following incorrect mapping:

    mapping.Add("latin1", new CharacterSet("latin1", 1));
    

    This meant that, for example, the Euro sign was not handled correctly.

    The correct mapping should have been:

    mapping.Add("latin1", new CharacterSet("windows-1252", 1));
    

    This is because MySQL's latin1 character set is the same as the windows-cp1252 character set and it extends the official ISO 8859-1 or IANA latin1. (Bug#51927)

  • A non-terminated string in SQL threw a CLR exception rather than a syntax exception. (Bug#51788)

  • When calling ExecuteNonQuery on a command object, the following exception occurred:

    Index and length must refer to a location within the string.
    Parameter name: length
    

    (Bug#51610)

  • The method Command.TrimSemicolons used StringBuilder, and therefore allocated memory for the query even if it did not need to be trimmed. This led to excessive memory consumption when executing a number of large queries. (Bug#51149)

  • MySqlCommand.Parameters.Clear() did not work. (Bug#50444)

  • When the MySqlScript.execute() method was called, the following exception was generated:

    InvalidOperationException : The CommandText property has not been properly initialized.

    (Bug#50344)

  • Binary Columns were not displayed in the Query Builder of Visual Studio. (Bug#50171)

  • When the UpdateBatchSize property was set to a value greater than 1, only the first row was applied to the database. (Bug#50123)

  • When using table per type inheritance and listing the contents of the parent table, the result of the query was a list of child objects, even though there was no related child record with the same parent Id. (Bug#49850)

  • MySqlDataReader.GetUInt64 returned an incorrect value when reading a BIGINT UNSIGNED column containing a value greater than 2147483647. (Bug#49794)

  • A FormatException was generated when an empty string was returned from a stored function. (Bug#49642)

  • When adding a data set in Visual Studio 2008, the following error was generated:

    Relations couldn't be addded. Column 'REFERENCED_TABLE_CATALOG' does not belong to table.

    This was due to a 'REFERENCED_TABLE_CATALOG' column not being included in the foreign keys collection. (Bug#48974)

  • Attempting to execute a load data local infile on a file where the user did not have write permissions, or the file was open in an editor gave an access denied error. (Bug#48944)

  • The method MySqlDataReader.GetSchemaTable() returned 0 in the NumericPrecision field for decimal and newdecimal columns. (Bug#48171)

  • When trying to create stored procedures from a SQL script, a MySqlException was thrown when attempting to redefine the DELIMITER:

            MySql.Data.MySqlClient.MySqlException was unhandled
            Message="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 'DELIMITER' at line 1"
            Source="MySql.Data"
            ErrorCode=-2147467259
            Number=1064
            StackTrace:
            à MySql.Data.MySqlClient.MySqlStream.ReadPacket()
            à MySql.Data.MySqlClient.NativeDriver.ReadResult(UInt64& affectedRows, Int64&
            lastInsertId)
            à MySql.Data.MySqlClient.MySqlDataReader.GetResultSet()
            à MySql.Data.MySqlClient.MySqlDataReader.NextResult()
            à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
            à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader()
            à MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()
          à MySql.Data.MySqlClient.MySqlScript.Execute()

    Note: The MySqlScript class has been fixed to support the delimiter statement as it is found in SQL scripts. (Bug#46429)

  • Calling a User Defined Function using Entity SQL in the Entity Framework caused a NullReferenceException. (Bug#45277)

  • A connection string set in web.config could not be reused after Visual Studio 2008 Professional was shut down. It continued working for the existing controls, but did not work for new controls added. (Bug#41629)

D.4.4.4. Changes in MySQL Connector/NET 6.0.5 (12 November 2009)

This is a new release, fixing recently discovered bugs.

Bugs fixed:

  • Cloning of MySqlCommand was not typesafe. To clone a MySqlCommand it was necessary to do:

            MySqlCommand clone = (MySqlCommand)((ICloneable)comm).Clone();
          

    MySQL Connector/NET was changed so that it was possible to do:

            MySqlCommand clone = comm.Clone();
          

    (Bug#48460)

  • If MySqlConnection.GetSchema was called for "Indexes" on a table named “b`a`d” as follows:

    DataTable schemaPrimaryKeys = connection.GetSchema(
      "Indexes",
      new string[] { null, schemaName, "b`a`d"});
    

    Then the following exception was generated:

    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 'a`d`' at line 1
    

    (Bug#48101)

  • It was not possible to retrieve a value from a MySQL server table, if the value was larger than that supported by the .NET type System.Decimal.

    MySQL Connector/NET was changed to expose the MySqlDecimal type, along with the supporting method GetMySqlDecimal. (Bug#48100)

  • An entity model created from a schema containing a table with a column of type UNSIGNED BIGINT and a view of the table did not behave correctly. When an entity was created and mapped to the view, the column that was of type UNSIGNED BIGINT was displayed as BIGINT. (Bug#47872)

  • When loading the MySQLClient-mono.sln file included with the Connector/NET source into Mono Develop, the following error occurred:

    /home/tbedford/connector-net-src/6.1/MySQLClient-mono.sln(22):
    Unsupported or unrecognized project:
    '/home/tbedford/connector-net-src/6.1/Installer/Installer.wixproj'
    

    If the file was modified to remove this problem, then attempting to build the solution generated the following error:

    /home/tbedford/connector-net-src/6.1/MySql.Data/Provider/Source/Connection.cs(280,46):
    error CS0115: `MySql.Data.MySqlClient.MySqlConnection.DbProviderFactory' is marked as an
    override but no suitable property found to override
    

    (Bug#47048)

  • If an error occurred during connection to a MySQL Server, deserializing the error message from the packet buffer caused a NullReferenceException to be thrown. When the method MySqlPacket::ReadString() attempted to retrieve the error message, the following line of code threw the exception:

            string s = encoding.GetString(bits, (int)buffer.Position, end - (int)buffer.Position);
          

    This was due to the fact that the encoding field had not been initialized correctly. (Bug#46844)

  • In the MySqlDataReader class the GetSByte function returned a byte value instead of an sbyte value. (Bug#46620)

  • The MySQL Connector/NET Profile Provider, MySql.Web.Profile.MySQLProfileProvider, generated an error when running on Mono. When an attempt was made to save a string in Profile.Name the string was not saved to the my_aspnet_Profiles table. If an attempt was made to force the save with Profile.Save() the following error was generated:

            Server Error in '/mono' Application
    
            --------------------------------------------------------------------------------
    
            The requested feature is not implemented.
            Description: HTTP 500. Error processing request.
    
            Stack Trace: 
    
            System.NotImplementedException: The requested feature is not implemented.
            at MySql.Data.MySqlClient.MySqlConnection.EnlistTransaction
            (System.Transactions.Transaction transaction) [0x00000] 
            at MySql.Data.MySqlClient.MySqlConnection.Open () [0x00000] 
            at MySql.Web.Profile.MySQLProfileProvider.SetPropertyValues
            (System.Configuration.SettingsContext context,
            System.Configuration.SettingsPropertyValueCollection collection) [0x00000] 
            
    
            --------------------------------------------------------------------------------
            Version information: Mono Version: 2.0.50727.1433; ASP.NET Version: 2.0.50727.1433
          

    (Bug#46375)

  • An exception was generated when using TIMESTAMP columns with the Entity Framework. (Bug#46311)

  • MySQL Connector/NET sometimes hung, without generating an exception. This happened if a read from a stream failed returning a 0, causing the code in LoadPacket() to enter an infinite loop. (Bug#46308)

  • When using MySQL Connector/NET 6.0.4 and a MySQL Server 4.1 an exception was generated when trying to execute:

            connection.GetSchema("Columns", ...);
          

    The exception generated was:

            'connection.GetSchema("Columns")' threw an exception of type
            'System.ArgumentException'System.Data.DataTable {System.ArgumentException}
            base{"Input string was not in a correct format.Couldn't store <'Select'> in
            NUMERIC_PRECISION Column.  Expected type is UInt64."}System.Exception
            {System.ArgumentException}
          

    (Bug#46270)

  • The MySQL Connector/NET method StoredProcedure.GetParameters(string) ignored the programmer's setting of the UseProcedureBodies option. This broke any application for which the application's parameter names did not match the parameter names in the Stored Procedure, resulting in an ArgumentException with the message “Parameter 'foo' not found in the collection.” and the following stack trace:

            MySql.Data.dll!MySql.Data.MySqlClient.MySqlParameterCollection.GetParameterFlexible(stri
            ng parameterName = "pStart", bool throwOnNotFound = true) Line 459C#
            MySql.Data.dll!MySql.Data.MySqlClient.StoredProcedure.Resolve() Line 157 + 0x25
            bytesC#
            MySql.Data.dll!MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(System.Data.CommandBeha
            vior behavior = SequentialAccess) Line 405 + 0xb bytesC#
            MySql.Data.dll!MySql.Data.MySqlClient.MySqlCommand.ExecuteDbDataReader(System.Data.Comma
            ndBehavior behavior = SequentialAccess) Line 884 + 0xb bytesC#
            System.Data.dll!System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(System
            .Data.CommandBehavior behavior) + 0xb bytes
            System.Data.dll!System.Data.Common.DbDataAdapter.FillInternal(System.Data.DataSet
            dataset = {System.Data.DataSet}, System.Data.DataTable[] datatables = null, int
            startRecord = 0, int maxRecords = 0, string srcTable = "Table", System.Data.IDbCommand
            command = {MySql.Data.MySqlClient.MySqlCommand}, System.Data.CommandBehavior behavior) +
            0x83 bytes
            System.Data.dll!System.Data.Common.DbDataAdapter.Fill(System.Data.DataSet dataSet, int
            startRecord, int maxRecords, string srcTable, System.Data.IDbCommand command,
            System.Data.CommandBehavior behavior) + 0x120 bytes
            System.Data.dll!System.Data.Common.DbDataAdapter.Fill(System.Data.DataSet dataSet) +
            0x5f bytes
          

    (Bug#46213)

  • Conversion of MySQL TINYINT(1) to boolean failed. (Bug#46205, Bug#46359, Bug#41953)

  • When populating a MySQL database table in Visual Studio using the Table Editor, if a VARCHAR(10) column was changed to a VARCHAR(20) column an exception was generated:

            SystemArgumentException: DataGridViewComboBoxCell value is not valid.
          To replace this default dialog please handle the DataError Event.

    (Bug#46100)

  • In MySQL Connector/NET 6.0.4 using GetProcData generated an error because the parameters data table was only created if MySQL Server was at least version 6.0.6, or if the UseProcedureBodies connection string option was set to true.

    Also the DeriveParameters command generated a null reference exception. This was because the parameters data table, which was null, was used in a for each loop. (Bug#45952)

  • The Entity Framework provider was not calling DBSortExpression correctly when the Skip and Take methods were used, such as in the following statement:

            TestModel.tblquarantine.OrderByDescending(q => q.MsgDate).Skip(100).Take(100).ToList();
          

    This resulted in the data being unsorted. (Bug#45723)

  • The EscapeString code carried out escaping by calling string.Replace multiple times. This resulted in a performance bottleneck, as for every line a new string was allocated and another was disposed of by the garbage collector. (Bug#45699)