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

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

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

Performance: The performance of internal functions that trim multiple spaces from strings when comparing them has been improved. (Bug#14637)

Incompatible Change: The following obsolete constructs have been removed. Where alternatives are shown, applications should be updated to use them.

(Bug#48048)

See also Bug#47974.

Incompatible Change: Aliases for wildcards (as in SELECT t.* AS 'alias' FROM t) are no longer accepted and result in an error. Previously, such aliases were ignored silently. (Bug#27249)

Incompatible Change: The server now includes dtoa, a library for conversion between strings and numbers by David M. Gay. In MySQL, this library provides the basis for improved conversion between string or DECIMAL values and approximate-value (FLOAT/DOUBLE) numbers:

Because the conversions produced by this library differ in some cases from previous results, the potential exists for incompatibilities in applications that rely on previous results. For example, applications that depend on a specific exact result from previous conversions might need adjustment to accommodate additional precision.

For additional information about the properties of dtoa conversions, see Section 11.2.2, “Type Conversion in Expression Evaluation”.

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

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

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

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

See also Bug#44270.

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

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

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

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

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

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

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

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

For boolean options, the option-processing library now prints additional information in the --help message: If the option is enabled by default, the message says so and indicates that the --skip form of the option disables the option. This affects all compiled MySQL programs that use the library. (Bug#35224)

The use of the SQL_CACHE and SQL_NO_CACHE options in SELECT statements now is checked more restrictively: 1) Previously, both options could be given in the same statement. This is no longer true; only one can be given. 2) Previously, these options could be given in SELECT statements that were not at the top-level. This is no longer true; the options are disallowed in subqueries (including subqueries in the FROM clause, and SELECT statements in unions other than the first SELECT. (Bug#35020)

Added the --auto-vertical-output option to mysql which causes result sets to be displayed vertically if they are too wide for the current window, and using normal tabular format otherwise. (This applies to statements terminated by ; or \G.) (Bug#26780)

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

See also Bug#46452.

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

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

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

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

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

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

(Bug#8368)

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

Some conversions between Japanese character sets are more efficient.

When the server detects MyISAM table corruption, it now writes additional information to the error log, such as the name and line number of the source file, and the list of threads accessing the table. Example: Got an error from thread_id=1, mi_dynrec.c:368. This is useful information to include in bug reports.

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

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

The maximum length of table comments was extended from 60 to 2048 characters. The maximum length of column comments was extended from 255 to 1024 characters. Index definitions now can include a comment of up to 1024 characters.

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

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

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

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

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

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

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

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

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

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

Incompatible Change: The parser accepted illegal syntax in a FOREIGN KEY clause:

These illegal syntaxes are now properly rejected. Existing applications that used them will require adjustment. (Bug#34455)

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

Incompatible Change: Several changes were made to the processing of multiple-table DELETE statements:

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

See also Bug#30234.

Incompatible Change: DROP TABLE now is allowed only if you have acquired a WRITE lock with LOCK TABLES, or if you hold no locks, or if the table is a TEMPORARY table.

Previously, if other tables were locked, you could drop a table with a read lock or no lock, which could lead to deadlocks between clients. The new stricter behavior means that some usage scenarios will fail when previously they did not. (Bug#25858)

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

This bug fix results in some incompatibilities with previous versions:

(Bug#989, Bug#39675)

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

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

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

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

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

See also Bug#46654.

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

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

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

Partitioning: When one user was in the midst of a transaction on a partitioned table, a second user performing an ALTER TABLE on this table caused the server to hang. (Bug#34604)

Partitioning: Portions of the partitioning code were refactored in response to potential regression issues uncovered while working on the fix for Bug#31210. (Bug#32115)

See also Bug#40281.

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

See also Bug#51716.

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

See also Bug#51787.

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

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

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

Replication: On a replication slave, a race condition between the I/O thread and FLUSH LOGS could crash the server. (Bug#50364)

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

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

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

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

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

See also Bug#48776.

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

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

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

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

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

This regression was introduced by Bug#13963.

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

See also Bug#40278.

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

See also Bug#319, Bug#38205.

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

(Bug#45855, Bug#45856)

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

See also Bug#39934.

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

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

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

(Bug#45516)

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

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

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

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

(Bug#43929)

See also Bug#37148.

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

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

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

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

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

See also Bug#38715, Bug#44312.

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

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

See also Bug#35543.

Replication: A CHANGE MASTER TO statement with no MASTER_HEARTBEAT_PERIOD option failed to reset the heartbeat period to its default value. (Bug#34686)

Replication: Formerly, only slaves that had been started with the --report-hosts option were visible in the output of SHOW SLAVE HOSTS. Now, all slaves that are registered with the master appear in SHOW SLAVE HOSTS output. (Bug#13963)

See also Bug#21132, Bug#21869.

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

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

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

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

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

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

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

An uninitialized hash table caused a crash when accessed. (Bug#50555)

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

comp_err did not build on FreeBSD. (Bug#50362)

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

mysqld did not recognize most of the options given on the command line when it was compiled for 32-bit Solaris using the Sun Studio compiler. (Bug#50221)

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

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

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

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

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

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

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

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

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

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

If IPv6 support in the operating system was turned off, mysqld crashed in network_init(). (Bug#48915)

Building MySQL on Fedora Core 12 64-bit failed, due to errors in comp_err. (Bug#48864)

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

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

If an INSERT DELAYED handler thread was killed by a connection, the error message was copied from the handler thread to the connection thread but not acted on, leading to an assert. (Bug#48725)

Concurrent execution of INSERT DELAYED and FLUSH TABLES could lead to deadlock. (Bug#48724)

If a prepared statement using a merged view referencing an INFORMATION_SCHEMA table was executed, no metadata lock of the view was taken. Consequently, it was possible for concurrent DDL statements on the view to execute and cause statements to be written in the wrong order to the binary log. (Bug#48315)

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

If REPAIR TABLE was used on a table already read-locked by LOCK TABLES, the repair mistakenly tried to upgrade the read lock to an exclusive lock, triggering an assertion. (Bug#48248)

FLUSH TABLES WITH READ LOCK could deadlock when executed against concurrent DDL statements for stored routines or account-management statements. (Bug#48210)

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

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

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

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

The assert could be raised if ALTER VIEW was used to alter a view (existing or nonexisting) and a temporary table with the same name already existed. (Bug#47335)

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

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

See also Bug#43733.

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

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

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

When HANDLER OPEN was attempted on a MERGE table, an error occurred because this is an unsupported operation, but locks could remain unreleased. (Bug#47098)

For debug builds, an assertion failure could result from concurrent execution of statements involving stored functions or triggers that were using several tables and DDL statements that affected those tables. (Bug#46748)

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

Selecting from a MERGE table with a corrupted child MyISAM table could cause a server crash when the server attempted to automatically repair the child table. (Bug#46610)

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

HANDLER OPEN followed by TRUNCATE TABLE could cause a server crash. (Bug#46452)

See also Bug#20667.

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

HANDLER statements within a transaction that already holds metadata locks could lead to deadlocks. (Bug#46224)

Deadlock could occur for INFORMATION_SCHEMA queries when execution attempted to open a table or its .frm file. (Bug#46044)

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

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

See also Bug#18484.

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

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

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

(Bug#45606)

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

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

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

A Windows Installation using the GUI installer would fail with:

MySQL Server 5.1 Setup Wizard ended prematurely

The wizard was interrupted before MySQL Server 5.1. could be completely installed.

Your system has not been modified. To complete installation at another time, please run
setup again.

Click Finish to exit the wizard

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

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

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

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

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

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

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

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

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

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

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

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

See also Bug#47757.

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

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

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

#Create a test table
CREATE TABLE tmp (id int, c char(2));                                           

#Create two VIEWs upon it
CREATE VIEW v1 AS SELECT * FROM tmp;                                            
CREATE VIEW v2 AS SELECT * FROM tmp;                                            

#Finally create a MERGE table upon the VIEWs
CREATE TABLE merge (id int, c char(2))
ENGINE=MERGE UNION(v1, v2);

#Reading from the merge table lead to a crash
SELECT * FROM merge;

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

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

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

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

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

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

In addition, the IPv6-enabled server on Windows interpeted the hostname localhost as ::1 only, which failed to match the default root@127.0.0.1 entry in the mysql.user privilege table. (Bug#43006)

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

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

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

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

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

Concurrent execution of a LOCK TABLES ... READ statement and DML statements affecting the same InnoDB table for debug builds of MySQL server might lead to Found lock of type 6 that is write and read locked warnings in the error log. (Bug#42147)

Setting key_buffer_size to a negative value could lead to very large allocations. Now an error occurs. (Bug#42103)

An assertion failure could occur if OPTIMIZE TABLE was started on an InnoDB table and the table was altered to a different storage engine during the optimization operation. (Bug#42074)

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

The patch for Bug#10374 broke named-pipe and shared-memory connections on Windows. (Bug#41860)

Purging the stored routine cache could take a long time and render the server unresponsive. (Bug#41804)

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

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

mysqld_safe did not treat dashes and underscores as equivalent in option names. Thanks to Erik Ljungstrom for the patch to fix this bug. (Bug#40368)

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

Plugin shutdown could lead to an assertion failure caused by using an already destroyed mutex in the metadata locking subsystem. (Bug#39674)

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

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

flush_cache_records() did not correctly check for errors that should cause statement execution to stop, leading to a server crash. (Bug#39022)

Valgrind warnings that occurred for SHOW TABLE STATUS with InnoDB tables were silenced. (Bug#38479)

An IPv6-enabled MySQL server did not resolve the IP addresses of incoming connections correctly, with the result that a connection that attempted to match any privilege table entries using fully-qualified domain names for hostnames or hostnames using wildcards were dropped. (Bug#38247)

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

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

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

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

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

The parser incorrectly allowed MySQL error code 0 to be specified for a condition handler. (This is incorrect because the condition must be a failure condition and 0 indicates success.) (Bug#36510)

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

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

mysql_stmt_prepare() did not reset the list of messages (those messages available via SHOW WARNINGS). (Bug#36004)

mysqlbinlog left temporary files on the disk after shutdown, leading to the pollution of the temporary directory, which eventually caused mysqlbinlog to fail. This caused problems in testing and other situations where mysqlbinlog might be invoked many times in a relatively short period of time. (Bug#35543)

When building MySQL when using a different target directory (for example using the VPATH environment variable), the build of the embedded readline component would fail. (Bug#35250)

String-valued system variables could be assigned literal values, but could not be assigned values using expressions. Now expressions are legal. (Bug#34883, Bug#46314)

The sql_mode system variable could be assigned the illegal value of '?'. (Bug#34834)

Some system variables could not be assigned the value DEFAULT to assign their default value. (Bug#34829, Bug#34878)

Compiling MySQL on FreeBSD would fail due to missing definitions for certain network constants. (Bug#34292)

Creation of a temporary BLOB or TEXT column could create a column with the wrong maximum length. (Bug#33969)

INSERT INTO ... VALUES(DEFAULT) failed to insert the correct value for ENUM columns. For MyISAM tables, an empty value was inserted. For CSV tables, the table became corrupt. (Bug#33717)

When read_only was enabled, the server incorrectly prevented data modifications to TEMPORARY tables belonging to transactional storage engines such as InnoDB. (Bug#33669)

Constant expressions in WHERE, HAVING, or ON clauses were not cached, but were evaluated for each row. This caused a slowdown of query execution, especially if constant user-defined functions or stored functions were used. (Bug#33546)

The parser accepted an INTO clause in nested SELECT statements, which is invalid because such statements must return their results to the outer context. (Bug#33204)

Killing a statement that invoked a stored function could return an incorrect error message indicating table corruption rather than that the statement had been interrupted. (Bug#32140)

Occurrence of an error within a stored routine did not always cause immediate statement termination. (Bug#31881)

For DROP FUNCTION db_name.func_name (that is, when the function name is qualified with the database name), the statement should apply only to a stored function named func_name in the given database. However, if a UDF with the same name existed, the statement dropped the UDF instead. (Bug#31767)

Concurrent statements using a stored function and DROP FUNCTION for that function could break statement-based replication. (Bug#30977)

mysqld sometimes miscalculated the number of digits required when storing a floating-point number in a CHAR column. This caused the value to be truncated, or (when using a debug build) caused the server to crash. (Bug#26788)

See also Bug#12860.

ALTER TABLE could not be used to add columns to a table if the table had an index on a utf8 column with a TEXT data type. (Bug#26180)

If an operation had an InnoDB table, and two triggers, AFTER UPDATE and AFTER INSERT, competing for different resources (such as two distinct MyISAM tables), the triggers were unable to execute concurrently. In addition, INSERT and UPDATE statements for the InnoDB table were unable to run concurrently. (Bug#26141)

Some system variables displayed by SHOW VARIABLES could not be selected using SELECT @@{GLOBAL,SESSION}.var_name. (Bug#25430)

Statements to create, alter, or drop a view were not waiting for completion of statements that were using the view, which led to incorrect sequences of statements in the binary log when statement-based logging was enabled. (Bug#25144)

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

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

Data truncated for column col_num at row row_num warnings were generated for some (constant) values that did not have too high precision. (Bug#24541)

A statement that caused a circular wait among statements did not return a deadlock error. Now the server detects deadlock and returns ER_LOCK_DEADLOCK. (Bug#22876)

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

When inserting an extraordinarly large value into a DOUBLE column, the value could be truncated in such a way that the new value cannot be reloaded manually or from the output of mysqldump. (Bug#21497)

The value of sql_slave_skip_counter was empty when displayed by SHOW VARIABLES or INFORMATION_SCHEMA.GLOBAL_VARIABLES. (Bug#20413, Bug#37187)

For INSERT DELAYED statements issued for a table while an ALTER TABLE operation on the table was in progress, the server could return a spurious Server shutdown in progress error. (Bug#18484)

See also Bug#45949.

Delayed-insert threads were counted as connected but not as created, incorrectly leading to a Threads_connected value greater than the Threads_created value. (Bug#17954)

The character set was not being properly initialized for CAST() with a type such as CHAR(2) BINARY, which resulted in incorrect results or a server crash. (Bug#17903)

Stored procedure exception handlers were catching fatal errors (such as out of memory errors), which could cause execution not to stop to due a continue handler. Now fatal errors are not caught by exception handlers and a fatal error is returned to the client. (Bug#15192)

Zero-padding of exponent values was not the same across platforms. (Bug#12860)

For CREATE TABLE, the parser did not enforce that parentheses were present in a CHECK (expr) clause; now it does. The parser did not enforce that CONSTRAINT [symbol] without a following CHECK clause was illegal; now it does. (Bug#11714, Bug#35578, Bug#38696)

If a connection was waiting for a GET_LOCK() lock or a SLEEP() call, and the connection aborted, the server did not detect this and thus did not close the connection. This caused a waste of system resources allocated to dead connections. Now the server checks such a connection every five seconds to see whether it has been aborted. If so, the connection is killed (and any lock request is aborted). (Bug#10374)

perror did not work for errors described in the sql/share/errmsg.txt file. (Bug#10143)

The grammar for GROUP BY, when used with WITH CUBE or WITH ROLLUP, caused a conflict with the grammar for view definitions that included WITH CHECK OPTION. (Bug#9801)

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

Labels in stored routines did not work if the character set was not latin1. (Bug#7088)

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

Replication: Introduced the --binlog-direct-non-transactional-updates server option. This option causes updates using the statement-based logging format to tables using nontransactional engines to be written directly to the binary log, rather than to the transaction cache.

Before using this option, be certain that you have no dependencies between transactional and nontransactional tables. A statement that both selects from an InnoDB table and inserts into a MyISAM table is an example of such a dependency. For more information, see Section 16.1.3.4, “Binary Log Options and Variables”. (Bug#46364)

See also Bug#28976, Bug#40116.

Performance: The method for comparing INFORMATION_SCHEMA names and database names was nonoptimal and an improvement was made: When the database name length is already known, a length check is made first and content comparison skipped if the lengths are unequal. (Bug#49501)

Performance: The MD5() and SHA1() functions had excessive overhead for short strings. (Bug#49491)

Security Fix: For servers built with yaSSL, a preauthorization buffer overflow could cause memory corruption or a server crash. We thank Evgeny Legerov from Intevydis for providing us with a proof-of-concept script that allowed us to reproduce this bug. (Bug#50227, CVE-2009-4484)

Incompatible Change: In plugin.h, the MYSQL_REPLICATION_PLUGIN symbol was out of synchrony with its value in MySQL 6.0 because the lower-valued MYSQL_AUDIT_PLUGIN was not present. To correct this, MYSQL_AUDIT_PLUGIN has been added in MySQL 5.5, changing the value of MYSQL_REPLICATION_PLUGIN from 5 to 6. Attempts to load the audit plugin produce an error occurs because only the MYSQL_AUDIT_PLUGIN symbol was added, not the audit plugin itself. This error will go away when the audit plugin is added to MySQL 5.5. Replication plugins from earlier 5.5.x releases must be recompiled against the current release before they will work with the current release. (Bug#49894)

Important Change: Replication: The RAND() function is now marked as unsafe for statement-based replication. Using this function now generates a warning when binlog_format=STATEMENT and causes the the format to switch to row-based logging when binlog_format=MIXED.

This change is being introduced because, when RAND() was logged in statement mode, the seed was also written to the binary log, so the replication slave generated the same sequence of random numbers as was generated on the master. While this could make replication work in some cases, the order of affected rows was still not guaranteed when this function was used in statements that could update multiple rows, such as UPDATE or INSERT ... SELECT; if the master and the slave retrieved rows in different order, they began to diverge. (Bug#49222)

Partitioning: When used on partitioned tables, the records_in_range handler call checked all partitions, rather than the unpruned partitions only. (Bug#48846)

See also Bug#37252, Bug#47261.

Partitioning: When an ALTER TABLE ... REORGANIZE PARTITION statement on an InnoDB table failed due to innodb_lock_wait_timeout expiring while waiting for a lock, InnoDB did not clean up any temporary files or tables which it had created. Attempting to reissue the ALTER TABLE statement following the timeout could lead to storage engine errors, or possibly a crash of the server. (Bug#47343)

Replication: FLUSH LOGS could in some circumstances crash the server. This occurred because the I/O thread could concurrently access the relay log I/O cache while another thread was performing the FLUSH LOGS, which closes and reopens the relay log and, while doing so, initializes (or re-initializes) its I/O cache. This could cause problems if some other thread (in this case, the I/O thread) is accessing it at the same time.

Now the thread performing the FLUSH LOGS takes a lock on the relay log before actually flushing it. (Bug#50364)

Replication: With semisynchronous replication, memory allocated for handling transactions could be freed while still in use, resulting in a server crash. (Bug#50157)

Replication: In some cases, inserting into a table with many columns could cause the binary log to become corrupted. (Bug#50018)

See also Bug#42749.

Replication: When using row-based replication, setting a BIT or CHAR column of a MyISAM table to NULL, then trying to delete from the table, caused the slave to fail with the error Can't find record in table. (Bug#49481, Bug#49482)

Replication: A LOAD DATA INFILE statement that loaded data into a table having a column name that had to be escaped (such as `key` INT) caused replication to fail when logging in mixed or statement mode. In such cases, the master wrote the LOAD DATA event into the binary log without escaping the column names. (Bug#49479)

See also Bug#47927.

Replication: When logging in row-based mode, DDL statements are actually logged as statements; however, statements that affected temporary tables and followed DDL statements failed to reset the binary log format to ROW, with the result that these statements were logged using the statement-based format. Now the state of binlog_format is restored after a DDL statement has been written to the binary log. (Bug#49132)

Replication: Spatial data types caused row-based replication to crash. (Bug#48776)

Replication: When using row-based logging, the statement CREATE TABLE t IF NOT EXIST ... SELECT was logged as CREATE TEMPORARY TABLE t IF NOT EXIST ... SELECT when t already existed as a temporary table. This was caused by the fact that the temporary table was opened and the results of the SELECT were inserted into it when a temporary table existed and had the same name.

Now, when this statement is executed, t is created as a base table, the results of the SELECT are inserted into it — even if there already exists a temporary table having the same name — and the statement is logged correctly. (Bug#47418)

See also Bug#47442.

Replication: Due to a change in the size of event representations in the binary log, when replicating from a MySQL 4.1 master to a slave running MySQL 5.0.60 or later, the START SLAVE UNTIL statement did not function correctly, stopping at the wrong position in the log. Now the slave detects that the master is using the older version of the binary log format, and corrects for the difference in event size, so that the slave stops in the correct position. (Bug#47142)

Replication: Manually removing entries from the binary log index file on a replication master could cause the server to repeatedly send the same binary log file to slaves. (Bug#28421)

The SSL certificates in the test suite were about to expire. They have been updated with expiration dates in the year 2015. (Bug#50642)

SPATIAL indexes were allowed on columns with non-spatial data types, resulting in a server crash for subsequent table inserts. (Bug#50574)

Index prefixes could be specified with a length greater than the associated column, resulting in a server crash for subsequent table inserts. (Bug#50542)

Use of loose index scan optimization for an aggregate function with DISTINCT (for example, COUNT(DISTINCT)) could produce incorrect results. (Bug#50539)

The printstack function does not exist on Solaris 8 or earlier, which would lead to a compilation failure. (Bug#50409)

A user could see tables in INFORMATION_SCHEMA.TABLES without appropriate privileges for them. (Bug#50276)

Debug output for join structures was garbled. (Bug#50271)

The server crashed when an InnoDB background thread attempted to write a message containing a partitioned table name to the error log. (Bug#50201)

Within a stored routine, selecting the result of CONCAT_WS() with a routine parameter argument into a user variable could return incorrect results. (Bug#50096)

The filesort sorting method applied to a CHAR(0) column could lead to a server crash. (Bug#49897)

EXPLAIN EXTENDED UNION ... ORDER BY caused a crash when the ORDER BY referred to a nonconstant or full-text function or a subquery. (Bug#49734)

Some prepared statements could raise an assertion when re-executed. (Bug#49570)

sql_buffer_result had an effect on non-SELECT statements, contrary to the documentation. (Bug#49552)

In some cases a subquery need not be evaluated because it returns only aggregate values that can be calculated from table metadata. This sometimes was not handled by the enclosing subquery, resulting in a server crash. (Bug#49512)

Mixing full-text searches and row expressions caused a crash. (Bug#49445)

Creating or dropping a table with 1023 transactions active caused an assertion failure. (Bug#49238)

mysql-test-run.pl now recognizes the MTR_TESTCASE_TIMEOUT, MTR_SUITE_TIMEOUT, MTR_SHUTDOWN_TIMEOUT, and MTR_START_TIMEOUT environment variables. If they are set, their values are used to set the --testcase-timeout, --suite-timeout, --shutdown-timeout, and --start-timeout options, respectively. (Bug#49210)

Several strmake() calls had an incorrect length argument (too large by one). (Bug#48983)

On Fedora 12, strmov() did not guarantee correct operation for overlapping source and destination buffer. Calls were fixed to use an overlap-safe version instead. (Bug#48866)

With one thread waiting for a lock on a table, if another thread dropped the table and created a new table with the same name and structure, the first thread would not notice that the table had been re-created and would try to used cached metadata that belonged to the old table but had been freed. (Bug#48157)

If an invocation of a stored procedure failed in the table-open stage, subsequent invocations that did not fail in that stage could cause a crash. (Bug#47649)

A crash occurred when a user variable that was assigned to a subquery result was used as a result field in a SELECT statement with aggregate functions. (Bug#47371)

When the mysql client was invoked with the --vertical option, it ignored the --skip-column-names option. (Bug#47147)

If innodb_force_recovery was set to 4 or higher, the server could crash when opening an InnoDB table containing an auto-increment column. MySQL versions 5.1.31 and later were affected. (Bug#46193)

The optimizer could continue to execute a query after a storage engine reported an error, leading to a server crash. (Bug#46175)

If EXPLAIN encountered an error in the query, a memory leak occurred. (Bug#45989)

A race condition on the privilege hash tables allowed one thread to try to delete elements that had already been deleted by another thread. A consequence was that SET PASSWORD or FLUSH PRIVILEGES could cause a crash. (Bug#35589, Bug#35591)

1) In rare cases, if a thread was interrupted during a FLUSH PRIVILEGES operation, a debug assertion occurred later due to improper diagnostic area setup. 2) A KILL operation could cause a console error message referring to a diagnostic area state without first ensuring that the state existed. (Bug#33982)

ALTER TABLE with both DROP COLUMN and ADD COLUMN clauses could crash or lock up the server. (Bug#31145)

The Table_locks_waited waited variable was not incremented in the cases that a lock had to be waited for but the waiting thread was killed or the request was aborted. (Bug#30331)

InnoDB Plugin has been upgraded to version 1.0.6. This version is considered of Release Candidate (RC) quality. The InnoDB Plugin Change History may contain information in addition to those changes reported here.

The version information in RPM package files has been changed:

For example, the generic x86 server RPM file of 5.5.1-m2 is named MySQL-server-5.5.1_m2-1.glibc23.i386.rpm. This improves consistency with other formats that also include the level (for this version: “m2”) in the file name. For example, the tar.gz filename is mysql-5.5.1-m2-linux-i686-glibc23.tar.gz. The different separator, underscore '_' for RPM, is required by the syntax of RPM.

Partitioning: The UNIX_TIMESTAMP() function is now supported in partitioning expressions using TIMESTAMP columns. For example, it now possible to create a partitioned table such as this one:

CREATE TABLE t (c TIMESTAMP) 
PARTITION BY RANGE ( UNIX_TIMESTAMP(c) ) (
    PARTITION p0 VALUES LESS THAN (631148400),
    PARTITION p1 VALUES LESS THAN (946681200),
    PARTITION p2 VALUES LESS THAN (MAXVALUE)
);

All other expressions involving TIMESTAMP values are now rejected with an error when attempting to create a new partitioned table or to alter an existing partitioned table.

When accessing an existing partitioned table having a timezone-dependent partitioning function (where the table was using a previous version of MySQL), a warning rather than an error is issued. In such cases, you should fix the table. One way of doing this is to alter the table's partitioning expression so that it uses UNIX_TIMESTAMP(). (Bug#42849)

Performance: When the query cache is fragmented, the size of the free block lists in the memory bins grows, which causes query cache invalidation to become slow. There is now a 50ms timeout for a SELECT statement waiting for the query cache lock. If the timeout expires, the statement executes without using the query cache. (Bug#39253)

See also Bug#21074.

Incompatible Change: Replication: The file names for the semisynchronous plugins were prefixed with lib, unlike file names for other plugins. The file names no longer have a lib prefix.

This change introduces an incompatibility if the plugins had been installed using the previous names. To handle this, uninstall the older version before installing the newer version. For example, use these statements for the master side plugins on Unix:

mysql> UNINSTALL PLUGIN rpl_semi_sync_master;
mysql> INSTALL PLUGIN rpl_semi_sync_master SONAME 'semisync_master.so';

If you do not uninstall the older version first, attempting to install the newer version results in an error:

mysql> INSTALL PLUGIN rpl_semi_sync_master SONAME 'semisync_master.so';
ERROR 1125 (HY000): Function 'rpl_semi_sync_master' already exists

For the slave side, similar statements apply:

mysql> UNINSTALL PLUGIN rpl_semi_sync_slave;
mysql> INSTALL PLUGIN rpl_semi_sync_slave SONAME 'semisync_slave.so';

Important Change: Replication: The following functions have been marked unsafe for statement-based replication:

None of the functions just listed are guaranteed to replicate correctly when using the statement-based format, because they can produce different results on the master and the slave. The use of any of these functions while binlog_format is set to STATEMENT is logged with the warning, Statement is not safe to log in statement format. When binlog_format is set to MIXED, the binary logging format is automatically switched to the row-based format whenever one of these functions is used. (Bug#47995)

Partitioning: When SHOW CREATE TABLE was invoked for a table that had been created using the COLUMNS keyword or the TO_SECONDS() function, the output contained the wrong MySQL version number in the conditional comments. (Bug#49591)

Partitioning: A query that searched on a ucs2 column failed if the table was partitioned. (Bug#48737)

Partitioning: In some cases, it was not possible to add a new column to a table that had subpartitions. (Bug#48276)

Partitioning: SELECT COUNT(*) from a partitioned table failed when using the ONLY_FULL_GROUP_BY SQL mode. (Bug#46923)

This regression was introduced by Bug#45807.

Partitioning: SUBPARTITION BY KEY failed with DEFAULT CHARSET=utf8. (Bug#45904)

Replication: When using row-based logging, TRUNCATE TABLE was written to the binary log even if the affected table was temporary, causing replication to fail. (Bug#48350)

Replication: A flaw in the implementation of the purging of binary logs could result in orphaned files being left behind in the following circumstances:

In addition, if the slave was not connected during the purge operation, it was possible for a log file that was in use to be removed; this could lead data loss and possible inconsistencies between the master and slave. (Bug#45292)

Replication: When using the STATEMENT or MIXED logging format, the statements LOAD DATA CONCURRENT LOCAL INFILE and LOAD DATA CONCURRENT INFILE were logged as LOAD DATA LOCAL INFILE and LOAD DATA LOCAL INFILE, respectively (in other words, the CONCURRENT keyword was omitted). As a result, when using replication with either of these logging modes, queries on the slaves were blocked by the replication SQL thread while trying to execute the affected statements. (Bug#34628)

Cluster Replication: When expire_logs_days was set, the thread performing the purge of the log files could deadlock, causing all binary log operations to stop. (Bug#49536)

For debug builds on Windows, SAFEMALLOC was defined inconsistently, leading to mismatches when using my_malloc() and my_free(). (Bug#49811)

The mysql.server script had incorrect shutdown logic. (Bug#49772)

The push_warning_printf() function was being called with an invalid error level MYSQL_ERROR::WARN_LEVEL_ERROR, causing an assertion failure. To fix the problem, MYSQL_ERROR::WARN_LEVEL_ERROR has been replaced by MYSQL_ERROR::WARN_LEVEL_WARN. (Bug#49638)

The result of comparison between nullable BIGINT and INT columns was inconsistent. (Bug#49517)

A Valgrind error in make_cond_for_table_from_pred() was corrected. Thanks to Sergey Petrunya for the patch to fix this bug. (Bug#49506)

When compiling on Windows, an error in the CMake definitions for InnoDB would cause the engine to be built incorrectly. (Bug#49502)

Incorrect cache initialization prevented storage of converted constant values and could produce incorrect comparison results. (Bug#49489)

Comparisons involving YEAR values could produce incorrect results. (Bug#49480)

See also Bug#43668.

Valgrind warnings for CHECKSUM TABLE were corrected. (Bug#49465)

Specifying an index algorithm (such as BTREE) for SPATIAL or FULLTEXT indexes caused a server crash. These index types do not support algorithm specification, and it is now disallowed to do so. (Bug#49250)

The optimizer sometimes incorrectly handled conditions of the form WHERE col_name='const1' AND col_name='const2'. (Bug#49199)

Execution of DECODE() and ENCODE() could be inefficient because multiple executions within a single statement reinitialized the random generator multiple times even with constant parameters. (Bug#49141)

With binary logging enabled, REVOKE ... ON {PROCEDURE|FUNCTION} FROM ... could cause a crash. (Bug#49119)

The LIKE operator did not work correctly when using an index for a ucs2 column. (Bug#49028)

check_key_in_view() was missing a DBUG_RETURN in one code branch, causing a crash in debug builds. (Bug#48995)

If a query involving a table was terminated with KILL, a subsequent SHOW CREATE TABLE for that table caused a server crash. (Bug#48985)

Privileges for stored routines were ignored for mixed-case routine names. (Bug#48872)

See also Bug#41049.

Building MySQL on Fedora Core 12 64-bit failed, due to errors in comp_err. (Bug#48864)

Concurrent ALTER TABLE operations on an InnoDB table could raise an assertion. (Bug#48782)

Incomplete reset of internal TABLE structures could cause a crash with eq_ref table access in subqueries. (Bug#48709)

During query execution, ranges could be merged incorrectly for OR operations and return an incorrect result. (Bug#48665)

The InnoDB Table Monitor reported the FLOAT and DOUBLE data types incorrectly. (Bug#48526)

Re-execution of a prepared statement could cause a server crash. (Bug#48508)

With row-based binary logging, the server crashed for statements of the form CREATE TABLE IF NOT EXISTS existing_view LIKE temporary_table. This occurred because the server handled the existing view as a table when logging the statement. (Bug#48506)

The error message for ER_UPDATE_INFO was subject to buffer overflow or truncation. (Bug#48500)

DISTINCT was ignored for queries with GROUP BY WITH ROLLUP and only const tables. (Bug#48475)

Loose index scan was inappropriately chosen for some WHERE conditions. (Bug#48472)

The server could crash and corrupt the tablespace if the InnoDB tablespace was configured with too small a value, or if many CREATE TEMPORARY TABLE statements were executed and the temporary file directory filled up with innodb_file_per_table enabled. (Bug#48469)

Parts of the range optimizer could be initialized incorrectly, resulting in Valgrind errors. (Bug#48459)

A bad typecast could cause query execution to allocate large amounts of memory. (Bug#48458)

SHOW BINLOG EVENTS could fail with a error: Wrong offset or I/O error. (Bug#48357)

Valgrind warnings related to binary logging of LOAD DATA INFILE statements were corrected. (Bug#48340)

On Windows, InnoDB could not be built as a statically linked library. (Bug#48317)

mysql_secure_installation did not work on Solaris. (Bug#48086)

When running mysql_secure_installation, the command would fail if the root password contained multiple spaces, \, # or quote characters. (Bug#48031)

MATCH IN BOOLEAN MODE searches could return too many results inside a subquery. (Bug#47930)

User-defined collations with an ID less then 256 were not initialized correctly when loaded and caused a server crash. (Bug#47756)

If a session held a global read lock acquired with FLUSH TABLES WITH READ LOCK, a lock for one table acquired with LOCK TABLES, and issued an INSERT DELAYED statement for another table, deadlock could occur. (Bug#47682)

The mysql client status command displayed an incorrect value for the server character set. (Bug#47671)

Connecting to a 4.1.x server from a 5.1.x or higher mysql client resulted in a memory-free error when disconnecting. (Bug#47655)

Queries containing GROUP BY ... WITH ROLLUP that did not use indexes could return incorrect results. (Bug#47650)

Assignment of a system variable sharing the same base name as a declared stored program variable in the same context could lead to a crash. (Bug#47627)

On Solaris, no stack trace was printed to the error log after a crash. (Bug#47391)

The first execution of STOP SLAVE UNTIL stopped too early. (Bug#47210)

The innodb_file_format_check system variable could not be set at runtime to DEFAULT or to the value of a user-defined variable. (Bug#47167)

After a binary upgrade to MySQL 5.1 from a MySQL 5.0 installation that contains ARCHIVE tables, accessing those tables caused the server to crash, even if you had run mysql_upgrade or CHECK TABLE ... FOR UPGRADE.

To work around this problem, use mysqldump to dump all ARCHIVE tables before upgrading, and reload them into MySQL 5.1 after upgrading. The same problem occurs for binary downgrades from MySQL 5.1 to 5.0. (Bug#47012)

The IGNORE clause on a DELETE statement masked an SQL statement error that occurred during trigger processing. (Bug#46425)

Valgrind errors for InnoDB Plugin were corrected. (Bug#45992, Bug#46656)

The return value was not checked for some my_hash_insert() calls. (Bug#45613)

It was possible for init_available_charsets() not to initialize correctly. (Bug#45058)

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

For a VARCHAR(N) column, ORDER BY BINARY(col_name) sorted using only the first N bytes of the column, even though column values could be longer than N bytes if they contained multibyte characters. (Bug#44131)

For YEAR(2) values, MIN(), MAX(), and comparisons could yield incorrect results. (Bug#43668)

Comparison with NULL values sometimes did not produce a correct result. (Bug#42760)

In debug builds, killing a LOAD XML INFILE statement raised an assertion.

Implemented in the course of fixing this bug, mysqltest has a new send_eval command that combines the functionality of the existing send and eval commands. (Bug#42520)

The server could crash when attempting to access a non-conformant mysql.proc system table. For example, the server could crash when invoking stored procedure-related statements after an upgrade from MySQL 5.0 to 5.1 without running mysql_upgrade. (Bug#41726)

The mysql_upgrade command would create three additional fields to the mysql.proc table (character_set_client, collation_connection, and db_collation), but did not populate the fields with correct values. This would lead to error messages reported during stored procedure execution. (Bug#41569)

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

When compressed MyISAM files were opened, they were always memory mapped, sometimes causing memory-swapping problems. To deal with this, a new system variable, myisam_mmap_size, was added to limit the amount of memory used for memory mapping of MyISAM files. (Bug#37408)

When running mysql_secure_installation on Windows, the command would fail to load a required module, Term::ReadKey, which was required for correct operation. (Bug#35106)

If the --log-bin server option was set to a directory name with a trailing component separator character, the basename of the binary log files was empty so that the created files were named .000001 and .index. The same thing occurred with the --log-bin-index, --relay-log, and --relay-log-index options. Now the server reports and error and exits. (Bug#34739)

If a comparison involved a constant value that required type conversion, the converted value might not be cached, resulting in repeated conversion and poorer performance. (Bug#34384)

Using the SHOW ENGINE INNODB STATUS statement when using partitions in InnoDB tables caused Invalid (old?) table or database name errors to be logged. (Bug#32430)

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

Under heavy load with a large query cache, invalidating part of the cache could cause the server to freeze (that is, to be unable to service other operations until the invalidation was complete). (Bug#21074)

See also Bug#39253.

On some Windows systems, InnoDB could report Operating system error number 995 in a file operation due to transient driver or hardware problems. InnoDB now retries the operation and adds Retry attempt is made to the error message. (Bug#3139)

The InnoDB Plugin is included in MySQL 5.5 releases as the built-in version of InnoDB. The version of the InnoDB Plugin in this release is 1.0.5 and is considered of Release Candidate (RC) quality.

The InnoDB Plugin offers new features, improved performance and scalability, enhanced reliability and new capabilities for flexibility and ease of use. Among the features of the InnoDB Plugin are “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 the InnoDB Plugin Manual at http://www.innodb.com/products/innodb_plugin/plugin-documentation. For general information about using InnoDB in MySQL, see Section 13.6, “The InnoDB Storage Engine”.

Incompatible Change: Dynamic plugins now must be linked against the libmysqlservices.a library (use -lmysqlservices). For an example showing what Makefile.am should look like, see Section 22.2.3.3, “Creating a Plugin Library”. (Bug#48461)

Incompatible Change: Several changes have been made regarding the language and character set of error messages:

For more information, see Section 9.2, “Setting the Error Message Language”, and Section 9.1.6, “Character Set for Error Messages”.

See also Bug#46218, Bug#46236.

Partitioning: New PARTITION BY RANGE COLUMNS(column_list) and PARTITION BY LIST COLUMNS(column_list) options are added for the CREATE TABLE and ALTER TABLE statements.

A major benefit of RANGE COLUMNS and LIST COLUMNS partitioning is that they make it possible to define ranges or lists based on column values that use string, date, or datetime values.

These new extensions also broaden the scope of partition pruning to provide better coverage for queries using comparisons on multiple columns in the WHERE clause, some examples being WHERE a = 1 AND b < 10 and WHERE a = 1 AND b = 10 AND c < 10.

For more information, see Section 17.2.1, “RANGE Partitioning”, Section 17.2.2, “LIST Partitioning”, and Section 17.4, “Partition Pruning”.

Partitioning: A new ALTER TABLE option, TRUNCATE PARTITION, makes it possible to delete rows from one or more selected partitions only. Unlike the case with ALTER TABLE ... DROP PARTITION, ALTER TABLE ... TRUNCATE PARTITION merely deletes all rows from the specified partition or partitions, and does not change the definition of the table.

Partitioning: It is now possible to assign indexes on partitioned MyISAM tables to key caches using the CACHE INDEX and to preload such indexes into the cache using LOAD INDEX INTO CACHE statements. Cache assignment and preloading of indexes for such tables can be performed for one, several, or all partitions of the table.

This functionality is supported for only those partitioned tables that employ the MyISAM storage engine.

Cluster Replication: Replication: A replication heartbeat mechanism has been added to facilitate monitoring. This provides an alternative to checking log files, making it possible to detect in real time when a slave has failed.

Configuration of heartbeats is done via a new MASTER_HEARTBEAT_PERIOD = interval clause for the CHANGE MASTER TO statement (see Section 12.6.2.1, “CHANGE MASTER TO Syntax”); monitoring can be done by checking the values of the status variables Slave_heartbeat_period and Slave_received_heartbeats (see Section 5.1.7, “Server Status Variables”).

The addition of replication heartbeats addresses a number of issues:

(Bug#20435, Bug#29309, Bug#30932)

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

The global server variables sync_master_info and sync_relay_log_info are introduced for use on replication slaves to control synchronization of, respectively, the master.info and relay.info files.

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

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

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

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

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

Replication: Because SHOW BINLOG EVENTS cannot be used to read events from relay log files, a new SHOW RELAYLOG EVENTS statement has been added for this purpose. (Bug#28777)

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

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

In conjunction with the introduction of IGNORE_SERVER_IDS, SHOW SLAVE STATUS has a new field Replicate_Ignore_Server_Ids that displays information about ignored servers. (Bug#25998)

See also Bug#27808.

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

The InnoDB buffer pool is divided into two sublists: A new sublist containing blocks that are heavily used by queries, and an old sublist containing less-used blocks and from which candidates for eviction are taken. In the default operation of the buffer pool, a block when read in is loaded at the midpoint and then moved immediately to the head of the new sublist as soon as an access occurs. In the case of a table scan (such as performed for a mysqldump operation), each block read by the scan ends up moving to the head of the new sublist because multiple rows are accessed from each block. This occurs even for a one-time scan, where the blocks are not otherwise used by other queries. Blocks may also be loaded by the read-ahead background thread and then moved to the head of the new sublist by a single access. These effects can be disadvantageous because they push blocks that are in heavy use by other queries out of the new sublist to the old sublist where they become subject to eviction.

InnoDB Plugin now provides two system variables that enable LRU algorithm tuning:

For additional information, see Section 7.4.6, “The InnoDB Buffer Pool”. (Bug#45015)

Two status variables have been added to SHOW STATUS output. Innodb_buffer_pool_read_ahead and Innodb_buffer_pool_read_ahead_evicted indicate the number of pages read in by the InnoDB read-ahead background thread, and the number of such pages evicted without ever being accessed, respectively. Also, the status variables Innodb_buffer_pool_read_ahead_rnd and Innodb_buffer_pool_read_ahead_seq status variables have been removed. (Bug#42885)

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

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

Previously, mysqldump would not dump the INFORMATION_SCHEMA database and ignored it if it was named on the command line. Now, mysqldump will dump INFORMATION_SCHEMA if it is named on the command line. Currently, this requires that the --skip-lock-tables (or --skip-opt) option be given. (Bug#33762)

Several undocumented C API functions were removed: mysql_manager_close(), mysql_manager_command(), mysql_manager_connect(), mysql_manager_fetch_line(), mysql_manager_init(), mysql_disable_reads_from_master(), mysql_disable_rpl_parse(), mysql_enable_reads_from_master(), mysql_enable_rpl_parse(), mysql_master_query(), mysql_master_send_query(), mysql_reads_from_master_enabled(), mysql_rpl_parse_enabled(), mysql_rpl_probe(), mysql_rpl_query_type(), mysql_set_master(), mysql_slave_query(), and mysql_slave_send_query(). (Bug#31952, Bug#31954)

Sinhala collations utf8_sinhala_ci and ucs2_sinhala_ci were added for the utf8 and ucs2 character sets. (Bug#26474)

If the value of the --log-warnings option is greater than 1, the server now writes access-denied errors for new connection attempts to the error log (for example, if a client user name or password is incorrect). (Bug#25822)

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

The TRADITIONAL SQL mode now includes NO_ENGINE_SUBSTITUTION. (Bug#21099)

MySQL now implements the SQL standard SIGNAL and RESIGNAL statements. See Section 12.8.8, “SIGNAL and RESIGNAL”. (Bug#11661)

The undocumented, deprecated, and not useful SHOW COLUMN TYPES statement has been removed. (Bug#5299)

The FORMAT() function now supports an optional third parameter that enables a locale to be specified to be used for the result number's decimal point, thousands separator, and grouping between separators. Allowable locale values are the same as the legal values for the lc_time_names system variable (see Section 9.7, “MySQL Server Locale Support”). For example, the result from FORMAT(1234567.89,2,'de_DE') is 1.234.567,89. If no locale is specified, the default is 'en_US'.

The Greek locale 'el_GR' is now an allowable value for the lc_time_names system variable.

Previously, in the absence of other information, the MySQL client programs mysql, mysqladmin, mysqlcheck, mysqlimport, and mysqlshow used the compiled-in default character set, usually latin1.

Now these clients can autodetect which character set to use based on the operating system setting, such as the value of the LANG or LC_ALL locale environment language on Unix system or the code page setting on Windows systems. For systems on which the locale is available from the OS, the client uses it to set the default character set rather than using the compiled-in default. Thus, users can configure the locale in their environment for use by MySQL clients. For example, setting LANG to ru_RU.KOI8-R causes the koi8r character set to be used. The OS character set is mapped to the closest MySQL character set if there is no exact match. If the client does not support the matching character set, it uses the compiled-in default. (For example, ucs2 is not supported as a connection character set.)

Third-party applications that wish to use character set autodetection based on the OS setting can use the following mysql_options() call before connecting to the server:

mysql_options(mysql,
              MYSQL_SET_CHARSET_NAME,
              MYSQL_AUTODETECT_CHARSET_NAME);

See Section 9.1.4, “Connection Character Sets and Collations”.

mysql_upgrade now has an --upgrade-system-tables option that causes only the system tables to be upgraded. With this option, data upgrades are not performed.

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

The server now supports a Debug Sync facility for thread synchronization during testing and debugging. To compile in this facility, configure MySQL with the --enable-debug-sync option. The debug_sync system variable provides the user interface Debug Sync. mysqld and mysql-test-run.pl support a --debug-sync-timeout option to enable the facility and set the default synchronization point timeout.

Added the TO_SECONDS() function, which converts a date or datetime value to a number of seconds since the year 0.

Parser performance was improved for identifier scanning and conversion of ASCII string literals.

The LOAD XML INFILE statement was added. This statement makes it possible to read data directly from XML files into database tables. For more information, see Section 12.2.7, “LOAD XML Syntax”.

Performance: The server unnecessarily acquired a query cache mutex even with the query cache disabled, resulting in a small performance decrement which could show up as threads often in state “invalidating query cache entries (table)”, particularly on a replication slave with row-based replication. Now if the server is started with query_cache_type set to 0, it does not acquire the query cache mutex. This has the implication that the query cache cannot be enabled at runtime. (Bug#38551)

Performance: The InnoDB adaptive hash latch is released (if held) for several potentially long-running operations. This improves throughput for other queries if the current query is removing a temporary table, changing a temporary table from memory to disk, using CREATE TABLE ... SELECT, or performing a MyISAM repair on a table used within a transaction. (Bug#32149)

Important Change: Security Fix: It was possible to circumvent privileges through the creation of MyISAM tables employing the DATA DIRECTORY and INDEX DIRECTORY options to overwrite existing table files in the MySQL data directory. Use of the MySQL data directory in DATA DIRECTORY and INDEX DIRECTORY is now disallowed. This is now also true of these options when used with partitioned tables and individual partitions of such tables. (Bug#32167, CVE-2008-2079)

See also Bug#39277.

Security Fix: MySQL clients linked against OpenSSL can be tricked not to check server certificates. (Bug#47320, CVE-2009-4028)

Security Fix: The server crashed if an account without the proper privileges attempted to create a stored procedure. (Bug#44658)

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

Incompatible Change: In binary installations of MySQL, the supplied binary-configure script would start and configure MySQL, even when command help was requested with the --help command-line option. The --help, if provided, will no longer start and install the server. (Bug#30954)

Incompatible Change: Access privileges for several statements are more accurately checked:

(Bug#27145)

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

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

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

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

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

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

Partitioning: An ALTER TABLE ... ADD PARTITION statement that caused open_files_limit to be exceeded led to a crash of the MySQL server. (Bug#46922)

See also Bug#47343.

Partitioning: When performing an INSERT ... SELECT into a partitioned table, read_buffer_size bytes of memory were allocated for every partition in the target table, resulting in consumption of large amounts of memory when the table had many partitions (more than 100).

This fix changes the method used to estimate the buffer size required for each partition and limits the total buffer size to a maximum of approximately 10 times read_buffer_size. (Bug#45840)

Partitioning: The cardinality of indexes on partitioned tables was calculated using the first partition in the table, which could result in suboptimal query execution plans being chosen. Now the partition having the most records is used instead, which should result in better use of indexes and thus improved performance of queries against partitioned tables in many if not most cases. (Bug#44059)

Partitioning: Truncating a partitioned MyISAM table did not reset the AUTO_INCREMENT value. (Bug#35111)

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

Replication: When using statement-based or mixed-format replication, the database name was not written to the binary log when executing a LOAD DATA statement. This caused problems when the table being loaded belonged to a database other than the current database; data could be loaded into the wrong table (if a table having the same name existed in the current database) or replication could fail (if no table having that name existed in the current database). Now a table referenced in a LOAD DATA statement is always logged using its fully qualified name when the database to which it belongs is not the current database. (Bug#48297)

Replication: When a session was closed on the master, temporary tables belonging to that session were logged with the wrong database names when either of the following conditions was true:

(Bug#48216)

See also Bug#46861, Bug#48297.

Replication: When using row-based replication, changes to nontransactional tables that occurred early in a transaction were not immediately flushed upon committing a statement. This behavior could break consistency since changes made to nontransactional tables become immediately visible to other connections. (Bug#47678)

See also Bug#47287, Bug#46864, Bug#43929, Bug#46129.

Replication: When mysqlbinlog --verbose was used to read a binary log that had been recorded using the row-based format, the output for events that updated some but not all columns of tables was not correct. (Bug#47323)

Replication: Performing ALTER TABLE ... DISABLE KEYS on a slave table caused row-based replication to fail. (Bug#47312)

Replication: When using the row-based format to replicate a transaction involving both transactional and nontransactional engines, which contained a DML statement affecting multiple rows, the statement failed; if this transaction was followed by a COMMIT, the master and the slave could diverge, because the statement was correctly rolled back on the master, but was applied on the slave. (Bug#47287)

See also Bug#46864.

Replication: BEGIN statements were not included in the output of mysqlbinlog. (Bug#46998)

Replication: A problem with the BINLOG statement in the output of mysqlbinlog could break replication; statements could be logged with the server ID stored within events by the BINLOG statement rather than the ID of the running server. With this fix, the server ID of the server executing the statements can no longer be overridden by the server ID stored in the binary log's format description statement. (Bug#46640)

This regression was introduced by Bug#32407.

Replication: When using row-based replication, DROP TEMPORARY TABLE IF EXISTS was written to the binary log if the table named in the statement did not exist, even though a DROP TEMPORARY TABLE statement should never be logged in row-based logging mode, whether the table exists or not. (Bug#46572)

Replication: Concurrent transactions that inserted rows into a table with an AUTO_INCREMENT column could break statement-based or mixed-format replication error 1062 Duplicate entry '...' for key 'PRIMARY' on the slave. This was especially likely to happen when one of the transactions activated a trigger that inserted rows into the table with the AUTO_INCREMENT column, although other conditions could also cause the issue to manifest. (Bug#45677)

Replication: The internal function get_master_version_and_clock() (defined in sql/slave.cc) ignored errors and passed directly when queries failed, or when queries succeeded but the result retrieved was empty. Now this function tries to reconnect the master if a query fails due to transient network problems, and to fail otherwise. The I/O thread now prints a warning if the same system variables do not exist on master (in the event the master is a very old version of MySQL, compared to the slave.) (Bug#45214)

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

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

Replication: By default, all statements executed by the mysql_upgrade program on the master are written to the binary log, then replicated to the slave. In some cases, this can result in problems; for example, it attempted to alter log tables on replicated databases (this failed due to logging being enabled).

As part of this fix, a mysql_upgrade option, --write-binlog, is added. Its inverse, --skip-write-binlog, can be used to disable binary logging while the upgrade is in progress. (Bug#43579)

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

(Bug#43075)

Replication: When the logging format was set without binary logging being enabled, the server failed to start. Now in such cases, the server starts successfully, binlog_format is set, and a warning is logged instead of an error. (Bug#42928)

Replication: On the master, if a binary log event is larger than max_allowed_packet, the error message ER_MASTER_FATAL_ERROR_READING_BINLOG is sent to a slave when it requests a dump from the master, thus leading the I/O thread to stop. On a slave, the I/O thread stops when receiving a packet larger than max_allowed_packet.

In both cases, however, there was no Last_IO_Error reported, which made it difficult to determine why the slave had stopped in such cases. Now, Last_IO_Error is reported when max_allowed_packet is exceeded, and provides the reason for which the slave I/O thread stopped. (Bug#42914)

See also Bug#14068, Bug#47200, Bug#47303.

Replication: When using statement-based replication and the transaction isolation level was set to READ COMMITTED or a less strict level, InnoDB returned an error even if the statement in question was filtered out according to the --binlog-do-db or --binlog-ignore-db rules in effect at the time. (Bug#42829)

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

See also Bug#38262, Bug#43992.

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

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

Replication: FLUSH LOGS did not actually close and reopen the binary log index file. (Bug#34582)

See also Bug#5.0.90.

Replication: An error message relating to permissions required for SHOW SLAVE STATUS was confusing. (Bug#34227)

Replication: The --base64-output option for mysqlbinlog was not honored for all types of events. This interfered in some cases with performing point-in-time recovery. (Bug#32407)

See also Bug#46640, Bug#34777.

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

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

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

See also Bug#48632.

Replication: Valgrind revealed an issue with mysqld that as corrected: memory corruption in replication slaves when switching databases. (Bug#19022)

API: The fix for Bug#24507 could lead in some cases to client application failures due to a race condition. Now the server waits for the “dummy” thread to return before exiting, thus making sure that only one thread can initialize the POSIX threads library. (Bug#42850)

Certain INTERVAL expressions could cause a crash on 64-bit systems. (Bug#48739)

Following a literal, the COLLATE clause was mishandled such that different results can be produced depending whether an index is used. (Bug#48447)

SUM() artificially increased the precision of a DECIMAL argument, which was truncated when a temporary table was created to hold the results. (Bug#48370)

See also Bug#45261.

If an outer query was invalid, a subquery might not even be set up. EXPLAIN EXTENDED did not expect this and caused a crash by trying to dereference improperly set up information. (Bug#48295)

A query containing a view using temporary tables and multiple tables in the FROM clause and PROCEDURE ANALYSE() caused a server crash.

As a result of this bug fix, PROCEDURE ANALYSE() is legal only in a top-level SELECT. (Bug#48293)

See also Bug#46184.

Error handling was missing for SELECT statements containing subqueries in the WHERE clause and that assigned a SELECT result to a user variable. The server could crash as a result. (Bug#48291)

An assertion could fail if the optimizer used a SPATIAL index. (Bug#48258, Bug#47019)

Memory-allocation failures were handled incorrectly in the InnoDB os_mem_alloc_large() function. (Bug#48237)

WHERE clauses with outer_value_list NOT IN subquery were handled incorrectly if the outer value list contained multiple items at least one of which could be NULL. (Bug#48177)

Searches using a non-default collation could return different results for a table when partitioning was and was not used. (Bug#48161)

A combination of GROUP BY WITH ROLLUP, DISTINCT and the const join type in a query caused a server crash when the optimizer chose to employ a temporary table to resolve DISTINCT. (Bug#48131)

The subquery optimizer had a memory leak. (Bug#48060)

Server shutdown failed on Windows. (Bug#48047)

In some cases, using a null microsecond part in a WHERE condition (for example, WHERE date_time_field <= 'YYYY-MM-DD HH:MM:SS.0000') could lead to incorrect results due to improper DATETIME comparison. (Bug#47963)

A build configured using the --without-server option did not compile the yaSSL code, so if --with-ssl was also used, the build failed. (Bug#47957)

When a query used a DATE or DATETIME value formatted using any separator characters other than hyphen ('-') and a >= condition matching only the greatest value in an indexed column, the result was empty if an index range scan was employed. (Bug#47925)

mysys/mf_keycache.c requires threading, but no test was made for thread support. (Bug#47923)

For debug builds, an assertion could fail during the next statement executed for a temporary table after a multiple-table UPDATE involving that table and modified an AUTO_INCREMENT column with a user-supplied value. (Bug#47919)

The mysys/mf_strip.c file, which defines the strip_sp() function, has been removed from the MySQL source. The function was no longer used within the main build, and the supplied function was causing symbol errors on Windows builds. (Bug#47857)

When building storage engines on Windows it was not possible to specify additional libraries within the CMake file required for the build. An ${engine}_LIBS macro has been added to the files to support these additional storage-engine specific libraries. (Bug#47797)

When building a pluggable storage engine on Windows, the engine name could be based on the directory name where the engine was located, rather than the configured storage engine name. (Bug#47795)

During cleanup of a stored procedure's internal structures, the flag to ignore the errors for INSERT IGNORE or UPDATE IGNORE was not cleaned up, which could result in a server crash. (Bug#47788)

If the first argument to GeomFromWKB() function was a geometry value, the function just returned its value. However, it failed to preserve the argument's null_value flag, which caused an unexpected NULL value to be returned to the caller, resulting in a server crash. (Bug#47780)

InnoDB could crash when updating spatial values. (Bug#47777)

The pthread_cond_wait() implementations for Windows could deadlock in some rare circumstances. (Bug#47768)

The encoding of values for SET system_variable = identifier statements was incorrect, resulting in incorrect error messages. (Bug#47597)

On WIndows, when an idle named pipe connection was forcibly closed with a KILL statement or because the server was being shut down, the thread that was closing the connection would hang infinitely. (Bug#47571, Bug#31621)

On Mac OS X or Windows, sending a SIGHUP signal to the server or an asynchronous flush (triggered by flush_time) caused the server to crash. (Bug#47525)

Debug builds could not be compiled with the Sun Studio compiler. (Bug#47474)

Queries of the form SELECT SUM(DISTINCT varchar_key) FROM tbl_name caused a server crash. (Bug#47421)

A function call could end without throwing an error or setting the return value. For example, this could happen when an error occurred while calculating the return value. This is fixed by setting the value to NULL when an error occurs during evaluation of an expression. (Bug#47412)

mysqladmin debug could crash on 64-bit systems. (Bug#47382)

A simple SELECT with implicit grouping could return many rows rather than a single row if the query was ordered by the aggregated column in the select list. (Bug#47280)

An assertion could be raised for CREATE TABLE if there was a pending INSERT DELAYED or REPLACE DELAYED for the same table. (Bug#47274)

InnoDB raised errors in some cases in a manner not compatible with SIGNAL and RESIGNAL. (Bug#47233)

A multiple-table UPDATE involving a natural join and a mergeable view raised an assertion. (Bug#47150)

On FreeBSD, memory mapping for MERGE tables could fail if underlying tables were empty. (Bug#47139)

Solaris binary packages now are compiled with -g0 rather than -g. (Bug#47137)

If an InnoDB table was created with the AUTO_INCREMENT table option to specify an initial auto-increment value, and an index was added in a separate operation later, the auto-increment value was lost (subsequent inserts began at 1 rather than the specified value). (Bug#47125)

Incorrect handling of predicates involving NULL by the range optimizer could lead to an infinite loop during query execution. (Bug#47123)

EXPLAIN caused a server crash for certain valid queries. (Bug#47106)

Repair by sort or parallel repair of MyISAM tables could fail to fail over to repair with key cache. (Bug#47073)

InnoDB Plugin did not compile on some Solaris systems. (Bug#47058)

On WIndows, when a failed I/O operation occurred with return code of ERROR_WORKING_SET_QUOTA, InnoDB intentionally crashed the server. Now InnoDB sleeps for 100ms and retries the failed operation. (Bug#47055)

The mysql_config script contained a reference to @innodb_system_libs@ that was not replaced with the corresponding library flags during the build process and ended up in the output of mysql_config --libs. (Bug#47007)

The configure option --without-server did not work. (Bug#46980)

Failed multiple-table DELETE statements could raise an assertion. (Bug#46958)

When MySQL crashed (or a snapshot was taken that simulates a crash), it was possible that internal XA transactions (used to synchronize the binary log and InnoDB) could be left in a PREPARED state, whereas they should be rolled back. This occurred when the server_id value changed before the restart, because that value was used to construct XID values.

Now the restriction is relaxed that the server_id value be consistent for XID values to be considered valid. The rollback phase should then be able to clean up all pending XA transactions. (Bug#46944)

When creating a new instance on Windows using mysqld-nt and the --install parameter, the value of the service would be set incorrectly, resulting in a failure to start the configured service. (Bug#46917)

The test suite was missing from RPM packages. (Bug#46834)

For InnoDB tables, an unnecessary table rebuild for ALTER TABLE could sometimes occur for metadata-only changes. (Bug#46760)

The server could crash for queries with the following elements: 1. An “impossible where” in the outermost SELECT; 2. An aggregate in the outermost SELECT; 3. A correlated subquery with a WHERE clause that includes an outer field reference as a top-level WHERE sargable predicate; (Bug#46749)

InnoDB Plugin did not compile using gcc 4.1 on PPC systems. (Bug#46718)

If InnoDB Plugin reached its limit on the number of concurrent transactions (1023), it wrote a descriptive message to the error log but returned a misleading error message to the client, or an assertion failure occurred. (Bug#46672)

See also Bug#18828.

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

The Serbian locale name 'sr_YU' is obsolete. It is still recognized for backward compatibility, but 'sr_RS' now should be used instead. (Bug#46633)

On Solaris and HP-UX systems with the environment set to the default C locale, MySQL client programs issued an Unknown OS character set error. (Bug#46619)

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

If a transaction was rolled back inside InnoDB due to a deadlock or lock wait timeout, and a statement in the transaction had an IGNORE clause, the server could crash at the end of the statement or on shutdown. (Bug#46539)

TRUNCATE TABLE for a table that was opened with HANDLER did not close the handler and left it in an inconsistent state that could lead to a server crash. Now TRUNCATE TABLE for a table closes all open handlers for the table. (Bug#46456)

Trailing spaces were not ignored for user-defined collations that mapped spaces to a character other than 0x20. (Bug#46448)

See also Bug#29468.

The server crashed if a shutdown occurred while a connection was idle. This happened because of a NULL pointer dereference while logging to the error log. (Bug#46267)

Dropping an InnoDB table that used an unknown collation (created on a different server, for example) caused a server crash. (Bug#46256)

The GPL and commercial license headers had different sizes, so that error log, backtrace, core dump, and cluster trace file line numbers could be off by one if they were not checked against the version of the source used for the build. (For example, checking a GPL build backtrace against commercial sources.) (Bug#46216)

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

See also Bug#48293.

After an error such as a table-full condition, INSERT IGNORE could cause an assertion failure for debug builds. (Bug#46075)

InnoDB did not disallow creation of an index with the name GEN_CLUST_INDEX, which is used internally. (Bug#46000)

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

Configuring MySQL for DTrace support resulted in a build failure on Solaris if the directory for the dtrace executable was not in PATH. (Bug#45810)

An infinite hang and 100% CPU usage occurred after handler tried to open a merge table.

If the command mysqladmin shutdown was executed during the hang, the debug server generated the following assert:

mysqld: table.cc:407: void free_table_share(TABLE_SHARE*): Assertion `share->ref_count ==
0' failed.
090610 14:54:04 - mysqld got signal 6 ;

(Bug#45781)

During the build of the Red Hat IA64 MySQL server RPM, the system library link order was incorrect. This made the resulting Red Hat IA64 RPM depend on "libc.so.6.1(GLIBC_PRIVATE)(64bit)", thus preventing installation of the package. (Bug#45706)

The caseinfo member of the CHARSET_INFO structure was not initialized for user-defined Unicode collations, leading to a server crash. (Bug#45645)

Appending values to an ENUM or SET definition is a metadata change for which ALTER TABLE need not rebuild the table, but it was being rebuilt anyway. (Bug#45567)

The socket system variable was unavailable on Windows. (Bug#45498)

The combination of MIN() or MAX() in the select list with WHERE and GROUP BY clauses could lead to incorrect results. (Bug#45386)

Truncation of DECIMAL values could lead to assertion failures; for example, when deducing the type of a table column from a literal DECIMAL value. (Bug#45261)

See also Bug#48370.

Client flags were incorrectly initialized for the embedded server, causing several tests in the jp test suite to fail. (Bug#45159)

Concurrent execution of statements requiring a table-level lock and statements requiring a non-table-level write lock for a table could deadlock. (Bug#45143)

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

mysqld_safe could fail to find the logger program. (Bug#44736)

The have_community_features system variable was renamed to have_profiling.

Previously, to enable profiling, it was necessary to run configure with the --enable-community-features and --enable-profiling options. Now only --enable-profiling is needed. (Bug#44651)

Some Perl scripts in AIX packages contained an incorrect path to the perl executable. (Bug#44643)

With InnoDB Plugin, renaming a table column and then creating an index on the renamed column caused a server crash to the .frm file and the InnoDB data directory going out of sync. Now InnoDB Plugin 1.0.5 returns an error instead: ERROR 1034 (HY000): Incorrect key file for table 'tbl_name'; try to repair it. To work around the problem, create another table with the same structure and copy the original table to it. (Bug#44571)

For debug builds, executing a stored procedure as a prepared statement could sometimes cause an assertion failure. (Bug#44521)

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

InnoDB did not always disallow creating tables containing columns with names that match the names of internal columns, such as DB_ROW_ID, DB_TRX_ID, DB_ROLL_PTR, and DB_MIX_ID. (Bug#44369)

An InnoDB error message incorrectly referred to the nonexistent innodb_max_files_open variable rather than to innodb_open_files. (Bug#44338)

SELECT ... WHERE ... IN (NULL, ...) was executed using a full table scan, even if the same query without the NULL used an efficient range scan. (Bug#44139)

See also Bug#18360.

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

LOAD DATA INFILE statements were written to the binary log in such a way that parsing problems could occur when re-executing the statement from the log. (Bug#43746)

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

See also Bug#47304.

Attempts to enable large_pages with a shared memory segment larger than 4GB caused a server crash. (Bug#43606)

For ALTER TABLE, renaming a DATETIME or TIMESTAMP column unnecessarily caused a table copy operation. (Bug#43508)

The weekday names for the Romanian lc_time_names locale 'ro_RO' were incorrect. Thanks to Andrei Boros for the patch to fix this bug. (Bug#43207)

XA START could cause an assertion failure or server crash when it is called after a unilateral rollback issued by the Resource Manager (both in a regular transaction and after an XA transaction). (Bug#43171)

Redefining a trigger could cause an assertion failure. (Bug#43054)

The FORCE INDEX FOR ORDER BY index hint was ignored when join buffering was used. (Bug#43029)

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

The NUM_FLAG bit of the MYSQL_FIELD.flags member now is set for columns of type MYSQL_TYPE_NEWDECIMAL. (Bug#42980)

Incorrect handling of range predicates combined with OR operators could yield incorrect results. (Bug#42846)

Failure to treat BIT values as unsigned could lead to unpredictable results. (Bug#42803)

For the embedded server on Windows, InnoDB crashed when innodb_file_per_table was enabled and a table name was in full path format. (Bug#42383)

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

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

Some queries with nested outer joins could lead to crashes or incorrect results because an internal data structure was handled improperly. (Bug#42116)

The server used the wrong lock type (always TL_READ instead of TL_READ_NO_INSERT when appropriate) for tables used in subqueries of UPDATE statements. This led in some cases to replication failure because statements were written in the wrong order to the binary log. (Bug#42108)

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

In a replication scenario with innodb_locks_unsafe_for_binlog enabled on the slave, where rows were changed only on the slave (not through replication), in some rare cases, many messages of the following form were written to the slave error log: InnoDB: Error: unlock row could not find a 4 mode lock on the record. (Bug#41756)

After renaming a user, granting that user privileges could result in the user having additional privileges other than those granted. (Bug#41597)

The mysql-stress-test.pl test script was missing from the noinstall packages on Windows. (Bug#41546)

With a nonstandard InnoDB page size, some error messages became inaccurate.

(Bug#41490)

In some cases, the server did not recognize lettercase differences between GRANT attributes such as table name or user name. For example, a user was able to perform operations on a table with privileges of another user with the same user name but in a different lettercase.

In consequence of this bug fix, the collation for the Routine_name column of the mysql.proc table is changed from utf8_bin to utf8_general_ci. (Bug#41049)

See also Bug#48872.

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

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

CREATE TABLE failed if a column name in a FOREIGN KEY clause was given in a lettercase different from the corresponding index definition. (Bug#39932)

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

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

ALTER TABLE neglected to preserve ROW_FORMAT information from the original table, which could cause subsequent ALTER TABLE and OPTIMIZE TABLE statements to lose the row format for InnoDB tables. (Bug#39200)

Simultaneous ANALYZE TABLE operations for an InnoDB tables could be subject to a race condition. (Bug#38996)

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

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

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

For certain SELECT statements using ref access, MySQL estimated an incorrect number of rows, which could lead to inefficient query plans. (Bug#38049)

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

The client library mishandled EINPROGRESS errors for connections in nonblocking mode. (Bug#37267)

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

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

Privileges for SHOW CREATE VIEW were not being checked correctly. (Bug#35996)

Different invocations of CHECKSUM TABLE could return different results for a table containing columns with spatial data types. (Bug#35570)

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

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

For its warning count, the mysql_info() C API function could print the number of truncated data items rather than the number of warnings. (Bug#34898)

Concurrent execution of FLUSH TABLES along with SHOW FUNCTION STATUS or SHOW PROCEDURE STATUS could cause a server crash. (Bug#34895)

Executing SHOW MASTER LOGS as a prepared statement without binary logging enabled caused a crash for debug builds. (Bug#34741)

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

A COMMENT longer than 64 characters caused CREATE PROCEDURE to fail. (Bug#34197)

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

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

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

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

The SHOW FUNCTION CODE and SHOW PROCEDURE CODE statements are not present in nondebug builds, but attempting to use them resulted in a “syntax error” message. Now the error message indicates that the statements are disabled and that you must use a debug build. (Bug#33637)

The LAST_DAY() and MAKEDATE() functions could return NULL, but the result metadata indicated NOT NULL. Thanks to Hiromichi Watari for the patch to fix this bug. (Bug#33629)

Instance Manager (mysqlmanager) has been removed, but a reference to it still appeared in the mysql.server script. (Bug#33472)

There was a race condition between the event scheduler and the server shutdown thread. (Bug#32771)

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

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

For const tables that were optimized away EXPLAIN EXTENDED displayed them in the FROM clause. Now they are not displayed. If all tables are optimized away, FROM DUAL is displayed. (Bug#30302)

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

In mysql, using Control-C to kill the current query resulted in a ERROR 1053 (08S01): Server shutdown in progress" message if the query was waiting for a lock. (Bug#28141)

When building MySQL on Windows from source, the WITH_BERKELEY_STORAGE_ENGINE option would fail to configure BDB support correctly. (Bug#27693)

The default database is no longer changed to NULL (“no database”) if DROP DATABASE for that database failed. (Bug#26704)

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

Referring to a stored function qualified with the name of one database and tables in another database caused a “table doesn't exist” error. (Bug#18444)

A Table ... doesn't exist error could occur for statements that called a function defined in another database. (Bug#17199)

The agent did not start because the file share/mysql-proxy/items/custom.xml was missing from the build, but referred to in the configuration file. The log recorded the following error:

 Default log:
 ------------
 2009-09-18 16:25:12: (critical) chassis.c:1097: could not raise RLIMIT_NOFILE to 8192,
Invalid argument (22). Current limit still 1024.
 2009-09-18 16:25:13: (critical) job_collect_mysql.c.1894: opening
'/data0/merlin/agent/2.0.7.7163/openSUSE10.3-x86-64bit/qa-merlin/share/mysql-proxy/items/c
ustom.xml' failed with: Failed to open file
'/data0/merlin/agent/2.0.7.7163/openSUSE10.3-x86-64bit/qa-merlin/share/mysql-proxy/items/c
ustom.xml': No such file or directory
 2009-09-18 16:25:13: ((error)) scheduler.c:318: register_classes() for plugin
collect_mysql failed

If the reference to share/mysql-proxy/items/custom.xml was removed from the “agent-item-files = ...” entry in the configuration file, then the agent started as expected. (Bug#47443)

After upgrading to Mac OS X Snow Leopard, the following error was generated when starting an agent:

Macintosh-6:replication ligaya$
./Master.5.1.34sp1/MEM_agent/etc/init.d/mysql-monitor-agent start
Starting MySQL Enterprise agent service...
./Master.5.1.34sp1/MEM_agent/etc/init.d/mysql-monitor-agent: line 175:   861 Trace/BPT
trap          nohup $MERLIN_AGENT_ROOTDIR/bin/mysql-monitor-agent $MERLIN_AGENT_OPTIONS >
/dev/null
 ERROR! MySQL Enterprise agent failed to start.

Further, when attempting to display the agent version the following error was generated:

Macintosh-6:replication ligaya$ ./Master.5.1.34sp1/MEM_agent/bin/mysql-monitor-agent -v
dyld: Library not loaded: /usr/lib/libxml2.2.dylib
  Referenced from:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices
.framework/Versions/A/DictionaryServices
  Reason: Incompatible library version: DictionaryServices requires version 10.0.0 or
later, but libxml2.2.dylib provides version 9.0.0
Trace/BPT trap

(Bug#47042)

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)

Initial setup and registration of MySQL Enterprise Monitor could fail on Mac OS X when communicating with the MySQL Enterprise website. (Bug#46571)

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)

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)

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)

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)

When running the shutdown script for Enterprise Dashboard, it took an unacceptably long time for Tomcat to terminate completely, the java process eventually had to be killed manually. (Bug#44327)

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)

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)

An error was generated when an attempt was made to rename a Replication Group to one that had previously been deleted. (Bug#43846)

A new topology was not discovered after the previous replication group was renamed. (Bug#43815)

On Unix systems, executing the command:

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

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)

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)

The generic Linux IA64 glibc2.3 Agent installer was missing from the build. (Bug#41224)

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

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)

The FreeBSD 7 Agent was inadvertently a Linux binary.

shell> file mysqlmonitoragent-2.0.5.7153-freebsd7-x86-32bit-installer.bin
mysqlmonitoragent-2.0.5.7153-freebsd7-x86-32bit-installer.bin: ELF 32-bit LSB executable,
Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs),
stripped

(Bug#44263)

Calling the Agent with the option --agent-run-os-tests resulted in a crash. This happened on Linux x86-64 systems. The resultant stack trace was:

(qa-merlin)
2009-03-04 16:39:42: (critical) chassis.c:1097: could not raise RLIMIT_NOFILE to 8192,
Invalid argument (22). Current limit still 1024.
sigar-test-all.c.124 (test_sigar_pid_get):
  pid = 5188
sigar-test-all.c.106 (test_sigar_mem_get):
...cut...
sigar-test-all.c.427 (test_sigar_file_system_list_get): (items = 13)
[0]
  fs.dirname = /
  fs.devname = /dev/mapper/vg00-root
  fs.typename = local
  fs.sys-type-name = ext3
  fs.type = 2
  fsusage.total = 15481840
  fsusage.free = 14116140
  fsusage.used = 1365700
  fsusage.avail = 13329708
  fsusage.files = 1966080
  fsusage.use_percent = 0.100000
[0]
  diskusage.reads = 315302
  diskusage.writes = 6318240
  diskusage.write_bytes = 25879511040
  diskusage.read_bytes = 6561092608
  diskusage.queue = 47457530080206
Segmentation fault

On some systems no output was shown, other than the message “Segmentation fault”. (Bug#43381)

Following a change in the replication configuration, MySQL Enterprise Monitor did not display the new topology correctly. (Bug#43240)

When a data collection became invalid, the agent sent NULLs for those collection values. However, the timestamps that it sent with the values were the timestamps from the last valid value that was collected.

Due to key constraints on the Service Manager side, MySQL Enterprise Monitor disregarded anything sent with duplicate timestamps, thus the NULLs received from the agent were never processed. Some mechanisms, such as replication discovery, depend on the NULLs to identify a situation where data has become invalid. (Bug#43239)

MySQL Enterprise Monitor did not add a log entry each time data was purged. The log entry should have noted how many rows of each type of data were purged (historical data, logs, quan data). (Bug#43159)

MySQL Enterprise Monitor generated a stack overflow. This was as a result of a bug in Hibernate, which caused Hibernate to enter infinite recursion while trying to load a relationship. (Bug#43107)

The “Table Cache Set Too Low For Startup” and “Table Cache Not Optimal” rules were not supported on MySQL 5.1 because the table_cache system variable was deprecated and replaced with table_open_cache. (Bug#42663)

Migrated server was not completely deleted.

In a Monitor that had been updated from 1.3.2 to 2.0.4, with 2 database servers queued for migration, if a server being migrated was deleted, or a migrated server was deleted, this would not be reflected in the user interface or in the license count, until Tomcat was restarted. (Bug#42604)

The installer used to upgrade from version 1.3 corrupted passwords containing the “?” character. (Bug#42452)

The replication status of a server was displayed as “unknown”. However, the agent logged no errors and the server showed no other event problems. The server status was displayed as “up” and the database connection was also displayed as “up”. (Bug#42407)

Sun multi-core processors caused all cores to be reported on the meta information page.

The larger T-series SPARC processors have 32+ cores. This caused the meta information page in the Dashboard to scroll as it reported each one. (Bug#42355)

If an attempt was made to disable a rule using the link next to the rule, the following error message was generated:

U0002 You must log in to access the requested resource. Go to login page.

However, clicking on the link did not prompt the user to login again. (Bug#42313)

Changing ssh-agent from OpenSSH or specifying a malevolent value of agent-host-id, could inject data into the monitored MySQL Server.

For example, setting agent-host-id to the value “I'm a test” would result in the following message in the error log:

2009-01-23 15:45:11: ((error)) agent_mysqld.c:281: mysql_real_query('INSERT INTO
mysql.inventory  (name, value) VALUES ( 'hostid', 'I'm a test' )') on 'mysql' failed: You
have an error in your SQL syntax; check the manual that corresponds to your MySQL server
version for the right syntax to use near 'm a test' )' at line 1 (mysql-errno = 1064)

(Bug#42306)

When SHOW GLOBAL STATUS returned a value greater than 214748364, it was sent to the Service Manager as 214748364. (Bug#42245)

The Agent failed to identify local sockets as local on Mac OS X 10.4.

If the Agent was configured to use a Unix domain socket on Mac OS X 10.4, it did not treat the connection as local and failed to provide CPU and memory information to MySQL Enterprise Monitor. This is shown in the log file:

2009-01-20 18:15:02: (message) network-socket.c:752: is-local family 0 != 1
2009-01-20 18:15:02: (message) agent_mysqld.c:322: [mysql] mysqld is not local or not
directly connected

However, this problem did not happen on Mac OS X 10.5. (Bug#42220)

Some graphs on the Graph tab were not updated after the page was refreshed, or Update was clicked.

The only way to get an updated graph was to change the graph size (in pixels) and then click Update. (Bug#42162)

The my.cnf file for the Enterprise Monitor internal database had the following configuration item:

innodb_autoextend_increment = 50M

This generated the error:

16:36:23 [Warning] option 'innodb_autoextend_increment': unsigned value 52428800
adjusted to 1000

This variable is interpreted as being specified in MB, so 50M would be 50 TB. Such a high value results in the variable being adjusted to 1000 MB.

The value in the configuration file should be:

innodb_autoextend_increment = 50

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

The Service Manager did not handle the case where the agent failed to supply a valid master_ip. The Service Manager would then not restart. The logs contained the following:

2009-01-09 14:39:50,472 ERROR [main:org.springframework.web.context.ContextLoader] Context
initialization failed
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with
name 'serverConnectionMonitor' defined in ServletContext resource
[/WEB-INF/applicationContext.xml]: Unsatisfied dependency expressed through constructor
argument with index 2 of type [com.mysql.etools.monitor.bo.Manager]: Error creating bean
with name 'manager' defined in ServletContext resource [/WEB-INF/applicationContext.xml]:
Invocation of init method failed; nested exception is
com.mysql.etools.monitor.pom.UnsupportedAttributeException:
101c6b5b-15eb-49aa-916c-843c51b28d38: mysql.slavestatus.Master_ip

(Bug#42005)

Having too many users with strong privileges generated Service Manager errors and events failed to be triggered.

If there were approximately 1000 users with full privileges and the value of group_concat_max_len was set to 100001, the size of the data that the agent sent to the Service Manager was too large and caused Service Manager errors. Also, the Security event “Account has Strong MySQL privileges” did not trigger. (Bug#41987)

Query Analyzer's Query Type filter for SELECT ignored statements starting with parenthesis.

If you sent a statement through Query Analyzer starting with parenthesis, such as:

(SELECT 1 FROM dual);

and then attempted to filter for SELECT queries only, queries starting with parenthesis were not displayed. (Bug#41968)

The agent angel process was spawning too soon, which caused a duplicate UUID error.

g_error() logged a fatal error, and called abort(). This terminated the program. Then the angel respawned with the same UUID, but with a -1 session resync request, which the MEM server denied because the old session was still active. This resulted in a permissions denied error (1142) on the mysql.inventory table.

2008-12-17 18:58:58: (message) agent_mysqld.c:313: [mysql] mysqld is local and directly connected
2008-12-17 18:58:58: ((error)) agent_mysqld.c:444: [mysql] mysql_real_query("SELECT value
FROM mysql.inventory WHERE name = 'uuid'") failed: SELECT command denied to user
'ent_agent'@'127.0.0.1' for table 'inventory' (errno=1142)
2008-12-17 18:58:58: (debug) chassis.c:282: 15134 returned: 15134
2008-12-17 18:58:58: (message) chassis.c:304: [angel] PID=15134 died on signal=6 (it used
0 kBytes max) ... waiting 3min before restart
2008-12-17 18:59:00: (debug) chassis.c:244: we are the child: 15149
2008-12-17 18:59:00: (message) chassis.c:259: [angel] we try to keep PID=15149 alive
2008-12-17 18:59:00: (debug) chassis.c:277: waiting for 15149
2008-12-17 18:59:00: (message) mysql-proxy 0.7.0 started
2008-12-17 18:59:00: (message) MySQL Monitor Agent 2.0.0.7111 started.

(Bug#41600)

master_uuid discovery did not work with MySQL Server versions prior to 5.1. master_uuid did not show in any Agent to Monitor communications, and no log or error messages were generated.

However, now the bug has been fixed, an Agent monitoring a 5.0 MySQL Server would register the following in its logs:

...
 <classname>slavestatus</classname>
 <instance>12515cdc-8c00-4223-9d2a-2666a403512c</instance>
 <attribute>Master_uuid</attribute>
</target>
<utc>2009-03-03T19:58:05.700Z</utc>
<value>b2fd9f86-6e42-49f2-b930-e8fb3e728179</value>

Note the presence of master_uuid. (Bug#41525)

The master_uuid was not used for replication topology discovery.

The agent collected master_uuid by reading the master.info file, and then running a SELECT directly against its master. This was to try and read the mysql.inventory table on the master to obtain the instance master_uuid.

However, this was not being used correctly by the replication topology discovery within the server. (Bug#41519)

Queries such as SELECT against the master mysql.inventory was not logged on slave-based agents. This made diagnosing topology discovery issues difficult. (Bug#41518)

After an error was generated due to an incorrect password while trying to create a new user, the following error was obtained when subsequently attempting to create a valid new user:

U0002 You must log in to access the requested resource

(Bug#41384)

Agent startup failed on Solaris 10. The error generated was:

# ./mysql-monitor-agent start
Bad string
ERROR! /opt/mysql/enterprise/agent/etc/mysql-monitor-agent.ini has to have a
[mysql-proxy].pid-file setting

This was caused by unexpected behavior of the tr command. (Bug#41260)

On the Query Analysis page, if a query was clicked the minimum displayed was greater than the average. (Bug#41259)

In some circumstances the agent/proxy ran out of file descriptors, causing secondary failures. It could not recover from that state. The relevant part of the log file is shown here:

2008-11-27 11:11:00: (critical) last message repeated 2 times
2008-11-27 11:11:00: (critical) job_collect_os.c:411: sigar_cpu_info_list_get() failed
2008-11-27 11:11:00: (critical) job_collect_os.c:445: sigar_cpu_list_get() failed
2008-11-27 11:11:00: (critical) job_collect_os.c:411: sigar_cpu_info_list_get() failed
2008-11-27 11:11:00: (critical) job_collect_os.c:445: sigar_cpu_list_get() failed
2008-11-27 11:11:00: (critical) job_collect_os.c:411: sigar_cpu_info_list_get() failed
2008-11-27 11:11:00: (critical) job_collect_os.c:445: sigar_cpu_list_get() failed
2008-11-27 11:11:00: (critical) job_collect_os.c:411: sigar_cpu_info_list_get() failed
2008-11-27 11:11:00: (critical) job_collect_os.c:445: sigar_cpu_list_get() failed
2008-11-27 11:11:30: (critical) network-socket.c.292: socket(127.0.0.1:3306) failed: Too many open files (24)
2008-11-27 11:11:30: (critical) proxy-plugin.c.1532: Cannot connect, all backends are down.
2008-11-27 11:20:22: (critical) last message repeated 4 times
2008-11-27 11:20:22: (critical) network-io.c:215:
curl_easy_perform('https://user:password@merlin-dashboard:443/heartbeat') failed:
SSL connection timeout (curl-error = 'Timeout was reached' (28), os-error = 'Connection refused' (111))

(Bug#41068)

If an installation of Service Manager 2.0.0.7102 included a backup directory, due to a previous upgrade, and was upgraded using at least Service Manager 2.0.0.7103, then the installer displayed an error message and exited.

The error message displayed was:

There has been an error.
Error renaming /Applications/mysql/enterprise/monitor/apache-tomcat to
/Applications/mysql/enterprise/monitor/backup/apache-tomcat
The application will exit now

(Bug#40996)

The Agent started without problems and connected to the master. But it was unable to perform a SELECT from the table mysql.inventory in order to obtain server information. (Bug#40933)

Canonical Query Text for Select -1 was displayed as SELECT -? instead of SELECT ? on the Query Analyzer tab. (Bug#40435)

The agent installer for Solaris 8 x86 32-bit was missing. (Bug#40248)

The MySQL Enterprise Monitor Dashboard did not display the subscribed notification group(s) on the Advisor Current Scheduled and Add to Schedule pages. (Bug#36007)

The startup scripts supplied with MySQL Network Monitoring and Advisory tool did not supply all of the LSB init.d script options required. A list of the required options can be found at the following website http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html

The required options missing include status and force-reload. The option status is used by monitoring tools and cluster software such as Red Hat Cluster, to ensure that the service is still running. The force-reload option is an alias for restart. (Bug#29848)

Multiple errors showed in the agent log after issuing a SHOW INNODB STATUS statement. The InnoDB Buffer Poolgraph also went blank. (Bug#27372)

The Monitor Agent did not log connections to, and disconnects from, the monitored database.

This meant it was not possible to check if the Agent was connected to the database by simply looking at the log file. (Bug#42403)

The Monitor Agent failed to create the mysql.inventory table. The logs displayed the following error message:

(critical) (share/mysql-proxy/quan.lua:711) [proxy] please add SELECT permissions for
this user on mysql.inventory to enable the QUAN feature, got Table 'mysql.inventory'
doesn't exist

This happened even though the Monitor Agent used the root account. (Bug#42389)

After installing Monitor Agent 2.0.4.7138 and then starting it with --version, the incorrect version was displayed. Although 2.0.4.7138 was installed, the Monitor Agent displayed the version number as 2.0.2.7138. (Bug#42263)

An invalid path was shown in the error message if the upgrade installer failed to find the previous install location.

The error message is shown below, note that the error message displays a different path to that provided by the user:

Please specify the directory that contains the previous installation of the MySQL
Enterprise Monitor Agent

Installation directory [/home/mysql/mysql/enterprise/agent]: /var/lib/mysql/agent

Warning: The directory /home/mysql/mysql/enterprise/agent does not contain a
previous installation. Please select the right installation directory.
Press [Enter] to continue :
----------------------------------------------------------------------------
Please specify the directory that contains the previous installation of the MySQL
Enterprise Monitor Agent

(Bug#42200)

The agent password error in the Service Manager did not log the originating host, making it impossible to determine the agent that failed to log in:

ErrorJan 5, 2009 4:56:08 PM<?xml version='1.0'?><exceptions><error><![CDATA[E1702:
IncorrectPasswordException: [agent]]]></error></exceptions>

(Bug#42139)

The Service Manager's JDBC connections did not have sql_mode set to include NO_ENGINE_SUBSTITUTION. This resulted in the failure of Data Definition Language (DDL) if the Service Manager was inadvertently pointed to an incorrect mysqld instance. (Bug#42137)

A number of Advisor rules had advice text that had not been translated into Japanese. The Advisors that contained untranslated rules included Performance, Schema and Security. (Bug#42067)

Monitor Agent configuration files had global read privileges on the filesystem. (Bug#41794)

When the log files rotated to the maximum allowed by the log4j configuration, the metadata contained in the FileAppender became out of synchronization due to a logic bug. This caused an assertion error on any subsequent request for the logs tab or data. (Bug#41593)

SNMP trap messages were sending 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)

On all available test systems, including SUSE Linux Enterprise Server (SLES) 9 and 10 x86-32, x86-64, IA64, and Ubuntu 6.10 x86-64, the agent memory grew incrementally within ~3 hours to ~25M.

The agents then switched to the 'red' condition on the dashboard and no more data was reported. The agent processes were still alive.

This was also present in MySQL Enterprise Monitor version 2.0.0.7111 on Suse 7.3, with the glibc2.2 x86 agent.

There was no load on the monitored servers, and the problem also occurred when the “self-quan” was not configured. (Bug#41244)

Although the Monitor tab loaded initially, after a 64-bit MySQL server running a 32-bit MySQL Monitor Agent was clicked, a Null Pointer Exception was generated. (Bug#41164)

The Monitor Agent startup configuration did not seem to work and did not generate a log file. (Bug#40583)

An error generated by a rule failed to clear.

When a rule was created with the os:disk:fs_used data item, if the instance was not a valid mount point then the Monitor Agent reported the error:

2008-08-11 17:57:00: (critical) disk-get failed for all: 2

Note the above instance was for “all”, and similar results occurred for instance “disk”.

The issue was that upon editing the rule, or even deleting the rule, the agent still showed the above error type. Restarting the agent and the monitoring service failed to remove the error. (Bug#38709)

If the “On Save send test trap” checkbox was checked when the Save button was clicked and the locale was set to Japanese, an error occurred. The orange error banner was displayed at the top of the page with the error message in Japanese. (Bug#32069)

The Monitor Agent failed to connect to the server, and no error message was displayed in the log file.

However, when the log verbosity level was set to message, the following message was recorded:

2009-01-12 13:34:43: (warning) agent_mysqld.c:600: agent connecting to mysql-server
failed: mysql_real_connect(host = '127.0.0.1', port = 3306, socket = ''): Lost connection
to MySQL server at 'reading initial communication packet', system error: 0 (mysql-errno =
2013)

(Bug#42044)

There was a mismatch between the contents of an SNMP Trap from MySQL Enterprise Monitor and the definition given in the file MONITOR.MIB. (Bug#41912)

If a copy was made of a standard rule, the resulting Wiki markup was incorrect, resulting in the display of user-interface text containing HTML markup. (Bug#41375)

Allowing the heat chart rules to be set to unscheduled caused the user interface to appear broken. (Bug#41312)

When a custom rule requiring disk information was created, for example:

[Expression]
%disk_reads%> THRESHOLD

[Thresholds]
Critical Alert: 9000
Warning Alert: 3000
Info Alert: 1000

[Variable Assignment]
variables: %disk_reads%
Data Item: os:disk:disk_reads
Instance: /

The following error was written to the file mysql-service-agent.log:

2007-09-05 17:11:00: (critical) disk-get failed for c0d0p1: 2

It therefore appeared that the Monitor Agent was not able to obtain the required information. (Bug#30820)

The Complete Setup button was missing from the Setup page you were taken to after the current subscription expired. (Bug#41685)

If the host-id of the monitored instance and the host-id of the current agent did not match, the agent generated the following error message:

Please TRUNCATE TABLE mysql.inventory on this mysql-instance and restart the agent.

However, it did not suggest using sql_log_bin = 0. This is used for all other actions against this table so that they are not replicated to slaves, each of which has their own copy of this table. (Bug#41673)

The Agent did not start up when the monitored server had many databases and tables, and was under heavy load. This was because the trigger_schema query was taking too long on agent start up. (Bug#41555)

The Monitor Agent failed to install on Solaris 10 x86. The following error was generated:

Installing
0% ______________ 50% ______________ 100%
########################################
Warning: Problem running post-install step.
Installation may not complete correctly
Error running /usr/local/mysqlagent/bin/mysql-monitor-agent
--defaults-file=/usr/local/mysqlagent/etc/mysql-monitor-agent.ini
--plugins=agent --agent-generate-uuid=true : 2008-12-12 13:06:02: (critical)
Conversion from character set '646' to 'UTF-8' is not supported
2008-12-12 13:06:02: (message) shutting down normally

(Bug#41445)

The console/stdout appender remained in the log4j configuration, which meant that all the MySQL Enterprise Monitor server logs were duplicated to Catalina's stdout, and thus catalina.out, which was wasteful, especially as that file was not rotated or managed. (Bug#41439)

When creating new multiple user accounts, the first attempt worked fine. However, following attempts to create new users did not show the Query Analyzer Options in the Create User popup until the role field was changed. (Bug#41430)

When login privileges were required the Service Manager did not redirect the user to the login page. This resulted in error messages being displayed rather than simply redirecting the user to the login page. This problem typically occurred if it was necessary to restart Tomcat. (Bug#41320)

The monitor 2.0.0.7105 and 2.0.0.7122 Solaris Intel update installer quits unexpectedly. The installer exits from the GUI in the Backup of Previous Installation screen, when OpenSolaris is running on top of Sun xVM.

The console output for both installer versions is given below:

shell> ./mysqlmonitor-2.0.0.7105-solaris-intel-update-installer.bin
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  73 (X_GetImage)
  Serial number of failed request:  21161
  Current serial number in output stream:  21161

shell> ./mysqlmonitor-2.0.0.7122-solaris-intel-update-installer.bin
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  73 (X_GetImage)
  Serial number of failed request:  21148
  Current serial number in output stream:  21148

(Bug#41315)

The Rename Group function failed if the new group name was different to the current one only in the case used; for example, if “Merlin” was changed to “MERLIN”.

The error generated was:

U0105 This group name is already in use. Enter a different name.

(Bug#41266)

The Agent returned an inventory list of all databases and tables. This information was not used by MySQL Enterprise Monitor, other than to populate the inv_databases and inv_tables tables. For large-scale deployments, where there were many databases and tables, this resulted in redundant XML messages being sent from the Agent to the Service Manager. (Bug#33150)

Having an installation with over 420 master binlogs resulted in the mysql::status graph not being plotted. (Bug#41314)

The MySQL Enterprise Monitor installer generated a segfault on RedHat Fedora 10:

shell> ./mysqlmonitor-2.0.0.7105-linux-x86-installer.bin
Segmentation fault

(Bug#41196)

Important Change: The server-name configuration parameter is deprecated. For compatibility, during an upgrade, the information will be migrated to a displayname configuration parameter within the individual instance configuration files. This configuration parameter is provided only for compatibility, as display name information is now stored within the main repository. Support for displayname is also deprecated and will be removed in a future release.

Important Note: The rules “32-Bit Binary Running on 64-Bit AMD Or Intel System” and “Key Buffer Size Greater Than 4 GB” occasionally do not evaluate correctly due to timing issues. This causes them to be displayed with the Severity level of “Unknown”. This is a known issue and will be resolved in future versions of MySQL Enterprise Monitor.

Important Note: When you start the Merlin 2.0 agent from the command line on Windows, you get the following error dialog:

"mysql-proxy.exe - Entry Point Not Found"
"The procedure entry point libiconv_set_relocation_prefix could not be located in the
dynamic link library iconv.dll"

If you click OK the agent works fine after that.

This only occurs when starting the agent from the command line, and only when there is another version of one of the DLLs that the agent uses somewhere on the current path. This error can be avoided by opening a command prompt, typing SET PATH= to clear the path, and then starting the agent.

The following has been added to the Tomcat config.properties properties file:

     # max connections in the pool for the repository
     default.maxActive=70

(Bug#40652)

The dashboard could be used to change the agent password to one containing the @ character, or other special characters, which subsequently caused errors. To fix this problem, special characters in passwords are now prevented by the dashboard. The list of disallowed special characters can be found at the following location: http://en.wikipedia.org/wiki/Percent-encoding#Types_of_URI_characters (Bug#37172)

The Query Analysis page was missing the Refresh dropdown control that the Monitor, Events, and Graphs pages had at the top. (Bug#36831)

The User Interface only returned error strings, without any associated error codes. This meant that if the error string was in a language that the user did not understand, it would be very difficult to determine which error actually occurred.

The User Interface now supports error codes, as well as error strings. This change allows easier testing of multiple locales. (Bug#32131)

The wording was changed on the fading popup subscription alert. The text “account” was changed to “subscription”. (Bug#31492)

The alert thresholds for the Query Cache Advisor were changed:

(Bug#30969)

The agent log file name has changed from mysql-service-agent.log to mysql-monitor-agent.log. The old log file will be retained during a upgrade install.

Starting a new agent against an instance that contained many databases broke up the initial discovery packet, causing collections such as CPU usage and their graphs to fail. See also Bug#33150 and Bug#41314. (Bug#41933)

When altering an existing rule you had to add an empty string, "", to any threshold level that was empty. Otherwise, the rule failed to run and the resulting exceptions caused the Events page to be unusable due to duplicate key exceptions. (Bug#41310)

After installing the 2.0.0.7119 Dashboard the following error was generated in the logs:

com.opensymphony.xwork2.util.OgnlValueStack  Warning  Dec 5, 2008 10:41:26 AM  Caught
an Ognl exception while getting property titleAddition

(Bug#41252)

The dc_ng_long_now table became very large partly due to an unused column begin_time. (Bug#41093)

Although there was a unique constraint on the user name, it was not enforced during first-time setup. This resulted in a stack trace being produced, rather than a more user-friendly error message, if the same name was used for the admin and agent accounts. (Bug#40870)

MySQL Enterprise Monitor server had stopped sending up/down SNMP traps. (Bug#40861)

The Query Analyzer's Explain Query tab did not have pop up text or a link to the documentation regarding SELECT queries. (Bug#40841)

When you tried to import a Trial-level advisor JAR using a Trial user account, one of the following error messages was generated:

U0009 The uploaded Advisor jar was invalid

U0161 Please import a Platinum level Advisor .jar to use with this Platinum level product key

(Bug#40834)

Meta Info on the Dashboard did not display information for the meta data os_description. (Bug#40830)

Attempting to create an alias of statements such as COMMIT, ROLLBACK, BEGIN, resulted in the error:

Can't find template commitTnx.st; group hierarchy is [HTMLFormatting]
org.antlr.stringtemplate.StringTemplateGroup.lookupTemplate(StringTemplateGroup.java:507)

(Bug#40736)

Trying to upgrade from 2.0.0.7088 to 2.0.0.7092 failed as there was a missing file. When the update program mysqlmonitor-2.0.0.7092-solaris-intel-update-installer.bin was run, the file /tmp/com/mysql/merlin/server/version.props could not be found. (Bug#40692)

On OS X with Java 1.5, Tomcat crashed on launch with the error:

Invalid memory access of location 00000007 eip=013df179

(Bug#40689)

When the agent was installed using the command line installer and --enableproxy 0 was specified, the installer should have removed quan.lua from the agent-item-files option in the INI file. (Bug#40551)

The Agent could not connect to a database with the hostname set to localhost. Doing so resulted in the error:

(critical) the MySQL server could not be reached at socket '(null)', we will check in 10 seconds

(Bug#40530)

The update installer for the 2.0 Monitor did not have an Is SSL support required? checkbox. Therefore, the appropriate SSL connector definition was commented out in the conf/server.xml file. (Bug#40414)

The Service Manager installer did not uninstall or wipe out the previous installation if you answered “Yes” to the question:

“The directory you selected already contains a MySQL installation. If you continue installation all data will be lost. Do you wish to continue?” (Bug#40410)

If you unchecked the Enable Proxy checkbox on the Query Analysis Configuration screen, the agent's INI file still contained proxy configuration data and was not commented out. (Bug#40272)

As different queries were sent through the agent it used increasing amounts of memory. (Bug#40260)

The Service Manager installer set the Java Virtual Machine option HeapDumpPath to <install_root>\temp on Windows and /tmp on other platforms. For consistency the HeapDumpPath directory should have been set to <install_root>\tmp on Windows. (Bug#40215)

When using the command line agent setup program, a socket file was not accepted for the monitored instance. (Bug#40085)

The language option when installing the MySQL Enterprise Monitor in Japanese using the command-line instllaer has been changed from jp to ja. (Bug#40082)

When monitoring MySQL 5.1.24 and above, the user used by the agent to connect to the MySQL server for monitoring must have the PROCESS privilege. (Bug#40050)

The check box option string “Is SSL support required?”, on the Tomcat Server Option dialog of the Monitor installation, was not correctly translated into Japanese. (Bug#39814)

The base application directory for the MySQL Enterprise Dashboard has been updated from http://localhost:18080/merlin to http://localhost:18080/. (Bug#39403)

If the Service Manager or the MySQL Server running the Repository crashed, they did not restart automatically. (Bug#39377)

If the agent crashed, there was no watchdog, angel or keep-alive mechanism to restart the agent and keep it running. (Bug#39374)

If the MySQL client libraries were located in a nonstandard location, the agent 2.0.0.7042 installer failed with a “library not found” error. (Bug#39317)

For the rule “Server-Enforced Data Integrity Checking Not Strict”, the Recommended Action did not display correctly. It displayed as SET sql_mode=modes, rather than SET [GLOBAL|SESSION] sql_mode=modes. (Bug#39261)

A query that was issued through the proxy, and that had an auto-explain performed on that query, did not give the correct response to a subsequent query of SELECT FOUND_ROWS(). (Bug#39223)

It was not possible to establish a connection with the Dashboard using the SSL protocol (https://). (Bug#39198)

When a 1.3 MySQL Enterprise Monitor installation with many rules scheduled was upgraded to 2.0, the upgraded installation was then found to have only the heat chart rules scheduled. (Bug#39043)

The agent installer did not allow a second agent to be installed on Windows. (Bug#38976)

The Dashboard incorrectly diplayed that insufficient licenses were available, even though sufficient licenses had been purchased. (Bug#38514)

After running the MySQL Service Agent uninstall program, the file /etc/init.d/mysql-service-agent remained present on the server. (Bug#38490)

The notice fader continued to display English text after you changed the locale to Japanese. (Bug#38460)

The Subscription Expired pop-up window referred to the “Global Preferences” page, instead of the “Global Settings” page. (Bug#38358)

An inappropriate time zone was used to parse user-entered date and time strings. (Bug#38323)

A sigar network stats error was generated on the Solaris platform:

# /opt/mysql/enterprise/agent/bin/mysql-service-agent --version
MySQL Service Agent - 1.2.0.7879, (glib lib=2.8.5, headers=2.8.5)

SunOS mysqlprd01 5.10 Generic_127127-11 sun4v sparc SUNW,T5240

2008-07-21 10:07:24: (critical) sigar_net_interface_config_primary_get() failed: 6
2008-07-21 10:08:00: (critical) sigar_net_interface_config_primary_get() failed: 6

# /opt/mysql/enterprise/agent/bin/sigar-test-all >/tmp/test.txt
sigar_net_interface_stat_get(e1000g0:2) failed#

(Bug#38302)

After deleting a server from the Settings, Manage Servers tab, at the very bottom of the page the Monitoring x instances on x host values did not reflect the deletion. (Bug#38225)

The MySQL Enterprise Monitor alert “INFO Alert - Users Can View All Databases On MySQL Server (v 1.5 *)” from the Security advisor was incorrect. This is because the default server behavior allows users to see databases for which they have privileges, not “all databases on server” as suggested by the alert. (Bug#38052)

The “Maximum Connection Limit Nearing Or Reached” advisor did not generate a new Critical Alert event when there was an open info success event. (Bug#37816)

The Linux IA64 installer appeared to crash. The installer appeared to crash on RH4_IA64 if called with option "--version":

-------------------------------------------------------------------------------
<INSTALLER> --version
mysqlmonitorage(30704): unaligned access to 0x6000000000a8413c, ip=0x2000000003ddd5f0
mysqlmonitorage(30704): unaligned access to 0x6000000000a84144, ip=0x2000000003ddd5f1
mysqlmonitorage(30704): unaligned access to 0x6000000000a8414c, ip=0x2000000003ddd600
mysqlmonitorage(30704): unaligned access to 0x6000000000a84154, ip=0x2000000003ddd601
MySQL Enterprise Monitor Agent 0.7.0.1737 --- Built on 2008-06-25 19:31:53

-------------------------------------------------------------------------------

However, this warning is harmless and will not impact the operation of the agent. (Bug#37496)

If the log-level option in the agent configuration file was set to an unknown level by mistake, the init.d script appeared to enter an infinite loop. (Bug#37108)

Malformatted server meta information appeared on the Dashboard; RAM and Disk Space appeared under the CPU category. (Bug#36740)

A “rename” link incorrectly appeared next to the Upgrade category on the Manage Rules page. (Bug#36584)

In the case where exceptions were passed through to the User Interface, the substituted arguments in the message contained developer-only information. (Bug#36580)

Agent Version, Last MySQL Contact, OS Info, CPU Info, and IP Addresses were all blank on the dashboard when the agent for the selected server was not functioning. (Bug#36301)

mysql-monitor-agent became confused by the .DS_Store files that are created on Mac OS X. (Bug#36216)

The rule “Key Buffer Size Greater Than 4 GB” incorrectly triggered the following alert:

CRITICAL Alert - Key Buffer Size Greater Than 4 GB

However, on non-Windows systems, a key buffer size greater than 4 GB is supported. (Bug#36143)

Since the repository database for MySQL Enterprise Monitor uses InnoDB there was no way to reduce the size of the data files after an old log/event data purge operation. Further, the purge data operation executed once per day, and had no option to trigger the purge operation manually. (Bug#35971)

On the Graphs page, if all graphs were expanded, then the Time Display interval updated, the page was refreshed with the Expand All button displayed, even though all the graphs were already expanded. (Bug#35917, Bug#35133)

The Meta Info area of the Monitor page incorrectly reported the operating system version number for the MySQL version. (Bug#35836)

The rule “XA Distributed Transaction Support Enabled For InnoDB” incorrectly sent a warning when the binary log was on. (Bug#35786)

On the Monitor page, the time displayed for Last MySQL Contact lagged behind that for Last Agent Contact by a large amount. (Bug#35774)

MySQL Enterprise Monitor did not update replication settings correctly. After a slave became the master, the Adviser still referred to it as a slave. (Bug#35771)

The Adviser email suggested using the --log-queries-not-using-indexes option. However, this option is not available in MySQL Server versions prior to 4.1. (Bug#35770)

Thumbnail graphs did not update properly after a time zone change. (Bug#35756)

If a system had a global wait_timeout lower than the general activity of the agent, the agent was disconnected. The monitored server then logged an error and incremented Aborted_clients. (Bug#35648)

Alerts fired after a blackout period based on data collections that happened during the blackout. (Bug#35617)

The translation of the Add Row button on the Rule Definition window was incorrect. (Bug#35495)

An uninstallation message asked about removing Apache files, even though Apache is no longer used. (Bug#35154)

After updating from a previous version to the latest 1.3 version, the Query Cache Has Sub-Optimal Hit Rate was still displayed in English after setting the locale to Japanese. Note, the rule was translated correctly if the full installer was used. (Bug#35134)

The MySQL Enterprise Monitor uninstall dialog box had missing text when using the Japanese locale. (Bug#34982)

Running the installer with the --help option caused an incorrect message to be displayed. (Bug#34200)

When using the unattended unInstall script on Linux together with the option --env deleteUserData=yes the correct warning text was displayed. However, this text should not be displayed in unattended mode. Further, the option --env deleteUserData=yes was not displayed by the --help output. (Bug#34071)

Platinum Unlimited customers sometimes received a warning stating incorrectly that their subscription supported zero hosts. (Bug#34010)

Clicking on the resolution notes link for a closed event on the events tab showed incorrect behavior. The popup initially showed the resolution notes, but when the resolution tab was clicked the notes disappeared and were replaced by an edit box. (Bug#33935)

The status on the product information page was not translated when the user locale was set to Japanese. (Bug#32785)

When the locale was set to Japanese, the date picker still had English month titles. (Bug#32741)

Flashing display of a pop-up used while saving outgoing email settings was caused by problematic initial placement calculations. (Bug#32579)

AIX 5.2 Agent did not work on AIX 5.3. (Bug#32414)

When the First Time Setup program was run it did not prompt the user to allow importing an Advisor bundle. (Bug#32199)

Agent on MacOSX did not read IP addresses for network interfaces correctly, so the monitor displayed empty host IP addresses. (Bug#32188)

HTML code in queries was not escaped when reporting replication errors, causing the code to be rendered into the page. (Bug#32186)

The First Run pop-up defaulted to English rather than to the locale set in the browser. (Bug#32129)

The error dialog box flashed in the upper left corner before being positioned in the center of the screen. This error dialog box now opens in the center of the screen. (Bug#32068)

The Events list did not take into account Daylight Time and Standard Time when listing events that happened during 1:00am-1:59am. An event that occurred at 1:10am Standard Time was listed before an event that occurred 50 minutes before it at 1:20am Daylight Time. (Bug#32016)

The pop-up for editing log levels failed to load due to bad instantiation data. (Bug#32013)

During the repeated hour of Daylight Savings Time (when 2am turns back into 1am), the graphs were not drawing data. Instead, there was a straight line from the point at 1:00 to the second 1:00, which is what happens if there is no data. The repository did, however, have data for this hour. (Bug#31997)

Only US English was supported for a locale setting. Other English variants are now available for the locale setting on the General Settings or the User Preferences pages. (Bug#31801)

If the user locale was changed the graph cache would continue to display the graph in the last locale until it timed out. (Bug#31680)

No init script was installed for the MySQL Network Monitoring Service Manager, and so it did not restart automatically on reboot. (Bug#31676)

The graph's displayed time was not the local time of the Dashboard corresponding to the requested time on the monitored server. (Bug#31656)

Saving a rule with a name that already existed resulted in a stack trace in the window, instead of a more user-friendly error message. (Bug#30925)

The network.mysql.com error messages were remapped thereby causing confusion. For example, the following error message:

E9000: MySQL Enterprise Customer Center is having difficulties fetching your contract information. Please contact enterprise-feedback@mysql.com for assistance.

Was remapped to:

Unable to connect to verify credentials (Bug#30873)

A newly added server showed as “down” in the user interface, and could potentially have sent a false alarm notification. (Bug#30735)

The information on the Advisors, Check For Updates page did not accurately reflect how many rules and graphs were actually in the database and available to the user. (Bug#29623)

The agent did not process SIGHUP. (Bug#29380)

Monitor did not have a facility to stop or downgrade an agent collection frequency. (Bug#28589)

After an agent installation was updated from 1.0.1.4391 to 1.1.0.4899, the version in the Add/Remove Programs menu was incorrectly displayed as 1.0.1.4391, even though the update was successful and the file version of agent.exe was correctly displayed as 1.1.0.4899. (Bug#27447)

When viewing the Results of an Event in the Events tab of the Dashboard, the Notifications section did not reflect the Notifications settings at the time the Event was triggered, but rather the Notifications settings at the time the Event Results were viewed. (Bug#26349)

When the Monitor Agent was remotely monitoring a MySQL server it incorrectly reported that it could collect operating system information. (Bug#22497)

The Account Without Password advisor did not report all users who were without a password, it only reported one. (Bug#15165)

If NO_BACKSLASH_ESCAPES mode was used on a server, escaping binary data led to server query parsing errors. (Bug#49029)

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)

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:

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.