Incompatible Change: If you upgrade to MySQL 5.4.3 from an earlier 5.4 release, the server may fail to start due to changes in the default values of innodb_log_files_in_group and innodb_log_file_size, which differ from those in earlier 5.4 releases. You should discard the old InnoDB log files and let MySQL 5.4.3 create new ones. It is necessary to shut down your current server cleanly so that no outstanding transaction information remains in the log. The procedure to use depends on the value of innodb_fast_shutdown used in your current server:

Incompatible Change: The following list indicates InnoDB configuration changes in MySQL 5.4.3, compared to previous versions of MySQL 5.4. For a description of cumulative changes in MySQL 5.4 compared to MySQL 5.1, see Section 1.5, “What Is New in MySQL 5.4”.

The default value of these system variables was changed:

These default value changes in most cases revert changes made in earlier MySQL 5.4 releases. The result is that the defaults are more similar to those in MySQL 5.1.

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. MySQL 5.4.1 was linked against this library, which improved performance but imposed some restrictions. As a result of these restrictions, MySQL 5.4.3 uses a different approach:

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:

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)

Performance: For MyISAM tables with bulk_insert_buffer_size values larger than 256KB, the performance of bulk insert operations such as multiple-row INSERT and INSERT ... SELECT operations has been improved greatly when up to a hundred rows are inserted at the same time. (Bug#44723)

Partitioning: Replication: Attempting to replicate an INSERT ... SELECT statement on a partitioned table using row-based replication caused the slave to crash. (Bug#44108)

Partitioning: When reorganizing partitions, not all affected subpartitions were removed prior to renaming. One way in which the issue was visible was that attempting to reorganize two partitions into a single partition having the same name as one of the original partitions could lead to a crash of the server. (Bug#47029)

See also Bug#45961, Bug#43729.

Partitioning: An INSERT ... SELECT statement on an empty partition of a partitioned table failed with ERROR 1030 (HY000): Got error 124 from storage engine. This issue also caused queries run against a partitioned table while a LOAD DATA CONCURRENT INFILE statement was in progress to fail with the same error. (Bug#46639)

See also Bug#35845, Bug#44657, Bug#45840.

Partitioning: An online or fast ALTER TABLE of a partitioned table could leave behind temporary files in the database directory. (Bug#46483)

Partitioning: A partitioned table having a TIMESTAMP column with a default value of CURRENT_TIMESTAMP and this column was not defined using an ON UPDATE option, an ALTER TABLE ... REORGANIZE PARTITION statement on the table caused the TIMESTAMP column value to be set to CURRENT_TIMESTAMP regardless. (Bug#46478)

Partitioning: Partition pruning did not always work correctly when the table's partitioning key used the TO_DAYS() function. (Bug#46362)

Partitioning: Inserting negative values into an AUTO_INCREMENT column of a partitioned table could lead to apparently unrelated errors or a crash of the server. (Bug#45823)

Partitioning: Attempting to access a partitioned table when partitioning support was disabled in a MySQL server binary that had been compiled with partitioning support caused the server to crash. (Bug#39893)

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

See also Bug#35843.

Partitioning: The use of TO_DAYS() in the partitioning expression led to selection failures when the column having the date value contained invalid dates. This occurred because the function returns NULL in such cases, and the partition containing NULL values was pruned away. For example, this problem occurred if '2001-02-00' was inserted into a DATE column of such a table, and a subsequent query on this table used WHERE date_col < '2001-02-00'—while '2001-01-01' is less than '2001-02-00', TO_DAYS('2001-02-00') evaluates as NULL, and so the row containing '2001-01-01' was not returned. Now, for tables using RANGE or LIST partitioning and having TO_DAYS() in the partitioning expression, the NULL partition is also scanned instead of being ignored.

The fix for this issue also corrects misbehavior such that a query of the form SELECT * FROM table WHERE date_col < date_val on a table partitioned by RANGE or LIST was handled as though the server SQL mode included ALLOW_INVALID_DATES even if this was not actually part of the server SQL mode at the time the query was issued. (Bug#20577)

See also Bug#18198, Bug#32021, Bug#46362.

Replication: Performing a multi-row update of the AUTO_INCREMENT column of a transactional table could result in an inconsistency between master and slave when there was a trigger on the transactional table that updated a nontransactional table. When such an update failed on the master, no rows were updated on the master, but some rows could (erroneously) be updated on the slave. (Bug#46864)

Replication: When using the --replicate-rewrite-db option and the database referenced by this option on the master was the current database when the connection to the slave was closed, any temporary tables existing in this database were not properly dropped. (Bug#46861)

Replication: When a statement that changed both transactional and nontransactional tables failed, the transactional changes were automatically rolled back on the master but the slave ignored the error and did not roll them back, thus leading to inconsistencies between master and slave.

This issue is fixed by automatically rolling back a statement that fails on the slave; however, the transaction is not rolled back unless a corresponding ROLLBACK statement is found in the relay log file. (Bug#46130)

See also Bug#33864.

Replication: When using row-based replication, importing a dump made with mysqldump and replicating a row with an AUTO_INCREMENT column set to 0, with NO_AUTO_VALUE_ON_ZERO active on the master, the row was inserted successfully on the master; however any setting for NO_AUTO_VALUE_ON_ZERO was ignored on the slave. When the AUTO_INCREMENT column was incremented, this caused replication to fail on the slave due to a duplicate key error. In some cases it could also cause the slave to crash. (Bug#45999)

Replication: When slave_transaction_retries is set, a statement that replicates, but is then rolled back due to a deadlock on the slave, should be retried. However, in certain cases, replication was stopped with error 1213 (Deadlock found when trying to get lock; try restarting transaction) instead, even when this variable was set. (Bug#45694)

Replication: The binary logging behavior (and thus, the replication behavior) of CREATE DATABASE IF NOT EXISTS, CREATE TABLE IF NOT EXISTS, and CREATE EVENT IF NOT EXISTS was not consistent among these statements, nor with that of DROP DATABASE IF EXISTS, DROP TABLE IF EXISTS, and DROP EVENT IF EXISTS: A DROP ... IF EXISTS statement is always logged even if the database object named in the statement does not exist. However, of the CREATE ... IF NOT EXISTS statements, only the CREATE EVENT IF NOT EXISTS statement was logged when the database object named in the statement already existed.

Now, every CREATE ... IF NOT EXISTS statement is written to the binary log (and thus replicated), whether the database object named in the statement exists or not. For more information, see Section 16.4.1.3, “Replication of CREATE ... IF NOT EXISTS Statements”.

Exception. Replication and logging of CREATE TABLE IF NOT EXISTS ... SELECT continues to be handled according to existing rules. See Section 16.4.1.4, “Replication of CREATE TABLE ... SELECT Statements”, for more information.

(Bug#45574)

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.

(Bug#45516)

Replication: In some cases, a STOP SLAVE statement could cause the replication slave to crash. This issue was specific to MySQL on Windows or Macintosh platforms. (Bug#45238, Bug#45242, Bug#45243, Bug#46013, Bug#46014, Bug#46030)

See also Bug#40796.

Replication: Creating a scheduled event whose DEFINER clause was either set to CURRENT_USER or not set explicitly caused the master and the slave to become inconsistent. This issue stems from the fact that, in both cases, the DEFINER is set to the CURRENT_USER of the current thread. (On the master, the CURRENT_USER is the mysqld user; on the slave, the CURRENT_USER is empty.)

This behavior has been modified as follows:

(Bug#44331)

See also Bug#42217.

Replication: When using the statement-based logging format, the only possible safe combination of transactional and nontransactional statements within the same transaction is to perform any updates on nontransactional tables (such as MyISAM tables) first, before updating any transactional tables (such as those using the InnoDB storage engine). This is due to the fact that, although a modification made to a nontransactional table is immediately visible to other connections, the update is not immediately written to the binary log, which can lead to inconsistencies between master and slave. (Other combinations may hide a causal dependency, thus making it impossible to write statements updating nontransactional tables to the binary log in the correct order.)

However, in some cases, this situation was not handled properly, and the determination whether a given statement was safe or not under these conditions was not always correct. In particular, a multi-table update that affected both transactional and nontransactional tables or a statement modifying data in a nontransactional table having a trigger that operated on a transactional table (or the reverse) was not determined to be unsafe when it should have been.

With this fix, the following determinations regarding replication safety are made when combining updates to transactional and nontransactional tables within the same transaction in statement-based logging mode:

(Bug#28976)

The ARCHIVE storage engine lost records during a bulk insert. (Bug#46961)

CONCAT_WS() could return incorrect results due to an argument buffer also being used as a result buffer. (Bug#46815)

Stack overflow checking did not account for the size of the structure stored in the heap. (Bug#46807)

The server crashed when re-using outer column references in correlated subqueries when the enclosing query used a temp table. (Bug#46791)

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)

Assertion failure could result from repeated execution of a stored procedure containing an incorrect query with a subselect. (Bug#46629)

CREATE TABLE ... SELECT could cause assertion failure if a table already existed with the same name and contained an AUTO_INCREMENT column. (Bug#46616)

SHOW CREATE TRIGGER for a MERGE table trigger caused an assertion failure. (Bug#46614)

In queries for which the loose index scan access method was chosen, using a condition of the form col_name rather than the equivalent col_name <> 0 caused an assertion failure. (Bug#46607)

The server ignored the setting of sync_frm for CREATE TABLE ... LIKE. (Bug#46591)

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)

An attempt to create a table with the same name as an existing view could cause a server crash. (Bug#46384)

A parser problem prevented properly stripping backquotes from an argument to a user-defined function (UDF). If the UDF was in an ORDER BY clause, its name would not be properly resolved against an alias with the same name in the select list. (Bug#46259)

A query containing a subquery in the FROM clause and PROCEDURE ANALYSE() caused a server crash. (Bug#46184)

See also Bug#48293.

Certain SELECT statements containing DISTINCT, GROUP BY, and HAVING clauses could hang in an infinite loop. (Bug#46159)

Killing a query that was performing a sort could result in a memory leak. (Bug#45962)

A Valgrind error when opening the init_file file was corrected. (Bug#45894)

CREATE TEMPORARY TABLE failed for InnoDB tables on systems with case-insensitive file systems when lower_case_table_names = 2 and the pathname of the temporary file directory contained uppercase characters. (Bug#45638)

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.

When re-installing MySQL on Windows on a server that has a data directory from a previous MySQL installation, the installer would fail to identify the existence of the installation and the password configured for the root user. (Bug#45200)

Debug builds of the server on Windows crashed in debugging code. (Bug#45118)

The default value of innodb_buffer_pool_size was set to 1GB in MySQL 5.4.0. This was too large for many installations, so the default has been lowered to 128MB. (Bug#44408)

SHOW ERRORS returned an empty result set after an attempt to drop a nonexistent table. (Bug#42364)

A test for stack growth failed on some platforms, leading to server crashes. (Bug#42213)

A buffer overflow could occur during handling of IS NULL ranges. (Bug#37044)

mysqladmin --wait ping crashed on Windows systems. (Bug#35132)

myisamchk performed parameter value casting at startup that generated unnecessary warning messages. (Bug#33785)

When using the ARCHIVE storage engine, SHOW TABLE STATUS displayed incorrect information for Max_data_length, Data_length and Avg_row_length. (Bug#29203)

As of MySQL 5.4.2, the InnoDB Plugin is included in MySQL 5.4 releases. The version of the InnoDB Plugin in this release is 1.0.4 and is considered of Beta quality. It becomes the built-in version of InnoDB in MySQL Server, replacing the version previously included as the built-in InnoDB engine.

A number of performance and scalability enhancements were made to the previous built-in version of InnoDB in MySQL 5.4.0 and 5.4.1. InnoDB Plugin also provides improvements in these areas, and in addition offers new features and capabilities for flexibility and ease of use. Among these features are enhanced reliability, “Fast index creation,” table and index compression, file format management, new INFORMATION_SCHEMA tables, capacity tuning, multiple background I/O threads, and group commit.

For information about these features, see InnoDB Plugin 1.0 for MySQL 5.1 User’s Guide. For general information about using InnoDB in MySQL, see Section 13.6, “The InnoDB Storage Engine”.

Due to inclusion of InnoDB Plugin, a number of InnoDB configuration changes were made, as described later in this section.

Incompatible Change: The inclusion of InnoDB Plugin as the built-in version of InnoDB in MySQL Server results in an incompatibility for upgrades from MySQL 5.1. InnoDB Plugin is available in MySQL 5.1 as of 5.1.38, but it is an optional storage engine that must be enabled explicitly using two server options:

[mysqld]
ignore-builtin-innodb
plugin-load=innodb=ha_innodb_plugin.so

If you were using InnoDB Plugin in MySQL 5.1 by means of those options, you must remove them after an upgrade to 5.4 or the server will fail to start.

Incompatible Change: If you upgrade to MySQL 5.4.2 from MySQL 5.1, the server may fail to start due to InnoDB log file configuration changes. MySQL 5.4 increases the default value of innodb_log_files_in_group from 2 to 3. It also increases the default value of innodb_log_file_size from 5MB to 128MB. (MySQL 5.4.0 increased the minimum value of innodb_log_file_size from 1MB to 32MB, but this has been reverted to 1MB in 5.4.2.)

For an upgrade to MySQL 5.4.2, you should discard the old InnoDB log files and let MySQL 5.4.2 create new ones. It is necessary to shut down your current server cleanly so that no outstanding transaction information remains in the log. The procedure to use depends on the value of innodb_fast_shutdown used in your current server:

Incompatible Change: The following list indicates InnoDB configuration changes in MySQL 5.4.2, compared to previous versions of MySQL 5.4. For a description of cumulative changes in MySQL 5.4 compared to MySQL 5.1, see Section 1.5, “What Is New in MySQL 5.4”.

These system variables were added:

More information about the new system variables can be found at InnoDB Plugin 1.0 for MySQL 5.1 User’s Guide.

These system variables have been made dynamic and can be modified at runtime:

These system variables were removed, along with the functionality that they represented:

The minimum value of these system variables was changed:

These minimum value changes in most cases revert changes made in MySQL 5.4.0.

The default value of this system variable was changed:

These status variables were renamed or removed:

Important Change: Replication: Previously, incident log events were represented as comments in the output from mysqlbinlog, making them effectively silent when playing back the binlog.

(An incident log event represents an incident that could cause the contents of the database to change without that event being recorded in the binary log.)

This meant that, if the SQL were applied to a server, it could potentially lead to the master and the slave having different data. To make it possible to handle incident log events without breaking applications that expect the previous behavior, the nonsense statement RELOAD DATABASE is added to the SQL output for that incident log event, which causes an error.

To use this functionality currently requires hand editing of the dump file and handling of each case on an individual basis by a database administrator before applying the output to a server. (Bug#44442)

Replication: With statement-based logging (SBL), repeatedly calling statements that are unsafe for SBL caused a warning message to be written to the error log for each statement, and there was no way to disable this behavior. Now the server logs messages about statements that are unsafe for statement-based logging only if the log_warnings variable is greater than 0. (Bug#46265)

The undocumented TRANSACTIONAL and PAGE_CHECKSUM keywords were removed from the grammar. (Bug#45829)

The minimum value for table_open_cache was increased from 64 to 400. (Bug#45475)

mysql_upgrade now displays a message indicating the connection parameters it uses when invoking mysqlcheck. (Bug#44638)

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)

Previously, SELECT ... INTO OUTFILE dumped column values without character set conversion, which could produce data files that cannot be imported without error if different columns used different character sets. A consequence of this is that mysqldump ignored the --default-character-set option if the --tab option was given (which causes SELECT ... INTO OUTFILE to be used to dump data.)

INTO OUTFILE now can be followed by a CHARACTER SET clause indicating the character set to which dumped values should be converted. Also, mysqldump adds a CHARACTER SET clause to the SELECT ... INTO OUTFILE statement used to dump data, so that --default-character-set is no longer ignored if --tab is given.

Other changes are that SELECT ... INTO OUTFILE enforces that ENCLOSED BY and ESCAPED BY arguments must be a single character, and SELECT ... INTO OUTFILE and LOAD DATA INFILE produce warnings if non-ASCII field or line separators are specified. (Bug#30946)

The maximum value for max_binlog_cache_size has been increased from 2³² – 1 to 2⁶⁴ – 1 (even on 32-bit platforms), which enables transactions 4GB and larger to be performed when binary logging is enabled. (Bug#10206)

Pluggable storage engines now can be built for Windows.

On Linux, 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. MySQL 5.4.1 was linked against this library, which improved performance but imposed some restrictions. As a result of these restrictions, MySQL 5.4.2 uses a different approach:

The MySQL euckr character set now can store extended codes [81...FE][41..5A,61..7A,81..FE], which makes euckr compatible with the Microsoft cp949 character set.

The optimizer_switch system variable is now available to control optimizations that can be switched on and off. See Section 7.2.18, “Using optimizer_switch to Control the Optimizer”.

Performance: With InnoDB tables, MySQL used a less-selective secondary index to avoid a filesort even if a prefix of the primary key was much more selective.

The fix for this problem might cause other queries to run more slowly. (Bug#45828)

Performance: InnoDB uses random numbers to generate dives into indexes for calculating index cardinality. However, under certain conditions, the algorithm did not generate random numbers, so ANALYZE TABLE did not update cardinality estimates properly. A new algorithm has been introduced with better randomization properties. (Bug#43660)

Performance: The table cache lock (LOCK_open) is now an adaptive mutex, which should improve performance in workloads where this lock is heavily contended. (Bug#43435)

Partitioning: Security Fix: Accessing a table having user-defined partitioning when the server SQL mode included ONLY_FULL_GROUP_BY caused the MySQL server to crash. For example, the following sequence of statements crashed the server:

DROP TABLE IF EXISTS t1;

SET SESSION SQL_MODE='ONLY_FULL_GROUP_BY';

CREATE TABLE t1 (id INT, KEY(id))
    PARTITION BY HASH(id) PARTITIONS 2;

(Bug#45807)

Security Fix: The strxnmov() library function could write a null byte after the end of the destination buffer. (Bug#44834)

Security Fix: Four potential format string vulnerabilities were fixed (discovered by the Veracode code analysis). (Bug#44166)

Incompatible Change: The server can load plugins under the control of startup options. For example, many storage engines can be built in pluggable form and loaded when the server starts. In the following descriptions, plugin_name stands for a plugin name such as innodb.

Previously, plugin options were handled like other boolean options (see Section 4.2.3.2, “Program Option Modifiers”). That is, any of these options enabled the plugin:

--plugin_name
--plugin_name=1
--enable-plugin_name

And these options disabled the plugin:

--plugin_name=0
--disable-plugin_name
--skip-plugin_name

However, use of a boolean option for plugin loading did not provide control over what to do if the plugin failed to start properly: Should the server exit, or start with the plugin disabled? The actual behavior has been that the server starts with the plugin disabled, which can be problematic. For example, if InnoDB fails to start, existing InnoDB tables become inaccessible, and attempts to create new InnoDB tables result in tables that use the default storage engine unless the NO_ENGINE_SUBSTITUTION SQL mode has been enabled to cause an error to occur instead.

Now, there is a change in the options used to control plugin loading, such that they have a tristate format:

The values OFF, ON, and FORCE are not case sensitive.

Suppose that CSV and InnoDB have been built as pluggable storage engines and that you want the server to load them at startup, subject to these conditions: The server is allowed to run if CSV initialization fails, but must require that InnoDB initialization succeed. To accomplish that, use these lines in an option file:

[mysqld]
csv=ON
innodb=FORCE

This change is incompatible with the previous implementation if you used options of the form --plugin_name=0 or --plugin_name=1, which should be changed to --plugin_name=OFF or --plugin_name=ON, respectively.

--enable-plugin_name is still supported and is the same as --plugin_name=ON. --disable-plugin_name and --skip-plugin_name are still supported and are the same as --plugin_name=OFF. (Bug#19027)

See also Bug#45336.

Important Change: Replication: BEGIN, COMMIT, and ROLLBACK statements are no longer affected by --replicate-do-db or --replicate-ignore-db rules. (Bug#43263)

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

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

See also Bug#43217.

Partitioning: Attempting to create a table using an invalid or inconsistent subpartition definition caused the server to crash. An example of such a statement is shown here:

CREATE TABLE t2 (s1 INT, s2 INT)
PARTITION BY LIST (s1) SUBPARTITION BY HASH (s2) SUBPARTITIONS 1
(
    PARTITION p1 VALUES IN (1),
    PARTITION p2 VALUES IN (2) (SUBPARTITION p3)  
);

(Bug#46354)

Partitioning: A failed RENAME TABLE operation on a table with user-defined partitioning left the table in an unusable state, due to only some of the table files having been renamed. (Bug#30102)

Replication: When a statement that changes a nontransactional table failed, the transactional cache was flushed, causing a mismatch between the execution and logging histories. Now we avoid flushing the transactional cache unless a COMMIT or ROLLBACK is issued. (Bug#46129)

Replication: For replication of a stored procedure that uses the gbk character set, the result on the master and slave differed. (Bug#45485)

Replication: The internal function purge_relay_logs() did not propagate an error occurring in another internal function count_relay_log_space(). (Bug#44115)

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.

(Bug#43929)

See also Bug#37148.

Replication: When using the MIXED logging format, after creating a temporary table and performing an update that switched the logging format to ROW, the format switch persisted following the update. This prevented any subsequent DDL statements on temporary tables from being written to the binary log until the temporary table was dropped. (Bug#43046)

See also Bug#40013.

This regression was introduced by Bug#20499.

Replication: Statements using LIMIT generated spurious Statement is not safe to log in statement format warnings in the error log, causing the log to grow rapidly in size. (Bug#42851)

See also Bug#46265, Bug#42415.

This regression was introduced by Bug#34768.

Replication: When using row-based logging, the length of an event for which the field metadata exceeded 255 bytes in size was incorrectly calculated. This could lead to corruption of the binary log, or cause the server to hang. (Bug#42749)

See also Bug#44548, Bug#44672, Bug#44752.

Replication: The warning Statement is not safe to log in statement format, issued in situations when it cannot be determined that a statement or other database event can be written reliably to the binary log using the statement-based format, has been changed to Statement may not be safe to log in statement format. (Bug#42415)

Replication: The Query_log_event used by replication to transfer a query to the slave has been refactored. Query_log_event also stores and sends the error code resulting from the execution since it, in some cases, is necessary to execute the statement on the slave as well, which should result in the same error code. The Query_log_event constructor previously worked out for itself the error code using a complex routine, the result of which was often set aside within the constructor itself. This was also involved with at least 2 known bugs relating to invalid errors, and taken as a clear sign that the constructor was not well-designed and needed to be re-written. (Bug#41948)

See also Bug#37145.

Replication: When replicating many temporary tables and inserts into those tables, executing STOP SLAVE followed by START SLAVE could cause the server to crash. This appeared to be caused by temporary tables preserving outdated thread references after the restart. (Bug#41725)

Replication: If the --log-bin-trust-function-creators option is not enabled, CREATE FUNCTION requires one of the modifiers DETERMINISTIC, NO SQL, or READS SQL DATA. When using statement-based mode, the execution of a stored function should follow the same rules; however, only functions defined with DETERMINISTIC could actually be executed. In addition, the wrong error was generated (ER_BINLOG_ROW_RBR_TO_SBR instead of ER_BINLOG_UNSAFE_ROUTINE).

Now execution of stored functions is compatible with creation in this regard; when a stored function without one of the modifiers above is executed in STATEMENT mode, the correct error is raised, and functions defined using NO SQL, READS SQL DATA, or both (that is, without using DETERMINISTIC) can be excuted. (Bug#41166)

Replication: When reading a binary log that was in use by a master or that had not been properly closed (possibly due to a crash), the following message was printed: Warning: this binlog was not closed properly. Most probably mysqld crashed writing it. This message did not take into account the possibility that the file was merely in use by the master, which caused some users concern who were not aware that this could happen.

To make this clear, the original message has been replaced with Warning: this binlog is either is use or was not closed properly. (Bug#34687)

open_binary_frm() performed a version test incorrectly, resulting in Valgrind errors. (Bug#46652)

Concurrent INSERT INTO ... SELECT statements for an InnoDB table could cause an AUTO_INCREMENT assertion failure. (Bug#46650)

Incorrect index optimization could lead to incorrect results or server crashes. (Bug#46454)

The server printed warnings at startup about adjusting the value of the max_join_size system variable. (These were harmless, but might be seen by users as significant.) (Bug#46385)

mysql did not handle backspace properly for multi-byte characters. This has been fixed now if mysql is linked with the readline library. It is not fixed if mysql is linked with libedit, which does not contain the necessary support for multi-byte character sets. (Bug#46310)

For InnoDB tables, an unnecessary table rebuild for ALTER TABLE could sometimes occur if ROW_FORMAT was specified. (Bug#46160)

The server crashed if evaluation of GROUP_CONCAT(... ORDER BY) required allocation of a sort buffer but allocation failed. (Bug#46080)

An optimization that moved an item from a subquery to an outer query could cause a server crash. (Bug#46051)

Several Valgrind warnings were corrected. (Bug#46003, Bug#46034, Bug#46042)

CREATE TABLE ... SELECT could cause a server crash if no default database was selected. (Bug#45998)

When creating tables using the IBMDB2I storage engine with the ibmdb2i_create_index_option option set to 1, creating an IBMDB2I table with a primary key should produce an additional index that uses EBCDIC hexadecimal sorting, but this index was not created. (Bug#45983)

The server crashed for attempts to use REPLACE or INSERT ... ON DUPLICATE KEY UPDATE with a view defined using a join. (Bug#45806)

Some collations were causing IBMDB2I to report inaccurate key range estimations to the optimizer for LIKE clauses that select substrings. This can be seen by running EXPLAIN. This problem primarily affects multi-byte and unicode character sets. (Bug#45803)

The MySQL Server crashed when performing a REPLACE into a MERGE table if there was a duplicate. (Bug#45800)

Inserting data into a table using the macce character set with the IBMDB2I storage engine would fail. (Bug#45793)

For problems reading SSL files during SSL initialization, the server wrote error messages to stderr rather than to the error log. (Bug#45770)

There was a race condition when changing innodb_commit_concurrency at runtime to the value DEFAULT. (Bug#45749)

See also Bug#42101.

Performing an empty XA transaction caused the server to crash for the next XA transaction. (Bug#45548)

The vendor name change from MySQL AB to Sun Microsystems, Inc. in RPM packages was not handled gracefully when upgrading MySQL using an RPM package. (Bug#45534)

SHOW CREATE TRIGGER requires the TRIGGER privilege but was not checking privileges. (Bug#45412)

An assertion failure could occur if InnoDB tried to unlock a record when the clustered index record was unknown. (Bug#45357)

Linker failures with libmysqld on VC++ 2008 were fixed. (Bug#45326)

If autocommit was enabled, InnoDB did not roll back DELETE or UPDATE statements if the statement was killed. (Bug#45309)

Compiler warnings on Mac OS X were fixed. (Bug#45286)

The optimizer mishandled “impossible range” conditions and returned empty results due to an uninitialized variable. (Bug#45266)

Use of DECIMAL constants with more than 65 digits in CREATE TABLE ... SELECT statements led to spurious errors or assertion failures. (Bug#45262)

The mysql client could misinterpret some character sequences as commands under some circumstances. (Bug#45236)

Running a SELECT query over an IBMDB2I table using the cp1250 character set would produce an error

ibmdb2i error 2027: Error converting single-byte sort sequence to UCS-2 

(Bug#45197)

Use of CONVERT() with an empty SET value could cause an assertion failure. (Bug#45168)

Use of ROUND() on a LONGTEXT or LONGBLOB column of a derived table could cause a server crash. (Bug#45152)

A problem of compiler register misallocation on 32-bit Linux was corrected. (Bug#45131)

DROP USER could fail to drop all privileges for an account if the PAD_CHAR_TO_FULL_LENGTH SQL mode was enabled. (Bug#45100)

InnoDB recovery could hang due to redo logging of doublewrite buffer pages. (Bug#45097)

Invalid memory reads could occur using the compressed client/server protocol. (Bug#45031)

Invalid input could cause invalid memory reads by the parser. (Bug#45010)

GROUP BY on a constant (single-row) InnoDB table joined to other tables caused a server crash. (Bug#44886)

ALTER TABLE on a view crashed the server. (Bug#44860)

When using partitioning with the IBMDB2I storage engine, the engine could report that a valid character set was not supported. (Bug#44856)

Running queries on tables with the IBMDB2I storage engine using the utf8 character would fail when using the 64-bit version of MySQL. (Bug#44811)

Index Merge followed by a filesort could result in a server crash if sort_buffer_size was not large enough for all sort keys. (Bug#44810)

See also Bug#40974.

UNCOMPRESSED_LENGTH() returned a garbage result when passed a string shorter than 5 bytes. Now UNCOMPRESSED_LENGTH() returns NULL and generates a warning. (Bug#44796)

Several Valgrind warnings were silenced. (Bug#44774, Bug#44792)

Selecting RAND(N) function where N is a column of a constant table (table with a single row) failed with a SIGFPE signal. (Bug#44768)

The PASSWORD() and OLD_PASSWORD() functions could read memory outside of an internal buffer when used with BLOB arguments. (Bug#44767)

Conversion of a string to a different character set could use the same buffer for input and output, leading to incorrect results or warnings. (Bug#44743, Bug#44766)

When reading binary data, the concatenation function for geometry data collections did not rigorously check for available data, leading to invalid reads and server crashes. (Bug#44684)

Some deprecation warning messages indicated feature removal in MySQL 5.2 rather than MySQL 6.0. (Bug#44676)

Code that optimized a read-only XA transaction failed to reset the XID once the transaction was no longer active. (Bug#44672)

During incorporation of a Google patch to SHOW ENGINE INNODB STATUS in MySQL 5.4.0, the TRANSACTIONS section of the output was inadvertently omitted. This section has been restored. (Bug#44671)

A Valgrind warning related to transaction processing was silenced. (Bug#44664)

If an error occurred during the creation of a table (for example, the table already existed) having an AUTO_INCREMENT column and a BEFORE trigger that used the INSERT ... SELECT construct, an internal flag was not reset properly. This led to a crash the next time the table was opened again. (Bug#44653)

Some files in an AIX tar file distribution unpacked with incorrect permissions. (Bug#44647)

When creating tables using the IBMDB2I storage engine, the RCDFMT (record format) that would be applied to the corresponding files within the IBM i would be set according to the table name. During whole table operations, the name could get modified to a value inconsistent with the table name. In addition, the record format would be inconsistent compared to the file content. The IBMDB2I storage engine now adds an explicit RCDFMT clause to the CREATE TABLE statement passed down to the DB2 storage engine layer. (Bug#44610)

Using mysql_stmt_execute() to call a stored procedure could cause a server crash. (Bug#44495)

innochecksum could incorrectly determine the input file name from the arguments. (Bug#44484)

The my-innodb-heavy-4G.cnf sample option file contained a setting for the no longer existing innodb_file_io_threads system variable. This has been replaced with settings for the innodb_write_io_threads and innodb_read_io_threads system variables with which innodb_file_io_threads has been replaced. (Bug#44470)

Creating a new instance after previously removing an instance would fail to complete the installation properly because the security settings could not be applied correctly. (Bug#44428)

Incorrect time was reported at the end of mysqldump output. (Bug#44424)

mysqlslap ignored the --csv option if it was given without an argument. (Bug#44412)

Caching of GROUP BY expressions could lead to mismatches between compile-time and runtime calculations and cause a server crash. (Bug#44399)

A deprecation warning message tested for an incorrect version number and caused an assertion failure. (Bug#44394)

Lettercase conversion in multibyte cp932 or sjis character sequences could produce incorrect results. (Bug#44352)

Assertion failure could occur for duplicate-key errors in INSERT INTO ... SELECT statements. (Bug#44306)

Incomplete cleanup of JOIN_TAB::select during the filesort of rows for a GROUP BY clause inside a subquery caused a server crash. (Bug#44290)

Trying to use an unsupported character set on an IBMDB2I table would produce DB2 error 2501 or 2511. The error has been updated to produce Error 2504 (Character set is unsupported). (Bug#44232)

For InnoDB tables with ROW_FORMAT = REDUNDANT, CHAR columns should be fixed-length and allow in-place updates. However, they were treated as variable-length if they contained utf8 data or NULL, preventing in-place updates. (Bug#44032)

InnoDB use of SELECT MAX(autoinc_column) could cause a crash when MySQL data dictionaries went out of sync. (Bug#44030)

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

On 64-bit Windows systems, myisamchk did not handle key_buffer_size values larger than 4GB. (Bug#43940)

For user-defined utf8 collations, attempts to store values too long for a column could cause a server crash. (Bug#43827)

Invalidation of query cache entries due to table modifications could cause threads to hang inside the query cache with state “freeing items”. (Bug#43758)

EXPLAIN EXTENDED could crash for UNION queries in which the last SELECT was not parenthesized and included an ORDER BY clause. (Bug#43612)

Enabling the event scheduler from within the file specified by --init-file caused a server crash. (Bug#43587)

Multiple-table updates for InnoDB tables could produce unexpected results. (Bug#43580)

The server did not always check the return value of calls to the hash_init() function. (Bug#43572)

If the client lost the connection to the MySQL server after mysql_stmt_prepare(), the first call to mysql_stmt_execute() returned an error (as expected) but consecutive calls to mysql_stmt_execute() or mysql_stmt_close() crashed the client. (Bug#43560)

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

For DELETE statements with ORDER BY var, where var was a global system variable with a NULL value, the server could crash. (Bug#42778)

configure.in contained references to literal instances of nm and libc, rather than to variables parameterized for the proper values on the current platform. (Bug#42721)

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

mysqladmin --count=X --sleep=Y incorrectly delayed Y seconds after the last iteration before exiting. (Bug#42639)

configure.in did not properly check for the pthread_setschedprio() function. (Bug#42599)

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

Builds linked against OpenSSL had a memory leak in association with use of X509 certificates. (Bug#42158)

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

See also Bug#45749.

SELECT ... INTO @var could produce values different from SELECT ... without the INTO clause. (Bug#42009)

mysql_zap did not work on Mac OS X. (Bug#41883)

A workaround for a Sun Studio bug was instituted. (Bug#41710)

A crash occurred due to a race condition between the merge table and table_cache evictions.

00000001403C452F    mysqld.exe!memcpy()[memcpy.asm:151]
00000001402A275F    mysqld.exe!ha_myisammrg::info()[ha_myisammrg.cc:854]
00000001402A2471    mysqld.exe!ha_myisammrg::attach_children()[ha_myisammrg.cc:488]
00000001402A2788    mysqld.exe!ha_myisammrg::extra()[ha_myisammrg.cc:863]
000000014015FC5D    mysqld.exe!attach_merge_children()[sql_base.cc:4135]
000000014016A4C1    mysqld.exe!open_tables()[sql_base.cc:4697]
000000014016A898    mysqld.exe!open_and_lock_tables_derived()[sql_base.cc:4956]
000000014018BB54    mysqld.exe!mysql_insert()[sql_insert.cc:613]
000000014019EDD3    mysqld.exe!mysql_execute_command()[sql_parse.cc:3066]
00000001401A2F06    mysqld.exe!mysql_parse()[sql_parse.cc:5791]
00000001401A3C1A    mysqld.exe!dispatch_command()[sql_parse.cc:1202]
00000001401A4CD7    mysqld.exe!do_command()[sql_parse.cc:857]
0000000140246327    mysqld.exe!handle_one_connection()[sql_connect.cc:1115]
00000001402B82C5    mysqld.exe!pthread_start()[my_winthread.c:85]
00000001403CAC37    mysqld.exe!_callthreadstart()[thread.c:295]
00000001403CAD05    mysqld.exe!_threadstart()[thread.c:275]
0000000077D6B69A    kernel32.dll!BaseThreadStart()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...

(Bug#41212)

Shared-memory connections did not work in Vista if mysqld was started from the command line. (Bug#41190)

For queries with a sufficient number of subqueries in the FROM clause of this form:

SELECT * FROM (SELECT 1) AS t1,
              (SELECT 2) AS t2,
              (SELECT 3) AS t3, ...

The query failed with a Too high level of nesting for select error, as though the query had this form:

SELECT * FROM (SELECT 1 FROM (SELECT 2 FROM (SELECT 3 FROM ...

(Bug#41156)

For views created with a column list clause, column aliases were not substituted when selecting through the view using a HAVING clause. (Bug#40825)

Some UPDATE statements that affected no rows returned a rows-affected count of one. (Bug#40565)

mysqladmin did not have enough space allocated for tracking all variables when using --vertical or --relative with extended-status. (Bug#40395)

Partitioning a log table caused a server crash. (Bug#40281)

When using quick access methods to search for rows in UPDATE and DELETE statements, there was no check whether a fatal error had already been sent to the client while evaluating the quick condition. Consequently, a false OK (following the error) was sent to the client, causing the error to be incorrectly transformed into a warning. (Bug#40113)

A multiple-table DELETE involving a table self-join could cause a server crash. (Bug#39918)

Creating an InnoDB table with a comment containing a '#' character caused foreign key constraints to be omitted. (Bug#39793)

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)

The mysql option --ignore-spaces was nonfunctional. (Bug#39101)

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

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

SHOW PROCESSLIST could access freed memory of a stored procedure run in a concurrent session. (Bug#38816)

During installation on Windows, the MySQL Instance Configuration Wizard window could be opened at a size too small to be usable. (Bug#38723)

make_binary_distribution did not always generate correct distribution names. (Bug#37808)

The server crashed when executing a prepared statement containing a duplicated MATCH() function call in the select list and ORDER BY clause; for example, SELECT MATCH(a) AGAINST('test') FROM t1 ORDER BY MATCH(a) AGAINST('test'). (Bug#37740)

The output of mysqldump --tab for views included a DROP TABLE statement without the IF EXISTS qualifier. (Bug#37377)

If a query was such as to produce the error 1054 Unknown column '...' in 'field list', using EXPLAIN EXTENDED with the query could cause a server crash. (Bug#37362)

In the mysql client, if the server connection was lost during repeated status commands, the client would fail to detect this and command output would be inconsistent. (Bug#37274)

In the mysql client, using a default character set of binary caused internal commands such as DELIMITER to become case sensitive. (Bug#37268)

A Valgrind error during subquery execution was corrected. (Bug#36995)

When invoked to start multiple server instances, mysqld_multi sometimes would fail to start them all due to not changing location into the base directory for each instance. (Bug#36654)

mysql_upgrade silently ignored the --basedir and --datadir options, which it accepts for backward compatibility. Now it prints a warning. (Bug#36558)

For InnoDB tables, poor cardinality statistics could result in poor query execution plans. (Bug#36513)

mysqldump --tab dumped triggers to stdout rather than to the .sql file for the corresponding table. (Bug#34861)

If the MYSQL_HISTFILE environment variable was set to /dev/null, the mysql client overwrote the /dev/null device file as a normal file. (Bug#34224)

Rows written to the slow query log could have an indeterminate Rows_examined value due to improper initialization. (Bug#34002)

mysqld_safe mishandled certain parameters if they contained spaces. (Bug#33685)

mysqlimport was not always compiled correctly to enable thread support, which is required for the --use-threads option. (Bug#32991)

mysqladmin kill did not work for thread IDs larger than 32 bits. (Bug#32457)

mysqlcheck failed to fix table names when the --fix-table-names and --all-in-1 options were both specified. (Bug#31821)

If the MySQL server was killed without the PID file being removed, attempts to stop the server with mysql.server stop waited 900 seconds before giving up. (Bug#31785)

When performing an installation on Windows using the GUI installer, the installer would fail to wait long enough during installation for the MySQL service to be installed, which would cause the installation to fail and may cause security settings, such as the root password to not be applied correctly. (Bug#30525)

mysql included extra spaces at the end of some result set lines. (Bug#29622)

Several client programs failed to interpret --skip-password as “send no password.” (Bug#28479)

The mysql client inconsistently handled NUL bytes in column data in various output formats. (Bug#28203)

mysqlimport did not correctly quote and escape table identifiers and file names. (Bug#28071)

Output from mysql --html did not encode the <, >, or & characters. (Bug#27884)

If the mysql client was built with the readline library and the .inputrc file mapped Space to the magic-space function, it became impossible to enter spaces. (Bug#27439)

mysql_convert_table_format did not prevent conversion of tables to MEMORY or BLACKHOLE tables, which could result in data loss. (Bug#27149)

Renaming a column that appeared in a foreign key definition did not update the foreign key definition with the new column name. (Bug#21704)

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

See also Bug#46672.

This release does not differ from 5.4.0 except that binary distributions are available for all MySQL-supported platforms, including Windows binaries with scalability improvements enabled. We expect that the scalability improvements will also benefit users of 64-bit Mac OS X and FreeBSD as well as 64-bit Linux/Solaris/SPARC, and potentially also users of 32-bit versions of these platforms.

MySQL 5.4 is based on MySQL 5.1 but includes small, high-impact changes to enhance scalability and performance in MySQL Server. For details, see Section 1.5, “What Is New in MySQL 5.4”.

Binary MySQL 5.4.0 distributions are available as 64-bit builds for Solaris 10-x86_64, Solaris10-SPARC, and Linux x86_64-glibc23.

If you use a source distribution, the BUILD/build_mccge.sh script can be used to configure and build MySQL 5.4.0. Run this script with the --help option to see the available options.

Incompatible Change: The following InnoDB system variable changes were made:

(Bug#42607, Bug#42608)

Incompatible Change: If you upgrade to MySQL 5.4.0 from MySQL 5.1, the server may fail to start due to InnoDB log file configuration changes. MySQL 5.4.0 increases the default value of innodb_log_files_in_group from 2 to 3. It also increases the default value of innodb_log_file_size from 5MB to 128MB and the minimum value of innodb_log_file_size from 1MB to 32MB.

For an upgrade, it is necessary to account for these changes. To do so, discard the old InnoDB log files and let MySQL 5.4.0 create new ones. It is necessary to shut down your current server cleanly so that no outstanding transaction information remains in the log. The procedure to use depends on the value of innodb_fast_shutdown used in your current server:

The Instance Manager (mysqlmanager) has been discontinued and is no longer provided in MySQL releases.

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)

Important Change: When using the MySQL Instance Configuration Wizard with a configuration where you already have an existing installation with a custom datadir, the wizard could reset the data to the default data directory. When performing an upgrade installation in this situation, you must re-specify your custom settings, including the datadir, to ensure that your configuration file is not reset to the default values. (Bug#37534)

Important Change: Uninstalling MySQL using the MySQL installer on Windows would delete the my.ini file. The file is no longer deleted. In addition, when a new installation is conducted, any existing cofiguration file will be renamed to myDATETIME.ini.bak during configuration. (Bug#36493)

Important Change: When installing MySQL on Windows, it was possible to install multiple editions (Complete, and Essential, for example) of the same version of MySQL, leading to two separate entries in the installed packages which were impossible to isolate. This could lead to problems with installation and uninstallation. The MySQL installer on Windows no longers allow multiple installations of the same version of MySQL on a single machine. (Bug#4217)

The MySQL Instance Configuration Wizard would fail to start correctly on Windows Vista. (Bug#42386)

When running the MySQL Instance Configuration Wizard in command-line only mode, the service name would be ignored (effectively creating all instances with the default MySQL service name), irrespective of the name specified on the command line. However, the wizard would attempt to start the service with the specified name, and would fail. (Bug#38379)

When using the MySQL MSI Installer on Windows and selecting Back after a choosing Repair, you would be returned to the Fresh Install section of the installer. You are now correctly returned to the Install, Repair, Modify screen. (Bug#37294)

Security Fix: A number of cross-site request forging issues have been identified and resolved. (Bug#52888, Bug#52910, Bug#52905, Bug#52897)

MySQL Enterprise Service Manager would crash during initial startup on Solaris SPARC 64-bit. (Bug#53751)

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

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 on a link to a support issue within the dashboard is now configured to open the issue within a new window. (Bug#50651)

Monitoring of a server that had INFORMATION_SCHEMA, and a large number of schemas and/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)

The smallest purge log time interval that could be set in the Dashboard was one week. MySQL Enterprise Monitor was changed to allow 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)

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)

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)

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

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 popup 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 statments did not show a rows graph within the statement popup 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 popup would cause a page reload, instead of just closing the popup 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 backwards (for example during time correction), then 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)

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:

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

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

Memory Usage Advisor

Performance Advisor

(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 popup. (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 allow 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”.

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 and/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 popup 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 popup to be hidden, and the Query Analyzer config popup 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” popup 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 Popup history graphs were inconsistent with the other graphs. In particular:

(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 popup 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:

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

(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 on 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 popups listed the Notification Groups targets in the order in which they were created, not alphabetical 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 on a query listed on the Query Analyzer page resulted in a delay of around 28 seconds before the popup was displayed. (Bug#44601)

The frequency shown on the Advanced tab of an Event popup 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 allow 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:

(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 allow 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 allowed 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)

MySQL Connector/ODBC has been changed to support the CLIENT_INTERACTIVE flag. (Bug#48603)

The SQLColumns function returned the incorrect transfer octet length and display size for DECIMAL type. (Bug#53235)

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)

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)

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

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 allowing faster configuration of a Data Source. (Bug#42905)

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)

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)

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)

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.

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)

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.

Explicit descriptors are implemented. (Bug#32064)

A full implementation of SQLForeignKeys based on the information available from INFORMATION_SCHEMA in 5.0 and later versions of the server has been implemented.

Changed SQL_ATTR_PARAMSET_SIZE to return an error until support for it is implemented.

Disabled MYSQL_OPT_SSL_VERIFY_SERVER_CERT when using an SSL connection.

SQLForeignKeys uses INFORMATION_SCHEMA when it is available on the server, which allows more complete information to be returned.

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:

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

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.

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: Disallow SET NAMES in initial statement and in executed statements.

A wrapper for the SQLGetPrivateProfileStringW() function, which is required for Unicode support, has been created. This function is missing from the unixODBC driver manager. (Bug#32685)

Added MSI installer for Windows 64-bit. (Bug#31510)

Implemented support for SQLCancel(). (Bug#15601)

Added support for SQL_NUMERIC_STRUCT. (Bug#3028, Bug#24920)

Removed nonthreadsafe configuration of the driver. The driver is now always built against the threadsafe version of libmysql.

Implemented native Windows setup library

Replaced the internal library which handles creation and loading of DSN information. The new library, which was originally a part of 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.

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.

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.

Added support for Unicode functions (SQLConnectW, etc).

Added descriptor support (SQLGetDescField, SQLGetDescRec, etc).

Added support for SQL_C_WCHAR.

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)

Added support for ODBC v2 statement options using attributes.

Driver now builds and is partially tested under Linux with the iODBC driver manager.

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.

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

Editing DSN no longer crashes ODBC data source administrator. (Bug#24675)

String query parameters are new escaped correctly. (Bug#19078)

Added support for column binding as SQL_NUMBERIC_STRUCT.

Added recognition of SQL_C_SHORT and SQL_C_TINYINT as C types.

Fixed wildcard handling of and listing of catalogs and tables in SQLTables.

Added limit of display size when requested via SQLColAttribute/SQL_DESC_DISPLAY_SIZE.

Fixed buffer length return for SQLDriverConnect.

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

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

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.

Added support for SQLStatistics to MYODBCShell.

Improved trace/log.

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.

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.

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

You no longer have to have MySQL Connector/ODBC 3.51 installed before installing this version.

The following ODBC API functions have been added in 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:

The following ODBC API function are implemented, but not yet support all the available attributes/options:

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)

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)

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)

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)

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:

(Bug#12805, Bug#30890)

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.

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

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.

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)

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.

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)

When using a rowset/cursor and add a new row with a number of fields, subsequent rows with fewer fields will include the original fields from the previous row in the final INSERT statement. (Bug#31246)

Uninitiated memory could be used when C/ODBC internally calls SQLGetFunctions(). (Bug#31055)

The wrong SQL_DESC_LITERAL_PREFIX would be returned for date/time types. (Bug#31009)

The wrong COLUMN_SIZE would be returned by SQLGetTypeInfo for the TIME columns (SQL_TYPE_TIME). (Bug#30939)

Clicking outside the character set selection box when configuring a new DSN could cause the wrong character set to be selected. (Bug#30568)

Not specifying a user in the DSN dialog would raise a warning even though the parameter is optional. (Bug#30499)

SQLSetParam() caused memory allocation errors due to driver manager's mapping of deprecated functions (buffer length -1). (Bug#29871)

When using ADO, a column marked as AUTO_INCREMENT could incorrectly report that the column allowed NULL values. This was dur to an issue with NULLABLE and IS_NULLABLE return values from the call to SQLColumns(). (Bug#26108)

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)

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.

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.

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.

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. In order to enable cached statement support you must switch enable the batched statement option (FLAG_MULTI_STATEMENTS, 67108864, or Allow multiple statements within a GUI configuration). Be aware that batched statements create an increased chance of SQL injection attacks and you must ensure that your application protects against this scenario. (Bug#7445)

The SQL_ATTR_ROW_BIND_OFFSET_PTR is now supported for row bind offsets. (Bug#6741)

The TRACE and TRACEFILE DSN options have been removed. Use the ODBC driver manager trace options instead.

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.

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.

It is now possible to specify a different character set as part of the DSN or connection string. This must be used instead of the SET NAMES statement. You can also configure the character set value from the GUI configuration. (Bug#9498, Bug#6667)

Fixed calling convention ptr and wrong free in myodbc3i, and fixed the null terminating (was only one, not two) when writing DSN to string.

Dis-allow NULL ptr for null indicator when calling SQLGetData() if value is null. Now returns SQL_ERROR w/state 22002.

The setup library has been split into its own RPM package, to allow installing the driver itself with no GUI dependencies.

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 allowed ODBC date (XXXX-01-01). Added another option (FLAG_MIN_DATE_TO_ZERO) to mirror this but for bound parameters. FLAG_MIN_DATE_TO_ZERO only changes 0000-01-01 to 0000-00-00. (Bug#13766)

If there was more than one unique key on a table, the correct fields were not used in handling SQLSetPos(). (Bug#10563)

When inserting a large BLOB field, 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.

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)

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)

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)

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

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)

N/A

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)

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)