This release contains 21 bug fixes, including a fix for a slowdown on loading of schema objects in the SQL Editor.

MySQL Workbench 5.2 GA

• Data Modeling

• Query (replaces the old MySQL Query Browser)

• Administration (replaces the old MySQL Administrator)

Sources and binary packages are available for several platforms, including Windows, Mac OS X and Linux.

In addition to the new Query/SQL Development and Administration modules, version 5.2 features improved stability and performance – especially in Windows, where OpenGL support has been enhanced and the UI was optimized to offer better responsiveness. This release also includes improvements to the scripting capabilities of the SQL Editor.

for MySQL has been released.  This is a maintenance release to the 6.3

release chain and includes 40 changes and fixes.

Version 6.3.8 is appropriate for use with versions of MySQL 5.0-5.5.

The new features in these releases are of beta quality. As with any
other pre-production release, caution should be taken when installing on
production level systems or systems with critical data.

Note that 5.6.4 includes all features in MySQL 5.5.

D.1.2. Changes in MySQL 5.6.4 (20 December 2011 Milestone 7)

Condition Handler Changes

* Incompatible Change: MySQL now supports the GET DIAGNOSTICS
statement. GET DIAGNOSTICS provides applications a
standardized way to obtain information from the diagnostics
area, such as whether the previous SQL statement produced an
exception and what it was. For more information, see Section
12.6.7.3, “GET DIAGNOSTICS Syntax.”

In addition several deficiencies in condition handler
processing rules were corrected so that MySQL behavior is more
like standard SQL:

+ Block scope is used in determining which handler to
select. Previously, a stored program was treated as
having a single scope for handler selection.

+ Condition precedence is more accurately resolved.

+ Diagnostics area clearing has changed. Bug #55843 caused
handled conditions to be cleared from the diagnostics
area before activating the handler. This made condition
information unavailable within the handler. Now condition
information is available to the handler, which can
inspect it with the GET DIAGNOSTICS statement. The
condition information is cleared when the handler exits,
if it has not already been cleared during handler
execution.

+ Previously, handlers were activated as soon as a
condition occurred. Now they are not activated until the
statement in which the condition occurred finishes
execution, at which point the most appropriate handler is
chosen. This can make a difference for statements that
raise multiple conditions, if a condition raised later
during statement execution has higher precedence than an
earlier condition and there are handlers in the same
scope for both conditions. Previously, the handler for
the first condition raised would be chosen, even if it
had a lower precedence than other handlers. Now the
handler for the condition with highest precedence is
chosen, even if it is not the first condition raised by
the statement.

+ Issues that caused server crashes resulting from
incorrect handler call stack processing were fixed.

The work just described involved several condition-handler bug
fixes:

+ The RETURN statement did not clear the diagnostics area
as it should have. Now the diagnostics area is cleared
before executing RETURN. This prevents a condition in a
nested function call from incorrectly propagating to an
outer scope. It also means there is no way to return an
SQL warning from a stored function. This change is not
backward compatible, but the resulting behavior is more
like standard SQL.

+ When an SQL HANDLER was activated, the handled condition
was immediately removed from the diagnostics area.
Consequently, any SQL diagnostic statement executed in
the handler was unable to examine the condition that
triggered the handler.

+ If multiple handlers existed at the same level within a
stored program, the wrong one could be chosen.

+ If an error occurred in a context where different
handlers were present at different levels of nesting, an
outer handler could be chosen rather than the innermost
one.

For more information, see Section 12.6.7.6, “Scope Rules for
Handlers.” (Bug #12951117, Bug #38806, Bug #11749343, Bug
#55852, Bug #11763171, Bug #61392, Bug #12652873, Bug #11660,
Bug #11745196)

Fractional Seconds Handling

* Incompatible Change: MySQL now permits fractional seconds for
TIME, DATETIME, and TIMESTAMP values, with up to microseconds
(6 digits) precision. To define a column that includes a
fractional seconds part, use the syntax type_name(fsp), where
type_name is TIME, DATETIME, or TIMESTAMP, and fsp is the
fractional seconds precision. For example:
CREATE TABLE t1 (t TIME(3), dt DATETIME(6));
The fsp value, if given, must be in the range 0 to 6. A value
of 0 signifies that there is no fractional part. If omitted,
the default precision is 0. (This differs from the standard
SQL default of 6, for compatibility with previous MySQL
versions.)
The following items summarize the implications of this change.
See also Section 10.3.4, “Fractional Seconds in Time Values.”

+ For TIME, DATETIME, and TIMESTAMP columns, the encoding
and storage requirements in new tables differ from such
columns in tables created previously because these types
now include a fractional seconds part.

+ Syntax for temporal literals now produces temporal
values: DATE ‘str’, TIME ‘str’, and TIMESTAMP ‘str’, and
the ODBC-syntax equivalents. Previously, the temporal
type keyword was ignored and these constructs produced
the string value.

+ Functions that take temporal arguments accept values with
fractional seconds. Return values from temporal functions
include fractional seconds as appropriate.

+ Three INFORMATION_SCHEMA tables, COLUMNS, PARAMETERS, and
ROUTINES, now have a DATETIME_PRECISION column. Its value
is the fractional seconds precision for TIME, DATETIME,
and TIMESTAMP columns, and NULL for other data types.

+ The C API accommodates fractional seconds as follows:
o In the MYSQL_FIELD column metadata structure, the
decimals member indicates the fractional seconds
precision for TIME, DATETIME, and TIMESTAMP columns.
Clients can determine whether a result set temporal
column has a fractional seconds part by checking for
a nonzero decimals value in the corresponding
MYSQL_FIELD structure. Previously, the decimals
member indicated the precision for numeric columns
and was zero otherwise.
o In the MYSQL_TIME structure used for the binary
protocol, the second_part member indicates the
microseconds part for TIME, DATETIME, and TIMESTAMP
columns. Previously, the second_part member was
unused.
In some cases, previously accepted syntax may produce
different results. The following items indicate where existing
code may need to be changed to avoid problems:

+ Some expressions produce results that differ from
previous results. Examples: The timestamp system variable
returns a value that includes a microseconds fractional
part rather than an integer. Functions that return a
result that includes the current time (such as CURTIME(),
SYSDATE(), or UTC_TIMESTAMP()) interpret an argument as
an fsp value and the return value includes a fractional
seconds part of that many digits. Previously, these
functions permitted an argument but ignored it.

+ TIME values are converted to DATETIME by adding the time
to the current date. (This means that the date part of
the result differs from the current date if the time
value is outside the range from ’00:00:00′ to
’23:59:59′.) Previously, conversion of TIME values to
DATETIME was unreliable. See Section 10.3.5, “Conversion
Between Date and Time Types.”

+ TIMESTAMP(N) was permitted in old MySQL versions, but N
was a display width rather than fractional seconds
precision. Support for this behavior was removed in MySQL
5.5.3, so applications that are reasonably up to date
should not be subject to this issue. Otherwise, code must
be rewritten.

Note
There may be problems replicating from a master server that
understands fractional seconds to an older slave that does
not:

+ For CREATE TABLE statements containing columns that have
an fsp value greater than 0, replication will fail due to
parser errors.

+ Statements that use temporal data types with an fsp value
of 0 will work for with statement-based logging but not
row-based logging. In the latter case, the data types
have binary formats and type codes on the master that
differ from those on the slave.

+ Some expression results will differ on master and slave.
For example, expressions that involve the timestamp
system variable or functions that return the current time
have different results, as described earlier.
(Bug #8523, Bug #11745064)

Optimizer Features

* These query optimizer improvements were implemented:

+ The optimizer detects and optimizes away these useless
query parts within IN/ALL/SOME/EXISTS subqueries:

o DISTINCT
o GROUP BY, if there is no HAVING clause and no
aggregate functions
o ORDER BY, which has no effect because LIMIT is not
supported in these subqueries

Performance Schema Notes

* The Performance Schema has these additions:

+ The Performance Schema now permits instrument and
consumer configuration at server startup, which
previously was possible only at runtime using UPDATE
statements for the setup_instruments and setup_consumers
tables. This change was made because configuration at
runtime is too late to disable instruments that have
already been initialized during server startup. For
example, the wait/sync/mutex/sql/LOCK_open mutex is
initialized once during server startup, so attempts to
disable the corresponding instrument at runtime have no
effect.

To control an instrument at server startup, use an option
of this form:

–performance_schema_instrument=’instrument_name=value’

Here, instrument_name is an instrument name such as
wait/sync/mutex/sql/LOCK_open, and value is one of these
values:

o off, false, or 0: Disable the instrument
o on, true, or 1: Enable and time the instrument
o counted: Enable and count (rather than time) the
instrument

Each –performance_schema_instrument option can specify
only one instrument name, but multiple instances of the
option can be given to configure multiple instruments. In
addition, patterns are permitted in instrument names to
configure instruments that match the pattern. To
configure all condition synchronization instruments as
enabled and counted, use this option:

–performance_schema_instrument=’wait/synch/cond/%=counted’

To disable all instruments, use this option:
–performance_schema_instrument=’%=off’

Longer instrument name strings take precedence over
shorter pattern names, regardless of order. For
information about specifying patterns to select
instruments, see Section 19.2.3.2.2, “Naming Instruments
or Consumers for Filtering Operations.”

An unrecognized instrument name is ignored. It is
possible that a plugin installed later may create the
instrument, at which time the name is recognized and
configured.

To control a consumer at server startup, use an option of
this form:

–performance_schema_consumer_consumer_name=value

Here, consumer_name is a consumer name such as
events_waits_history, and value is one of these values:

o off, false, or 0: Do not collect events for the
consumer
o on, true, or 1: Collect events for the consumer

For example, to enable the events_waits_history consumer,
use this option:

–performance_schema_consumer_events_waits_history=on

The permitted consumer names can be found by examining
the setup_consumers table. Patterns are not permitted.
Along with the preceding changes to permit configuration
at server startup, the default instrument and consumer
configuration has changed. Previously, all instruments
and consumers were enabled by default. Now, instruments
are disabled except the statement, I/O, and idle
instruments. Consumers are disabled except the global,
thread, and statement consumers. These changes produce a
default configuration with minimal overhead.

+ Tables that have an EVENT_ID column now also have an
END_EVENT_ID column to support determination of nested
event relationships:

o events_waits_current, events_waits_history,
events_waits_history_long

o events_stages_current, events_stages_history,
events_stages_history_long

o events_statements_current,
events_statements_history,
events_statements_history_long

As before, EVENT_ID is populated with the thread current
event counter when an event starts. In addition,
END_EVENT_ID is NULL until the event ends, at which point
it is set to the new thread current event counter. This
permits the relationship “event A is included in event B”
to be determined using the following expression, without
having to follow each inclusion relationship using
NESTING_EVENT_ID:

A.EVENT_ID<= B.EVENT_ID AND B.END_EVENT_ID<= A.END_EVENT_ID

+ The Performance Schema aggregates file I/O operations in
two places, the events_waits_summary_xxx tables and the
file_summary_xxx tables. It was possible to join the
events_waits_summary_global_by_event_name table to the
file_summary_by_event_name by using the EVENT_NAME
column. However, it was not possible to do the same with
the events_waits_summary_by_instance and
file_summary_by_instance tables because the former uses
OBJECT_INSTANCE_BEGIN as the instance identifier and the
latter uses FILE_NAME. This means that it was possible to
obtain both file I/O latency and usage per file, but not
to correctly correlate latency to usage when there was
more than one form of file (such as multiple redo logs,
table files, and so forth).

To address this issue, the file_summary_by_instance table
now has an OBJECT_INSTANCE_BEGIN column. In addition,
both file_summary_by_instance and
file_summary_by_event_name have additional aggregation
columns (such as timer wait information), which in many
cases makes it possible to obtain the desired summary
information without need for a join at all.

If you upgrade to this release of MySQL from an earlier
version, you must run mysql_upgrade (and restart the server)
to incorporate these changes into the performance_schema
database.

For more information, see Chapter 19, “MySQL Performance
Schema.”

Functionality Added or Changed

* Replication: Previously, replication slaves could connect to
the master server only through master accounts that use native
authentication. Now replication slaves can also connect
through master accounts that use nonnative authentication if
the required client-side plugin is installed on the slave side
in the directory named by the slave plugin_dir system
variable. (Bug #12897501)

* The optimizer trace capability now tracks temporary tables
created by the server during statement execution. (Bug
#13400713)

* Performance of metadata locking operations on Windows XP
systems was improved by instituting a cache for metadata lock
objects. This permits the server to avoid expensive operations
for creation and destruction of synchronization objects on XP.
A new system variable, metadata_locks_cache_size, permits
control over the size of the cache. The default size is 1024.
(Bug #12695572)

* Upgrading from an Advanced GPL RPM package to an Advanced RPM
package did not work. Now on Linux it is possible to use rpm
-U to replace any installed MySQL product by any other of the
same release family. It is not necessary to remove the old
produce with rpm -e first. (Bug #11886309)

* The make_win_bin_dist script is no longer used and has been
removed from MySQL distributions and the manual. (Bug #58241)

* MEMORY table creation time is now available in the CREATE_TIME
column of the INFORMATION_SCHEMA.TABLES table and the
Create_time column of SHOW TABLE STATUS output. (Bug #51655,
Bug #11759349)

* Previously, MySQL servers from 5.1 and up refused to open
ARCHIVE tables created in 5.0 because opening them caused a
server crash. The server now can open 5.0 ARCHIVE tables, and
REPAIR TABLE updates them to the format used in 5.6. However,
the recommended upgrade procedure is still to dump 5.0 ARCHIVE
tables before upgrading and reload them after upgrading. (Bug
#48633, Bug #11756687)

* The MySQL code base was changed to permit use of the C++
Standard Library and to enable exceptions and runtime type
information (RTTI). This change has the following
implications:

+ Libraries and executables depend on some C++ standard
library. On Linux, this has not been the case previously.
On Solaris, the default dependency has changed from the
default library to libstlport, which is now included with
binary distributions for users whose system does not have
it.

+ The -fno-rtti and -fno-exceptions options are no longer
used to build plugins, such as storage engines. Users who
write their own plugins should omit these options if they
were using tem.

+ C++ users who compile from source should set CXX to a C++
compiler rather than a C compiler. For example, use g++
rather than gcc. This includes the server as well as
client programs.

+ mysql_config now has a –cxxflags option. This is like
the –cflags option, but produces flags appropriate for a
C++ compiler rather than a C compiler.

+ User-defined functions can be written in C++ using
standard library features.

* New optimizations apply to read-only InnoDB transactions. See
Section 13.2.5.2.2, “Optimizations for Read-Only Transactions”
for details. The new optimizations make autocommit more
applicable to InnoDB queries than before, as a way to signal
that a transaction is read-only because it is a
single-statement SELECT.

* You can now set the InnoDB page size for uncompressed tables
to 8KB or 4KB, as an alternative to the default 16KB. This
setting is controlled by the innodb_page_size configuration
option. You specify the size when creating the MySQL instance.
All InnoDB tablespaces within an instance share the same page
size. Smaller page sizes can help to avoid redundant or
inefficient I/O for certain combinations of workload and
storage devices, particularly SSD devices with small block
sizes.

* MySQL now supports FULLTEXT indexes for InnoDB tables. The
core syntax is very similar to the FULLTEXT capability from
earlier releases, with the CREATE TABLE and CREATE INDEX
statements, and MATCH() … AGAINST() clause in the SELECT
statement. The new @ operator allows proximity searches for
terms that are near each other in the document. The detailed
search processing is controlled by a new set of configuration
options: innodb_ft_enable_stopword,
innodb_ft_server_stopword_table,
innodb_ft_user_stopword_table, innodb_ft_cache_size,
innodb_ft_min_token_size, and innodb_ft_max_token_size. You
can monitor the workings of the InnoDB full-text search system
by querying new INFORMATION_SCHEMA tables:
innodb_ft_default_stopword, innodb_ft_index_table,
innodb_ft_index_cache, innodb_ft_config, innodb_ft_deleted,
and innodb_ft_being_deleted.

Bugs Fixed

* Incompatible Change: Replication: The statements in the
following list are now marked as unsafe for statement-based
replication. This is due to the fact that each of these
statements depends on the results of a SELECT statement whose
order cannot always be determined. When using STATEMENT
logging mode, a warning is issued in the binary log for any of
these statements; when using MIXED logging mode, the statement
is logged using the row-based format.

+ INSERT … SELECT … ON DUPLICATE KEY UPDATE
+ REPLACE … SELECT
+ CREATE TABLE … IGNORE SELECT
+ CREATE TABLE … REPLACE SELECT
+ INSERT IGNORE … SELECT
+ UPDATE IGNORE

When upgrading, you should note the use of these statements in
your applications, keeping in mind that a statement that
inserts or replaces rows obtained from a SELECT can take up
many times as much space in the binary log when logged using
row-based format than when only the statement itself is
logged. Depending on the number and size of the rows selected
and inserted (or replaced) by any such statements, the
difference in size of the binary log after the logging of
these statements is switched from statement-based to row-based
can potentially be several orders of magnitude. See Section
15.1.2.1, “Advantages and Disadvantages of Statement-Based and
Row-Based Replication.” (Bug #11758262, Bug #50439)

* Incompatible Change: Previously, “Aborted connection” errors
were written to the error log based on the session value of
log_warnings, which permitted users with minimal privileges to
cause many messages to be written to the log unless restricted
by the MAX_CONNECTIONS_PER_HOUR resource limit. Now this
logging is based on the global log_warnings variable. There
are no remaining uses of the session log_warnings variable, so
it has been removed that the variable has only a global value.
(Bug #53466, Bug #11761014)

* Important Change: InnoDB Storage Engine: Data from BLOB
columns could be lost if the server crashed at a precise
moment when other columns were being updated in an InnoDB
table. (Bug #12704861)

* InnoDB Storage Engine: This fix improves the performance of
instrumentation code for InnoDB buffer pool operations. (Bug
#12950803, Bug #62294)

* InnoDB Storage Engine: Unused functions were removed from the
internal InnoDB code related to mini-transactions, to clarify
the logic. (Bug #12626794, Bug #61240)

* InnoDB Storage Engine: Lookups using secondary indexes could
give incorrect matches under a specific set of conditions. The
conditions involve an index defined on a column prefix, for a
BLOB or other long column stored outside the index page, with
a table using the Barracuda file format. (Bug #12601439)

* InnoDB Storage Engine: This fix corrects cases where the MySQL
server could hang or abort with a long semaphore wait message.
(This is a different issue than when these symptoms occurred
during a CHECK TABLE statement.) (Bug #11766591, Bug #59733)

* Partitioning: CHECKSUM TABLE returned 0 for a partitioned
table unless the statement was used with the EXTENDED option.
(Bug #11933226, Bug #60681)

* Partitioning: Error 1214 (ER_TABLE_CANT_HANDLE_FT), given when
trying to use a FULLTEXT index with a partitioned table,
displayed the misleading text The used table type doesn’t
support FULLTEXT indexes was misleading and has been replaced
with Error 1752 (ER_FULLTEXT_NOT_SUPPORTED_WITH_PARTITIONING)
which shows the more accurate FULLTEXT index is not supported
for partitioned tables. (Bug #11763825, Bug #56590)

* Replication: The value set for the slave_parallel_workers
system variable (or the corresponding –slave-parallel-workers
server option) was not always honored correctly; in such cases
a random value was used. (Bug #13334470)

* Replication: Several warnings and informational messages were
revised for typographic errors and clarity. (Bug #12947248,
Bug #12978113)

* Replication: A replication master could send damaged events to
slaves after the binary log disk on the master became full. To
correct this issue, only complete events are now pushed by the
master dump thread to the slave I/O thread. In addition, the
error text that the master sends to the slave when an
incomplete event is found now states that the incomplete event
may have been caused by running out of disk space on the
master, and provides coordinates of the first and the last
event bytes read. (Bug #11747416, Bug #32228)

* A derived table with more than 64 columns caused a server
crash. (Bug #13354889)

* Writes to the slow log involved a call to thd->current_utime()
even if no log entries ended up being written, unnecessarily
reducing performance. (Bug #13326965)

* Rounding DBL_MAX returned DBL_MAX, not ‘inf’. (Bug #13261955)

* Access privileges were checked for each stored program
instruction, even if the instruction used no tables, resulting
in reduced performance. (Bug #13251277)

* The error message for ER_EVENT_CANNOT_ALTER_IN_THE_PAST was
incorrect. (Bug #13247871)

* During the table-opening process, memory was allocated and
later freed that was needed view loading, even for statements
that did not use views. These unnecessary allocation and free
operations are no longer done. (Bug #13116518)

* Subqueries with OUTER JOIN could return incorrect results if
the subquery referred to a column from another SELECT. (Bug
#13068506)

* The Performance Schema nested some network I/O events within
the wrong statement. (Bug #12981100)

* mysql_plugin mishandled the –plugin-ini, –mysqld, and
–my-print-defaults options under some circumstances. (Bug
#12968815)

* mysql_plugin returned the wrong error code from failed server
bootstrap execution. (Bug #12968567)

* Internal conversion of zero to binary and back could yield a
result with incorrect precision. (Bug #12911710)

* Valgrind warnings generated by filesort operations were fixed.
(Bug #12856915)

* Partitioning: Using ALTER TABLE to remove partitioning from a
valid MyISAM table could corrupt it. (Bug #52599, Bug
#11760213)

* An IN-to-EXISTS subquery transformation could yield incorrect
results if the outer value list contained NULL. (Bug
#12838171)

* With index condition pushdown enabled, STRAIGHT_JOIN queries
could produce incorrect results. (Bug #12822678, Bug
#12724899)

* The result of ROUND() was incorrect for certain numbers. (Bug
#12744991)

* A warning resulting from use of SPACE() referred to REPEAT()
in the warning message. (Bug #12735829)

* IN and EXISTS subqueries with DISTINCT and ORDER BY could
return incorrect results. (Bug #12709738)

* Several improvements were made to the libedit library bundled
with MySQL distributions, and that is available for all
platforms that MySQL supports except Windows.

+ Navigation keys did not work for UTF-8 input.

+ Word navigation and delete operations did not work for
UTF-8 input with Cyrillic characters.

+ Nonlatin characters were corrupted in overwrite mode for
UTF-8 input.

+ Long queries caused the statement history file to become
corrupted.

+ The Alt key caused history operations to fail.

(Bug #12605400, Bug #12613725, Bug #12618092, Bug #12624155,
Bug #12617651, Bug #12605388)

* SELECT SQL_BUFFER_RESULT query results included too many rows
if a GROUP BY clause was optimized away. (Bug #12578908)

* mysqldump –all-databases did not dump the replication log
tables. (They could be dumped only by naming them explicitly
when invoking mysqldump, and using the –master-data option.)

As a result of the fix for this problem, it is now possible to
execute statements requiring read locks on the replication log
tables at any time, while any statements requiring a write
lock on either or both of these tables are disallowed whenever
replication is in progress. For more information, see Section
15.2.2, “Replication Relay and Status Logs.” (Bug #12402875,
Bug #60902)

* mysqld_safe did not properly check for an already running
instance of mysqld. (Bug #11878394)

* Replication: –replicate-rewrite-db=from_name->to_name did not
work correctly when the name of the source database
(from_name) consisted of only a single character. (Bug #34332,
Bug #11747866)

* If index condition pushdown access was chosen and then
abandoned, some variables were not cleared, leading to
incorrect query results. (Bug #62533)

* For a lower_case_table_names value of 1 or 2 and a database
having a mixed-case name, calling a stored function using a
fully qualified name including the database name failed. (Bug
#60347, Bug #11840395)

* mysql_upgrade did not upgrade the system tables or create the
mysql_upgrade_info file when run with the –write-binlog or
–skip-write-binlog option. (Bug #60223, Bug #11827359)

* A multiple-table UPDATE statement required the UPDATE
privilege on a view which was only read if the view was
processed using the merge algorithm. (Bug #59957, Bug
#11766767)

* When a join operation contained a view, the optimizer
sometimes failed to associate the view’s WHERE clause
with the first table or view in a join when it was
possible to do so, resulting in a less efficient query.
(Bug #59696, Bug #11766559)

* An assertion was raised when selecting from a view that
selects from a view that used a user-defined function that had
been deleted. (Bug #59546, Bug #11766440)

* The help message for mysql_install_db did not indicate that it
supports the –defaults-file, –defaults-extra-file and
–no-defaults options. (Bug #58898, Bug #11765888)

* mysql_install_db printed the –skip-grant-tables server option
as –skip-grant in one of its error messages. (Bug #58534, Bug
#11765553)

* An assertion designed to detect zero-length sort keys also was
raised when the entire key set fit in memory. (Bug #58200, Bug
#11765254)

* During optimization, ZEROFILL values may be converted to
string constants. However, CASE expressions did not handle
switching data types after the planning stage, leading to CASE
finding a null pointer instead of its argument. (Bug #57135,
Bug #11764313)

* If a plugin was uninstalled, thread local variables for plugin
variables of string type with wth PLUGIN_VAR_MEMALLOC flag
were not freed. (Bug #56652, Bug #11763882)

* Deadlock could occur when these four things happened at the
same time: 1) An old dump thread was waiting for the binary
log to grow. 2) The slave server that replicates from the old
dump thread tried to reconnect. During reconnection, the new
dump thread tried to kill the old dump thread. 3) A KILL
statement tried to kill the old dump thread. 4) An INSERT
statement caused a binary log rotation. (Bug #56299, Bug
#11763573)

* myisampack could create corrupt FULLTEXT indexes when
compressing tables. (Bug #53646, Bug #11761180)

* The SQL_BIG_RESULT modifier could change the results for
queries that included a GROUP BY clause. (Bug #53534, Bug
#11761078)

* ARCHIVE tables with NULL columns could cause server crashes or
become corrupt under concurrent load. (Bug #51252, Bug
#11758979)

* InnoDB used incorrect identifier quoting style in an error
message that resulted in an error if a user followed the
suggestion in the message. (Bug #49556, Bug #11757503)

* OPTIMIZE TABLE could corrupt MyISAM tables if myisam_use_mmap
was enabled. (Bug #49030, Bug #11757032)

* A query that selected a GROUP_CONCAT() function result could
return different values depending on whether an ORDER BY of
the function result was present. (Bug #41090, Bug #11750518)

* A linking problem prevented the FEDERATED storage engine
plugin from loading. (Bug #40942, Bug #11750417)

* Subqueries could return incorrect results when materialization
was enabled. (Bug #40037, Bug #11749901, Bug #12705660, Bug
#12908058)

* For debug builds, an assertion could be raised for ALTER
statements that performed a RENAME operation. This occurred
for storage engine handlertons that exposed the
HTON_FLUSH_AFTER_RENAME flag. (Bug #38028, Bug #11749050)

* The estimate of space required for filesort operations could
be too high, resulting in inefficient initialization. (Bug
#37359, Bug #11748783)

* An ALTER TABLE that included an ADD … AFTER operation to add
a new column after a column that had been modified earlier in
the statement failed to find the existing column. (Bug #34972,
Bug #11748057)

* For FEDERATED tables, loss of connection to the remote table
during some insert operations could cause a server crash. (Bug
#34660, Bug #11747970)

* For some queries, the index_merge access method was used even
when more expensive then ref access. (Bug #32254, Bug
#11747423)

MySQL 5.5 includes several high-impact enhancements to improve the performance and scalability of the MySQL Database, taking advantage of the latest multi-CPU and multi-core hardware and operating systems. In

addition, with release 5.5, InnoDB is now the default storage engine for the MySQL Database, delivering ACID transactions, referential integrity and crash recovery by default.

MySQL 5.5 also provides a number of additional enhancements including:

- Significantly improved performance on Windows, with various Windows specific features and improvements

- Higher availability, with new semi-synchronous replication and Replication Heart Beat

- Improved usability, with Improved index and table partitioning, SIGNAL/RESIGNAL support and enhanced diagnostics, including a new Performance Schema monitoring capability.

The following section lists the changes in the MySQL source code since the previous released version of MySQL 5.5.

Changes in MySQL 5.5.15 (28 July 2011)

Functionality Added or Changed

* The undocumented –all option for perror is deprecated and

will be removed in MySQL 5.6.

Bugs Fixed

* InnoDB Storage Engine: A failed CREATE INDEX operation for an

InnoDB table could result in some memory being allocated but

not freed. This memory leak could affect tables created with

the ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED setting. (Bug

#12699505)

* Partitioning: Auto-increment columns of partitioned tables

were checked even when they were not being written to. In

debug builds, this could lead to a server crash. (Bug

#11765667, Bug #58655)

* Partitioning: The UNIX_TIMESTAMP() function was not treated as

a monotonic function for purposes of partition pruning. (Bug

#11746819, Bug #28928)

* Compiling the server with maintainer mode enabled failed for

gcc 4.6 or higher. (Bug #12727287)

* The option-parsing code for empty strings leaked memory. (Bug

#12589928)

* Previously, an inappropriate error message was produced if a

multiple-table update for an InnoDB table with a clustered

primary key would update a table through multiple aliases, and

perform an update that may physically move the row in at least

one of these aliases. Now the error message is: Primary

key/partition key update is not permitted since the table is

updated both as ‘tbl_name1′ and ‘tbl_name2′ (Bug #11882110)

See also Bug #11764529.

* Replication: If a LOAD DATA INFILE statement—replicated

using statement-based replication—featured a SET clause, the

name-value pairs were regenerated using a method

(Item::print()) intended primarily for generating output for

statements such as EXPLAIN EXTENDED, and which cannot be

relied on to return valid SQL. This could in certain cases

lead to a crash on the slave.

To fix this problem, the server now names each value in its

original, user-supplied form, and uses that to create LOAD

DATA INFILE statements for statement-based replication. (Bug

#60580, Bug #11902767)

See also Bug #34283, Bug #11752526, Bug #43746.

* ALTER TABLE {MODIFY|CHANGE} … FIRST did nothing except

rename columns if the old and new versions of the table had

exactly the same structure with respect to column data types.

As a result, the mapping of column name to column data was

incorrect. The same thing happened for ALTER TABLE DROP COLUMN

… ADD COLUMN statements intended to produce a new version of

the table with exactly the same structure as the old version.

(Bug #61493, Bug #12652385)

* Incorrect handling of metadata locking for FLUSH TABLES WITH

READ LOCK for statements requiring prelocking caused two

problems:

+ Execution of any data-changing statement that required

prelocking (that is, involved a stored function or

trigger) as part of a transaction slowed down somewhat

all subsequent statements in the transaction. Performance

in a transaction that periodically involved such

statements gradually degraded over time.

+ Execution of any data-changing statement that required

prelocking as part of a transaction prevented a

concurrent FLUSH TABLES WITH READ LOCK from proceeding

until the end of the transaction rather than at the end

of the particular statement.

(Bug #61401, Bug #12641342)

* The fractional part of the “Queries per second” value could be

displayed incorrectly in MySQL status output (for example, in

the output from mysqladmin status or the mysql STATUS

command). (Bug #61205, Bug #12565712)

* LOAD DATA INFILE incorrectly parsed relative data file path

names that ascended more than three levels in the file system

and as a consequence was unable to find the file. (Bug #60987,

Bug #12403662)

* For unknown users, the native password plugin reported

incorrectly that no password had been specified even when it

had. (Bug #59792, Bug #11766641)

* For MyISAM tables, attempts to insert incorrect data into an

indexed GEOMETRY column could result in table corruption. (Bug

#57323, Bug #11764487)

* In debug builds, Field_new_decimal::store_value() was subject

to buffer overflows. (Bug #55436, Bug #11762799)

* A race condition between loading a stored routine using the

name qualified by the database name and dropping that database

resulted in a spurious error message: The table mysql.proc is

missing, corrupt, or contains bad data (Bug #47870, Bug

#11756013)

world’s most popular open source database. MySQL 5.5.13 is recommended

for use on production systems.

MySQL 5.5 includes several high-impact enhancements to improve the

performance and scalability of the MySQL Database, taking advantage of

the latest multi-CPU and multi-core hardware and operating systems. In

addition, with release 5.5, InnoDB is now the default storage engine for

the MySQL Database, delivering ACID transactions, referential integrity

and crash recovery by default.

MySQL 5.5 also provides a number of additional enhancements including:

- Significantly improved performance on Windows, with various Windows specific features and improvements

- Higher availability, with new semi-synchronous replication and Replication Heart Beat

- Improved usability, with Improved index and table partitioning, SIGNAL/RESIGNAL support and enhanced diagnostics, including a new Performance Schema monitoring capability.

Changes in MySQL 5.5.13 :

Note:

Very old (MySQL 4.0) clients are not working temporarily due to a

problem discovered after the release of MySQL 5.5.12. We are

looking at fixing the problem.

Bugs fixed:

* InnoDB Storage Engine: If the server crashed while an XA

transaction was prepared but not yet committed, the

transaction could remain in the system after restart, and

cause a subsequent shutdown to hang. (Bug #11766513, Bug

#59641)

* InnoDB Storage Engine: Similar problem to the foreign key

error in bug #11831040 / 60196 / 60909, but with a different

root cause and occurring on Mac OS X. With the setting

lower_case_table_names=2, inserts into InnoDB tables covered

by foreign key constraints could fail after a server restart.

* Partitioning: The internal get_partition_set() function did

not take into account the possibility that a key specification

could be NULL in some cases. (Bug #12380149)

* Partitioning: When executing a row-ordered retrieval index

merge, the partitioning handler used memory from that

allocated for the table, rather than that allocated to the

query, causing table object memory not to be freed until the

table was closed. (Bug #11766249, Bug #59316)

* Replication: A spurious error malformed binlog: it does not

contain any Format_description_log_event… was generated when

mysqlbinlog was invoked using –base64-output=decode-row and

–start-position=pos, where pos is a point in the binary log

past the format description log event. However, there is

nothing unsafe about not printing the format description log

event, so the error has been removed for this case. (Bug

#12354268)

* Replication: Typographical errors appeared in the text of

several replication error messages. (The word “position” was

misspelled as “postion”.) (Bug #11762616, Bug #55229)

* Assignments to NEW.var_name within triggers, where var_name

had a BLOB or TEXT type, were not properly handled and

produced incorrect results. (Bug #12362125)

* XA COMMIT could fail to clean up the error state if it

discovered that the current XA transaction had to be rolled

back. Consequently, the next XA transaction could raise an

assertion when it checked for proper cleanup of the previous

transaction. (Bug #12352846)

* An internal client macro reference was removed from the

client_plugin.h header file. This reference made the file

unusable. (Bug #60746, Bug #12325444)

* The server consumed memory for repeated invocation of some

stored procedures, which was not released until the connection

terminated. (Bug #60025, Bug #11848763)

* The server did not check for certain invalid out of order

sequences of XA statements, and these sequences raised an

assertion. (Bug #59936, Bug #11766752, Bug #12348348)

* With the conversion from GNU autotools to CMake for

configuring MySQL, the USE_SYMDIR preprocessor symbol was

omitted. This caused failure of symbolic links (described at

Section 7.11.3.1, “Using Symbolic Links”). (Bug #59408, Bug

#11766320)

* The incorrect max_length value for YEAR values could be used

in temporary result tables for UNION, leading to incorrect

results. (Bug #59343, Bug #11766270)

* In Item_func_in::fix_length_and_dec(), a Valgrind warning for

uninitialized values was corrected. (Bug #59270, Bug

#11766212)

* In ROUND() calculations, a Valgrind warning for uninitialized

memory was corrected. (Bug #58937, Bug #11765923)

* Valgrind warnings caused by comparing index values to an

uninitialized field were corrected. (Bug #58705, Bug

#11765713)

* LOAD DATA INFILE errors could leak I/O cache memory. (Bug

#58072, Bug #11765141)

* For LOAD DATA INFILE, multibyte character sequences could be

pushed onto a stack too small to accommodate them. (Bug

#58069, Bug #11765139)

* Internal Performance Schema header files were unnecessarily

installed publicly. (Bug #53281)

* On Linux, the mysql client built using the bundled libedit did

not read ~/.editrc. (Bug #49967, Bug #11757855)

* The optimizer sometimes incorrectly processed HAVING clauses

for queries that did not also have an ORDER BY clause. (Bug

#48916, Bug #11756928)

* PROCEDURE ANALYZE() could leak memory for NULL results, and

could return incorrect results if used with a LIMIT clause.

(Bug #48137, Bug #11756242)

* With DISTINCT CONCAT(col,…) returned incorrect results when

the arguments to CONCAT() were columns with an integer data

type declared with a display width narrower than the values in

the column. (For example, if an INT(1) column contain 1111.)

(Bug #4082)

MySQL 5.5 includes several high-impact enhancements to improve the performance and scalability of the MySQL Database, taking advantage of the latest multi-CPU and multi-core hardware and operating systems. In addition, with release 5.5, InnoDB is now the default storage engine for the MySQL Database, delivering ACID transactions, referential integrity and crash recovery by default.

MySQL 5.5 also provides a number of additional enhancements including:

- Significantly improved performance on Windows, with various Windows specific features and improvements

- Higher availability, with new semi-synchronous replication and Replication Heart Beat

- Improved usability, with Improved index and table partitioning, SIGNAL/RESIGNAL support and enhanced diagnostics, including a new PERFORMANCE_SCHEMA

The following section lists the changes in the MySQL source code since the previous released version of MySQL 5.5.

—-

D.1.2. Changes in MySQL 5.5.10

Configuration Notes:

* MySQL releases are now built on all platforms using CMake

rather than the GNU autotools, so autotools support has been

removed. For instructions on building MySQL with CMake, see

Section 2.11, “Installing MySQL from Source.” Third-party

tools that need to extract the MySQL version number formerly

found in configure.in can use the VERSION file. See Section

2.11.6, “MySQL Configuration and Third-Party Tools.”

C API Notes:

* Incompatible Change: The shared library version of the client

library was increased to 18 to reflect ABI changes, and avoid

compatibility problems with the client library in MySQL 5.1.

Note that this is an incompatible change between 5.5.10 and

earlier 5.5 versions, so client programs that use the 5.5

client library should be recompiled against the 5.5.10 client

library.

Functionality added or changed:

* MySQL distributions now include auth_socket, a server-side

authentication plugin that authenticates clients that connect

from the local host through the Unix socket file. The plugin

uses the SO_PEERCRED socket option to obtain information about

the user running the client program (and thus can be built

only on systems that support this option. For a connection to

succeed, the plugin requires a match between the login name of

the connecting client user and the MySQL user name presented

by the client program. For more information, see Section

5.5.6.1.4, “The Socket Peer-Credential Authentication Plugin.”

(Bug #59017, Bug #11765993)

* The mysql_upgrade, mysqlbinlog, mysqlcheck, mysqlimport,

mysqlshow, and mysqlslap clients now have –default-auth and

–plugin-dir options for specifying which authentication

plugin and plugin directory to use. (Bug #58139)

* Boolean system variables can be enabled at run time by setting

them to the value ON or OFF, but previously this did not work

at server startup. Now at startup such variables can be

enabled by setting them to ON or TRUE, or disabled by setting

them to OFF or FALSE. Any other nonnumeric variable is

invalid. (Bug #46393)

See also Bug #51631.

* Previously, for queries that were aborted due to sort problem,

the server wrote the message Sort aborted to the error log.

Now the server writes more information to provide a more

specific message, such as:

[ERROR] mysqld: Sort aborted: Out of memory (Needed 24 bytes)

[ERROR] mysqld: Out of sort memory,

consider increasing server sort buffer size

[ERROR] mysqld: Sort aborted: Out of sort memory,

consider increasing server sort buffer size

[ERROR] mysqld: Sort aborted: Incorrect number of arguments for

FUNCTION test.f1; expected 0, got 1

In addition, if the server was started with –log-warnings=2,

the server write information about the host, user, and query.

(Bug #36022, Bug #11748358)

* mysqldump –xml now displays comments from column definitions.

(Bug #13618)

* MySQL distributions now include mysql_clear_password, a

client-side authentication plugin that sends the password to

the server without hashing or encryption. Although this is

insecure, and thus apprpropriate precautions should be taken

such as using an SSL connection, the plugin is useful in

conjunction with server-side plugins that must have access to

the original password in clear text. For more information, see

Section 5.5.6.1.3, “The Clear Text Client-Side Authentication

Plugin.”

Bugs fixed:

* InnoDB Storage Engine: Raised the number of I/O requests that

each AIO

(http://dev.mysql.com/doc/innodb/1.1/en/glossary.html#glos_aio

) helper thread could process, from 32 to 256. The new limit

applies to Linux and Unix platforms; the limit on Windows

remains 32. (Bug #59472)

* InnoDB Storage Engine: InnoDB returned values for “rows

examined” in the query plan that were higher than expected.

NULL values were treated in an inconsistent way. The

inaccurate statistics could trigger “false positives” in

combination with the MAX_JOIN_SIZE setting, because the

queries did not really examine as many rows as reported. (Bug

#30423)

* Replication: When using the statement-based logging format,

INSERT ON DUPLICATE KEY UPDATE and INSERT IGNORE statements

affecting transactional tables that did not fail were not

written to the binary log if they did not insert any rows.

(With statement-based logging, all successful statements

should be logged, whether they do or do not cause any rows to

be changed.) (Bug #59338)

* Replication: Formerly, STOP SLAVE stopped the slave I/O thread

first and then stopped the slave SQL thread; thus, it was

possible for the I/O thread to stop after replicating only

part of a transaction which the SQL thread was executing, in

which case—if the transaction could not be rolled back

safely—the SQL thread could hang.

Now, STOP SLAVE stops the slave SQL thread first and then

stops the I/O thread; this guarantees that the I/O thread can

fetch any remaining events in the transaction that the SQL

thread is executing, so that the SQL thread can finish the

transaction if it cannot be rolled back safely. (Bug #58546)

* DES_DECRYPT() could crash if the argument was not produced by

DES_ENCRYPT(). (Bug #59632, Bug #11766505)

* The server and client did not always properly negotiate

authentication plugin names. (Bug #59453)

* –autocommit=ON did not work (it set the global autocommit

value to 0, not 1). (Bug #59432)

* A query of the following form returned an incorrect result,

where the values for col_name in the result set were entirely

replaced with NULL values:

SELECT DISTINCT col_name … ORDER BY col_name DESC;

(Bug #59308, Bug #11766241)

* SHOW PRIVILEGES did not display a row for the PROXY privilege.

(Bug #59275)

* SHOW PROFILE could truncate source file names or fail to show

function names. (Bug #59273, Bug #11766214)

* DELETE or UPDATE statements could fail if they used DATE or

DATETIME values with a year, month, or day part of zero. (Bug

#59173)

* The ESCAPE clause for the LIKE operator allows only

expressions that evaluate to a constant at execution time, but

aggregate functions were not being rejected. (Bug #59149)

* Memory leaks detected by Valgrind, some of which could cause

incorrect query results, were corrected. (Bug #59110, Bug

#11766075)

* The DEFAULT_CHARSET and DEFAULT_COLLATION CMake options did

not work. (Bug #58991)

* An OUTER JOIN query using WHERE column IS NULL could return an

incorrect result. (Bug #58490, Bug #11765513)

* Starting the server with the –defaults-file=file_name option,

where the file name had no extension, caused a server crash.

(Bug #58455, Bug #11765482)

* Outer joins with an empty table could produce incorrect

results. (Bug #58422)

* In debug builds, SUBSTRING_INDEX(FORMAT(…), FORMAT(…))

could cause a server crash. (Bug #58371)

* When mysqladmin was run with the –sleep and –count options,

it went into an infinite loop executing the specified command.

(Bug #58221)

* Some string manipulating SQL functions use a shared string

object intended to contain an immutable empty string. This

object was used by the SQL function SUBSTRING_INDEX() to

return an empty string when one argument was of the wrong

datatype. If the string object was then modified by the SQL

function INSERT(), undefined behavior ensued. (Bug #58165, Bug

#11765225)

* Parsing nested regular expressions could lead to recursion

resulting in a stack overflow crash. (Bug #58026, Bug

#11765099)

* The fix for Bug#25192 caused load_defaults() to add an

argument separator to distinguish options loaded from

configure files from those provided on the command line,

whether or not the application needed it. (Bug #57953)

* The mysql client went into an infinite loop if the standard

input was a directory. (Bug #57450)

* Outer joins on a unique key could return incorrect results.

(Bug #57034)

* The expression const1 BETWEEN const2 AND field was optimized

incorrectly and produced incorrect results. (Bug #57030, Bug

#11764215)

* Some RPM installation scripts used a hardcoded value for the

data directory, which could result in a failed installation

for users who have a nonstandard data directory location. The

same was true for other configuration values such as the PID

file name. (Bug #56581, Bug #11763817)

* On FreeBSD and OpenBSD, the server incorrectly checked the

range of the system date, causing legal values to be rejected.

(Bug #55755, Bug #11763089)

* Sorting using ORDER BY AVG(DISTINCT decimal_col) caused a

server crash or incorrect results. (Bug #52123, Bug #11759784)

* When using ExtractValue() or UpdateXML(), if the XML to be

read contained an incomplete XML comment, MySQL read beyond

the end of the XML string when processing, leading to a crash

of the server. (Bug #44332)

* DATE_ADD() and DATE_SUB() return a string if the first

argument is a string, but incorrectly returned a binary

string. Now they return a character string with a collation of

connection_collation. (Bug #31384, Bug #11747221)

MySQL Workbench 5.2 GA

- Data Modeling

- Query (replaces the old MySQL Query Browser)

- Administration (replaces the old MySQL Administrator)

In addition to the new Query/SQL Development and Administration modules, version 5.2 features improved stability and performance – especially in Windows, where OpenGL support has been enhanced and the UI was optimized to offer better responsiveness.

For a detailed list of resolved issues, see the change log:  http://dev.mysql.com/doc/workbench/en/wb-change-history.html

The tabbed interface has been refreshed to obtain a clearer separation between different modules of Workbench, while improving responsiveness when switching between tabs. The Query Formatter has been rewritten and is now faster and more robust on its handling of queries. The layout of the Administration module has been changed to allow for easier future expansion and use less vertical screen space. Parts that had problems managing MySQL 5.5 servers have been fixed along other total of 53 bugs or enhancement requests have been addressed.

Management System, has been released.  Please note that the active

maintenance of 5.0 has ended, and these builds are only provided

because of the fixes to security bugs as described below.

Changes in MySQL 5.0.92  (7 February, 2011)

Functionality added or changed:

* The time zone tables available at

http://dev.mysql.com/downloads/timezones.html have been

updated. These tables can be used on systems such as

Windows or HP-UX that do not include zoneinfo files.

(Bug#40230:http://bugs.mysql.com/bug.php?id=40230)

Bugs fixed:

* Security Fix: During evaluation of arguments to

extreme-value functions (such as LEAST() and GREATEST()),

type errors did not propagate properly, causing the

server to crash.

(Bug#55826:http://bugs.mysql.com/bug.php?id=55826,

CVE-2010-3833

(http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3833)

* Security Fix: The server could crash after materializing

a derived table that required a temporary table for

grouping.

(Bug#55568:http://bugs.mysql.com/bug.php?id=55568,

CVE-2010-3834

(http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3834)

* Security Fix: A user-variable assignment expression that

is evaluated in a logical expression context can be

precalculated in a temporary table for GROUP BY. However,

when the expression value is used after creation of the

temporary table, it was re-evaluated, not read from the

table and a server crash resulted.

(Bug#55564:http://bugs.mysql.com/bug.php?id=55564,

CVE-2010-3835

(http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3835)

* Security Fix: Joins involving a table with a unique SET

column could cause a server crash.

(Bug#54575:http://bugs.mysql.com/bug.php?id=54575,

CVE-2010-3677

(http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3677)

* Security Fix: Pre-evaluation of LIKE predicates during

view preparation could cause a server crash.

(Bug#54568:http://bugs.mysql.com/bug.php?id=54568,

CVE-2010-3836

(http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3836)

* Security Fix: GROUP_CONCAT() and WITH ROLLUP together

could cause a server crash.

(Bug#54476:http://bugs.mysql.com/bug.php?id=54476,

CVE-2010-3837

(http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3837)

* Security Fix: Queries could cause a server crash if the

GREATEST() or LEAST() function had a mixed list of

numeric and LONGBLOB arguments, and the result of such a

function was processed using an intermediate temporary

table.

(Bug#54461:http://bugs.mysql.com/bug.php?id=54461,

CVE-2010-3838

(http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3838)

* Security Fix: Using EXPLAIN with queries of the form

SELECT … UNION … ORDER BY (SELECT … WHERE …)

could cause a server crash.

(Bug#52711:http://bugs.mysql.com/bug.php?id=52711,

CVE-2010-3682

(http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3682)

* InnoDB Storage Engine: Creating or dropping a table with

1023 transactions active caused an assertion failure.

(Bug#49238:http://bugs.mysql.com/bug.php?id=49238)

* The make_binary_distribution target to make could fail on

some platforms because the lines generated were too long

for the shell.

(Bug#54590:http://bugs.mysql.com/bug.php?id=54590)

* A client could supply data in chunks to a prepared

statement parameter other than of type TEXT or BLOB using

the mysql_stmt_send_long_data() C API function (or

COM_STMT_SEND_LONG_DATA command). This led to a crash

because other data types are not valid for long data.

(Bug#54041:http://bugs.mysql.com/bug.php?id=54041)

* Builds of the embedded mysqld would fail due to a missing

element of the struct NET.

(Bug#53908:http://bugs.mysql.com/bug.php?id=53908,

Bug#53912:http://bugs.mysql.com/bug.php?id=53912)

* The definition of the MY_INIT macro in my_sys.h included

an extraneous semicolon, which could cause compilation

failure.

(Bug#53906:http://bugs.mysql.com/bug.php?id=53906)

* If the remote server for a FEDERATED table could not be

accessed, queries for the INFORMATION_SCHEMA.TABLES table

failed.

(Bug#35333:http://bugs.mysql.com/bug.php?id=35333)

* mysqld could fail during execution when using SSL.

(Bug#34236:http://bugs.mysql.com/bug.php?id=34236)

* Threads that were calculating the estimated number of

records for a range scan did not respond to the KILL

statement. That is, if a range join type is possible

(even if not selected by the optimizer as a join type of

choice and thus not shown by EXPLAIN), the query in the

statistics state (shown by the SHOW PROCESSLIST) did not

respond to the KILL statement.

(Bug#25421:http://bugs.mysql.com/bug.php?id=25421)

world’s most popular open source database. MySQL 5.5.9 is recommended

for use on production systems.

MySQL 5.5 includes several high-impact changes to address scalability

and performance issues in MySQL Server.  These changes exploit advances

in hardware and CPU design and enable better utilization of existing

hardware.  MySQL 5.5 also provides a number of other new enhancements,

including:

- InnoDB I/O Subsystem Changes

- Enhanced Solaris Support

- Diagnostic and Monitoring Capabilities

The following section lists the changes in the MySQL source code since

the previous released version of MySQL 5.5.

—-

D.1.2. Changes in MySQL 5.5.9

Configuration Notes:

* MySQL releases are now built on all platforms using CMake

rather than the GNU autotools, so autotools support has been

removed. For instructions on building MySQL with CMake, see

Section 2.11, “Installing MySQL from Source.” Third-party

tools that need to extract the MySQL version number formerly

found in configure.in can use the VERSION file. See Section

2.11.6, “MySQL Configuration and Third-Party Tools.”

Functionality added or changed:

* The mysqladmin and mysqldump clients now have –default-auth

and –plugin-dir options for specifying which authentication

plugin and plugin directory to use.

(Bug#58139: http://bugs.mysql.com/bug.php?id=58139)

* sql_priv.h now includes an OPTION_ALLOW_BATCH flag for the

transaction_allow_batching

(http://dev.mysql.com/doc/refman/5.1/en/server-system-variable

s.html#sysvar_transaction_allow_batching) feature of MySQL

Cluster. (Bug#57604: http://bugs.mysql.com/bug.php?id=57604)

* Boolean system variables can be enabled at run time by setting

them to the value ON or OFF, but previously this did not work

at server startup. Now at startup such variables can be

enabled by setting them to ON or TRUE. Any other nonnumeric

variable is interpreted as OFF.

(Bug#46393: http://bugs.mysql.com/bug.php?id=46393 improves on

this such that ON, TRUE, OFF, and FALSE are recognized, and

other values are invalid.)

(Bug#51631: http://bugs.mysql.com/bug.php?id=51631)

Bugs fixed:

* Incompatible Change: When auto_increment_increment is greater

than one, values generated by a bulk insert that reaches the

maximum column value could wrap around rather producing an

overflow error.

As a consequence of the fix, it is no longer possible for an

auto-generated value to be equal to the maximum BIGINT

UNSIGNED value. It is still possible to store that value

manually, if the column can accept it.

(Bug#39828: http://bugs.mysql.com/bug.php?id=39828)

* Important Change: Partitioning: Date and time functions used

as partitioning functions now have the types of their operands

checked; use of a value of the wrong type is now disallowed in

such cases. In addition, EXTRACT(WEEK FROM col), where col is

a DATE or DATETIME column, is now disallowed altogether

because its return value depends on the value of the

default_week_format system variable.

(Bug#54483: http://bugs.mysql.com/bug.php?id=54483)

See also Bug#57071: http://bugs.mysql.com/bug.php?id=57071.

* Partitioning: InnoDB Storage Engine: The partitioning handler

did not pass locking information to a table’s storage engine

handler. This caused high contention and thus slower

performance when working with partitioned InnoDB tables.

(Bug#59013: http://bugs.mysql.com/bug.php?id=59013)

* InnoDB Storage Engine: When multiple InnoDB buffer pools were

enabled, SHOW ENGINE INNODB commands displayed information

about each one, but not summary information combining

statistics for the entire buffer pool subsystem. Now, the

aggregated information is displayed in the BUFFER POOL AND

MEMORY section, and information about individual buffer pool

instances is displayed in a new INDIVIDUAL BUFFER POOL INFO

section. (Bug#58461: http://bugs.mysql.com/bug.php?id=58461)

* InnoDB Storage Engine: The command to create a debug build

(cmake -DWITH_DEBUG …) now automatically sets the InnoDB

debugging flag UNIV_DEBUG on all platforms. Formerly, the

UNIV_DEBUG flag might not be set for Windows platforms with

Visual Studio and not on OS X with Xcode.

(Bug#58279: http://bugs.mysql.com/bug.php?id=58279)

* InnoDB Storage Engine: In InnoDB status output, the value for

I/O sum[] could be incorrect, displayed as a very large

number. (Bug#57600: http://bugs.mysql.com/bug.php?id=57600)

* InnoDB Storage Engine: It was not possible to query the

information_schema.innodb_trx table while other connections

were running queries involving BLOB types.

(Bug#55397: http://bugs.mysql.com/bug.php?id=55397)

* InnoDB Storage Engine: When the lowercase_system_names

variable was set to 2, InnoDB could fail to restore a

mysqldump dump of a table with foreign key constraints

involving case-sensitive names.

(Bug#55222: http://bugs.mysql.com/bug.php?id=55222)

* InnoDB Storage Engine: The OPTIMIZE TABLE statement would

reset the auto-increment counter for an InnoDB table. Now the

auto-increment value is preserved across this operation.

(Bug#18274: http://bugs.mysql.com/bug.php?id=18274)

* Partitioning: A failed ALTER TABLE … TRUNCATE PARTITION

statement was still written to the binary log.

(Bug#58147: http://bugs.mysql.com/bug.php?id=58147)

* Partitioning: Failed ALTER TABLE … PARTITION statements

could cause memory leaks.

(Bug#56380: http://bugs.mysql.com/bug.php?id=56380)

See also Bug#46949: http://bugs.mysql.com/bug.php?id=46949,

Bug#56996: http://bugs.mysql.com/bug.php?id=56996.

* Replication: While an INSERT DELAYED statement with a single

inserted value does not return any visible warnings, such a

warning could be still written into the error log.

(Bug#57666: http://bugs.mysql.com/bug.php?id=57666)

See also Bug#49567: http://bugs.mysql.com/bug.php?id=49567.

* Replication: When closing a session that used temporary

tables, binary logging could sometimes fail with a spurious

Failed to write the DROP statement for temporary tables to

binary log.

(Bug#57288: http://bugs.mysql.com/bug.php?id=57288)

* Replication: Due to changes made in MySQL 5.5.3, settings made

in the binlog_cache_size and max_binlog_cache_size server

system variables affected both the binary log statement cache

(also introduced in that version) and the binary log

transactional cache (formerly known simply as the binary log

cache). This meant that the resources used as a result of

setting either or both of these variables were double the

amount expected. To rectify this problem, these variables now

affect only the transactional cache. The fix for this issue

also introduces two new system variables

binlog_stmt_cache_size and max_binlog_stmt_cache_size, which

affect only the binary log statement cache.

In addition, the Binlog_cache_use status variable was

incremented whenever either cache was used, and

Binlog_cache_disk_use was incremented whenever the disk space

from either cache was used, which caused problems with

performance tuning of the statement and transactional caches,

because it was not possible to determine which of these was

being exceeded when attempting to troubleshoot excessive disk

seeks and related problems. This issue is solved by changing

the behavior of these two status variables such that they are

incremented only in response to usage of the binary log

transactional cache, as well as by introducing two new status

variables Binlog_stmt_cache_use and

Binlog_stmt_cache_disk_use, which are incremented only by

usage of the binary log statement cache.

For more information, see Section 17.1.3.4, “System variables

used with the binary log,” and Section 5.1.6, “Server Status

Variables.”

(Bug#57275: http://bugs.mysql.com/bug.php?id=57275)

* Replication: By default, a value is generated for an

AUTO_INCREMENT column by inserting either NULL or 0 into the

column. Setting the NO_AUTO_VALUE_ON_ZERO server SQL mode

suppresses this behavior for 0, so that it occurs only when

NULL is inserted into the column.

This behavior is also followed on a replication slave (by the

slave SQL thread) when applying events that have been logged

on the master using the statement-based format. However, when

applying events that had been logged using the row-based

format, NO_AUTO_VALUE_ON_ZERO was ignored, which could lead to

an assertion.

To fix this issue, the value of an AUTO_INCREMENT column is no

longer generated when applying an event that was logged using

the row-based row format, as this value is already contained

in the changes applied on the slave.

(Bug#56662: http://bugs.mysql.com/bug.php?id=56662)

* Replication: The Binlog_cache_use and Binlog_cache_disk_use

status variables were incremented twice by a change to a table

using a transactional storage engine.

(Bug#56343: http://bugs.mysql.com/bug.php?id=56343)

* Replication: The BINLOG statement modified the values of

session variables, which could lead to problems with

operations such a point-in-time recovery. One such case

occurred when replaying a row-based binary log which relied on

setting foreign_key_checks = OFF on the session level in order

to create and populate a set of InnoDB tables having foreign

key constraints.

(Bug#54903: http://bugs.mysql.com/bug.php?id=54903)

* Replication: mysqlbinlog printed USE statements to its output

only when the default database changed between events. To

illustrate how this could cause problems, suppose that a user

issued the following sequence of statements:

CREATE DATABASE mydb;

USE mydb;

CREATE TABLE mytable (column_definitions);

DROP DATABASE mydb;

CREATE DATABASE mydb;

USE mydb;

CREATE TABLE mytable (column_definitions);

When played back using mysqlbinlog, the second CREATE TABLE

statement failed with Error: No Database Selected because the

second USE statement was not played back, due to the fact that

a database other than mydb was never selected.

This fix insures that mysqlbinlog outputs a USE statement

whenever it reads one from the binary log.

(Bug#50914: http://bugs.mysql.com/bug.php?id=50914)

* Replication: Previously, when a statement failed with a

different error on the slave than on the master, the slave SQL

thread displayed a message containing:

+ The error message for the master error code

+ The master error code

+ The error message for the slaves error code

+ The slave error code

However, the slave has no information with which to fill in

any print format specifiers for the master message, so it

actually displayed the message format string. To make it

clearer that the slave is not displaying the actual message as

it appears on the master, the slave now indicates that the

master part of the output is the message format, not the

actual message. For example, previously the slave displayed

information like this:

Error: “Query caused different errors on master and slave.

Error on master: ‘Duplicate entry ‘%-.192s’ for key %d’

(1062), Error on slave: ‘no error’ (0). Default database:

‘test’. Query: ‘insert into t1 values(1),(2)’” (expected

different error codes on master and slave)

Now the slave displays this:

Error: “Query caused different errors on master and slave.

Error on master: message format=’Duplicate entry ‘%-.192s’ for

key %d’ error code=1062 ; Error on slave: actual message=’no

error’, error code=0. Default database: ‘test’. Query: ‘insert

into t1 values(1),(2)’” (expected different error codes on

master and slave)

(Bug#46697: http://bugs.mysql.com/bug.php?id=46697)

* Replication: When an error occurred in the generation of the

name for a new binary log file, the error was logged but not

shown to the user.

(Bug#46166: http://bugs.mysql.com/bug.php?id=46166)

See also Bug#37148: http://bugs.mysql.com/bug.php?id=37148,

Bug#40611: http://bugs.mysql.com/bug.php?id=40611,

Bug#43929: http://bugs.mysql.com/bug.php?id=43929,

Bug#51019: http://bugs.mysql.com/bug.php?id=51019.

* Comparisons of aggregate values with TIMESTAMP values were

incorrect. (Bug#59330: http://bugs.mysql.com/bug.php?id=59330)

* For DIV expressions, assignment of the result to multiple

variables could cause a server crash.

(Bug#59241: http://bugs.mysql.com/bug.php?id=59241)

See also Bug#8457: http://bugs.mysql.com/bug.php?id=8457.

* MIN(year_col) could return an incorrect result in some cases.

(Bug#59211: http://bugs.mysql.com/bug.php?id=59211)

* mysqlslap failed to check for a NULL return from

mysql_store_result() and crashed trying to process the result

set. (Bug#59109: http://bugs.mysql.com/bug.php?id=59109)

* In a subquery, a UNION with no referenced tables (or only a

reference to the virtual table dual) did not allow an ORDER BY

clause. (Bug#58970: http://bugs.mysql.com/bug.php?id=58970)

* Configuring MySQL with -DWITHOUT_PERFSCHEMA_STORAGE_ENGINE=1

caused build failures.

(Bug#58953: http://bugs.mysql.com/bug.php?id=58953)

* Several Valgrind warnings were fixed.

(Bug#58948: http://bugs.mysql.com/bug.php?id=58948,

Bug#59021: http://bugs.mysql.com/bug.php?id=59021)

* OPTIMIZE TABLE for an InnoDB table could raise an assertion if

the operation failed because it had been killed.

(Bug#58933: http://bugs.mysql.com/bug.php?id=58933)

* If max_allowed_packet was set larger than 16MB, the server

failed to reject too-large packets with “Packet too large”

errors. (Bug#58887: http://bugs.mysql.com/bug.php?id=58887)

* A NOT IN predicate with a subquery containing a HAVING clause

could retrieve too many rows, when the subquery itself

returned NULL.

(Bug#58818: http://bugs.mysql.com/bug.php?id=58818)

* EXPLAIN could crash for queries that accessed two derived

tables. (Bug#58730: http://bugs.mysql.com/bug.php?id=58730)

* On Solaris, the MySQL build failed if it was configured with

debugging enabled.

(Bug#58699: http://bugs.mysql.com/bug.php?id=58699)

* Issuing EXPLAIN EXTENDED for a query that would use condition

pushdown could cause mysqld to crash.

(Bug#58553: http://bugs.mysql.com/bug.php?id=58553)

* An assertion could be raised for queries for which the

optimizer could choose between Index Merge range access or

const ref access methods.

(Bug#58456: http://bugs.mysql.com/bug.php?id=58456)

* If MySQL was built with Visual Studio Express, the project

wixca was not built.

(Bug#58411: http://bugs.mysql.com/bug.php?id=58411)

* EXPLAIN could crash for queries that used GROUP_CONCAT().

(Bug#58396: http://bugs.mysql.com/bug.php?id=58396)

* CMake polluted the source tree by writing installation-related

temporary files there.

(Bug#58372: http://bugs.mysql.com/bug.php?id=58372)

* Security context references in sp_head.cc were rewritten for

improved DTrace compatibility.

(Bug#58350: http://bugs.mysql.com/bug.php?id=58350)

* The ucs2 character set does not support characters outside the

Basic Multilingual Plane (BMP), but converting a string

containing such characters did not produce a

conversion-failure warning.

(Bug#58321: http://bugs.mysql.com/bug.php?id=58321)

* A Valgrind failure occurred in fn_format when called from

archive_discover.

(Bug#58205: http://bugs.mysql.com/bug.php?id=58205)

* CMake did not add LINK_LIBRARIES for MYSQL_ADD_PLUGIN for

libmysqld. (Bug#58158: http://bugs.mysql.com/bug.php?id=58158)

* An assertion could be raised if the server was closing a

session at the same time the session was being killed by

another thread.

(Bug#58136: http://bugs.mysql.com/bug.php?id=58136)

* Condition pushdown optimization could push down conditions

with incorrect column references.

(Bug#58134: http://bugs.mysql.com/bug.php?id=58134)

* Configuration with maintainer mode enabled resulted in errors

when compiling with icc.

(Bug#57991: http://bugs.mysql.com/bug.php?id=57991,

Bug#58871: http://bugs.mysql.com/bug.php?id=58871)

* An ORDER BY clause was bound to the incorrect substatement

when used in UNION context.

(Bug#57986: http://bugs.mysql.com/bug.php?id=57986)

* The BIT_AND() function could return incorrect results when a

join returned no matching rows.

(Bug#57954: http://bugs.mysql.com/bug.php?id=57954)

* If the set of values aggregated with AVG(DISTINCT) contained a

NULL value, the function result could be incorrect.

(Bug#57932: http://bugs.mysql.com/bug.php?id=57932)

* In rare cases, LIKE expressions failed for an indexed column

that used a collation containing contractions.

(Bug#57737: http://bugs.mysql.com/bug.php?id=57737)

* Unnecessary subquery evaluation in contexts such as statement

preparation or view creation could cause a server crash.

(Bug#57703: http://bugs.mysql.com/bug.php?id=57703)

* View creation could produce Valgrind warnings.

(Bug#57352: http://bugs.mysql.com/bug.php?id=57352)

* NULL geometry values could cause a crash in

Item_func_spatial_collection::fix_length_and_dec.

(Bug#57321: http://bugs.mysql.com/bug.php?id=57321)

* It was possible to compile mysqld with Performance Schema

support but with a dummy atomic-operations implementation,

which caused a server crash. This problem does not affect

binary distributions. It is helpful as a safety measure for

users who build MySQL from source.

(Bug#56769: http://bugs.mysql.com/bug.php?id=56769)

* The cp1251 character set did not properly support the Euro

sign (0×88). For example, converting a string containing this

character to utf8 resulted in ‘?’ rather than the utf8 Euro

sign. (Bug#56639: http://bugs.mysql.com/bug.php?id=56639)

* Some unsigned system variables could be displayed with

negative values.

(Bug#55794: http://bugs.mysql.com/bug.php?id=55794)

* CREATE DATABASE and DROP DATABASE caused mysql –one-database

to lose track of the statement-filtering context.

(Bug#54899: http://bugs.mysql.com/bug.php?id=54899)

* An assertion could be raised during concurrent execution of

DROP DATABASE and REPAIR TABLE if the drop deleted a table’s

.TMD file at the same time the repair tried to read details

from the old file that was just removed.

A problem could also occur when DROP TABLE tried to remove all

files belonging to a table at the same time REPAIR TABLE had

just deleted the table’s .TMD file.

(Bug#54486: http://bugs.mysql.com/bug.php?id=54486)

* After compilation from source, all header files were installed

in the same directory, even those that should be installed

into subdirectories of the installation include directory.

(Bug#51925: http://bugs.mysql.com/bug.php?id=51925)

* When mysqld printed crash dump information, it incorrectly

indicated that some valid pointers were invalid.

(Bug#51817: http://bugs.mysql.com/bug.php?id=51817)

* On Mac OS X, a configuration error caused the preference pane

to fail. (Bug#51264: http://bugs.mysql.com/bug.php?id=51264)

* On FreeBSD, if mysqld was killed with a SIGHUP signal, it

could corrupt InnoDB .ibd files.

(Bug#51023: http://bugs.mysql.com/bug.php?id=51023)

* An assertion could be raised if -1 was inserted into an

AUTO_INCREMENT column by a statement writing more than one

row. (Bug#50619: http://bugs.mysql.com/bug.php?id=50619)

* If a client supplied a user name longer than the maximum 16

characters allowed for names stored in the MySQL grant tables,

all characters were being considered significant.

Historically, only the first 16 characters were used to check

for a match; this behavior was restored.

(Bug#49752: http://bugs.mysql.com/bug.php?id=49752)

* The my_seek() and my_tell() functions ignored the MY_WME flag

when they returned an error, which could cause client programs

to hang. (Bug#48451: http://bugs.mysql.com/bug.php?id=48451)

* During assignment of values to system variables, legality

checks on the value range occurred too late, preventing proper

error checking.

(Bug#43233: http://bugs.mysql.com/bug.php?id=43233)

* On Solaris, time-related functions such as NOW() or SYSDATE()

could return a constant value.

(Bug#42054: http://bugs.mysql.com/bug.php?id=42054)

* If the remote server for a FEDERATED table could not be

accessed, queries for the INFORMATION_SCHEMA.TABLES table

failed. (Bug#35333: http://bugs.mysql.com/bug.php?id=35333)