Table of Contents
This appendix lists the changes from version to version in the MySQL source code through the latest version of MySQL 5.0, which is currently MySQL 5.0.85. Starting with MySQL 5.0, we began offering a new version of the Manual for each new series of MySQL releases (5.0, 5.1, and so on). For information about changes in previous release series of the MySQL database software, see the corresponding version of this Manual. For information about legacy versions of the MySQL software through the 4.1 series, see MySQL 3.23, 4.0, 4.1 Reference Manual.
We update this section as we add new features in the 5.0 series, so that everybody can follow the development process.
This section documents all enhancements, changes, and bug fixes made to MySQL Enterprise Server and MySQL Community Server.
Releases in MySQL Enterprise Server are divided into the following release packs:
Rapid Update Service Packs are issued once a month and incorporate all the bug fixes and security updates introduced since the previous MySQL Enterprise Server release. A single Service Pack can be used to update MySQL Enterprise Server; it is not necessary to install intervening service packs to bring your system up to date.
Quarterly Service Packs are issued each quarter and incorporate all the bug fixes and security updates introduced up to the Rapid Update that the QSP it is based on, and possibly some critical bug fixes and security updates from later releases. A single Service Pack can be used to update MySQL Enterprise Server; it is not necessary to install intervening service packs to bring your system up to date.
Hot-fix releases incorporate fixes for bugs that caused significant issues that are not released as part of a Service Pack.
Note that we tend to update the manual at the same time we make changes to MySQL. If you find a recent version of MySQL listed here that you can't find on our download page (http://dev.mysql.com/downloads/), it means that the version has not yet been released (and will normally be marked so in the appropriate Release Note section).
The date mentioned with a release version is the date of the last Bazaar commit on which the release was based, not the date when the packages were made available. The binaries are usually made available a few days after the date of the tagged ChangeSet, because building and testing all packages takes some time.
For information on how to determine your current version and release type, see Section 2.2, “Determining your current MySQL version”.
The manual included in the source and binary distributions may not be fully accurate when it comes to the release changelog entries, because the integration of the manual happens at build time. For the most up-to-date release changelog, please refer to the online version instead.
The following list summarizes what has been done in the 5.0 tree. For a full list of changes, please refer to the changelog sections for each individual 5.0 release.
VARCHAR and
VARBINARY columns retain trailing
spaces. A VARCHAR() or
VARBINARY column can contain up
to 65,535 characters or bytes, respectively.
Strict SQL mode, which causes an error instead of a warning when inserting an incorrect value into a column. See Section 5.1.7, “Server SQL Modes”.
A new fixed-point math library supports precision math,
resulting in more accurate results when working with the
DECIMAL and
NUMERIC data types. For details,
see Section 11.13, “Precision Math”.
Basic support for views. See Section 18.4, “Using Views”.
Basic support for stored procedures and functions (SQL:2003 style). See Section 18.2, “Using Stored Routines (Procedures and Functions)”.
Basic support for triggers. See Section 18.3, “Using Triggers”.
Basic support for read-only server side cursors. For information
about using cursors within stored routines, see
Section 12.8.5, “Cursors”. For information about using cursors
from within the C API, see
Section 20.9.7.3, “mysql_stmt_attr_set()”.
Support for SELECT INTO
, where the
variables can be a mix of global and local types. See
Section 12.8.3.3, “list_of_varsSELECT ... INTO Statement”.
MEMORY (HEAP) tables can
have VARCHAR columns.
When using a constant string or a function that generates a
string result in CREATE ... SELECT, MySQL
creates the result column based on the maximum length of the
string or expression:
| Maximum Length | Data type |
| = 0 | CHAR(0) |
| < 512 | VARCHAR( |
| >= 512 | TEXT |
Removed the update log. It is fully replaced by the binary log.
If the MySQL server is started with
--log-update, it is translated to
--log-bin (or ignored if the
server is explicitly started with
--log-bin), and a warning message
is written to the error log. Setting
sql_log_update silently sets
sql_log_bin instead (or do
nothing if the server is explicitly started with
--log-bin).
Removed support for the ISAM storage engine.
If you have ISAM tables, you should convert
them before upgrading. See
Section 2.18.1.2, “Upgrading from MySQL 4.1 to 5.0”.
Removed support for RAID options in
MyISAM tables. If you have tables that use
these options, you should convert them before upgrading. See
Section 2.18.1.2, “Upgrading from MySQL 4.1 to 5.0”.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server and MySQL Community Server release (5.0.84). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Bugs fixed:
The server crashed if evaluation of
GROUP_CONCAT(... ORDER BY)
required allocation of a sort buffer but allocation failed.
(Bug#46080)
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server and MySQL Community Server release (5.0.83). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Bugs fixed:
Performance:
The InnoDB adaptive hash latch is released
(if held) for serveral 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: Replication:
BEGIN,
COMMIT, and
ROLLBACK
statements are no longer affected by
--replicate-do-db or
--replicate-ignore-db rules.
(Bug#43263)
Replication: When reading a binary log that was in use by a master or that had not been properly closed (possibly due to a crash), the following message was printed: Warning: this binlog was not closed properly. Most probably mysqld crashed writing it. This message did not take into account the possibility that the file was merely in use by the master, which caused some users concern who were not aware that this could happen.
To make this clear, the original message has been replaced with Warning: this binlog is either is use or was not closed properly. (Bug#34687)
The server crashed for attempts to use
REPLACE or
INSERT ... ON DUPLICATE
KEY UPDATE with a view defined using a join.
(Bug#45806)
The combination of MIN() or
MAX() in the select list with
WHERE and GROUP BY clauses
could lead to incorrect results.
(Bug#45386)
The mysql client could misinterpret some character sequences as commands under some circumstances. (Bug#45236)
Use of ROUND() on a
LONGTEXT or
LONGBLOB column of a derived
table could cause a server crash.
(Bug#45152)
Index Merge followed by a filesort could result in a server
crash if sort_buffer_size was
not large enough for all sort keys.
(Bug#44810)
The PASSWORD() and
OLD_PASSWORD() functions could
read memory outside of an internal buffer when used with
BLOB arguments.
(Bug#44767)
A workaround for a Sun Studio bug was instituted. (Bug#41710)
Shared-memory connections did not work in Vista if mysqld was started from the command line. (Bug#41190)
Valgrind warnings that occurred for SHOW
TABLE STATUS with InnoDB tables
were silenced.
(Bug#38479)
In the mysql client, using a default
character set of binary caused internal
commands such as DELIMITER to become case
sensitive.
(Bug#37268)
When invoked to start multiple server instances, mysqld_multi sometimes would fail to start them all due to not changing location into the base directory for each instance. (Bug#36654)
On Windows, the _PC macro in
my_global.h was causing problems for modern
compilers. It has been removed because it is no longer used.
(Bug#34309)
Setting the session value of the
max_allowed_packet or
net_buffer_length system
variable was allowed but had no effect. The session value of
these variables is now read only.
(Bug#32223)
See also Bug#22891.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server and MySQL Community Server release (5.0.82). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Functionality added or changed:
The time zone tables for Windows available at http://dev.mysql.com/downloads/timezones.html have been updated. (Bug#39923)
Bugs fixed:
Replication:
When stopping and restarting the slave while it was replicating
temporary tables, the slave server could crash or raise an
assertion failure. This was due to the fact that, although
temporary tables were saved between slave thread restarts, the
reference to the thread being used
(table->in_use) was not being properly
updated when restarting, continuing to reference the old thread
instead of the new one. This issue affected statement-based
replication only.
(Bug#41725)
UNCOMPRESSED_LENGTH() returned a
garbage result when passed a string shorter than 5 bytes. Now
UNCOMPRESSED_LENGTH() returns
NULL and generates a warning.
(Bug#44796)
Several Valgrind warnings were silenced. (Bug#44774, Bug#44792)
Incorrect time was reported at the end of mysqldump output. (Bug#44424)
EXPLAIN
EXTENDED could crash for
UNION queries in which the last
SELECT was not parenthesized and
included an ORDER BY clause.
(Bug#43612)
SELECT ... INTO
@var could produce values different from
SELECT ...
without the INTO clause.
(Bug#42009)
Using --hexdump together
with
--read-from-remote-server
caused mysqlbinlog to crash.
(Bug#41943)
A crash occurred due to a race condition between the merge table
and table_cache evictions.
00000001403C452F mysqld.exe!memcpy()[memcpy.asm:151] 00000001402A275F mysqld.exe!ha_myisammrg::info()[ha_myisammrg.cc:854] 00000001402A2471 mysqld.exe!ha_myisammrg::attach_children()[ha_myisammrg.cc:488] 00000001402A2788 mysqld.exe!ha_myisammrg::extra()[ha_myisammrg.cc:863] 000000014015FC5D mysqld.exe!attach_merge_children()[sql_base.cc:4135] 000000014016A4C1 mysqld.exe!open_tables()[sql_base.cc:4697] 000000014016A898 mysqld.exe!open_and_lock_tables_derived()[sql_base.cc:4956] 000000014018BB54 mysqld.exe!mysql_insert()[sql_insert.cc:613] 000000014019EDD3 mysqld.exe!mysql_execute_command()[sql_parse.cc:3066] 00000001401A2F06 mysqld.exe!mysql_parse()[sql_parse.cc:5791] 00000001401A3C1A mysqld.exe!dispatch_command()[sql_parse.cc:1202] 00000001401A4CD7 mysqld.exe!do_command()[sql_parse.cc:857] 0000000140246327 mysqld.exe!handle_one_connection()[sql_connect.cc:1115] 00000001402B82C5 mysqld.exe!pthread_start()[my_winthread.c:85] 00000001403CAC37 mysqld.exe!_callthreadstart()[thread.c:295] 00000001403CAD05 mysqld.exe!_threadstart()[thread.c:275] 0000000077D6B69A kernel32.dll!BaseThreadStart() Trying to get some variables. Some pointers may be invalid and cause the dump to abort...
For some queries, an equality propagation problem could cause
a = b and b = a to be
handled differently.
(Bug#40925)
For views created with a column list clause, column aliases were
not substituted when selecting through the view using a
HAVING clause.
(Bug#40825)
A multiple-table DELETE involving
a table self-join could cause a server crash.
(Bug#39918)
Creating an InnoDB table with a comment
containing a '#' character caused foreign key
constraints to be omitted.
(Bug#39793)
The mysql option
--ignore-spaces was nonfunctional.
(Bug#39101)
If a query was such as to produce the error 1054
Unknown column '...' in 'field list', using
EXPLAIN
EXTENDED with the query could cause a server crash.
(Bug#37362)
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server and MySQL Community Server release (5.0.80). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Bugs fixed:
Replication:
Restarting the replication slave — either by using
STOP SLAVE plus
START SLAVE, or by restarting the
slave mysqld process — could sometimes
cause the slave to crash when using a debug version of the
server.
(Bug#38694)
Replication: Killing the thread executing a DDL statement, after it had finished its execution but before it had written the binlog event, caused the error code in the binlog event to be set (incorrectly) to ER_SERVER_SHUTDOWN or ER_QUERY_INTERRUPTED, which caused replication to fail. (Bug#37145)
Replication: Column aliases used inside subqueries were ignored in the binary log. (Bug#35515)
Replication:
The statements
DROP PROCEDURE
IF EXISTS and
DROP FUNCTION IF
EXISTS were not written to the binary log if the
procedure or function to be dropped did not exist.
(Bug#13684)
See also Bug#25705.
Use of HANDLER statements with
INFORMATION_SCHEMA tables caused a server
crash. Now HANDLER is prohibited
with such tables.
(Bug#44151)
myisamchk could display a negative
Max keyfile length value.
(Bug#43950)
mysqld_multi incorrectly passed
--no-defaults to
mysqld_safe.
(Bug#43876)
On Windows, a server crash occurred for attempts to insert a
floating-point value into a CHAR
column with a maximum length less than the converted
floating-point value length.
(Bug#43833)
InnoDB uses random numbers to
generate dives into indexes for calculating index cardinality.
However, under certain conditions, the algorithm did not
generate random numbers, so ANALYZE
TABLE did not update cardinality estimates properly. A
new algorithm has been introduced with better randomization
properties, together with a system variable,
innodb_use_legacy_cardinality_algorithm,
that controls which algorithm to use. The default value of the
variable is 1 (ON), to use the original
algorithm for compatibility with existing applications. The
variable can be set to 0 (OFF) to use the new
algorithm with improved randomness.
(Bug#43660)
UNION of floating-point numbers
did unnecessary rounding.
(Bug#43432)
Certain statements might open a table and then wait for an
impending global read lock without noticing whether they hold a
table being waiting for by the global read lock, causing a hang.
Affected statements are
SELECT ... FOR
UPDATE,
LOCK TABLES ...
WRITE,
TRUNCATE
TABLE, and
LOAD DATA
INFILE.
(Bug#43230)
The InnoDB
btr_search_drop_page_hash_when_freed()
function had a race condition.
(Bug#42279)
Compressing a table with the myisampack utility caused the server to produce Valgrind warnings when it opened the table. (Bug#41541)
For a MyISAM table with
DELAY_KEY_WRITE enabled, the index file could
be corrupted without the table being marked as crashed if the
server was killed.
(Bug#41330)
Multiple-table UPDATE statements
did not properly activate triggers.
(Bug#39953)
The functions listed in Section 11.12.4.2.3, “Creating Geometry Values Using MySQL-Specific Functions”, previously accepted WKB arguments and returned WKB values. They now accept WKB or geometry arguments and return geometry values.
The functions listed in Section 11.12.4.2.2, “Creating Geometry Values Using WKB Functions”, previously accepted WKB arguments and returned geometry values. They now accept WKB or geometry arguments and return geometry values. (Bug#38990)
An UPDATE statement that updated
a column using the same
DES_ENCRYPT() value for each row
actually updated different rows with different values.
(Bug#35087)
For shared-memory connections, the read and write methods did
not properly handle asynchronous close events, which could lead
to the client locking up waiting for a server response. For
example, a call to
mysql_real_query() would block
forever on the client side if the executed statement was aborted
on the server side. Thanks to Armin Schöffmann for the bug
report and patch.
(Bug#33899)
CHECKSUM TABLE was not killable
with KILL QUERY.
(Bug#33146)
myisamchk and myisampack
were not being linked with the library that enabled support for
* filename pattern expansion.
(Bug#29248)
COMMIT did not delete savepoints
if there were no changes in the transaction.
(Bug#26288)
Several memory allocation functions were not being checked for out-of-memory return values. (Bug#25058)
This is a bugfix release for the current MySQL Community Server production release family. It replaces MySQL 5.0.77.
Functionality added or changed:
Security Enhancement:
To enable stricter control over the location from which
user-defined functions can be loaded, the
plugin_dir system variable has
been backported from MySQL 5.1. If the value is nonempty,
user-defined function object files can be loaded only from the
directory named by this variable. If the value is empty, the
behavior that is used prior to the inclusion of
plugin_dir applies: The UDF
object files must be located in a directory that is searched by
your system's dynamic linker.
(Bug#37428)
A new status variable,
Queries, indicates the number
of statements executed by the server. This includes statements
executed within stored programs, unlike the
Questions variable which
includes only statements sent to the server by clients.
(Bug#41131)
Previously, index hints did not work for
FULLTEXT searches. Now they work as follows:
For natural language mode searches, index hints are silently
ignored. For example, IGNORE INDEX(i) is
ignored with no warning and the index is still used.
For boolean mode searches, index hints are honored. (Bug#38842)
Bugs fixed:
Important Change: Security Fix: Additional corrections were made for the symlink-related privilege problem originally addressed in MySQL 5.0.60. The original fix did not correctly handle the data directory path name if it contained symlinked directories in its path, and the check was made only at table-creation time, not at table-opening time later. (Bug#32167, CVE-2008-2079)
See also Bug#39277.
Security Enhancement:
The server consumed excess memory while parsing statements with
hundreds or thousands of nested boolean conditions (such as
OR (OR ... (OR ... ))). This could lead to a
server crash or incorrect statement execution, or cause other
client statements to fail due to lack of memory. The latter
result constitutes a denial of service.
(Bug#38296)
Incompatible Change:
There were some problems using DllMain()
hook functions on Windows that automatically do global and
per-thread initialization for
libmysqld.dll:
Per-thread initialization: MySQL internally counts the
number of active threads, which causes a delay in
my_end() if not all threads have
exited. But there are threads that can be started either by
Windows internally (often in TCP/IP scenarios) or by users.
Those threads do not necessarily use
libmysql.dll functionality but still
contribute to the open-thread count. (One symptom is a
five-second delay in times for PHP scripts to finish.)
Process-initialization:
my_init() calls
WSAStartup that itself loads DLLs and
can lead to a deadlock in the Windows loader.
To correct these problems, DLL initialization code now is not
invoked from libmysql.dll by default. To
obtain the previous behavior (DLL initialization code will be
called), set the LIBMYSQL_DLLINIT environment
variable to any value. This variable exists only to prevent
breakage of existing Windows-only applications that do not call
mysql_thread_init() and work
okay today. Use of LIBMYSQL_DLLINIT is
discouraged and is removed in MySQL 6.0.
(Bug#37226, Bug#33031)
Incompatible Change:
SHOW STATUS took a lot of CPU
time for calculating the value of the
Innodb_buffer_pool_pages_latched
status variable. Now this variable is calculated and included in
the output of SHOW STATUS only if
the UNIV_DEBUG symbol is defined at MySQL
build time.
(Bug#36600)
Incompatible Change:
In connection with view creation, the server created
arc directories inside database directories
and maintained useless copies of .frm files
there. Creation and renaming procedures of those copies as well
as creation of arc directories has been
discontinued.
This change does cause a problem when downgrading to older server versions which manifests itself under these circumstances:
Create a view v_orig in MySQL 5.0.72 or
higher.
Rename the view to v_new and then back to
v_orig.
Downgrade to an older 5.0.x server and run mysql_upgrade.
Try to rename v_orig to
v_new again. This operation fails.
As a workaround to avoid this problem, use either of these approaches:
Dump your data using mysqldump before downgrading and reload the dump file after downgrading.
Instead of renaming a view after the downgrade, drop it and recreate it.
The downgrade problem introduced by the fix for this bug has been addressed as Bug#40021. (Bug#17823)
Replication: When rotating relay log files, the slave deletes relay log files and then edits the relay log index file. Formerly, if the slave shut down unexpectedly between these two events, the relay log index file could then reference relay logs that no longer existed. Depending on the circumstances, this could when restarting the slave cause either a race condition or the failure of replication. (Bug#38826, Bug#39325)
In example option files provided in MySQL distributions, the
thread_stack value was
increased from 64K to 128K.
(Bug#41577)
SET PASSWORD caused a server
crash if the account name was given as
CURRENT_USER().
(Bug#41456)
The
INFORMATION_SCHEMA.SCHEMA_PRIVILEGES
table was limited to 7680 rows.
(Bug#41079)
In debug builds, obsolete debug code could be used to crash the server. (Bug#41041)
CHECK TABLE ... FOR
UPGRADE did not check for incompatible collation
changes made in MySQL 5.0.48 (Bug#27562, Bug#29461, Bug#29499).
This also affects mysqlcheck and
mysql_upgrade, which cause that statement to
be executed. See Section 2.18.3, “Checking Whether Table Indexes Must Be Rebuilt”.
(Bug#40984)
See also Bug#39585.
Some queries that used a “range checked for each record” scan could return incorrect results. (Bug#40974)
Certain SELECT queries could fail
with a Duplicate entry error.
(Bug#40953)
The FEDERATED handler had a memory
leak.
(Bug#40875)
IF(..., CAST( as
an argument to an aggregate function could cause an assertion
failure.
(Bug#40761)longtext_val AS
UNSIGNED), signed_val)
Prepared statements allowed invalid dates to be inserted when
the ALLOW_INVALID_DATES SQL
mode was not enabled.
(Bug#40365)
mc.exe is no longer needed to compile MySQL on Windows. This makes it possible to build MySQL from source using Visual Studio Express 2008. (Bug#40280)
Support for the revision field in
.frm files has been removed. This addresses
the downgrading problem introduced by the fix for Bug#17823.
(Bug#40021)
If the operating system is configured to return leap seconds
from OS time calls or if the MySQL server uses a time zone
definition that has leap seconds, functions such as
NOW() could return a value having
a time part that ends with :59:60 or
:59:61. If such values are inserted into a
table, they would be dumped as is by
mysqldump but considered invalid when
reloaded, leading to backup/restore problems.
Now leap second values are returned with a time part that ends
with :59:59. This means that a function such
as NOW() can return the same
value for two or three consecutive seconds during the leap
second. It remains true that literal temporal values having a
time part that ends with :59:60 or
:59:61 are considered invalid.
For additional details about leap-second handling, see Section 9.7.2, “Time Zone Leap Second Support”. (Bug#39920)
The server could crash during a sort-order optimization of a dependent subquery. (Bug#39844)
With the ONLY_FULL_GROUP_BY
SQL mode enabled, the check for nonaggregated columns in queries
with aggregate functions, but without a GROUP
BY clause was treating all the parts of the query as
if they were in the select list. This is fixed by ignoring the
nonaggregated columns in the WHERE clause.
(Bug#39656)
The server crashed if an integer field in a CSV file did not have delimiting quotes. (Bug#39616)
Creating a table with a comment of 62 characters or longer caused a server crash. (Bug#39591)
CHECK TABLE failed for
MyISAM
INFORMATION_SCHEMA tables.
(Bug#39541)
InnoDB could hang trying to open an adaptive
hash index.
(Bug#39483)
For a TIMESTAMP column in an
InnoDB table, testing the column with
multiple conditions in the WHERE clause
caused a server crash.
(Bug#39353)
The server returned a column type of
VARBINARY rather than
DATE as the result from the
COALESCE(),
IFNULL(),
IF(),
GREATEST(), or
LEAST() functions or
CASE expression if the result was
obtained using filesort in an anonymous
temporary table during the query execution.
(Bug#39283)
References to local variables in stored procedures are replaced
with
NAME_CONST( when written to the
binary log. However, an “illegal mix of collation”
error might occur when executing the log contents if the value's
collation differed from that of the variable. Now information
about the variable collation is written as well.
(Bug#39182)name,
value)
Some recent releases for Solaris 10 were built on Solaris 10 U5,
which included a new version of libnsl.so
that does not work on U4 or earlier. To correct this, Solaris 10
builds now are created on machines that do not have that
upgraded libnsl.so, so that they will work
on Solaris 10 installations both with and without the upgraded
libnsl.so.
(Bug#39074)
With binary logging enabled CREATE
VIEW was subject to possible buffer overwrite and a
server crash.
(Bug#39040)
Queries of the form SELECT ... REGEXP BINARY
NULL could lead to a hung or crashed server.
(Bug#39021)
Statements of the form INSERT ... SELECT .. ON
DUPLICATE KEY UPDATE could result in a server crash.
(Bug#39002)col_name =
DEFAULT
Column names constructed due to wild-card expansion done inside a stored procedure could point to freed memory if the expansion was performed after the first call to the stored procedure. (Bug#38823)
Repeated CREATE
TABLE ... SELECT statements, where the created table
contained an AUTO_INCREMENT column, could
lead to an assertion failure.
(Bug#38821)
If delayed insert failed to upgrade the lock, it did not free
the temporary memory storage used to keep newly constructed
BLOB values in memory, resulting
in a memory leak.
(Bug#38693)
A server crash resulted from concurrent execution of a
multiple-table UPDATE that used a
NATURAL or USING join
together with FLUSH
TABLES WITH READ LOCK or ALTER
TABLE for the table being updated.
(Bug#38691)
On ActiveState Perl, mysql-test-run.pl --start-and-exit started but did not exit. (Bug#38629)
Server-side cursors were not initialized properly, which could cause a server crash. (Bug#38486)
Stored procedures involving substrings could crash the server on certain platforms due to invalid memory reads. (Bug#38469)
A server crash or Valgrind warnings could result when a stored procedure selected from a view that referenced a function. (Bug#38291)
Incorrect handling of aggregate functions when loose index scan was used caused a server crash. (Bug#38195)
Queries containing a subquery with DISTINCT
and ORDER BY could cause a server crash.
(Bug#38191)
Queries with a HAVING clause could return a
spurious row.
(Bug#38072)
Use of spatial data types in prepared statements could cause memory leaks or server crashes. (Bug#37956, Bug#37671)
The server crashed if an argument to a stored procedure was a subquery that returned more than one row. (Bug#37949)
When analyzing the possible index use cases, the server was incorrectly reusing an internal structure, leading to a server crash. (Bug#37943)
A SELECT with a NULL NOT
IN condition containing a complex subquery from the
same table as in the outer select caused an assertion failure.
(Bug#37894)
For InnoDB tables, ORDER BY ...
DESC sometimes returned results in ascending order.
(Bug#37830)
If a table has a BIT NOT NULL column
c1 with a length shorter than 8 bits and some
additional NOT NULL columns
c2, ..., and a
SELECT query has a
WHERE clause of the form (c1 =
, the
query could return an unexpected result set.
(Bug#37799)constant) AND c2 ...
Nesting of IF() inside of
SUM() could cause an extreme
server slowdown.
(Bug#37662)
The MONTHNAME() and
DAYNAME() functions returned a
binary string, so that using
LOWER() or
UPPER() had no effect. Now
MONTHNAME() and
DAYNAME() return a value in
character_set_connection
character set.
(Bug#37575)
TIMEDIFF() was erroneously
treated as always returning a positive result. Also,
CAST() of
TIME values to
DECIMAL dropped the sign of
negative values.
(Bug#37553)
See also Bug#42525.
mysqlcheck used
SHOW FULL
TABLES to get the list of tables in a database. For
some problems, such as an empty .frm file
for a table, this would fail and mysqlcheck
then would neglect to check other tables in the database.
(Bug#37527)
The <=>
operator could return incorrect results when comparing
NULL to DATE,
TIME, or
DATETIME values.
(Bug#37526)
Updating a view with a subquery in the CHECK
option could cause an assertion failure.
(Bug#37460)
Statements that displayed the value of system variables (for
example, SHOW VARIABLES) expect
variable values to be encoded in
character_set_system. However,
variables set from the command line such as
basedir or
datadir were encoded using
character_set_filesystem and
not converted correctly.
(Bug#37339)
For a MyISAM table with CHECKSUM =
1 and ROW_FORMAT = DYNAMIC table
options, a data consistency check (maximum record length) could
fail and cause the table to be marked as corrupted.
(Bug#37310)
The max_length result set metadata value was
calculated incorrectly under some circumstances.
(Bug#37301)
CREATE INDEX could crash with
InnoDB plugin 1.0.1.
(Bug#37284)
Certain boolean-mode FULLTEXT searches that
used the truncation operator did not return matching records and
calculated relevance incorrectly.
(Bug#37245)
The NO_BACKSLASH_ESCAPES SQL
mode was ignored for
LOAD DATA
INFILE and SELECT INTO ... OUTFILE.
The setting is taken into account now.
(Bug#37114)
On a 32-bit server built without big tables support, the offset
argument in a LIMIT clause might be truncated
due to a 64-bit to 32-bit cast.
(Bug#37075)
If the server failed to expire binary log files at startup, it could crash. (Bug#37027)
The code for the ut_usectime() function in
InnoDB did not handle errors from the
gettimeofday() system call. Now it retries
gettimeofday() several times and updates
the value of the
Innodb_row_lock_time_max
status variable only if ut_usectime() was
successful.
(Bug#36819)
Use of CONVERT() with
GROUP BY to convert numeric values to
CHAR could return truncated
results.
(Bug#36772)
A query which had an ORDER BY DESC clause
that is satisfied with a reverse range scan could cause a server
crash for some specific CPU/compiler combinations.
(Bug#36639)
Dumping information about locks in use by sending a
SIGHUP signal to the server or by invoking
the mysqladmin debug command could lead to a
server crash in debug builds or to undefined behavior in
production builds.
(Bug#36579)
The mysql client, when built with Visual Studio 2005, did not display Japanese characters. (Bug#36279)
When the fractional part in a multiplication of
DECIMAL values overflowed, the
server truncated the first operand rather than the longest. Now
the server truncates so as to produce more precise
multiplications.
(Bug#36270)
A read past the end of the string could occur while parsing the
value of the
--innodb-data-file-path option.
(Bug#36149)
Host name values in SQL statements were not being checked for
'@', which is illegal according to RFC952.
(Bug#35924)
The UUID() function returned
UUIDs with the wrong time; this was because the offset for the
time part in UUIDs was miscalculated.
(Bug#35848)
SHOW CREATE TABLE did not display
a printable value for the default value of
BIT columns.
(Bug#35796)
mysql_install_db failed on machines that had
the host name set to localhost.
(Bug#35754)
Dynamic plugins failed to load on i5/OS. (Bug#35743)
Freeing of an internal parser stack during parsing of complex stored programs caused a server crash. (Bug#35577, Bug#37269, Bug#37228)
The max_length metadata value was calculated
incorrectly for the FORMAT()
function, which could cause incorrect result set metadata to be
sent to clients.
(Bug#35558)
Index scans performed with the sort_union()
access method returned wrong results, caused memory to be
leaked, and caused temporary files to be deleted when the limit
set by sort_buffer_size was
reached.
(Bug#35477, Bug#35478)
If the server crashed with an InnoDB error
due to unavailability of undo slots, errors could persist during
rollback when the server was restarted: There are two
UNDO slot caches (for
INSERT and
UPDATE). If all slots end up in
one of the slot caches, a request for a slot from the other slot
cache would fail. This can happen if the request is for an
UPDATE slot and all slots are in
the INSERT slot cache, or vice
versa.
(Bug#35352)
For InnoDB tables, ALTER TABLE
DROP failed if the name of the column to be dropped
began with “foreign”.
(Bug#35220)
perror on Windows did not know about Win32 system error codes. (Bug#34825)
EXPLAIN EXTENDED evaluation of aggregate
functions that required a temporary table caused a server crash.
(Bug#34773)
Queries of the form SELECT ... WHERE
failed
when the server used a single-byte character set and the client
used a multi-byte character set.
(Bug#34760)string = ANY(...)
See also Bug#20835.
Using OPTIMIZE TABLE as the first
statement on an InnoDB table with an
AUTO_INCREMENT column could cause a server
crash.
(Bug#34286)
mysql_install_db failed if the server was
running with an SQL mode of
TRADITIONAL. This program now
resets the SQL mode internally to avoid this problem.
(Bug#34159)
Changes to build files were made to enable the MySQL distribution to compile on Microsoft Visual C++ Express 2008. (Bug#33907)
The mysql client incorrectly parsed statements containing the word “delimiter” in mid-statement.
This fix is different from the one applied for this bug in MySQL 5.0.66. (Bug#33812)
See also Bug#38158.
For a stored procedure containing a SELECT * ... RIGHT
JOIN query, execution failed for the second call.
(Bug#33811)
Previously, use of index hints with views (which do not have indexes) produced the error ERROR 1221 (HY000): Incorrect usage of USE/IGNORE INDEX and VIEW. Now this produces ERROR 1176 (HY000): Key '...' doesn't exist in table '...', the same error as for base tables without an appropriate index. (Bug#33461)
Cached queries that used 256 or more tables were not properly
cached, so that later query invalidation due to a
TRUNCATE
TABLE for one of the tables caused the server to hang.
(Bug#33362)
Some division operations produced a result with incorrect precision. (Bug#31616)
mysql_upgrade attempted to use the
/proc file system even on systems that do
not have it.
(Bug#31605)
mysqldump could fail to dump views containing a large number of columns. (Bug#31434)
Queries executed using join buffering of
BIT columns could produce
incorrect results.
(Bug#31399)
ALTER TABLE CONVERT TO CHARACTER SET did not
convert TINYTEXT or
MEDIUMTEXT columns to a longer
text type if necessary when converting the column to a different
character set.
(Bug#31291)
For installation on Solaris using pkgadd
packages, the mysql_install_db script was
generated in the scripts directory, but the
temporary files used during the process were left there and not
deleted.
(Bug#31052)
Several MySQL programs could fail if the HOME
environment variable had an empty value.
(Bug#30394)
On NetWare, mysql_install_db could appear to execute normally even if it failed to create the initial databases. (Bug#30129)
The Serbian translation for the
ER_INCORRECT_GLOBAL_LOCAL_VAR
error was corrected.
(Bug#29738)
XA transaction rollbacks could result in corrupted transaction states and a server crash. (Bug#28323)
The BUILD/check-cpu build script failed if gcc had a different name (such as gcc.real on Debian). (Bug#27526)
On Windows, Visual Studio does not take into account some x86
hardware limitations, which led to incorrect results converting
large DOUBLE values to unsigned
BIGINT values.
(Bug#27483)
SSL support was not included in some “generic” RPM packages. (Bug#26760)
In some cases, the parser interpreted the ;
character as the end of input and misinterpreted stored program
definitions.
(Bug#26030)
The Questions status variable
is intended as a count of statements sent by clients to the
server, but was also counting statements executed within stored
routines.
(Bug#24289)
For access to the
INFORMATION_SCHEMA.VIEWS table, the
server did not check the SHOW
VIEW and SELECT
privileges, leading to inconsistency between output from that
table and the SHOW CREATE VIEW
statement.
(Bug#22763)
The FLUSH
PRIVILEGES statement did not produce an error when it
failed.
(Bug#21226)
A race condition between the mysqld.exe server and the Windows service manager could lead to inability to stop the server from the service manager. (Bug#20430)
mysqld_safe would sometimes fail to remove
the pid file for the old mysql process after
a crash. As a result, the server would fail to start due to a
false A mysqld process already exists...
error.
(Bug#11122)
This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.79). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Support Ending for AIX 5.2: Per the MySQL Support Lifecycle policy regarding ending support for OS versions that have reached vendor end of life, we plan to discontinue building or supporting MySQL binaries for AIX 5.2 as of April 30, 2009. This release of MySQL 5.0 (5.0.80) is the last MySQL 5.0 release with support for AIX 5.2. For more information, see the March 24, 2009 note at MySQL Product Support EOL Announcements.
Functionality added or changed:
The MD5 algorithm now uses the Xfree implementation. (Bug#42434)
Bugs fixed:
Replication:
An INSERT
DELAYED into a
TIMESTAMP column issued
concurrently with an insert on the same column not using
DELAYED, but applied after the other insert,
was logged using the same timestamp as generated by the other
(non-DELAYED) insert.
(Bug#41719)
An attempt by a user who did not have the
SUPER privilege to kill a system
thread could cause a server crash.
(Bug#43748)
Use of USE INDEX hints could cause
EXPLAIN
EXTENDED to crash.
(Bug#43354)
mysql crashed if a request for the current
database name returned an empty result, such as after the client
has executed a preceding SET
sql_select_limit=0 statement.
(Bug#43254)
The strings/CHARSET_INFO.txt file was not
included in source distributions.
(Bug#42937)
mysqldump included views that were excluded
with the --ignore-table
option.
(Bug#42635)
Passing an unknown time zone specification to
CONVERT_TZ() resulted in a memory
leak.
(Bug#42502)
With more than two arguments,
LEAST(),
GREATEST(), and
CASE could unnecessarily return
Illegal mix of collations errors.
(Bug#41627)
The mysql client could misinterpret its input if a line was longer than an internal buffer. (Bug#41486)
In the help command output displayed by
mysql, the description for the
\c (clear) command was
misleading.
(Bug#41268)
The use of NAME_CONST() can
result in a problem for
CREATE TABLE ...
SELECT statements when the source column expressions
refer to local variables. Converting these references to
NAME_CONST() expressions can
result in column names that are different on the master and
slave servers, or names that are too long to be legal column
identifiers. A workaround is to supply aliases for columns that
refer to local variables.
Now a warning is issued in such cases that indicate possible problems. (Bug#35383)
CHECK TABLE,
REPAIR TABLE,
ANALYZE TABLE, and
OPTIMIZE TABLE erroneously
reported a table to be corrupt if the table did not exist or the
statement was terminated with
KILL.
(Bug#29458)
The Time column for SHOW
PROCESSLIST output now can have negative values.
Previously, the column was unsigned and negative values were
displayed incorrectly as large positive values. Negative values
can occur if a thread alters the time into the future with
SET TIMESTAMP =
or the thread is
executing on a slave and processing events from a master that
has its clock set ahead of the slave.
(Bug#22047)value
Restoring a mysqldump dump file containing
FEDERATED tables failed because the file
contained the data for the table. Now only the table definition
is dumped (because the data is located elsewhere).
(Bug#21360)
This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.78). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Functionality added or changed:
The libedit library was upgraded to version
2.11.
(Bug#42433)
The query cache now checks whether a
SELECT statement begins with
SQL_NO_CACHE to determine whether it can skip
checking for the query result in the query cache. This is not
supported when SQL_NO_CACHE occurs within a
comment.
(Bug#37416)
Bugs fixed:
Replication: Server IDs greater than 2147483647 (232 – 1) were represented by negative numbers in the binary log. (Bug#37313)
Replication:
The
--replicate-
options were not evaluated correctly when replicating
multi-table updates.
*-table
As a result of this fix, replication of multi-table updates no longer fails when an update references a missing table but does not update any of its columns. (Bug#37051)
Replication:
When its disk becomes full, a replication slave may wait while
writing the binary log, relay log or
MyISAM tables, continuing after
space has been made available. The error message provided in
such cases was not clear about the frequency with which checking
for free space is done (once every 60 seconds), and how long the
server waits after space has been freed before continuing (also
60 seconds); this caused users to think that the server had
hung.
These issues have been addressed by making the error message clearer, and dividing it into two separate messages:
The error message Disk is full writing
'filename' (Errcode:
error_code). Waiting for someone
to free space... (Expect up to 60 secs delay for server to
continue after freeing disk space) is printed
only once.
The warning Retry in 60 secs, Message reprinted in 600 secs is printed once every for every 10 times that the check for free space is made; that is, the check is performed once each 60 seconds, but the reminder that space needs to be freed is printed only once every 10 minutes (600 seconds).
On 32-bit Windows, mysqld could not use large buffers due to a 2GB user mode address limit. (Bug#43082)
The use by libedit of the
__weak_reference() macro caused compilation
failure on FreeBSD.
(Bug#42817)
Tables could enter open table cache for a thread without being properly cleaned up, leading to a server crash. (Bug#42419)
mysqldumpslow parsed the
--debug and
--verbose options
incorrectly.
(Bug#42027)
String reallocation could cause memory overruns. (Bug#41868)
Queries that used the loose index scan access method could return no rows. (Bug#41610)
In InnoDB recovery after a server crash,
rollback of a transaction that updated a column from
NULL to NULL could cause
another crash.
(Bug#41571)
If InnoDB reached its limit on the number of
concurrent transactions (1023), it wrote a descriptive message
to the error log but returned a misleading error message to the
client, or an assertion failure occurred.
(Bug#41529)
Use of SELECT * allowed users with rights to
only some columns of a view to access all columns.
(Bug#41354)
The server did not robustly handle problems hang if a table
opened with HANDLER needed to be
re-opened because it had been altered to use a different storage
engine that does not support
HANDLER. The server also failed
to set an error if the re-open attempt failed. These problems
could cause the server to crash or hang.
(Bug#41110, Bug#41112)
For prepared statements, multibyte character sets were not
taking into account when calculating
max_length for string values and
mysql_stmt_fetch() could return
truncated strings.
(Bug#41078)
The mysql_change_user() C API
function changed the value of the
sql_big_selects session
variable.
(Bug#40363)
See also Bug#20023.
For a view that references a table in another database, mysqldump wrote the view name qualified with the current database name. This makes it impossible to reload the dump file into a different database. (Bug#40345)
For an InnoDB table,
DROP TABLE or
ALTER TABLE ...
DISCARD TABLESPACE could take a long time or cause a
server crash.
(Bug#39939)
perror did not produce correct output for error codes 153 to 163. (Bug#39370)
Comparisons between row constructors, such as (a, b) =
(c, d) resulted in unnecessary Illegal mix of
collations errors for string columns.
(Bug#37601)
An argument to the MATCH()
function that was an alias for an expression other than a column
name caused a server crash.
(Bug#36737)
For DROP FUNCTION with names that
were qualified with a database name, the database name was
handled in case-sensitive fashion even with
lower_case_table_names set to
1.
(Bug#33813)
mysqldump --compatible=mysql40 emitted
statements referring to the
character_set_client system
variable, which is unknown before MySQL 4.1. Now the statements
are enclosed in version-specific comments.
(Bug#33550)
Use of MBR spatial functions such as
MBRTouches() with columns of
InnoDB tables caused a server crash rather
than an error.
(Bug#31435)
The mysql client mishandled input parsing if
a delimiter command was not first on the
line.
(Bug#31060)
For installation on Solaris using pkgadd
packages, the mysql_install_db script was
generated in the scripts directory, but the
temporary files used during the process were left there and not
deleted.
(Bug#31052)
SHOW PRIVILEGES listed the
CREATE ROUTINE privilege as
having a context of Functions,Procedures, but
it is a database-level privilege.
(Bug#30305)
SHOW TABLE STATUS could fail to
produce output for tables with non-ASCII characters in their
name.
(Bug#25830)
Floating-point numbers could be handled with different numbers of digits depending on whether the text or prepared-statement protocol was used. (Bug#21205)
Incorrect length metadata could be returned for LONG
TEXT columns when a multibyte server character set was
used.
(Bug#19829)
ROUND() sometimes returned
different results on different platforms.
(Bug#15936)
This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.76). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Bugs fixed:
MySQL Cluster: Packaging:
Packages for MySQL Cluster were missing the
libndbclient.so and
libndbclient.a files.
(Bug#42278)
An optimization introduced for Bug#37553 required an explicit
cast to be added for some uses of
TIMEDIFF() because automatic
casting could produce incorrect results. (It was necessary to
use TIME(TIMEDIFF(...)).)
(Bug#42525)
The SSL certficates included with MySQL distributions were regenerated because the previous ones had expired. (Bug#42366)
Dependent subqueries such as the following caused a memory leak proportional to the number of outer rows:
SELECT COUNT(*) FROM t1, t2 WHERE t2.b IN (SELECT DISTINCT t2.b FROM t2 WHERE t2.b = t1.a);
Some queries using NAME_CONST(.. COLLATE
...) led to a server crash due to a failed type cast.
(Bug#42014)
On Mac OS X, some of the universal client libraries were not actually universal and were missing code for one or more architectures. (Bug#41940)
DATE_FORMAT() could cause a
server crash for year-zero dates.
(Bug#41470)
When substituting system constant functions with a constant
result, the server was not expecting NULL
function return values and could crash.
(Bug#41437)
For a TIMESTAMP NOT
NULL DEFAULT ... column, storing
NULL as the return value from some functions
caused a “cannot be NULL” error.
NULL returns now correctly cause the column
default value to be stored.
(Bug#41370)
The Windows installer displayed incorrect product names in some images. (Bug#40845)
The query cache stored only partial query results if a statement failed while the results were being sent to the client. This could cause other clients to hang when trying to read the cached result. Now if a statement fails, the result is not cached. (Bug#40264)
The expression ROW(...) IN (SELECT ... FROM
DUAL) always returned TRUE.
(Bug#39069)
The greedy optimizer could cause a server crash due to improper handling of nested outer joins. (Bug#38795)
Use of COUNT(DISTINCT) prevented
NULL testing in the HAVING
clause.
(Bug#38637)
Enabling the sync_frm system
variable had no effect on the handling of
.frm files for views.
(Bug#38145)
The query cache stored packets containing the server status of the time when the cached statement was run. This might lead to an incorrect transaction status on the client side if a statement was cached during a transaction and later served outside a transaction context (or vice versa). (Bug#36326)
If the system time was adjusted backward during query execution, the apparent execution time could be negative. But in some cases these queries would be written to the slow query log, with the negative execution time written as a large unsigned number. Now statements with apparent negative execution time are not written to the slow query log. (Bug#35396)
For mysqld_multi, using the
--mysqld=mysqld_safe option
caused the --defaults-file
and --defaults-extra-file
options to behave the same way.
(Bug#32136)
Attempts to open a valid MERGE table sometimes resulted in a
ER_WRONG_MRG_TABLE error. This
happened after failure to open an invalid MERGE table had also
generated an ER_WRONG_MRG_TABLE
error.
(Bug#32047)
The mysql_change_user() C API
function caused global
Com_ status
variable values to be incorrect.
(Bug#31222)xxx
For Solaris package installation using
pkgadd, the postinstall script failed,
causing the system tables in the mysql
database not to be created.
(Bug#31164)
This is a bugfix release for the current MySQL Community Server production release family. It replaces MySQL 5.0.67 (binary) and 5.0.75 (source-only).
Functionality added or changed:
Security Enhancement:
To enable stricter control over the location from which
user-defined functions can be loaded, the
plugin_dir system variable has
been backported from MySQL 5.1. If the value is nonempty,
user-defined function object files can be loaded only from the
directory named by this variable. If the value is empty, the
behavior that is used prior to the inclusion of
plugin_dir applies: The UDF
object files must be located in a directory that is searched by
your system's dynamic linker.
(Bug#37428)
A new status variable,
Queries, indicates the number
of statements executed by the server. This includes statements
executed within stored programs, unlike the
Questions variable which
includes only statements sent to the server by clients.
(Bug#41131)
Previously, index hints did not work for
FULLTEXT searches. Now they work as follows:
For natural language mode searches, index hints are silently
ignored. For example, IGNORE INDEX(i) is
ignored with no warning and the index is still used.
For boolean mode searches, index hints are honored. (Bug#38842)
Bugs fixed:
Important Change: Security Fix: Additional corrections were made for the symlink-related privilege problem originally addressed in MySQL 5.0.60. The original fix did not correctly handle the data directory path name if it contained symlinked directories in its path, and the check was made only at table-creation time, not at table-opening time later. (Bug#32167, CVE-2008-2079)
See also Bug#39277.
Security Enhancement:
The server consumed excess memory while parsing statements with
hundreds or thousands of nested boolean conditions (such as
OR (OR ... (OR ... ))). This could lead to a
server crash or incorrect statement execution, or cause other
client statements to fail due to lack of memory. The latter
result constitutes a denial of service.
(Bug#38296)
Incompatible Change:
There were some problems using DllMain()
hook functions on Windows that automatically do global and
per-thread initialization for
libmysqld.dll:
Per-thread initialization: MySQL internally counts the
number of active threads, which causes a delay in
my_end() if not all threads have
exited. But there are threads that can be started either by
Windows internally (often in TCP/IP scenarios) or by users.
Those threads do not necessarily use
libmysql.dll functionality but still
contribute to the open-thread count. (One symptom is a
five-second delay in times for PHP scripts to finish.)
Process-initialization:
my_init() calls
WSAStartup that itself loads DLLs and
can lead to a deadlock in the Windows loader.
To correct these problems, DLL initialization code now is not
invoked from libmysql.dll by default. To
obtain the previous behavior (DLL initialization code will be
called), set the LIBMYSQL_DLLINIT environment
variable to any value. This variable exists only to prevent
breakage of existing Windows-only applications that do not call
mysql_thread_init() and work
okay today. Use of LIBMYSQL_DLLINIT is
discouraged and is removed in MySQL 6.0.
(Bug#37226, Bug#33031)
Incompatible Change:
SHOW STATUS took a lot of CPU
time for calculating the value of the
Innodb_buffer_pool_pages_latched
status variable. Now this variable is calculated and included in
the output of SHOW STATUS only if
the UNIV_DEBUG symbol is defined at MySQL
build time.
(Bug#36600)
Incompatible Change:
In connection with view creation, the server created
arc directories inside database directories
and maintained useless copies of .frm files
there. Creation and renaming procedures of those copies as well
as creation of arc directories has been
discontinued.
This change does cause a problem when downgrading to older server versions which manifests itself under these circumstances:
Create a view v_orig in MySQL 5.0.72 or
higher.
Rename the view to v_new and then back to
v_orig.
Downgrade to an older 5.0.x server and run mysql_upgrade.
Try to rename v_orig to
v_new again. This operation fails.
As a workaround to avoid this problem, use either of these approaches:
Dump your data using mysqldump before downgrading and reload the dump file after downgrading.
Instead of renaming a view after the downgrade, drop it and recreate it.
The downgrade problem introduced by the fix for this bug has been addressed as Bug#40021. (Bug#17823)
Replication: When rotating relay log files, the slave deletes relay log files and then edits the relay log index file. Formerly, if the slave shut down unexpectedly between these two events, the relay log index file could then reference relay logs that no longer existed. Depending on the circumstances, this could when restarting the slave cause either a race condition or the failure of replication. (Bug#38826, Bug#39325)
In example option files provided in MySQL distributions, the
thread_stack value was
increased from 64K to 128K.
(Bug#41577)
SET PASSWORD caused a server
crash if the account name was given as
CURRENT_USER().
(Bug#41456)
The
INFORMATION_SCHEMA.SCHEMA_PRIVILEGES
table was limited to 7680 rows.
(Bug#41079)
In debug builds, obsolete debug code could be used to crash the server. (Bug#41041)
CHECK TABLE ... FOR
UPGRADE did not check for incompatible collation
changes made in MySQL 5.0.48 (Bug#27562, Bug#29461, Bug#29499).
This also affects mysqlcheck and
mysql_upgrade, which cause that statement to
be executed. See Section 2.18.3, “Checking Whether Table Indexes Must Be Rebuilt”.
(Bug#40984)
See also Bug#39585.
Some queries that used a “range checked for each record” scan could return incorrect results. (Bug#40974)
Certain SELECT queries could fail
with a Duplicate entry error.
(Bug#40953)
The FEDERATED handler had a memory
leak.
(Bug#40875)
IF(..., CAST( as
an argument to an aggregate function could cause an assertion
failure.
(Bug#40761)longtext_val AS
UNSIGNED), signed_val)
Prepared statements allowed invalid dates to be inserted when
the ALLOW_INVALID_DATES SQL
mode was not enabled.
(Bug#40365)
mc.exe is no longer needed to compile MySQL on Windows. This makes it possible to build MySQL from source using Visual Studio Express 2008. (Bug#40280)
Support for the revision field in
.frm files has been removed. This addresses
the downgrading problem introduced by the fix for Bug#17823.
(Bug#40021)
If the operating system is configured to return leap seconds
from OS time calls or if the MySQL server uses a time zone
definition that has leap seconds, functions such as
NOW() could return a value having
a time part that ends with :59:60 or
:59:61. If such values are inserted into a
table, they would be dumped as is by
mysqldump but considered invalid when
reloaded, leading to backup/restore problems.
Now leap second values are returned with a time part that ends
with :59:59. This means that a function such
as NOW() can return the same
value for two or three consecutive seconds during the leap
second. It remains true that literal temporal values having a
time part that ends with :59:60 or
:59:61 are considered invalid.
For additional details about leap-second handling, see Section 9.7.2, “Time Zone Leap Second Support”. (Bug#39920)
The server could crash during a sort-order optimization of a dependent subquery. (Bug#39844)
With the ONLY_FULL_GROUP_BY
SQL mode enabled, the check for nonaggregated columns in queries
with aggregate functions, but without a GROUP
BY clause was treating all the parts of the query as
if they were in the select list. This is fixed by ignoring the
nonaggregated columns in the WHERE clause.
(Bug#39656)
The server crashed if an integer field in a CSV file did not have delimiting quotes. (Bug#39616)
Creating a table with a comment of 62 characters or longer caused a server crash. (Bug#39591)
CHECK TABLE failed for
MyISAM
INFORMATION_SCHEMA tables.
(Bug#39541)
InnoDB could hang trying to open an adaptive
hash index.
(Bug#39483)
For a TIMESTAMP column in an
InnoDB table, testing the column with
multiple conditions in the WHERE clause
caused a server crash.
(Bug#39353)
The server returned a column type of
VARBINARY rather than
DATE as the result from the
COALESCE(),
IFNULL(),
IF(),
GREATEST(), or
LEAST() functions or
CASE expression if the result was
obtained using filesort in an anonymous
temporary table during the query execution.
(Bug#39283)
References to local variables in stored procedures are replaced
with
NAME_CONST( when written to the
binary log. However, an “illegal mix of collation”
error might occur when executing the log contents if the value's
collation differed from that of the variable. Now information
about the variable collation is written as well.
(Bug#39182)name,
value)
Some recent releases for Solaris 10 were built on Solaris 10 U5,
which included a new version of libnsl.so
that does not work on U4 or earlier. To correct this, Solaris 10
builds now are created on machines that do not have that
upgraded libnsl.so, so that they will work
on Solaris 10 installations both with and without the upgraded
libnsl.so.
(Bug#39074)
With binary logging enabled CREATE
VIEW was subject to possible buffer overwrite and a
server crash.
(Bug#39040)
Queries of the form SELECT ... REGEXP BINARY
NULL could lead to a hung or crashed server.
(Bug#39021)
Statements of the form INSERT ... SELECT .. ON
DUPLICATE KEY UPDATE could result in a server crash.
(Bug#39002)col_name =
DEFAULT
Column names constructed due to wild-card expansion done inside a stored procedure could point to freed memory if the expansion was performed after the first call to the stored procedure. (Bug#38823)
Repeated CREATE
TABLE ... SELECT statements, where the created table
contained an AUTO_INCREMENT column, could
lead to an assertion failure.
(Bug#38821)
If delayed insert failed to upgrade the lock, it did not free
the temporary memory storage used to keep newly constructed
BLOB values in memory, resulting
in a memory leak.
(Bug#38693)
A server crash resulted from concurrent execution of a
multiple-table UPDATE that used a
NATURAL or USING join
together with FLUSH
TABLES WITH READ LOCK or ALTER
TABLE for the table being updated.
(Bug#38691)
On ActiveState Perl, mysql-test-run.pl --start-and-exit started but did not exit. (Bug#38629)
Server-side cursors were not initialized properly, which could cause a server crash. (Bug#38486)
Stored procedures involving substrings could crash the server on certain platforms due to invalid memory reads. (Bug#38469)
A server crash or Valgrind warnings could result when a stored procedure selected from a view that referenced a function. (Bug#38291)
Incorrect handling of aggregate functions when loose index scan was used caused a server crash. (Bug#38195)
Queries containing a subquery with DISTINCT
and ORDER BY could cause a server crash.
(Bug#38191)
Queries with a HAVING clause could return a
spurious row.
(Bug#38072)
Use of spatial data types in prepared statements could cause memory leaks or server crashes. (Bug#37956, Bug#37671)
The server crashed if an argument to a stored procedure was a subquery that returned more than one row. (Bug#37949)
When analyzing the possible index use cases, the server was incorrectly reusing an internal structure, leading to a server crash. (Bug#37943)
A SELECT with a NULL NOT
IN condition containing a complex subquery from the
same table as in the outer select caused an assertion failure.
(Bug#37894)
For InnoDB tables, ORDER BY ...
DESC sometimes returned results in ascending order.
(Bug#37830)
If a table has a BIT NOT NULL column
c1 with a length shorter than 8 bits and some
additional NOT NULL columns
c2, ..., and a
SELECT query has a
WHERE clause of the form (c1 =
, the
query could return an unexpected result set.
(Bug#37799)constant) AND c2 ...
Nesting of IF() inside of
SUM() could cause an extreme
server slowdown.
(Bug#37662)
The MONTHNAME() and
DAYNAME() functions returned a
binary string, so that using
LOWER() or
UPPER() had no effect. Now
MONTHNAME() and
DAYNAME() return a value in
character_set_connection
character set.
(Bug#37575)
TIMEDIFF() was erroneously
treated as always returning a positive result. Also,
CAST() of
TIME values to
DECIMAL dropped the sign of
negative values.
(Bug#37553)
See also Bug#42525.
mysqlcheck used
SHOW FULL
TABLES to get the list of tables in a database. For
some problems, such as an empty .frm file
for a table, this would fail and mysqlcheck
then would neglect to check other tables in the database.
(Bug#37527)
The <=>
operator could return incorrect results when comparing
NULL to DATE,
TIME, or
DATETIME values.
(Bug#37526)
Updating a view with a subquery in the CHECK
option could cause an assertion failure.
(Bug#37460)
Statements that displayed the value of system variables (for
example, SHOW VARIABLES) expect
variable values to be encoded in
character_set_system. However,
variables set from the command line such as
basedir or
datadir were encoded using
character_set_filesystem and
not converted correctly.
(Bug#37339)
For a MyISAM table with CHECKSUM =
1 and ROW_FORMAT = DYNAMIC table
options, a data consistency check (maximum record length) could
fail and cause the table to be marked as corrupted.
(Bug#37310)
The max_length result set metadata value was
calculated incorrectly under some circumstances.
(Bug#37301)
CREATE INDEX could crash with
InnoDB plugin 1.0.1.
(Bug#37284)
Certain boolean-mode FULLTEXT searches that
used the truncation operator did not return matching records and
calculated relevance incorrectly.
(Bug#37245)
The NO_BACKSLASH_ESCAPES SQL
mode was ignored for
LOAD DATA
INFILE and SELECT INTO ... OUTFILE.
The setting is taken into account now.
(Bug#37114)
On a 32-bit server built without big tables support, the offset
argument in a LIMIT clause might be truncated
due to a 64-bit to 32-bit cast.
(Bug#37075)
If the server failed to expire binary log files at startup, it could crash. (Bug#37027)
The code for the ut_usectime() function in
InnoDB did not handle errors from the
gettimeofday() system call. Now it retries
gettimeofday() several times and updates
the value of the
Innodb_row_lock_time_max
status variable only if ut_usectime() was
successful.
(Bug#36819)
Use of CONVERT() with
GROUP BY to convert numeric values to
CHAR could return truncated
results.
(Bug#36772)
A query which had an ORDER BY DESC clause
that is satisfied with a reverse range scan could cause a server
crash for some specific CPU/compiler combinations.
(Bug#36639)
Dumping information about locks in use by sending a
SIGHUP signal to the server or by invoking
the mysqladmin debug command could lead to a
server crash in debug builds or to undefined behavior in
production builds.
(Bug#36579)
The mysql client, when built with Visual Studio 2005, did not display Japanese characters. (Bug#36279)
When the fractional part in a multiplication of
DECIMAL values overflowed, the
server truncated the first operand rather than the longest. Now
the server truncates so as to produce more precise
multiplications.
(Bug#36270)
A read past the end of the string could occur while parsing the
value of the
--innodb-data-file-path option.
(Bug#36149)
Host name values in SQL statements were not being checked for
'@', which is illegal according to RFC952.
(Bug#35924)
The UUID() function returned
UUIDs with the wrong time; this was because the offset for the
time part in UUIDs was miscalculated.
(Bug#35848)
SHOW CREATE TABLE did not display
a printable value for the default value of
BIT columns.
(Bug#35796)
mysql_install_db failed on machines that had
the host name set to localhost.
(Bug#35754)
Dynamic plugins failed to load on i5/OS. (Bug#35743)
Freeing of an internal parser stack during parsing of complex stored programs caused a server crash. (Bug#35577, Bug#37269, Bug#37228)
The max_length metadata value was calculated
incorrectly for the FORMAT()
function, which could cause incorrect result set metadata to be
sent to clients.
(Bug#35558)
Index scans performed with the sort_union()
access method returned wrong results, caused memory to be
leaked, and caused temporary files to be deleted when the limit
set by sort_buffer_size was
reached.
(Bug#35477, Bug#35478)
If the server crashed with an InnoDB error
due to unavailability of undo slots, errors could persist during
rollback when the server was restarted: There are two
UNDO slot caches (for
INSERT and
UPDATE). If all slots end up in
one of the slot caches, a request for a slot from the other slot
cache would fail. This can happen if the request is for an
UPDATE slot and all slots are in
the INSERT slot cache, or vice
versa.
(Bug#35352)
For InnoDB tables, ALTER TABLE
DROP failed if the name of the column to be dropped
began with “foreign”.
(Bug#35220)
perror on Windows did not know about Win32 system error codes. (Bug#34825)
EXPLAIN EXTENDED evaluation of aggregate
functions that required a temporary table caused a server crash.
(Bug#34773)
Queries of the form SELECT ... WHERE
failed
when the server used a single-byte character set and the client
used a multi-byte character set.
(Bug#34760)string = ANY(...)
See also Bug#20835.
Using OPTIMIZE TABLE as the first
statement on an InnoDB table with an
AUTO_INCREMENT column could cause a server
crash.
(Bug#34286)
mysql_install_db failed if the server was
running with an SQL mode of
TRADITIONAL. This program now
resets the SQL mode internally to avoid this problem.
(Bug#34159)
Changes to build files were made to enable the MySQL distribution to compile on Microsoft Visual C++ Express 2008. (Bug#33907)
The mysql client incorrectly parsed statements containing the word “delimiter” in mid-statement.
This fix is different from the one applied for this bug in MySQL 5.0.66. (Bug#33812)
See also Bug#38158.
For a stored procedure containing a SELECT * ... RIGHT
JOIN query, execution failed for the second call.
(Bug#33811)
Previously, use of index hints with views (which do not have indexes) produced the error ERROR 1221 (HY000): Incorrect usage of USE/IGNORE INDEX and VIEW. Now this produces ERROR 1176 (HY000): Key '...' doesn't exist in table '...', the same error as for base tables without an appropriate index. (Bug#33461)
Cached queries that used 256 or more tables were not properly
cached, so that later query invalidation due to a
TRUNCATE
TABLE for one of the tables caused the server to hang.
(Bug#33362)
Some division operations produced a result with incorrect precision. (Bug#31616)
mysql_upgrade attempted to use the
/proc file system even on systems that do
not have it.
(Bug#31605)
mysqldump could fail to dump views containing a large number of columns. (Bug#31434)
Queries executed using join buffering of
BIT columns could produce
incorrect results.
(Bug#31399)
ALTER TABLE CONVERT TO CHARACTER SET did not
convert TINYTEXT or
MEDIUMTEXT columns to a longer
text type if necessary when converting the column to a different
character set.
(Bug#31291)
For installation on Solaris using pkgadd
packages, the mysql_install_db script was
generated in the scripts directory, but the
temporary files used during the process were left there and not
deleted.
(Bug#31052)
Several MySQL programs could fail if the HOME
environment variable had an empty value.
(Bug#30394)
On NetWare, mysql_install_db could appear to execute normally even if it failed to create the initial databases. (Bug#30129)
The Serbian translation for the
ER_INCORRECT_GLOBAL_LOCAL_VAR
error was corrected.
(Bug#29738)
XA transaction rollbacks could result in corrupted transaction states and a server crash. (Bug#28323)
The BUILD/check-cpu build script failed if gcc had a different name (such as gcc.real on Debian). (Bug#27526)
On Windows, Visual Studio does not take into account some x86
hardware limitations, which led to incorrect results converting
large DOUBLE values to unsigned
BIGINT values.
(Bug#27483)
SSL support was not included in some “generic” RPM packages. (Bug#26760)
In some cases, the parser interpreted the ;
character as the end of input and misinterpreted stored program
definitions.
(Bug#26030)
The Questions status variable
is intended as a count of statements sent by clients to the
server, but was also counting statements executed within stored
routines.
(Bug#24289)
For access to the
INFORMATION_SCHEMA.VIEWS table, the
server did not check the SHOW
VIEW and SELECT
privileges, leading to inconsistency between output from that
table and the SHOW CREATE VIEW
statement.
(Bug#22763)
The FLUSH
PRIVILEGES statement did not produce an error when it
failed.
(Bug#21226)
A race condition between the mysqld.exe server and the Windows service manager could lead to inability to stop the server from the service manager. (Bug#20430)
mysqld_safe would sometimes fail to remove
the pid file for the old mysql process after
a crash. As a result, the server would fail to start due to a
false A mysqld process already exists...
error.
(Bug#11122)
This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.74). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Functionality added or changed:
Bugs fixed:
Replication: When rotating relay log files, the slave deletes relay log files and then edits the relay log index file. Formerly, if the slave shut down unexpectedly between these two events, the relay log index file could then reference relay logs that no longer existed. Depending on the circumstances, this could when restarting the slave cause either a race condition or the failure of replication. (Bug#38826, Bug#39325)
In example option files provided in MySQL distributions, the
thread_stack value was
increased from 64K to 128K.
(Bug#41577)
SET PASSWORD caused a server
crash if the account name was given as
CURRENT_USER().
(Bug#41456)
The
INFORMATION_SCHEMA.SCHEMA_PRIVILEGES
table was limited to 7680 rows.
(Bug#41079)
In debug builds, obsolete debug code could be used to crash the server. (Bug#41041)
Some queries that used a “range checked for each record” scan could return incorrect results. (Bug#40974)
Certain SELECT queries could fail
with a Duplicate entry error.
(Bug#40953)
IF(..., CAST( as
an argument to an aggregate function could cause an assertion
failure.
(Bug#40761)longtext_val AS
UNSIGNED), signed_val)
The server crashed if an integer field in a CSV file did not have delimiting quotes. (Bug#39616)
Creating a table with a comment of 62 characters or longer caused a server crash. (Bug#39591)
InnoDB could hang trying to open an adaptive
hash index.
(Bug#39483)
Use of spatial data types in prepared statements could cause memory leaks or server crashes. (Bug#37956, Bug#37671)
The MONTHNAME() and
DAYNAME() functions returned a
binary string, so that using
LOWER() or
UPPER() had no effect. Now
MONTHNAME() and
DAYNAME() return a value in
character_set_connection
character set.
(Bug#37575)
Certain boolean-mode FULLTEXT searches that
used the truncation operator did not return matching records and
calculated relevance incorrectly.
(Bug#37245)
The code for the ut_usectime() function in
InnoDB did not handle errors from the
gettimeofday() system call. Now it retries
gettimeofday() several times and updates
the value of the
Innodb_row_lock_time_max
status variable only if ut_usectime() was
successful.
(Bug#36819)
A read past the end of the string could occur while parsing the
value of the
--innodb-data-file-path option.
(Bug#36149)
SHOW CREATE TABLE did not display
a printable value for the default value of
BIT columns.
(Bug#35796)
The max_length metadata value was calculated
incorrectly for the FORMAT()
function, which could cause incorrect result set metadata to be
sent to clients.
(Bug#35558)
EXPLAIN EXTENDED evaluation of aggregate
functions that required a temporary table caused a server crash.
(Bug#34773)
The mysql client incorrectly parsed statements containing the word “delimiter” in mid-statement.
This fix is different from the one applied for this bug in MySQL 5.0.66. (Bug#33812)
See also Bug#38158.
Queries executed using join buffering of
BIT columns could produce
incorrect results.
(Bug#31399)
ALTER TABLE CONVERT TO CHARACTER SET did not
convert TINYTEXT or
MEDIUMTEXT columns to a longer
text type if necessary when converting the column to a different
character set.
(Bug#31291)
On Windows, Visual Studio does not take into account some x86
hardware limitations, which led to incorrect results converting
large DOUBLE values to unsigned
BIGINT values.
(Bug#27483)
SSL support was not included in some “generic” RPM packages. (Bug#26760)
This is a bugfix release for the current MySQL Community Server production release family. It replaces MySQL 5.0.67.
Functionality added or changed:
Security Enhancement:
To enable stricter control over the location from which
user-defined functions can be loaded, the
plugin_dir system variable has
been backported from MySQL 5.1. If the value is nonempty,
user-defined function object files can be loaded only from the
directory named by this variable. If the value is empty, the
behavior that is used prior to the inclusion of
plugin_dir applies: The UDF
object files must be located in a directory that is searched by
your system's dynamic linker.
(Bug#37428)
Previously, index hints did not work for
FULLTEXT searches. Now they work as follows:
For natural language mode searches, index hints are silently
ignored. For example, IGNORE INDEX(i) is
ignored with no warning and the index is still used.
For boolean mode searches, index hints are honored. (Bug#38842)
Bugs fixed:
Important Change: Security Fix: Additional corrections were made for the symlink-related privilege problem originally addressed in MySQL 5.0.60. The original fix did not correctly handle the data directory path name if it contained symlinked directories in its path, and the check was made only at table-creation time, not at table-opening time later. (Bug#32167, CVE-2008-2079)
See also Bug#39277.
Security Enhancement:
The server consumed excess memory while parsing statements with
hundreds or thousands of nested boolean conditions (such as
OR (OR ... (OR ... ))). This could lead to a
server crash or incorrect statement execution, or cause other
client statements to fail due to lack of memory. The latter
result constitutes a denial of service.
(Bug#38296)
Incompatible Change:
There were some problems using DllMain()
hook functions on Windows that automatically do global and
per-thread initialization for
libmysqld.dll:
Per-thread initialization: MySQL internally counts the
number of active threads, which causes a delay in
my_end() if not all threads have
exited. But there are threads that can be started either by
Windows internally (often in TCP/IP scenarios) or by users.
Those threads do not necessarily use
libmysql.dll functionality but still
contribute to the open-thread count. (One symptom is a
five-second delay in times for PHP scripts to finish.)
Process-initialization:
my_init() calls
WSAStartup that itself loads DLLs and
can lead to a deadlock in the Windows loader.
To correct these problems, DLL initialization code now is not
invoked from libmysql.dll by default. To
obtain the previous behavior (DLL initialization code will be
called), set the LIBMYSQL_DLLINIT environment
variable to any value. This variable exists only to prevent
breakage of existing Windows-only applications that do not call
mysql_thread_init() and work
okay today. Use of LIBMYSQL_DLLINIT is
discouraged and is removed in MySQL 6.0.
(Bug#37226, Bug#33031)
Incompatible Change:
SHOW STATUS took a lot of CPU
time for calculating the value of the
Innodb_buffer_pool_pages_latched
status variable. Now this variable is calculated and included in
the output of SHOW STATUS only if
the UNIV_DEBUG symbol is defined at MySQL
build time.
(Bug#36600)
Incompatible Change:
In connection with view creation, the server created
arc directories inside database directories
and maintained useless copies of .frm files
there. Creation and renaming procedures of those copies as well
as creation of arc directories has been
discontinued.
This change does cause a problem when downgrading to older server versions which manifests itself under these circumstances:
Create a view v_orig in MySQL 5.0.72 or
higher.
Rename the view to v_new and then back to
v_orig.
Downgrade to an older 5.0.x server and run mysql_upgrade.
Try to rename v_orig to
v_new again. This operation fails.
As a workaround to avoid this problem, use either of these approaches:
Dump your data using mysqldump before downgrading and reload the dump file after downgrading.
Instead of renaming a view after the downgrade, drop it and recreate it.
The downgrade problem introduced by the fix for this bug has been addressed as Bug#40021. (Bug#17823)
CHECK TABLE ... FOR
UPGRADE did not check for incompatible collation
changes made in MySQL 5.0.48 (Bug#27562, Bug#29461, Bug#29499).
This also affects mysqlcheck and
mysql_upgrade, which cause that statement to
be executed. See Section 2.18.3, “Checking Whether Table Indexes Must Be Rebuilt”.
(Bug#40984)
See also Bug#39585.
The FEDERATED handler had a memory
leak.
(Bug#40875)
Prepared statements allowed invalid dates to be inserted when
the ALLOW_INVALID_DATES SQL
mode was not enabled.
(Bug#40365)
mc.exe is no longer needed to compile MySQL on Windows. This makes it possible to build MySQL from source using Visual Studio Express 2008. (Bug#40280)
Support for the revision field in
.frm files has been removed. This addresses
the downgrading problem introduced by the fix for Bug#17823.
(Bug#40021)
If the operating system is configured to return leap seconds
from OS time calls or if the MySQL server uses a time zone
definition that has leap seconds, functions such as
NOW() could return a value having
a time part that ends with :59:60 or
:59:61. If such values are inserted into a
table, they would be dumped as is by
mysqldump but considered invalid when
reloaded, leading to backup/restore problems.
Now leap second values are returned with a time part that ends
with :59:59. This means that a function such
as NOW() can return the same
value for two or three consecutive seconds during the leap
second. It remains true that literal temporal values having a
time part that ends with :59:60 or
:59:61 are considered invalid.
For additional details about leap-second handling, see Section 9.7.2, “Time Zone Leap Second Support”. (Bug#39920)
The server could crash during a sort-order optimization of a dependent subquery. (Bug#39844)
With the ONLY_FULL_GROUP_BY
SQL mode enabled, the check for nonaggregated columns in queries
with aggregate functions, but without a GROUP
BY clause was treating all the parts of the query as
if they were in the select list. This is fixed by ignoring the
nonaggregated columns in the WHERE clause.
(Bug#39656)
CHECK TABLE failed for
MyISAM
INFORMATION_SCHEMA tables.
(Bug#39541)
For a TIMESTAMP column in an
InnoDB table, testing the column with
multiple conditions in the WHERE clause
caused a server crash.
(Bug#39353)
The server returned a column type of
VARBINARY rather than
DATE as the result from the
COALESCE(),
IFNULL(),
IF(),
GREATEST(), or
LEAST() functions or
CASE expression if the result was
obtained using filesort in an anonymous
temporary table during the query execution.
(Bug#39283)
References to local variables in stored procedures are replaced
with
NAME_CONST( when written to the
binary log. However, an “illegal mix of collation”
error might occur when executing the log contents if the value's
collation differed from that of the variable. Now information
about the variable collation is written as well.
(Bug#39182)name,
value)
Some recent releases for Solaris 10 were built on Solaris 10 U5,
which included a new version of libnsl.so
that does not work on U4 or earlier. To correct this, Solaris 10
builds now are created on machines that do not have that
upgraded libnsl.so, so that they will work
on Solaris 10 installations both with and without the upgraded
libnsl.so.
(Bug#39074)
With binary logging enabled CREATE
VIEW was subject to possible buffer overwrite and a
server crash.
(Bug#39040)
Queries of the form SELECT ... REGEXP BINARY
NULL could lead to a hung or crashed server.
(Bug#39021)
Statements of the form INSERT ... SELECT .. ON
DUPLICATE KEY UPDATE could result in a server crash.
(Bug#39002)col_name =
DEFAULT
Column names constructed due to wild-card expansion done inside a stored procedure could point to freed memory if the expansion was performed after the first call to the stored procedure. (Bug#38823)
Repeated CREATE
TABLE ... SELECT statements, where the created table
contained an AUTO_INCREMENT column, could
lead to an assertion failure.
(Bug#38821)
If delayed insert failed to upgrade the lock, it did not free
the temporary memory storage used to keep newly constructed
BLOB values in memory, resulting
in a memory leak.
(Bug#38693)
A server crash resulted from concurrent execution of a
multiple-table UPDATE that used a
NATURAL or USING join
together with FLUSH
TABLES WITH READ LOCK or ALTER
TABLE for the table being updated.
(Bug#38691)
On ActiveState Perl, mysql-test-run.pl --start-and-exit started but did not exit. (Bug#38629)
Server-side cursors were not initialized properly, which could cause a server crash. (Bug#38486)
Stored procedures involving substrings could crash the server on certain platforms due to invalid memory reads. (Bug#38469)
A server crash or Valgrind warnings could result when a stored procedure selected from a view that referenced a function. (Bug#38291)
Incorrect handling of aggregate functions when loose index scan was used caused a server crash. (Bug#38195)
Queries containing a subquery with DISTINCT
and ORDER BY could cause a server crash.
(Bug#38191)
Queries with a HAVING clause could return a
spurious row.
(Bug#38072)
The server crashed if an argument to a stored procedure was a subquery that returned more than one row. (Bug#37949)
When analyzing the possible index use cases, the server was incorrectly reusing an internal structure, leading to a server crash. (Bug#37943)
A SELECT with a NULL NOT
IN condition containing a complex subquery from the
same table as in the outer select caused an assertion failure.
(Bug#37894)
For InnoDB tables, ORDER BY ...
DESC sometimes returned results in ascending order.
(Bug#37830)
If a table has a BIT NOT NULL column
c1 with a length shorter than 8 bits and some
additional NOT NULL columns
c2, ..., and a
SELECT query has a
WHERE clause of the form (c1 =
, the
query could return an unexpected result set.
(Bug#37799)constant) AND c2 ...
Nesting of IF() inside of
SUM() could cause an extreme
server slowdown.
(Bug#37662)
TIMEDIFF() was erroneously
treated as always returning a positive result. Also,
CAST() of
TIME values to
DECIMAL dropped the sign of
negative values.
(Bug#37553)
See also Bug#42525.
mysqlcheck used
SHOW FULL
TABLES to get the list of tables in a database. For
some problems, such as an empty .frm file
for a table, this would fail and mysqlcheck
then would neglect to check other tables in the database.
(Bug#37527)
The <=>
operator could return incorrect results when comparing
NULL to DATE,
TIME, or
DATETIME values.
(Bug#37526)
Updating a view with a subquery in the CHECK
option could cause an assertion failure.
(Bug#37460)
Statements that displayed the value of system variables (for
example, SHOW VARIABLES) expect
variable values to be encoded in
character_set_system. However,
variables set from the command line such as
basedir or
datadir were encoded using
character_set_filesystem and
not converted correctly.
(Bug#37339)
For a MyISAM table with CHECKSUM =
1 and ROW_FORMAT = DYNAMIC table
options, a data consistency check (maximum record length) could
fail and cause the table to be marked as corrupted.
(Bug#37310)
The max_length result set metadata value was
calculated incorrectly under some circumstances.
(Bug#37301)
CREATE INDEX could crash with
InnoDB plugin 1.0.1.
(Bug#37284)
The NO_BACKSLASH_ESCAPES SQL
mode was ignored for
LOAD DATA
INFILE and SELECT INTO ... OUTFILE.
The setting is taken into account now.
(Bug#37114)
On a 32-bit server built without big tables support, the offset
argument in a LIMIT clause might be truncated
due to a 64-bit to 32-bit cast.
(Bug#37075)
If the server failed to expire binary log files at startup, it could crash. (Bug#37027)
Use of CONVERT() with
GROUP BY to convert numeric values to
CHAR could return truncated
results.
(Bug#36772)
A query which had an ORDER BY DESC clause
that is satisfied with a reverse range scan could cause a server
crash for some specific CPU/compiler combinations.
(Bug#36639)
Dumping information about locks in use by sending a
SIGHUP signal to the server or by invoking
the mysqladmin debug command could lead to a
server crash in debug builds or to undefined behavior in
production builds.
(Bug#36579)
The mysql client, when built with Visual Studio 2005, did not display Japanese characters. (Bug#36279)
When the fractional part in a multiplication of
DECIMAL values overflowed, the
server truncated the first operand rather than the longest. Now
the server truncates so as to produce more precise
multiplications.
(Bug#36270)
Host name values in SQL statements were not being checked for
'@', which is illegal according to RFC952.
(Bug#35924)
The UUID() function returned
UUIDs with the wrong time; this was because the offset for the
time part in UUIDs was miscalculated.
(Bug#35848)
mysql_install_db failed on machines that had
the host name set to localhost.
(Bug#35754)
Dynamic plugins failed to load on i5/OS. (Bug#35743)
Freeing of an internal parser stack during parsing of complex stored programs caused a server crash. (Bug#35577, Bug#37269, Bug#37228)
Index scans performed with the sort_union()
access method returned wrong results, caused memory to be
leaked, and caused temporary files to be deleted when the limit
set by sort_buffer_size was
reached.
(Bug#35477, Bug#35478)
If the server crashed with an InnoDB error
due to unavailability of undo slots, errors could persist during
rollback when the server was restarted: There are two
UNDO slot caches (for
INSERT and
UPDATE). If all slots end up in
one of the slot caches, a request for a slot from the other slot
cache would fail. This can happen if the request is for an
UPDATE slot and all slots are in
the INSERT slot cache, or vice
versa.
(Bug#35352)
For InnoDB tables, ALTER TABLE
DROP failed if the name of the column to be dropped
began with “foreign”.
(Bug#35220)
perror on Windows did not know about Win32 system error codes. (Bug#34825)
Queries of the form SELECT ... WHERE
failed
when the server used a single-byte character set and the client
used a multi-byte character set.
(Bug#34760)string = ANY(...)
See also Bug#20835.
Using OPTIMIZE TABLE as the first
statement on an InnoDB table with an
AUTO_INCREMENT column could cause a server
crash.
(Bug#34286)
mysql_install_db failed if the server was
running with an SQL mode of
TRADITIONAL. This program now
resets the SQL mode internally to avoid this problem.
(Bug#34159)
Changes to build files were made to enable the MySQL distribution to compile on Microsoft Visual C++ Express 2008. (Bug#33907)
For a stored procedure containing a SELECT * ... RIGHT
JOIN query, execution failed for the second call.
(Bug#33811)
Previously, use of index hints with views (which do not have indexes) produced the error ERROR 1221 (HY000): Incorrect usage of USE/IGNORE INDEX and VIEW. Now this produces ERROR 1176 (HY000): Key '...' doesn't exist in table '...', the same error as for base tables without an appropriate index. (Bug#33461)
Cached queries that used 256 or more tables were not properly
cached, so that later query invalidation due to a
TRUNCATE
TABLE for one of the tables caused the server to hang.
(Bug#33362)
Some division operations produced a result with incorrect precision. (Bug#31616)
mysql_upgrade attempted to use the
/proc file system even on systems that do
not have it.
(Bug#31605)
mysqldump could fail to dump views containing a large number of columns. (Bug#31434)
Several MySQL programs could fail if the HOME
environment variable had an empty value.
(Bug#30394)
On NetWare, mysql_install_db could appear to execute normally even if it failed to create the initial databases. (Bug#30129)
The Serbian translation for the
ER_INCORRECT_GLOBAL_LOCAL_VAR
error was corrected.
(Bug#29738)
XA transaction rollbacks could result in corrupted transaction states and a server crash. (Bug#28323)
The BUILD/check-cpu build script failed if gcc had a different name (such as gcc.real on Debian). (Bug#27526)
In some cases, the parser interpreted the ;
character as the end of input and misinterpreted stored program
definitions.
(Bug#26030)
The Questions status variable
is intended as a count of statements sent by clients to the
server, but was also counting statements executed within stored
routines.
(Bug#24289)
For access to the
INFORMATION_SCHEMA.VIEWS table, the
server did not check the SHOW
VIEW and SELECT
privileges, leading to inconsistency between output from that
table and the SHOW CREATE VIEW
statement.
(Bug#22763)
The FLUSH
PRIVILEGES statement did not produce an error when it
failed.
(Bug#21226)
A race condition between the mysqld.exe server and the Windows service manager could lead to inability to stop the server from the service manager. (Bug#20430)
mysqld_safe would sometimes fail to remove
the pid file for the old mysql process after
a crash. As a result, the server would fail to start due to a
false A mysqld process already exists...
error.
(Bug#11122)
This is a Service Pack release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.74).
If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Functionality added or changed:
The libedit library was upgraded to version
2.11.
(Bug#42433)
Bugs fixed:
An attempt by a user who did not have the
SUPER privilege to kill a system
thread could cause a server crash.
(Bug#43748)
Tables could enter open table cache for a thread without being properly cleaned up, leading to a server crash. (Bug#42419)
The SSL certficates included with MySQL distributions were regenerated because the previous ones had expired. (Bug#42366)
Some queries using NAME_CONST(.. COLLATE
...) led to a server crash due to a failed type cast.
(Bug#42014)
DATE_FORMAT() could cause a
server crash for year-zero dates.
(Bug#41470)
SET PASSWORD caused a server
crash if the account name was given as
CURRENT_USER().
(Bug#41456)
When substituting system constant functions with a constant
result, the server was not expecting NULL
function return values and could crash.
(Bug#41437)
Creating a table with a comment of 62 characters or longer caused a server crash. (Bug#39591)
EXPLAIN EXTENDED evaluation of aggregate
functions that required a temporary table caused a server crash.
(Bug#34773)
This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.72). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Functionality added or changed:
Previously, index hints did not work for
FULLTEXT searches. Now they work as follows:
For natural language mode searches, index hints are silently
ignored. For example, IGNORE INDEX(i) is
ignored with no warning and the index is still used.
For boolean mode searches, index hints are honored. (Bug#38842)
Bugs fixed:
CHECK TABLE ... FOR
UPGRADE did not check for incompatible collation
changes made in MySQL 5.0.48 (Bug#27562, Bug#29461, Bug#29499).
This also affects mysqlcheck and
mysql_upgrade, which cause that statement to
be executed. See Section 2.18.3, “Checking Whether Table Indexes Must Be Rebuilt”.
(Bug#40984)
See also Bug#39585.
The FEDERATED handler had a memory
leak.
(Bug#40875)
Prepared statements allowed invalid dates to be inserted when
the ALLOW_INVALID_DATES SQL
mode was not enabled.
(Bug#40365)
Support for the revision field in
.frm files has been removed. This addresses
the downgrading problem introduced by the fix for Bug#17823.
(Bug#40021)
If the operating system is configured to return leap seconds
from OS time calls or if the MySQL server uses a time zone
definition that has leap seconds, functions such as
NOW() could return a value having
a time part that ends with :59:60 or
:59:61. If such values are inserted into a
table, they would be dumped as is by
mysqldump but considered invalid when
reloaded, leading to backup/restore problems.
Now leap second values are returned with a time part that ends
with :59:59. This means that a function such
as NOW() can return the same
value for two or three consecutive seconds during the leap
second. It remains true that literal temporal values having a
time part that ends with :59:60 or
:59:61 are considered invalid.
For additional details about leap-second handling, see Section 9.7.2, “Time Zone Leap Second Support”. (Bug#39920)
With the ONLY_FULL_GROUP_BY
SQL mode enabled, the check for nonaggregated columns in queries
with aggregate functions, but without a GROUP
BY clause was treating all the parts of the query as
if they were in the select list. This is fixed by ignoring the
nonaggregated columns in the WHERE clause.
(Bug#39656)
CHECK TABLE failed for
MyISAM
INFORMATION_SCHEMA tables.
(Bug#39541)
With binary logging enabled CREATE
VIEW was subject to possible buffer overwrite and a
server crash.
(Bug#39040)
Queries with a HAVING clause could return a
spurious row.
(Bug#38072)
TIMEDIFF() was erroneously
treated as always returning a positive result. Also,
CAST() of
TIME values to
DECIMAL dropped the sign of
negative values.
(Bug#37553)
See also Bug#42525.
mysqlcheck used
SHOW FULL
TABLES to get the list of tables in a database. For
some problems, such as an empty .frm file
for a table, this would fail and mysqlcheck
then would neglect to check other tables in the database.
(Bug#37527)
Updating a view with a subquery in the CHECK
option could cause an assertion failure.
(Bug#37460)
Statements that displayed the value of system variables (for
example, SHOW VARIABLES) expect
variable values to be encoded in
character_set_system. However,
variables set from the command line such as
basedir or
datadir were encoded using
character_set_filesystem and
not converted correctly.
(Bug#37339)
CREATE INDEX could crash with
InnoDB plugin 1.0.1.
(Bug#37284)
Use of CONVERT() with
GROUP BY to convert numeric values to
CHAR could return truncated
results.
(Bug#36772)
The mysql client, when built with Visual Studio 2005, did not display Japanese characters. (Bug#36279)
perror on Windows did not know about Win32 system error codes. (Bug#34825)
Queries of the form SELECT ... WHERE
failed
when the server used a single-byte character set and the client
used a multi-byte character set.
(Bug#34760)string = ANY(...)
See also Bug#20835.
For a stored procedure containing a SELECT * ... RIGHT
JOIN query, execution failed for the second call.
(Bug#33811)
Previously, use of index hints with views (which do not have indexes) produced the error ERROR 1221 (HY000): Incorrect usage of USE/IGNORE INDEX and VIEW. Now this produces ERROR 1176 (HY000): Key '...' doesn't exist in table '...', the same error as for base tables without an appropriate index. (Bug#33461)
Some division operations produced a result with incorrect precision. (Bug#31616)
A race condition between the mysqld.exe server and the Windows service manager could lead to inability to stop the server from the service manager. (Bug#20430)
This is a Service Pack release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.72).
If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Functionality added or changed:
Previously, index hints did not work for
FULLTEXT searches. Now they work as follows:
For natural language mode searches, index hints are silently
ignored. For example, IGNORE INDEX(i) is
ignored with no warning and the index is still used.
For boolean mode searches, index hints are honored. (Bug#38842)
Bugs fixed:
MySQL Cluster: Packaging:
Packages for MySQL Cluster were missing the
libndbclient.so and
libndbclient.a files.
(Bug#42278)
Support for the revision field in
.frm files has been removed. This addresses
the downgrading problem introduced by the fix for Bug#17823.
(Bug#40021)
If the operating system is configured to return leap seconds
from OS time calls or if the MySQL server uses a time zone
definition that has leap seconds, functions such as
NOW() could return a value having
a time part that ends with :59:60 or
:59:61. If such values are inserted into a
table, they would be dumped as is by
mysqldump but considered invalid when
reloaded, leading to backup/restore problems.
Now leap second values are returned with a time part that ends
with :59:59. This means that a function such
as NOW() can return the same
value for two or three consecutive seconds during the leap
second. It remains true that literal temporal values having a
time part that ends with :59:60 or
:59:61 are considered invalid.
For additional details about leap-second handling, see Section 9.7.2, “Time Zone Leap Second Support”. (Bug#39920)
Queries of the form SELECT ... WHERE
failed
when the server used a single-byte character set and the client
used a multi-byte character set.
(Bug#34760)string = ANY(...)
See also Bug#20835.
This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.70). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Bugs fixed:
Incompatible Change:
In connection with view creation, the server created
arc directories inside database directories
and maintained useless copies of .frm files
there. Creation and renaming procedures of those copies as well
as creation of arc directories has been
discontinued.
This change does cause a problem when downgrading to older server versions which manifests itself under these circumstances:
Create a view v_orig in MySQL 5.0.72 or
higher.
Rename the view to v_new and then back to
v_orig.
Downgrade to an older 5.0.x server and run mysql_upgrade.
Try to rename v_orig to
v_new again. This operation fails.
As a workaround to avoid this problem, use either of these approaches:
Dump your data using mysqldump before downgrading and reload the dump file after downgrading.
Instead of renaming a view after the downgrade, drop it and recreate it.
The downgrade problem introduced by the fix for this bug has been addressed as Bug#40021. (Bug#17823)
mc.exe is no longer needed to compile MySQL on Windows. This makes it possible to build MySQL from source using Visual Studio Express 2008. (Bug#40280)
The server could crash during a sort-order optimization of a dependent subquery. (Bug#39844)
The server returned a column type of
VARBINARY rather than
DATE as the result from the
COALESCE(),
IFNULL(),
IF(),
GREATEST(), or
LEAST() functions or
CASE expression if the result was
obtained using filesort in an anonymous
temporary table during the query execution.
(Bug#39283)
References to local variables in stored procedures are replaced
with
NAME_CONST( when written to the
binary log. However, an “illegal mix of collation”
error might occur when executing the log contents if the value's
collation differed from that of the variable. Now information
about the variable collation is written as well.
(Bug#39182)name,
value)
Some recent releases for Solaris 10 were built on Solaris 10 U5,
which included a new version of libnsl.so
that does not work on U4 or earlier. To correct this, Solaris 10
builds now are created on machines that do not have that
upgraded libnsl.so, so that they will work
on Solaris 10 installations both with and without the upgraded
libnsl.so.
(Bug#39074)
Column names constructed due to wild-card expansion done inside a stored procedure could point to freed memory if the expansion was performed after the first call to the stored procedure. (Bug#38823)
If delayed insert failed to upgrade the lock, it did not free
the temporary memory storage used to keep newly constructed
BLOB values in memory, resulting
in a memory leak.
(Bug#38693)
A server crash resulted from concurrent execution of a
multiple-table UPDATE that used a
NATURAL or USING join
together with FLUSH
TABLES WITH READ LOCK or ALTER
TABLE for the table being updated.
(Bug#38691)
On ActiveState Perl, mysql-test-run.pl --start-and-exit started but did not exit. (Bug#38629)
Stored procedures involving substrings could crash the server on certain platforms due to invalid memory reads. (Bug#38469)
The server crashed if an argument to a stored procedure was a subquery that returned more than one row. (Bug#37949)
When analyzing the possible index use cases, the server was incorrectly reusing an internal structure, leading to a server crash. (Bug#37943)
A SELECT with a NULL NOT
IN condition containing a complex subquery from the
same table as in the outer select caused an assertion failure.
(Bug#37894)
On a 32-bit server built without big tables support, the offset
argument in a LIMIT clause might be truncated
due to a 64-bit to 32-bit cast.
(Bug#37075)
Host name values in SQL statements were not being checked for
'@', which is illegal according to RFC952.
(Bug#35924)
mysql_install_db failed on machines that had
the host name set to localhost.
(Bug#35754)
Dynamic plugins failed to load on i5/OS. (Bug#35743)
XA transaction rollbacks could result in corrupted transaction states and a server crash. (Bug#28323)
The Questions status variable
is intended as a count of statements sent by clients to the
server, but was also counting statements executed within stored
routines.
(Bug#24289)
For access to the
INFORMATION_SCHEMA.VIEWS table, the
server did not check the SHOW
VIEW and SELECT
privileges, leading to inconsistency between output from that
table and the SHOW CREATE VIEW
statement.
(Bug#22763)
mysqld_safe would sometimes fail to remove
the pid file for the old mysql process after
a crash. As a result, the server would fail to start due to a
false A mysqld process already exists...
error.
(Bug#11122)
This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.68). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Functionality added or changed:
Security Enhancement:
To enable stricter control over the location from which
user-defined functions can be loaded, the
plugin_dir system variable has
been backported from MySQL 5.1. If the value is nonempty,
user-defined function object files can be loaded only from the
directory named by this variable. If the value is empty, the
behavior that is used prior to the inclusion of
plugin_dir applies: The UDF
object files must be located in a directory that is searched by
your system's dynamic linker.
(Bug#37428)
Bugs fixed:
Important Change: Security Fix: Additional corrections were made for the symlink-related privilege problem originally addressed in MySQL 5.0.60. The original fix did not correctly handle the data directory path name if it contained symlinked directories in its path, and the check was made only at table-creation time, not at table-opening time later. (Bug#32167, CVE-2008-2079)
See also Bug#39277.
Incompatible Change:
There were some problems using DllMain()
hook functions on Windows that automatically do global and
per-thread initialization for
libmysqld.dll:
Per-thread initialization: MySQL internally counts the
number of active threads, which causes a delay in
my_end() if not all threads have
exited. But there are threads that can be started either by
Windows internally (often in TCP/IP scenarios) or by users.
Those threads do not necessarily use
libmysql.dll functionality but still
contribute to the open-thread count. (One symptom is a
five-second delay in times for PHP scripts to finish.)
Process-initialization:
my_init() calls
WSAStartup that itself loads DLLs and
can lead to a deadlock in the Windows loader.
To correct these problems, DLL initialization code now is not
invoked from libmysql.dll by default. To
obtain the previous behavior (DLL initialization code will be
called), set the LIBMYSQL_DLLINIT environment
variable to any value. This variable exists only to prevent
breakage of existing Windows-only applications that do not call
mysql_thread_init() and work
okay today. Use of LIBMYSQL_DLLINIT is
discouraged and is removed in MySQL 6.0.
(Bug#37226, Bug#33031)
For a TIMESTAMP column in an
InnoDB table, testing the column with
multiple conditions in the WHERE clause
caused a server crash.
(Bug#39353)
Queries of the form SELECT ... REGEXP BINARY
NULL could lead to a hung or crashed server.
(Bug#39021)
Statements of the form INSERT ... SELECT .. ON
DUPLICATE KEY UPDATE could result in a server crash.
(Bug#39002)col_name =
DEFAULT
Repeated CREATE
TABLE ... SELECT statements, where the created table
contained an AUTO_INCREMENT column, could
lead to an assertion failure.
(Bug#38821)
A server crash or Valgrind warnings could result when a stored procedure selected from a view that referenced a function. (Bug#38291)
Incorrect handling of aggregate functions when loose index scan was used caused a server crash. (Bug#38195)
If a table has a BIT NOT NULL column
c1 with a length shorter than 8 bits and some
additional NOT NULL columns
c2, ..., and a
SELECT query has a
WHERE clause of the form (c1 =
, the
query could return an unexpected result set.
(Bug#37799)constant) AND c2 ...
The <=>
operator could return incorrect results when comparing
NULL to DATE,
TIME, or
DATETIME values.
(Bug#37526)
For a MyISAM table with CHECKSUM =
1 and ROW_FORMAT = DYNAMIC table
options, a data consistency check (maximum record length) could
fail and cause the table to be marked as corrupted.
(Bug#37310)
The max_length result set metadata value was
calculated incorrectly under some circumstances.
(Bug#37301)
The NO_BACKSLASH_ESCAPES SQL
mode was ignored for
LOAD DATA
INFILE and SELECT INTO ... OUTFILE.
The setting is taken into account now.
(Bug#37114)
A query which had an ORDER BY DESC clause
that is satisfied with a reverse range scan could cause a server
crash for some specific CPU/compiler combinations.
(Bug#36639)
Dumping information about locks in use by sending a
SIGHUP signal to the server or by invoking
the mysqladmin debug command could lead to a
server crash in debug builds or to undefined behavior in
production builds.
(Bug#36579)
When the fractional part in a multiplication of
DECIMAL values overflowed, the
server truncated the first operand rather than the longest. Now
the server truncates so as to produce more precise
multiplications.
(Bug#36270)
Changes to build files were made to enable the MySQL distribution to compile on Microsoft Visual C++ Express 2008. (Bug#33907)
mysqldump could fail to dump views containing a large number of columns. (Bug#31434)
Several MySQL programs could fail if the HOME
environment variable had an empty value.
(Bug#30394)
The BUILD/check-cpu build script failed if gcc had a different name (such as gcc.real on Debian). (Bug#27526)
This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.66a). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Bugs fixed:
Security Enhancement:
The server consumed excess memory while parsing statements with
hundreds or thousands of nested boolean conditions (such as
OR (OR ... (OR ... ))). This could lead to a
server crash or incorrect statement execution, or cause other
client statements to fail due to lack of memory. The latter
result constitutes a denial of service.
(Bug#38296)
Incompatible Change:
SHOW STATUS took a lot of CPU
time for calculating the value of the
Innodb_buffer_pool_pages_latched
status variable. Now this variable is calculated and included in
the output of SHOW STATUS only if
the UNIV_DEBUG symbol is defined at MySQL
build time.
(Bug#36600)
Server-side cursors were not initialized properly, which could cause a server crash. (Bug#38486)
Queries containing a subquery with DISTINCT
and ORDER BY could cause a server crash.
(Bug#38191)
For InnoDB tables, ORDER BY ...
DESC sometimes returned results in ascending order.
(Bug#37830)
Nesting of IF() inside of
SUM() could cause an extreme
server slowdown.
(Bug#37662)
If the server failed to expire binary log files at startup, it could crash. (Bug#37027)
The UUID() function returned
UUIDs with the wrong time; this was because the offset for the
time part in UUIDs was miscalculated.
(Bug#35848)
Freeing of an internal parser stack during parsing of complex stored programs caused a server crash. (Bug#35577, Bug#37269, Bug#37228)
Index scans performed with the sort_union()
access method returned wrong results, caused memory to be
leaked, and caused temporary files to be deleted when the limit
set by sort_buffer_size was
reached.
(Bug#35477, Bug#35478)
If the server crashed with an InnoDB error
due to unavailability of undo slots, errors could persist during
rollback when the server was restarted: There are two
UNDO slot caches (for
INSERT and
UPDATE). If all slots end up in
one of the slot caches, a request for a slot from the other slot
cache would fail. This can happen if the request is for an
UPDATE slot and all slots are in
the INSERT slot cache, or vice
versa.
(Bug#35352)
For InnoDB tables, ALTER TABLE
DROP failed if the name of the column to be dropped
began with “foreign”.
(Bug#35220)
Using OPTIMIZE TABLE as the first
statement on an InnoDB table with an
AUTO_INCREMENT column could cause a server
crash.
(Bug#34286)
mysql_install_db failed if the server was
running with an SQL mode of
TRADITIONAL. This program now
resets the SQL mode internally to avoid this problem.
(Bug#34159)
Cached queries that used 256 or more tables were not properly
cached, so that later query invalidation due to a
TRUNCATE
TABLE for one of the tables caused the server to hang.
(Bug#33362)
mysql_upgrade attempted to use the
/proc file system even on systems that do
not have it.
(Bug#31605)
On NetWare, mysql_install_db could appear to execute normally even if it failed to create the initial databases. (Bug#30129)
The Serbian translation for the
ER_INCORRECT_GLOBAL_LOCAL_VAR
error was corrected.
(Bug#29738)
In some cases, the parser interpreted the ;
character as the end of input and misinterpreted stored program
definitions.
(Bug#26030)
The FLUSH
PRIVILEGES statement did not produce an error when it
failed.
(Bug#21226)
This is a bugfix release for the current MySQL Community Server production release family. It replaces MySQL 5.0.51b.
Functionality added or changed:
Security Enhancement:
To enable stricter control over the location from which
user-defined functions can be loaded, the
plugin_dir system variable has
been backported from MySQL 5.1. If the value is nonempty,
user-defined function object files can be loaded only from the
directory named by this variable. If the value is empty, the
behavior that is used prior to the inclusion of
plugin_dir applies: The UDF
object files must be located in a directory that is searched by
your system's dynamic linker.
(Bug#37428)
Important Change: Incompatible Change:
The FEDERATED storage engine is now disabled
by default in the .cnf files shipped with
MySQL distributions (my-huge.cnf,
my-medium.cnf, and so forth). This affects
server behavior only if you install one of these files.
(Bug#37069)
Cluster API: Important Change:
Because NDB_LE_MemoryUsage.page_size_kb shows
memory page sizes in bytes rather than kilobytes, it has been
renamed to page_size_bytes. The name
page_size_kb is now deprecated and thus
subject to removal in a future release, although it currently
remains supported for reasons of backward compatibility. See
The Ndb_logevent_type Type, for more information about
NDB_LE_MemoryUsage.
(Bug#30271)
Important Change:
Some changes were made to
CHECK TABLE ... FOR
UPGRADE and REPAIR
TABLE with respect to detection and handling of tables
with incompatible .frm files (files created
with a different version of the MySQL server). These changes
also affect mysqlcheck because that program
uses CHECK TABLE and
REPAIR TABLE, and thus also
mysql_upgrade because that program invokes
mysqlcheck.
If your table was created by a different version of the
MySQL server than the one you are currently running,
CHECK TABLE ...
FOR UPGRADE indicates that the table has an
.frm file with an incompatible version.
In this case, the result set returned by
CHECK TABLE contains a line
with a Msg_type value of
error and a Msg_text
value of Table upgrade required. Please do "REPAIR
TABLE `
tbl_name`" to fix
it!
REPAIR TABLE without
USE_FRM upgrades the
.frm file to the current version.
If you use REPAIR TABLE ...USE_FRM and
your table was created by a different version of the MySQL
server than the one you are currently running,
REPAIR TABLE will not attempt
to repair the table. In this case, the result set returned
by REPAIR TABLE contains a
line with a Msg_type value of
error and a Msg_text
value of Failed repairing incompatible .FRM
file.
Previously, use of REPAIR TABLE
...USE_FRM with a table created by a different
version of the MySQL server risked the loss of all rows in
the table.
mysql_upgrade now has a
--tmpdir option to enable
the location of temporary files to be specified.
(Bug#36469)
mysql-test-run.pl now supports
--client-bindir and
--client-libdir options for specifying the
directory where client binaries and libraries are located.
(Bug#34995)
The ndbd and ndb_mgmd man pages have been reclassified from volume 1 to volume 8. (Bug#34642)
For binary .tar.gz packages,
mysqld and other binaries now are compiled
with debugging symbols included to enable easier use with a
debugger. If you do not need debugging symbols and are short on
disk space, you can use strip to remove the
symbols from the binaries.
(Bug#33252)
mysqldump produces a -- Dump
completed on comment
at the end of the dump if
DATE--comments is given. The date
causes dump files for identical data take at different times to
appear to be different. The new options
--dump-date and
--skip-dump-date
control whether the date is added to the comment.
--skip-dump-date
suppresses date printing. The default is
--dump-date (include the date
in the comment).
(Bug#31077)
mysqltest now has mkdir
and rmdir commands for creating and removing
directories.
(Bug#31004)
The mysql_odbc_escape_string() C API
function has been removed. It has multi-byte character escaping
issues, doesn't honor the
NO_BACKSLASH_ESCAPES SQL mode
and is not needed anymore by Connector/ODBC as of 3.51.17.
(Bug#29592)
The default value of the
connect_timeout system variable
was increased from 5 to 10 seconds. This might help in cases
where clients frequently encounter errors of the form
Lost connection to MySQL server at
'.
(Bug#28359)XXX', system error:
errno
The use of InnoDB hash indexes now can be
controlled by setting the new
innodb_adaptive_hash_index
system variable at server startup. By default, this variable is
enabled. See Section 13.2.10.4, “Adaptive Hash Indexes”.
The argument for the mysql-test-run.pl
--do-test and --skip-test
options is now interpreted as a Perl regular expression if there
is a pattern metacharacter in the argument value. This allows
more flexible specification of which tests to perform or skip.
Bugs fixed:
Performance:
InnoDB adaptive hash latches could be held
too long during filesort operations, resulting in a server
crash. Now the hash latch is released when a query on
InnoDB tables performs a filesort. This
eliminates the crash and may provide significant performance
improvements on systems on which many queries using filesorts
with temporary tables are being performed.
(Bug#32149)
Important Change: Security Fix:
It was possible to circumvent privileges through the creation of
MyISAM tables employing the DATA
DIRECTORY and INDEX DIRECTORY
options to overwrite existing table files in the MySQL data
directory. Use of the MySQL data directory in DATA
DIRECTORY and INDEX DIRECTORY path
name is now disallowed.
Additional fixes were made in MySQL 5.0.70.
See also Bug#39277.
Security Fix: Three vulnerabilities in yaSSL versions 1.7.5 and earlier were discovered that could lead to a server crash or execution of unauthorized code. The exploit requires a server with yaSSL enabled and TCP/IP connections enabled, but does not require valid MySQL account credentials. The exploit does not apply to OpenSSL.
The proof-of-concept exploit is freely available on the Internet. Everyone with a vulnerable MySQL configuration is advised to upgrade immediately.
Security Fix:
Using RENAME TABLE against a
table with explicit DATA DIRECTORY and
INDEX DIRECTORY options can be used to
overwrite system table information by replacing the symbolic
link points. the file to which the symlink points.
MySQL will now return an error when the file to which the symlink points already exists. (Bug#32111, CVE-2007-5969)
Security Fix:
ALTER VIEW retained the original
DEFINER value, even when altered by another
user, which could allow that user to gain the access rights of
the view. Now ALTER VIEW is
allowed only to the original definer or users with the
SUPER privilege.
(Bug#29908)
Security Fix:
When using a FEDERATED table, the local
server could be forced to crash if the remote server returned a
result with fewer columns than expected.
(Bug#29801)
Security Enhancement: It was possible to force an error message of excessive length which could lead to a buffer overflow. This has been made no longer possible as a security precaution. (Bug#32707)
Incompatible Change:
It was possible to use FRAC_SECOND as a
synonym for MICROSECOND with
DATE_ADD(),
DATE_SUB(), and
INTERVAL; now, using
FRAC_SECOND with anything other than
TIMESTAMPADD() or
TIMESTAMPDIFF() produces a syntax
error.
It is now possible (and preferable) to use
MICROSECOND with
TIMESTAMPADD() and
TIMESTAMPDIFF(), and
FRAC_SECOND is now deprecated.
(Bug#33834)
Incompatible Change:
With ONLY_FULL_GROUP_BY SQL
mode enabled, queries such as SELECT a FROM t1 HAVING
COUNT(*)>2 were not being rejected as they should
have been.
This fix results in the following behavior:
There is a check against mixing group and nongroup columns
only when
ONLY_FULL_GROUP_BY is
enabled.
This check is done both for the select list and for the
HAVING clause if there is one.
This behavior differs from previous versions as follows:
Previously, the HAVING clause was not
checked when
ONLY_FULL_GROUP_BY was
enabled; now it is checked.
Previously, the select list was checked even when
ONLY_FULL_GROUP_BY was not
enabled; now it is checked only when
ONLY_FULL_GROUP_BY is
enabled.
Incompatible Change: The MySQL 5.0.50 patch for this bug was reverted because it changed the behavior of a General Availability MySQL release. (Bug#30234)
See also Bug#27525.
Incompatible Change: It was possible to create a view having a column whose name consisted of an empty string or space characters only.
One result of this bug fix is that aliases for columns in the
view SELECT statement are checked to ensure
that they are legal column names. In particular, the length must
be within the maximum column length of 64 characters, not the
maximum alias length of 256 characters. This can cause problems
for replication or loading dump files. For additional
information and workarounds, see
Section D.4, “Restrictions on Views”.
(Bug#27695)
See also Bug#31202.
Incompatible Change:
Several type-preserving functions and operators returned an
incorrect result type that does not match their argument types:
COALESCE(),
IF(),
IFNULL(),
LEAST(),
GREATEST(),
CASE. These now aggregate using the
precise SQL types of their arguments rather than the internal
type. In addition, the result type of the
STR_TO_DATE() function is now
DATETIME by default.
(Bug#27216)
Incompatible Change: It was possible for option files to be read twice at program startup, if some of the standard option file locations turned out to be the same directory. Now duplicates are removed from the list of files to be read.
Also, users could not override system-wide settings using
~/.my.cnf because
SYSCONFDIR/my.cnf~/.my.cnf can override system-wide
settings.
The fix for this problem had a side effect such that on Unix,
MySQL programs looked for options in
~/my.cnf rather than the standard location
of ~/.my.cnf. That problem was addressed as
Bug#38180.
(Bug#20748)
Important Change: MySQL Cluster:
AUTO_INCREMENT columns had the following
problems when used in NDB tables:
The AUTO_INCREMENT counter was not
updated correctly when such a column was updated.
AUTO_INCREMENT values were not
prefetched beyond statement boundaries.
AUTO_INCREMENT values were not handled
correctly with
INSERT
IGNORE statements.
After being set,
ndb_autoincrement_prefetch_sz
showed a value of 1, regardless of the value it had
actually been set to.
As part of this fix, the behavior of
ndb_autoincrement_prefetch_sz
has changed. Setting this to less than 32 no longer has any
effect on prefetching within statements (where IDs are now
always obtained in batches of 32 or more), but only between
statements. The default value for this variable has also
changed, and is now 1.
(Bug#25176, Bug#31956, Bug#32055)
Important Change: Replication:
When the master crashed during an update on a transactional
table while in autocommit mode,
the slave failed. This fix causes every transaction (including
autocommit transactions) to be
recorded in the binlog as starting with a
BEGIN and
ending with a COMMIT or
ROLLBACK.
(Bug#26395)
Important Change:
The server no longer issues warnings for truncation of excess
spaces for values inserted into
CHAR columns. This reverts a
change in the previous release that caused warnings to be
issued.
(Bug#30059)
Replication: Important Note: Network timeouts between the master and the slave could result in corruption of the relay log. This fix rectifies a long-standing replication issue when using unreliable networks, including replication over wide area networks such as the Internet. If you experience reliability issues and see many You have an error in your SQL syntax errors on replication slaves, we strongly recommend that you upgrade to a MySQL version which includes this fix. (Bug#26489)
MySQL Cluster:
When configured with NDB support,
MySQL failed to compile using gcc 4.3 on
64bit FreeBSD systems.
(Bug#34169)
MySQL Cluster: The failure of a DDL statement could sometimes lead to node failures when attempting to execute subsequent DDL statements. (Bug#34160)
MySQL Cluster:
Extremely long SELECT statements
(where the text of the statement was in excess of 50000
characters) against NDB tables
returned empty results.
(Bug#34107)
MySQL Cluster:
A periodic failure to flush the send buffer by the
NDB TCP transporter could cause a
unnecessary delay of 10 ms between operations.
(Bug#34005)
MySQL Cluster:
When all data and SQL nodes in the cluster were shut down
abnormally (that is, other than by using STOP
in the cluster management client), ndb_mgm
used excessive amounts of CPU.
(Bug#33237)
MySQL Cluster:
An improperly reset internal signal was observed as a hang when
using events in the NDB API but
could result in various errors.
(Bug#33206)
MySQL Cluster: Incorrectly handled parameters could lead to a crash in the Transaction Coordinator during a node failure, causing other data nodes to fail. (Bug#33168)
MySQL Cluster: The failure of a master node could lead to subsequent failures in local checkpointing. (Bug#32160)
MySQL Cluster:
An uninitialized variable in the
NDB storage engine code led to
AUTO_INCREMENT failures when the server was
compiled with gcc 4.2.1.
(Bug#31848)
This regression was introduced by Bug#27437.
MySQL Cluster:
An error with an if statement in
sql/ha_ndbcluster.cc could potentially lead
to an infinite loop in case of failure when working with
AUTO_INCREMENT columns in
NDB tables.
(Bug#31810)
MySQL Cluster:
The NDB storage engine code was not
safe for strict-alias optimization in gcc
4.2.1.
(Bug#31761)
MySQL Cluster:
Primary keys on variable-length columns (such as
VARCHAR) did not work correctly.
(Bug#31635)
MySQL Cluster: Transaction atomicity was sometimes not preserved between reads and inserts under high loads. (Bug#31477)
MySQL Cluster:
Numerous NDBCLUSTER test failures
occurred in builds compiled using icc on IA64
platforms.
(Bug#31239)
MySQL Cluster: Transaction timeouts were not handled well in some circumstances, leading to excessive number of transactions being aborted unnecessarily. (Bug#30379)
MySQL Cluster: Having tables with a great many columns could cause Cluster backups to fail. (Bug#30172)
MySQL Cluster:
Issuing an
INSERT ...
ON DUPLICATE KEY UPDATE concurrently with or following
a TRUNCATE statement on an
NDB table failed with
NDB error 4350
Transaction already aborted.
(Bug#29851)
MySQL Cluster: In some cases, the cluster managment server logged entries multiple times following a restart of mgmd. (Bug#29565)
MySQL Cluster: An interpreted program of sufficient size and complexity could cause all cluster data nodes to shut down due to buffer overruns. (Bug#29390)
MySQL Cluster:
It was possible in config.ini to define
cluster nodes having node IDs greater than the maximum allowed
value.
(Bug#28298)
MySQL Cluster:
UPDATE IGNORE could sometimes fail on
NDB tables due to the use of
unitialized data when checking for duplicate keys to be ignored.
(Bug#25817)
MySQL Cluster:
When inserting a row into an NDB
table with a duplicate value for a nonprimary unique key, the
error issued would reference the wrong key.
This improves on an initial fix for this issue made in MySQL 5.0.30 and MySQL 5.0.33 (Bug#21072)
Replication: Some kinds of internal errors, such as Out of memory errors, could cause the server to crash when replicating statements with user variables.
certain internal errors. (Bug#37150)
Replication:
CREATE PROCEDURE and
CREATE FUNCTION statements
containing extended comments were not written to the binary log
correctly, causing parse errors on the slave.
(Bug#36570)
See also Bug#32575.
Replication:
insert_id was not written to
the binary log for inserts into BLACKHOLE
tables.
(Bug#35178)
Replication: The character sets and collations used for constant identifiers in stored procedures were not replicated correctly. (Bug#34289)
Replication:
A CREATE USER,
DROP USER, or
RENAME USER statement that fails
on the master, or that is a duplicate of any of these
statements, is no longer written to the binlog; previously,
either of these occurrences could cause the slave to fail.
See also Bug#29749.
Replication:
SHOW BINLOG EVENTS could fail
when the binlog contained one or more events whose size was
close to the value of
max_allowed_packet.
(Bug#33413)
Replication:
An extraneous
ROLLBACK
statement was written to the binary log by a connection that did
not use any transactional tables.
(Bug#33329)
Replication:
When a stored routine or trigger, running on a master that used
MySQL 5.0 or MySQL 5.1.11 or earlier, performed an insert on an
AUTO_INCREMENT column, the
insert_id value was not
replicated correctly to a slave running MySQL 5.1.12 or later
(including any MySQL 6.0 release).
(Bug#33029)
See also Bug#19630.
Replication:
CREATE VIEW statements containing
extended comments were not written to the binary log correctly,
causing parse errors on the slave. Now, all comments are
stripped from such statements before being written to the binary
log.
(Bug#32575)
See also Bug#36570.
Replication:
SQL statements containing comments using --
syntax were not replayable by mysqlbinlog,
even though such statements replicated correctly.
(Bug#32205)
Replication: It was possible for the name of the relay log file to exceed the amount of memory reserved for it, possibly leading to a crash of the server. (Bug#31836)
See also Bug#28597.
Replication: Corruption of log events caused the server to crash on 64-bit Linux systems having 4 GB of memory or more. (Bug#31793)
Replication:
Use of the @@hostname system variable in
inserts in mysql_system_tables_data.sql did
not replicate. The workaround is to select its value into a user
variable (which does replicate) and insert that.
(Bug#31167)
Replication:
STOP SLAVE did not stop
connection attempts properly. If the IO slave thread was
attempting to connect, STOP SLAVE
waited for the attempt to finish, sometimes for a long period of
time, rather than stopping the slave immediately.
(Bug#31024)
See also Bug#30932.
Replication:
Issuing a DROP VIEW statement
caused replication to fail if the view did not actually exist.
(Bug#30998)
Replication: One thread could read uninitialized memory from the stack of another thread. This issue was only known to occur in a mysqld process acting as both a master and a slave. (Bug#30752)
Replication:
Replication of LOAD
DATA INFILE could fail when
read_buffer_size was larger
than max_allowed_packet.
(Bug#30435)
Replication:
Setting server_id did not
update its value for the current session.
(Bug#28908)
Replication: Due a previous change in how the default name and location of the binary log file were determined, replication failed following some upgrades. (Bug#28597, Bug#28603)
See also Bug#31836.
This regression was introduced by Bug#20166.
Replication:
MASTER_POS_WAIT() did not return
NULL when the server was not a slave.
(Bug#26622)
Replication:
Stored procedures having BIT
parameters were not replicated correctly.
(Bug#26199)
Replication:
Issuing SHOW SLAVE STATUS as
mysqld was shutting down could cause a crash.
(Bug#26000)
Replication:
An UPDATE statement using a
stored function that modified a nontransactional table was not
logged if it failed. This caused the copy of the
nontransactional table on the master have a row that the copy on
the slave did not.
In addition, when an
INSERT ...
ON DUPLICATE KEY UPDATE statement encountered a
duplicate key constraint, but the
UPDATE did not actually change
any data, the statement was not logged. As a result of this fix,
such statements are now treated the same for logging purposes as
other UPDATE statements, and so
are written to the binary log.
(Bug#23333)
See also Bug#12713.
Replication:
The nonspecific error message Wrong parameters to
function register_slave resulted when
START SLAVE failed to register on
the master due to excess length of any the slave server options
--report-host,
--report-user, or
--report-password. An error
message specific to each of these options is now returned in
such cases. The new error messages are:
Failed to register slave: too long 'report-host'
Failed to register slave: too long 'report-user'
Failed to register slave; too long 'report-password'
See also Bug#19328.
Replication:
A replication slave sometimes failed to reconnect because it was
unable to run SHOW SLAVE HOSTS.
It was not necessary to run this statement on slaves (since the
master should track connection IDs), and the execution of this
statement by slaves was removed.
(Bug#21132)
Replication:
PURGE BINARY LOGS TO and PURGE
BINARY LOGS BEFORE did not handle missing binary log
files correctly or in the same way. Now for both of these
statements, if any files listed in the
.index file are missing from the file
system, the statement fails with an error.
(Bug#18199, Bug#18453)
Replication:
START SLAVE UNTIL
MASTER_LOG_POS=
issued on a slave that was using
position--log-slave-updates and that was
involved in circular replication would cause the slave to run
and stop one event later than that specified by the value of
position.
(Bug#13861)
Cluster API:
When reading a BIT(64) value using
NdbOperation:getValue(), 12 bytes were
written to the buffer rather than the expected 8 bytes.
(Bug#33750)
The fix for Bug#20748 caused a problem such that on Unix, MySQL
programs looked for options in ~/my.cnf
rather than the standard location of
~/.my.cnf.
(Bug#38180)
The fix for Bug#33812 had the side effect of causing the mysql client not to be able to read some dump files produced with mysqldump. To address this, that fix was reverted. (Bug#38158)
Some binary distributions had a duplicate “-64bit” suffix in the file name. (Bug#37623)
On Windows 64-bit systems, temporary variables of
long types were used to store
ulong values, causing key cache
initialization to receive distorted parameters. The effect was
that setting key_buffer_size to
values of 2GB or more caused memory exhaustion to due allocation
of too much memory.
(Bug#36705)
Multiple-table UPDATE statements
that used a temporary table could fail to update all qualifying
rows or fail with a spurious duplicate-key error.
(Bug#36676)
A REGEXP match could return
incorrect rows when the previous row matched the expression and
used CONCAT() with an empty
string.
(Bug#36488)
mysqltest ignored the value of
--tmpdir in one place.
(Bug#36465)
The mysql client failed to recognize comment
lines consisting of -- followed by a newline.
(Bug#36244)
Conversion of a FLOAT ZEROFILL value to
string could cause a server crash if the value was
NULL.
(Bug#36139)
On Windows, the installer attempted to use JScript to determine whether the target data directory already existed. On Windows Vista x64, this resulted in an error because the installer was attempting to run the JScript in a 32-bit engine, which wasn't registered on Vista. The installer no longer uses JScript but instead relies on a native WiX command. (Bug#36103)
An error in calculation of the precision of zero-length items
(such as NULL) caused a server crash for
queries that employed temporary tables.
(Bug#36023)
For EXPLAIN EXTENDED, execution of an
uncorrelated IN subquery caused a crash if
the subquery required a temporary table for its execution.
(Bug#36011)
The server crashed inside NOT IN subqueries
with an impossible WHERE or
HAVING clause, such as NOT IN
(SELECT ... FROM t1, t2, ... WHERE 0).
(Bug#36005)
Grouping or ordering of long values in unindexed
BLOB or
TEXT columns with the
gbk or big5 character set
crashed the server.
(Bug#35993)
SET GLOBAL debug='' resulted in a Valgrind
warning in DbugParse(), which was reading
beyond the end of the control string.
(Bug#35986)
An empty bit-string literal (b'') caused a
server crash. Now the value is parsed as an empty bit value
(which is treated as an empty string in string context or 0 in
numeric context).
(Bug#35658)
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)
There was a memory leak when connecting to a
FEDERATED table using a connection string
that had a host value of localhost or omitted
the host and a port value of 0 or omitted the
port.
(Bug#35509)
The code for detecting a byte order mark (BOM) caused mysql to crash for empty input. (Bug#35480)
Using LOAD DATA
INFILE with a view could crash the server.
(Bug#35469)
The combination of
GROUP_CONCAT(),
DISTINCT, and LEFT JOIN
could crash the server when the right table is empty.
(Bug#35298)
When a view containing a reference to DUAL
was created, the reference was removed when the definition was
stored, causing some queries against the view to fail with
invalid SQL syntax errors.
(Bug#35193)
Debugging symbols were missing for some executables in Windows binary distributions. (Bug#35104)
A query that performed a
ref_or_null join where the
second table used a key having one or columns that could be
NULL and had a column value that was
NULL caused the server to crash.
(Bug#34945)
This regression was introduced by Bug#12144.
Some binaries produced stack corruption messages due to being built with versions of bison older than 2.1. Builds are now created using bison 2.3. (Bug#34926)
mysqldump failed to return an error code when
using the --master-data option
without binary logging being enabled on the server.
(Bug#34909)
Under some circumstances, the value of
mysql_insert_id() following a
SELECT ... INSERT statement could return an
incorrect value. This could happen when the last SELECT
... INSERT did not involve an
AUTO_INCREMENT column, but the value of
mysql_insert_id() was changed by
some previous statements.
(Bug#34889)
Table and database names were mixed up in some places of the subquery transformation procedure. This could affect debugging trace output and further extensions of that procedure. (Bug#34830)
A malformed URL used for a FEDERATED
table's CONNECTION option value in a
CREATE TABLE statement was not
handled correctly and could crash the server.
(Bug#34788)
Queries such as SELECT ROW(1, 2) IN (SELECT t1.a, 2)
FROM t1 GROUP BY t1.a (combining row constructors and
subqueries in the FROM clause) could lead to
assertion failure or unexpected error messages.
(Bug#34763)
Using NAME_CONST() with a negative number and
an aggregate function caused MySQL to crash. This could also
have a negative impact on replication.
(Bug#34749)
A memory-handling error associated with use of
GROUP_CONCAT() in subqueries
could result in a server crash.
(Bug#34747)
For an indexed integer column
col_name and a value
N that is one greater than the
maximum value allowed for the data type of
col_name, conditions of the form
WHERE failed to return rows
where the value of col_name <
Ncol_name is
N - 1
Executing a TRUNCATE statement on
a table having both a foreign key reference and a
DELETE trigger crashed the
server.
(Bug#34643)
Some subqueries using an expression that included an aggregate function could fail or in some cases lead to a crash of the server. (Bug#34620)
A server crash could occur if
INFORMATION_SCHEMA tables built in memory
were swapped out to disk during query execution.
(Bug#34529)
CAST(AVG( produced incorrect results for
non-arg) AS
DECIMAL)DECIMAL arguments.
(Bug#34512)
mysql_explain_log concatenated multiple-line
statements, causing malformed results for statements that
contained SQL comments beginning with --.
(Bug#34339)
Executing an ALTER VIEW statement
on a table crashed the server.
(Bug#34337)
Several additional configuration scripts in the
BUILD directory now are included in source
distributions. These may be useful for users who wish to build
MySQL from source. (See
Section 2.16.3, “Installing from the Development Source Tree”, for information about
what they do.)
(Bug#34291)
Under some conditions, a SET GLOBAL
innodb_commit_concurrency or SET GLOBAL
innodb_autoextend_increment statement could fail.
(Bug#34223)
mysqldump attempts to set the
character_set_results system
variable after connecting to the server. This failed for pre-4.1
servers that have no such variable, but
mysqldump did not account for this and 1)
failed to dump database contents; 2) failed to produce any error
message alerting the user to the problem.
(Bug#34192)
mysql_install_db failed if the server was
running with an SQL mode of
TRADITIONAL. This program now
resets the SQL mode internally to avoid this problem.
(Bug#34159)
For a FEDERATED table with an index on a
nullable column, accessing the table could crash a server,
return an incorrect result set, or return ERROR 1030
(HY000): Got error 1430 from storage engine.
(Bug#33946)
Passing anything other than an integer argument to a
LIMIT clause in a prepared statement would
fail. (This limitation was introduced to avoid replication
problems; for example, replicating the statement with a string
argument would cause a parse failure in the slave). Now,
arguments to the LIMIT clause are converted
to integer values, and these converted values are used when
logging the statement.
(Bug#33851)
An internal buffer in mysql was too short. Overextending it could cause stack problems or segmentation violations on some architectures. (This is not a problem that could be exploited to run arbitrary code.) (Bug#33841)
A query using WHERE
(column1=', where
string1' AND
column2=constant1) OR
(column1='string2' AND
column2=constant2)col1 used a binary collation and
string1 matched
string2 except for case, failed to
match any records even when matches were found by a query using
the equivalent clause WHERE
column2=.
(Bug#33833)constant1 OR
column2=constant2
The mysql client incorrectly parsed statements containing the word “delimiter” in mid-statement.
The fix for this bug had the side effect of causing the problem reported in Bug#38158, so it was reverted in MySQL 5.0.67. (Bug#33812)
Large unsigned integers were improperly handled for prepared statements, resulting in truncation or conversion to negative numbers. (Bug#33798)
Reuse of prepared statements could cause a memory leak in the embedded server. (Bug#33796)
The server crashed when executing a query that had a subquery
containing an equality X=Y where Y referred to a named select
list expression from the parent select. The server crashed when
trying to use the X=Y equality for
ref-based access.
(Bug#33794)
Some queries using a combination of IN,
CONCAT(), and an implicit type
conversion could return an incorrect result.
(Bug#33764)
In some cases a query that produced a result set when using
ORDER BY ASC did not return any results when
this was changed to ORDER BY DESC.
(Bug#33758)
Disabling concurrent inserts caused some cacheable queries not to be saved in the query cache. (Bug#33756)
Use of uninitialized memory for filesort in a
subquery caused a server crash.
(Bug#33675)
The server could crash when
REPEAT
or another control instruction was used in conjunction with
labels and a
LEAVE
instruction.
(Bug#33618)
The parser allowed control structures in compound statements to have mismatched beginning and ending labels. (Bug#33618)
make_binary_distribution passed the
--print-libgcc-file option to the C compiler,
but this does not work with the ICC compiler.
(Bug#33536)
Certain combinations of views, subselects with outer references and stored routines or triggers could cause the server to crash. (Bug#33389)
SET GLOBAL myisam_max_sort_file_size=DEFAULT
set myisam_max_sort_file_size
to an incorrect value.
(Bug#33382)
See also Bug#31177.
SLEEP(0) failed to return on
64-bit Mac OS X due to a bug in
pthread_cond_timedwait().
(Bug#33304)
CREATE TABLE ...
SELECT created tables that for date columns used the
obsolete Field_date type instead of
Field_newdate.
(Bug#33256)
Granting the UPDATE privilege on
one column of a view caused the server to crash.
(Bug#33201)
For DECIMAL columns used with the
ROUND(
or
X,D)TRUNCATE(
function with a nonconstant value of
X,D)D, adding an ORDER
BY for the function result produced misordered output.
(Bug#33143)
Some valid SELECT statements
could not be used as views due to incorrect column reference
resolution.
(Bug#33133)
The fix for Bug#11230 and Bug#26215 introduced a significant input-parsing slowdown for the mysql client. This has been corrected. (Bug#33057)
When MySQL was built with OpenSSL, the SSL library was not properly initialized with information of which endpoint it was (server or client), causing connection failures. (Bug#33050)
Under some circumstances a combination of aggregate functions
and GROUP BY in a
SELECT query over a view could
lead to incorrect calculation of the result type of the
aggregate function. This in turn could lead to incorrect
results, or to crashes on debug builds of the server.
(Bug#33049)
For DISTINCT queries, MySQL 4.0 and 4.1
stopped reading joined tables as soon as the first matching row
was found. However, this optimization was lost in MySQL 5.0,
which instead read all matching rows. This fix for this
regression may result in a major improvement in performance for
DISTINCT queries in cases where many rows
match.
(Bug#32942)
The server was built even when configure was
run with the --without-server
option.
(Bug#32898)
See also Bug#23973.
Repeated creation and deletion of views within prepared statements could eventually crash the server. (Bug#32890)
See also Bug#34587.
UNION constructs cannot contain
SELECT ... INTO except in the final
SELECT. However, if a
UNION was used in a subquery and
an INTO clause appeared in the top-level
query, the parser interpreted it as having appeared in the
UNION and raised an error.
(Bug#32858)
The correct data type for a NULL column
resulting from a UNION could be
determined incorrectly in some cases: 1) Not correctly inferred
as NULL depending on the number of selects;
2) Not inferred correctly as NULL if one
select used a subquery.
(Bug#32848)
An ORDER BY query using IS
NULL in the WHERE clause did not
return correct results.
(Bug#32815)
For queries containing GROUP_CONCAT(DISTINCT
, there was a
limitation that the col_list ORDER BY
col_list)DISTINCT columns had to
be the same as ORDER BY columns. Incorrect
results could be returned if this was not true.
(Bug#32798)
Incorrect assertions could cause a server crash for
DELETE triggers for transactional
tables.
(Bug#32790)
Use of the cp932 character set with
CAST() in an ORDER
BY clause could cause a server crash.
(Bug#32726)
Inserting strings with a common prefix into a table that used
the ucs2 character set corrupted the table.
(Bug#32705)
A subquery using an IS NULL check of a column
defined as NOT NULL in a table used in the
FROM clause of the outer query produced an
invalid result.
(Bug#32694)
Specifying a nonexistent column for an
INSERT DELAYED statement caused a
server crash rather than producing an error.
(Bug#32676)
Use of CLIENT_MULTI_QUERIES caused
libmysqld to crash.
(Bug#32624)
The INTERVAL() function
incorrectly handled NULL values in the value
list.
(Bug#32560)
Use of a NULL-returning GROUP
BY expression in conjunction with WITH
ROLLUP could cause a server crash.
(Bug#32558)
See also Bug#31095.
A SELECT ... GROUP BY
query failed
with an assertion if the length of the
bit_columnBIT column used for the
GROUP BY was not an integer multiple of 8.
(Bug#32556)
Using SELECT INTO OUTFILE with 8-bit
ENCLOSED BY characters led to corrupted data
when the data was reloaded using LOAD DATA INFILE. This was
because SELECT INTO OUTFILE failed to escape
the 8-bit characters.
(Bug#32533)
For FLUSH TABLES WITH
READ LOCK, the server failed to properly detect
write-locked tables when running with low-priority updates,
resulting in a crash or deadlock.
(Bug#32528)
A build problem introduced in MySQL 5.0.52 was resolved: The x86 32-bit Intel icc-compiled server binary had unwanted dependences on Intel icc runtime libraries. (Bug#32514)
Queries using LIKE on tables having indexed
CHAR columns using either of the
eucjpms or ujis character
sets did not return correct results.
(Bug#32510)
The rules for valid column names were being applied differently for base tables and views. (Bug#32496)
Sending several KILL
QUERY statements to target a connection running
SELECT SLEEP() could freeze the server.
(Bug#32436)
ssl-cipher values in option files were not
being read by libmysqlclient.
(Bug#32429)
Repeated execution of a query containing a
CASE
expression and numerous AND and
OR relations could crash the server. The root
cause of the issue was determined to be that the internal
SEL_ARG structure was not properly
initialized when created.
(Bug#32403)
Referencing within a subquery an alias used in the
SELECT list of the outer query
was incorrectly permitted.
(Bug#32400)
An ORDER BY query on a view created using a
FEDERATED table as a base table caused the
server to crash.
(Bug#32374)
Comparison of a BIGINT NOT NULL column with a
constant arithmetic expression that evaluated to NULL mistakenly
caused the error Column '...' cannot be
null (error 1048).
(Bug#32335)
Assigning a 65,536-byte string to a
TEXT column (which can hold a
maximum of 65,535 bytes) resulted in truncation without a
warning. Now a truncation warning is generated.
(Bug#32282)
The LAST_DAY() function returns a
DATE value, but internally the
value did not have the time fields zeroed and calculations
involving the value could return incorrect results.
(Bug#32270)
MIN() and
MAX() could return incorrect
results when an index was present if a loose index scan was
used.
(Bug#32268)
Executing a prepared statement associated with a materialized cursor sent to the client a metadata packet with incorrect table and database names. The problem occurred because the server sent the name of the temporary table used by the cursor instead of the table name of the original table.
The same problem occured when selecting from a view, in which case the name of the table name was sent, rather than the name of the view. (Bug#32265)
Memory corruption could occur due to large index map in
Range checked for each record status reported
by EXPLAIN
SELECT. The problem was based in an incorrectly
calculated length of the buffer used to store a hexadecimal
representation of an index map, which could result in buffer
overrun and stack corruption under some circumstances.
(Bug#32241)
Various test program cleanups were made: 1)
mytest and libmysqltest
were removed. 2) bug25714 displays an error
message when invoked with incorrect arguments or the
--help option. 3)
mysql_client_test exits cleanly with a proper
error status.
(Bug#32221)
The default grant tables on Windows contained information for
host production.mysql.com, which should not
be there.
(Bug#32219)
Under certain conditions, the presence of a GROUP
BY clause could cause an ORDER BY
clause to be ignored.
(Bug#32202)
For comparisons of the form date_col OP
datetime_const (where
OP is
=,
<,
>,
<=,
or
>=),
the comparison is done using
DATETIME values, per the fix for
Bug#27590. However that fix caused any index on
date_col not to be used and
compromised performance. Now the index is used again.
(Bug#32198)
DATETIME arguments specified in
numeric form were treated by
DATE_ADD() as
DATE values.
(Bug#32180)
InnoDB does not support
SPATIAL indexes, but could crash when asked
to handle one. Now an error is returned.
(Bug#32125)
The server crashed on optimizations involving a join of
INT and
MEDIUMINT columns and a system
variable in the WHERE clause.
(Bug#32103)
SHOW STATUS caused a server crash
if InnoDB had not been initialized.
(Bug#32083)
With lower_case_table_names
set, CREATE TABLE LIKE was treated
differently by libmysqld than by the
nonembedded server.
(Bug#32063)
Within a subquery, UNION was
handled differently than at the top level, which could result in
incorrect results or a server crash.
(Bug#32036, Bug#32051)
User-defined functions are not loaded if the server is started
with the --skip-grant-tables
option, but the server did not properly handle this case and
issued an Out of memory error message
instead.
(Bug#32020)
HOUR(),
MINUTE(), and
SECOND() could return nonzero
values for DATE arguments.
(Bug#31990)
A column with malformed multi-byte characters could cause the full-text parser to go into an infinite loop. (Bug#31950)
Changing the SQL mode to cause dates with “zero”
parts to be considered invalid (such as
'1000-00-00') could result in indexed and
nonindexed searches returning different results for a column
that contained such dates.
(Bug#31928)
Queries testing numeric constants containing leading zeroes
against ZEROFILL columns were not evaluated
correctly.
(Bug#31887)
In debug builds, testing the result of an IN
subquery against NULL caused an assertion
failure.
(Bug#31884)
mysql-test-run.pl sometimes set up test scenarios in which the same port number was passed to multiple servers, causing one of them to be unable to start. (Bug#31880)
Comparison results for BETWEEN were
different from those for operators like
< and
> for
DATETIME-like values with
trailing extra characters such as '2007-10-01 00:00:00
GMT-6'. BETWEEN treated
the values as DATETIME, whereas
the other operators performed a binary-string comparison. Now
they all uniformly use a DATETIME
comparison, but generate warnings for values with trailing
garbage.
(Bug#31800)
Name resolution for correlated subqueries and
HAVING clauses failed to distinguish which of
two was being performed when there was a reference to an outer
aliased field. This could result in error messages about a
HAVING clause for queries that had no such
clause.
(Bug#31797)
If an error occurred during file creation, the server sometimes did not remove the file, resulting in an unused file in the file system. (Bug#31781)
The server could crash during filesort for
ORDER BY based on expressions with
INET_NTOA() or
OCT() if those functions returned
NULL.
(Bug#31758)
For a fatal error during a filesort in
find_all_keys(), the error was returned
without the necessary handler uninitialization, causing an
assertion failure.
(Bug#31742)
The examined-rows count was not incremented for
const queries.
(Bug#31700)
The mysql_change_user() C API
function was subject to buffer overflow.
(Bug#31669)
For SELECT ... INTO
OUTFILE, if the ENCLOSED BY string
is empty and the FIELDS TERMINATED BY string
started with a special character (one of n,
t, r,
b, 0,
Z, or N), every occurrence
of the character within field values would be duplicated.
(Bug#31663)
SHOW COLUMNS and
DESCRIBE displayed
null as the column type for a view with no
valid definer. This caused mysqldump to
produce a nonreloadable dump file for the view.
(Bug#31662)
The mysqlbug script did not include the
correct values of CFLAGS and
CXXFLAGS that were used to configure the
distribution.
(Bug#31644)
ucs2 does not work as a client character set,
but attempts to use it as such were not rejected. Now
character_set_client cannot be
set to ucs2. This also affects statements
such as SET NAMES and SET CHARACTER
SET.
(Bug#31615)
The server returned the error message Out of memory; restart server and try again when the actual problem was that the sort buffer was too small. Now an appropriate error message is returned in such cases. (Bug#31590)
A buffer used when setting variables was not dimensioned to
accommodate the trailing '\0' byte, so a
single-byte buffer overrun was possible.
(Bug#31588)
HAVING could treat lettercase of table
aliases incorrectly if
lower_case_table_names was
enabled.
(Bug#31562)
The fix for Bug#24989 introduced a problem such that a
NULL thread handler could be used during a
rollback operation. This problem is unlikely to be seen in
practice.
(Bug#31517)
Killing a CREATE TABLE ... LIKE statement
that was waiting for a name lock caused a server crash. When the
statement was killed, the server attempted to release locks that
were not held.
(Bug#31479)
The length of the result from
IFNULL() could be calculated
incorrectly because the sign of the result was not taken into
account.
(Bug#31471)
Queries that used the ref
access method or index-based subquery execution over indexes
that have DECIMAL columns could
fail with an error Column
.
(Bug#31450)col_name cannot be null
SELECT 1 REGEX NULL caused an assertion
failure for debug servers.
(Bug#31440)
Executing RENAME while tables were open for
use with HANDLER statements could
cause a server crash.
(Bug#31409)
mysql-test-run.pl tried to create files in a
directory where it could not be expected to have write
permission. mysqltest created
.reject files in a directory other than the
one where test results go.
(Bug#31398)
For an almost-full MyISAM table, an insert
that failed could leave the table in a corrupt state.
(Bug#31305)
myisamchk --unpack could corrupt a table that when unpacked has static (fixed-length) row format. (Bug#31277)
CONVERT( would fail on invalid input, but processing
was not aborted for the val,
DATETIME)WHERE clause, leading
to a server crash.
(Bug#31253)
Allocation of an insufficiently large group-by buffer following creation of a temporary table could lead to a server crash. (Bug#31249)
Use of DECIMAL( in
n,
n) ZEROFILLGROUP_CONCAT() could cause a
server crash.
(Bug#31227)
When sorting privilege table rows, the server treated escaped
wildcard characters (\% and
\_) the same as unescaped wildcard characters
(% and _), resulting in
incorrect row ordering.
(Bug#31194)
Server variables could not be set to their current values on Linux platforms. (Bug#31177)
See also Bug#6958.
WIth small values of
myisam_sort_buffer_size,
REPAIR TABLE for
MyISAM tables could cause a server crash.
(Bug#31174)
If MAKETIME() returned
NULL when used in an ORDER
BY that was evaluated using
filesort, a server crash could result.
(Bug#31160)
Full-text searches on ucs2 columns caused a
server crash. (FULLTEXT indexes on
ucs2 columns cannot be used, but it should be
possible to perform IN BOOLEAN MODE searches
on ucs2 columns without a crash.)
(Bug#31159)
Data in BLOB or
GEOMETRY columns could be cropped when
performing a UNION query.
(Bug#31158)
An assertion designed to detect a bug in the
ROLLUP implementation would incorrectly be
triggered when used in a subquery context with noncacheable
statements.
(Bug#31156)
Selecting spatial types in a
UNION could cause a server crash.
(Bug#31155)
Use of GROUP_CONCAT(DISTINCT
caused an
assertion failure.
(Bug#31154)bit_column)
The server crashed in the parser when running out of memory. Memory handling in the parser has been improved to gracefully return an error when out-of-memory conditions occur in the parser. (Bug#31153)
MySQL declares a UNIQUE key as a
PRIMARY key if it doesn't have
NULL columns and is not a partial key, and
the PRIMARY key must alway be the first key.
However, in some cases, a nonfirst key could be reported as
PRIMARY, leading to an assert failure by
InnoDB. This is fixed by correcting the key
sort order.
(Bug#31137)
GROUP BY NULL WITH ROLLUP could cause a
server crash.
(Bug#31095)
See also Bug#32558.
REGEXP operations could cause a
server crash for character sets such as ucs2.
Now the arguments are converted to utf8 if
possible, to allow correct results to be produced if the
resulting strings contain only 8-bit characters.
(Bug#31081)
Internal conversion routines could fail for several multi-byte
character sets (big5,
cp932, euckr,
gb2312, sjis) for empty
strings or during evaluation of SOUNDS
LIKE.
(Bug#31069, Bug#31070)
Many nested subqueries in a single query could led to excessive memory consumption and possibly a crash of the server. (Bug#31048)
The MOD() function and the
% operator crashed the server for a divisor
less than 1 with a very long fractional part.
(Bug#31019)
On Windows, the pthread_mutex_trylock()
implementation was incorrect.
(Bug#30992)
A character set introducer followed by a hexadecimal or bit-value literal did not check its argument and could return an ill-formed result for invalid input. (Bug#30986)
CHAR( did not check its
argument and could return an ill-formed result for invalid
input.
(Bug#30982)str USING
charset)
The result from
CHAR() did not add a leading 0x00 byte for input
strings with an odd number of bytes.
(Bug#30981)str USING
ucs2
On Windows, SHOW PROCESSLIST
could display process entries with a State
value of *** DEAD ***.
(Bug#30960)
The GeomFromText() function could
cause a server crash if the first argument was
NULL or the empty string.
(Bug#30955)
MAKEDATE() incorrectly moved year
values in the 100–200 range into the 1970–2069
range. (This is legitimate for 00–99, but three-digit
years should be used unchanged.)
(Bug#30951)
When invoked with constant arguments,
STR_TO_DATE() could use a cached
value for the format string and return incorrect results.
(Bug#30942)
GROUP_CONCAT() returned
',' rather than an empty string when the
argument column contained only empty strings.
(Bug#30897)
ROUND(
or
X,D)TRUNCATE(
for nonconstant values of X,D)D could
crash the server if these functions were used in an
ORDER BY that was resolved using
filesort.
(Bug#30889)
For MEMORY tables, lookups for
NULL values in BTREE
indexes could return incorrect results.
(Bug#30885)
Calling NAME_CONST() with
nonconstant arguments triggered an assertion failure.
Nonconstant arguments are now disallowed.
(Bug#30832)
For a spatial column with a regular
(non-SPATIAL) index, queries failed if the
optimizer tried to use the index.
(Bug#30825)
Values for the --tc-heuristic-recover option
incorrectly were treated as values for the
--myisam-stats-method option.
(Bug#30821)
The optimizer incorrectly optimized conditions out of the
WHERE clause in some queries involving
subqueries and indexed columns.
(Bug#30788)
If an alias was used to refer to the value returned by a stored function within a subselect, the outer select recognized the alias but failed to retrieve the value assigned to it in the subselect. (Bug#30787)
Improper calculation of CASE
expression results could lead to value truncation.
(Bug#30782)
On Windows, the pthread_mutex_trylock()
implementation was incorrect. One symptom was that invalidating
the query cache could cause a server crash.
(Bug#30768)
A multiple-table UPDATE involving
transactional and nontransactional tables caused an assertion
failure.
(Bug#30763)
Under some circumstances,
CREATE TABLE ...
SELECT could crash the server or incorrectly report
that the table row size was too large.
(Bug#30736)
Using the MIN() or
MAX() function to select one part
of a multi-part key could cause a crash when the function result
was NULL.
(Bug#30715)
The optimizer could ignore ORDER BY in cases
when the result set is ordered by filesort,
resulting in rows being returned in incorrect order.
(Bug#30666)
MyISAM tables could not exceed 4294967295
(2^32 - 1) rows on Windows.
(Bug#30638)
mysql-test-run.pl could not run
mysqld with root
privileges.
(Bug#30630)
Binary logging for a stored procedure differed depending on whether or not execution occurred in a prepared statement. (Bug#30604)
For MEMORY tables,
DELETE statements that remove
rows based on an index read could fail to remove all matching
rows.
(Bug#30590)
Using GROUP BY on an expression of the form
timestamp_col DIV
number
The options available to the CHECK
TABLE statement were also allowed in
OPTIMIZE TABLE and
ANALYZE TABLE statements, but
caused corruption during their execution. These options were
never supported for these statements, and an error is now raised
if you try to apply these options to these statements.
(Bug#30495)
When expanding a * in a
USING or NATURAL join, the
check for table access for both tables in the join was done
using only the grant information of the first table.
(Bug#30468)
When casting a string value to an integer, cases where the input
string contained a decimal point and was long enough to overrun
the unsigned long long type were not handled
correctly. The position of the decimal point was not taken into
account which resulted in miscalculated numbers and incorrect
truncation to appropriate SQL data type limits.
(Bug#30453)
Versions of mysqldump from MySQL 4.1 or
higher tried to use START TRANSACTION WITH CONSISTENT
SNAPSHOT if the
--single-transaction and
--master-data options were
given, even with servers older than 4.1 that do not support
consistent snapshots.
(Bug#30444)
For CREATE ... SELECT ... FROM, where the
resulting table contained indexes, adding
SQL_BUFFER_RESULT to the
SELECT part caused index
corruption in the table.
(Bug#30384)
An orphaned PID file from a no-longer-running process could cause mysql.server to wait for that process to exit even though it does not exist. (Bug#30378)
The optimizer made incorrect assumptions about the value of the
is_member value for user-defined functions,
sometimes resulting in incorrect ordering of UDF results.
(Bug#30355)
Some valid euc-kr characters having the
second byte in the ranges [0x41..0x5A] and
[0x61..0x7A] were rejected.
(Bug#30315)
Simultaneous ALTER TABLE
statements for BLACKHOLE tables caused 100%
CPU use due to locking problems.
(Bug#30294)
Setting certain values on a table using a spatial index could cause the server to crash. (Bug#30286)
Tables with a GEOMETRY column could be marked
as corrupt if you added a non-SPATIAL index
on a GEOMETRY column.
(Bug#30284)
Some INFORMATION_SCHEMA tables are intended
for internal use, but could be accessed by using
SHOW statements.
(Bug#30079)
On some 64-bit systems, inserting the largest negative value
into a BIGINT column resulted in
incorrect data.
(Bug#30069)
Specifying the --without-geometry option for
configure caused server compilation to fail.
(Bug#29972)
Under some circumstances, a UDF initialization function could be passed incorrect argument lengths. (Bug#29804)
configure did not find nss
on some Linux platforms.
(Bug#29658)
The mysql_config command would output
CFLAGS values that were incompatible with C++
for the HP-UX platform.
(Bug#29645)
InnoDB had a race condition for an adaptive
hash rw-lock waiting for an X-lock. This fix may also provide
significant speed improvements on systems experiencing problems
with contention for the adaptive hash index.
(Bug#29560)
Views were treated as insertable even if some base table columns with no default value were omitted from the view definition. (This is contrary to the condition for insertability that a view must contain all columns in the base table that do not have a default value.) (Bug#29477)
The mysql client program now ignores Unicode byte order mark (BOM) characters at the beginning of input files. Previously, it read them and sent them to the server, resulting in a syntax error.
Presence of a BOM does not cause mysql to
change its default character set. To do that, invoke
mysql with an option such as
--default-character-set=utf8.
(Bug#29323)
For transactional tables, an error during a multiple-table
DELETE statement did not roll
back the statement.
(Bug#29136)
The log and
log_slow_queries system
variables were displayed by SHOW
VARIABLES but could not be accessed in expressions as
@@log and
@@log_slow_queries. Also, attempting to set
them with SET produced an incorrect
Unknown system variable message. Now these
variables can be accessed in expressions and attempting to set
their values produces an error message that the variable is read
only.
(Bug#29131)
Denormalized double-precision numbers cannot be handled properly by old MIPS pocessors. For IRIX, this is now handled by enabling a mode to use a software workaround. (Bug#29085)
SHOW VARIABLES did not display
the relay_log,
relay_log_index, or
relay_log_info_file system variables.
(Bug#28893)
The MySQL preferences pane did not work to start or stop MySQL on Mac OS X 10.5 (Leopard). (Bug#28854)
When doing a DELETE on a table
that involved a JOIN with
MyISAM or MERGE tables and
the JOIN referred to the same table, the
operation could fail reporting ERROR 1030 (HY000): Got
error 134 from storage engine. This was because scans
on the table contents would change because of rows that had
already been deleted.
(Bug#28837)
On Windows, mysql_upgrade created temporary
files in C:\ and did not clean them up.
(Bug#28774)
Index hints specified in view definitions were ignored when using the view to select from the base table. (Bug#28702)
Views do not have indexes, so index hints do not apply. Use of index hints when selecting from a view is now disallowed. (Bug#28701)
After changing the SQL mode to a restrictive value that would make already-inserted dates in a column be considered invalid, searches returned different results depending on whether the column was indexed. (Bug#28687)
For upgrading to a new major version using RPM packages (such as 4.1 to 5.0), if the installation procedure found an existing MySQL server running, it could fail to shut down the old server, but also erroneously removed the server's socket file. Now the procedure checks for an existing server package from a different vendor or major MySQL version. In such case, it refuses to install the server and recommends how to safely remove the old packages before installing the new ones. (Bug#28555)
The result from CHAR() was
incorrectly assumed in some contexts to return a single-byte
result.
(Bug#28550)
mysqlhotcopy silently skipped databases with names consisting of two alphanumeric characters. (Bug#28460)
The parser confused user-defined function (UDF) and stored
function creation for CREATE
FUNCTION and required that there be a default database
when creating UDFs, although there is no such requirement.
(Bug#28318, Bug#29816)
The SQL parser did not accept an empty
UNION=() clause. This meant that, when there
were no underlying tables specified for a
MERGE table, SHOW CREATE
TABLE and mysqldump both output
statements that could not be executed.
Now it is possible to execute a CREATE
TABLE or ALTER TABLE
statement with an empty UNION=() clause.
However, SHOW CREATE TABLE and
mysqldump do not output the
UNION=() clause if there are no underlying
tables specified for a MERGE table. This also
means it is now possible to remove the underlying tables for a
MERGE table using ALTER TABLE ...
UNION=().
(Bug#28248)
The result of a comparison between
VARBINARY and
BINARY columns differed depending
on whether the VARBINARY column
was indexed.
(Bug#28076)
The metadata in some MYSQL_FIELD members
could be incorrect when a temporary table was used to evaluate a
query.
(Bug#27990)
An ORDER BY at the end of a
UNION affected individual
SELECT statements rather than the
overall query result.
(Bug#27848)
comp_err created files with permissions such that they might be inaccessible during make install operations. (Bug#27789)
It was possible to exhaust memory by repeatedly running
index_merge queries and never
performing any FLUSH
TABLES statements.
(Bug#27732)
The anonymous accounts were not being created during MySQL installation. (Bug#27692)
When utf8 was set as the connection character
set, using SPACE() with a
non-Unicode column produced an error.
(Bug#27580)
See also Bug#23637.
A race condition between killing a statement and the thread executing the statement could lead to a situation such that the binary log contained an event indicating that the statement was killed, whereas the statement actually executed to completion. (Bug#27571)
Some queries using the
NAME_CONST() function failed to
return either a result or an error to the client, causing it to
hang. This was due to the fact that there was no check to insure
that both arguments to this function were constant expressions.
(Bug#27545, Bug#32559)
With the read_only system
variable enabled, CREATE DATABASE
and DROP DATABASE were allowed to
users who did not have the SUPER
privilege.
(Bug#27440)
resolveip failed to produce correct results for host names that begin with a digit. (Bug#27427)
In ORDER BY clauses, mixing aggregate
functions and nongrouping columns is not allowed if the
ONLY_FULL_GROUP_BY SQL mode is
enabled. However, in some cases, no error was thrown because of
insufficient checking.
(Bug#27219)
For the --record_log_pos
option, mysqlhotcopy now determines the slave
status information from the result of SHOW
SLAVE STATUS by using the
Relay_Master_Log_File and
Exec_Master_Log_Pos values rather than the
Master_Log_File and
Read_Master_Log_Pos values. This provides a
more accurate indication of slave execution relative to the
master.
(Bug#27101)
The MySQL Instance Configuration Wizard would not allow you to choose a service name, even though the criteria for the service name were valid. The code that checks the name has been updated to support the correct criteria of any string less than 256 character and not containing either a forward or backward slash character. (Bug#27013)
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.
config-win.h unconditionally defined
bool as BOOL,
causing problems on systems where bool is 1
byte and BOOL is 4 bytes.
(Bug#26461)
The internal init_time() library function
was renamed to my_init_time() to avoid
conflicts with external libraries.
(Bug#26294)
On Windows, for distributions built with debugging support, mysql could crash if the user typed Control-C. (Bug#26243)
mysqlcheck -A -r did not correctly identify all tables that needed repairing. (Bug#25347)
On Windows, an error in configure.js caused
installation of source distributions to fail.
(Bug#25340)
Using mysqldump in MySQL 5.1 resulted in dump
files that could not be loaded in MySQL 5.0 because
USING
options in index definitions appeared after the index column
list, whereas 5.0 accepted only the old syntax that has
type_nameUSING before the column list. The parser in
5.0 now accepts USING following the column
list.
(Bug#25162)
The client library had no way to return an error if no
connection had been established. This caused problems such as
mysql_library_init() failing
silently if no errmsg.sys file was
available.
(Bug#25097)
On Mac OS X, the StartupItem for MySQL did not work. (Bug#25008)
For Windows 64-bit builds, enabling shared-memory support caused client connections to fail. (Bug#24992)
If the expected precision of an arithmetic expression exceeded the maximum precision supported by MySQL, the precision of the result was reduced by an unpredictable or arbitrary amount, rather than to the maximum precision. In some cases, exceeding the maximum supported precision could also lead to a crash of the server. (Bug#24907)
mysql did not use its completion table. Also, the table contained few entries. (Bug#24624)
If a user installed MySQL Server and set a password for the
root user, and then uninstalled and
reinstalled MySQL Server to the same location, the user could
not use the MySQL Instance Config wizard to configure the server
because the uninstall operation left the previous data directory
intact. The config wizard assumed that any
new install (not an upgrade) would have the default data
directory where the root user has no
password. The installer now writes a registry key named
FoundExistingDataDir. If the installer finds
an existing data directory, the key will have a value of 1,
otherwise it will have a value of 0. When
MySQLInstanceConfig.exe is run, it will
attempt to read the key. If it can read the key, and the value
is 1 and there is no existing instance of the server (indicating
a new installation), the Config Wizard will allow the user to
input the old password so the server can be configured.
(Bug#24215)
The MySQL header files contained some duplicate macro definitions that could cause compilation problems. (Bug#23839)
SHOW COLUMNS on a
TEMPOARY table caused locking issues.
(Bug#23588)
For distributions compiled with the bundled
libedit library, there were difficulties
using the mysql client to enter input for
non-ASCII or multi-byte characters.
(Bug#23097)
For Windows Vista, MySQLInstanceConfig.exe did not include a proper manifest enabling it to run with administrative privileges. (Bug#22563)
See also Bug#24732.
On Mac OS X, mysqld did not react to Ctrl-C
when run under gdb, even when run with the
--gdb option.
(Bug#21567)
mysql_config output did not include
-lmygcc on some platforms when it was needed.
(Bug#21158)
mysql-stress-test.pl and mysqld_multi.server.sh were missing from some binary distributions. (Bug#21023, Bug#25486)
mysqldumpslow returned a confusing error message when no configuration file was found. (Bug#20455)
Host names sometimes were treated as case sensitive in
account-management statements (CREATE
USER, GRANT,
REVOKE, and so forth).
(Bug#19828)
The readline library has been updated to
version 5.2. This addresses issues in the
mysql client where history and editing within
the client would fail to work as expected.
(Bug#18431)
The Aborted_clients status
variable was incremented twice if a client exited without
calling mysql_close().
(Bug#16918)
The parser used signed rather than unsigned values in some cases that caused legal lengths in column declarations to be rejected. (Bug#15776)
A SET column whose definition specified 64
elements could not be updated using integer values.
(Bug#15409)
Clients were ignoring the TCP/IP port number specified as the default port via the --with-tcp-port configuration option. (Bug#15327)
Zero-padding of exponent values was not the same across platforms. (Bug#12860)
Values of types REAL ZEROFILL,
DOUBLE ZEROFILL, FLOAT
ZEROFILL, were not zero-filled when converted to a
character representation in the C prepared statement API.
(Bug#11589)
mysql stripped comments from statements sent
to the server. Now the
--comments or
--skip-comments option can be
used to control whether to retain or strip comments. The default
is --skip-comments.
(Bug#11230, Bug#26215)
If an INSERT ...
SELECT statement is executed, and no automatically
generated value is successfully inserted, then
mysql_insert_id() returns the ID
of the last inserted row.
If no automatically generated value is successfully inserted,
then mysql_insert_id() returns
0.
(Bug#9481)
MySQLInstanceConfig.exe did not save the
innodb_data_home_dir value to
the my.ini file under certain
circumstances.
(Bug#6627)
Several buffer-size system variables were either being handled incorrectly for large values (for settings larger than 4GB, they were truncated to values less than 4GB without a warning), or were limited unnecessarily to 4GB even on 64-bit systems. The following changes were made:
For key_buffer_size, values
larger than 4GB are allowed on 64-bit platforms (except
Windows, for which large values are truncated to 4GB with a
warning).
For join_buffer_size,
sort_buffer_size, and
myisam_sort_buffer_size,
values are limited to 4GB on all platforms. Larger values
are truncated to 4GB with a warning.
In addition, settings for
read_buffer_size and
read_rnd_buffer_size are
limited to 2GB on all platforms. Larger values are truncated to
2GB with a warning.
(Bug#5731, Bug#29419, Bug#29446)
Executing DISABLE KEYS and ENABLE
KEYS on a nonempty table would cause the size of the
index file for the table to grow considerable. This was because
the DISABLE KEYS operation would only mark
the existing index, without deleting the index blocks. The
ENABLE KEYS operation would re-create the
index, adding new blocks, while the previous index blocks would
remain. Existing indexes are now dropped and recreated when the
ENABLE KEYS statement is executed.
(Bug#4692)
This is a Service Pack release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.66a).
If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Functionality added or changed:
Security Enhancement:
To enable stricter control over the location from which
user-defined functions can be loaded, the
plugin_dir system variable has
been backported from MySQL 5.1. If the value is nonempty,
user-defined function object files can be loaded only from the
directory named by this variable. If the value is empty, the
behavior that is used prior to the inclusion of
plugin_dir applies: The UDF
object files must be located in a directory that is searched by
your system's dynamic linker.
(Bug#37428)
Bugs fixed:
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 path
name is now disallowed.
Additional corrections were made to handle the data directory path name if it contains symlinked directories in its path, and to make the check both at table-creation time and at table-opening time later. (Bug#32167, CVE-2008-2079)
See also Bug#39277.
Security Enhancement:
The server consumed excess memory while parsing statements with
hundreds or thousands of nested boolean conditions (such as
OR (OR ... (OR ... ))). This could lead to a
server crash or incorrect statement execution, or cause other
client statements to fail due to lack of memory. The latter
result constitutes a denial of service.
(Bug#38296)
This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This is a bugfix release that replaces MySQL 5.0.66.
Bugs fixed:
This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This release was withdrawn from production due to the side effect produced by Bug#20748. It has been replaced by MySQL 5.0.66a, which should be used instead.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.64). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Functionality added or changed:
mysql-test-run.pl now supports
--client-bindir and
--client-libdir options for specifying the
directory where client binaries and libraries are located.
(Bug#34995)
Bugs fixed:
Incompatible Change:
An additional correction to the original MySQL 5.0.64 fix was
made to normalize directory names before adding them to the list
of directories. This prevents /etc/ and
/etc from being considered different, for
example.
(Bug#20748)
See also Bug#38180.
Replication: Some kinds of internal errors, such as Out of memory errors, could cause the server to crash when replicating statements with user variables.
certain internal errors. (Bug#37150)
Some binary distributions had a duplicate “-64bit” suffix in the file name. (Bug#37623)
The mysql client failed to recognize comment
lines consisting of -- followed by a newline.
(Bug#36244)
An empty bit-string literal (b'') caused a
server crash. Now the value is parsed as an empty bit value
(which is treated as an empty string in string context or 0 in
numeric context).
(Bug#35658)
mysqlbinlog left temporary files on the disk after shutdown, leading to the pollution of the temporary directory, which eventually caused mysqlbinlog to fail. This caused problems in testing and other situations where mysqlbinlog might be invoked many times in a relatively short period of time. (Bug#35543)
The code for detecting a byte order mark (BOM) caused mysql to crash for empty input. (Bug#35480)
The mysql client incorrectly parsed statements containing the word “delimiter” in mid-statement.
The fix for this bug had the side effect of causing the problem reported in Bug#38158, so it was reverted in MySQL 5.0.67. (Bug#33812)
This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.62). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Functionality added or changed:
Important Change: Incompatible Change:
The FEDERATED storage engine is now disabled
by default in the .cnf files shipped with
MySQL distributions (my-huge.cnf,
my-medium.cnf, and so forth). This affects
server behavior only if you install one of these files.
(Bug#37069)
Bugs fixed:
Replication:
CREATE PROCEDURE and
CREATE FUNCTION statements
containing extended comments were not written to the binary log
correctly, causing parse errors on the slave.
(Bug#36570)
See also Bug#32575.
On Windows 64-bit systems, temporary variables of
long types were used to store
ulong values, causing key cache
initialization to receive distorted parameters. The effect was
that setting key_buffer_size to
values of 2GB or more caused memory exhaustion to due allocation
of too much memory.
(Bug#36705)
Multiple-table UPDATE statements
that used a temporary table could fail to update all qualifying
rows or fail with a spurious duplicate-key error.
(Bug#36676)
A REGEXP match could return
incorrect rows when the previous row matched the expression and
used CONCAT() with an empty
string.
(Bug#36488)
For EXPLAIN EXTENDED, execution of an
uncorrelated IN subquery caused a crash if
the subquery required a temporary table for its execution.
(Bug#36011)
This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.60). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Functionality added or changed:
Important Change:
Some changes were made to
CHECK TABLE ... FOR
UPGRADE and REPAIR
TABLE with respect to detection and handling of tables
with incompatible .frm files (files created
with a different version of the MySQL server). These changes
also affect mysqlcheck because that program
uses CHECK TABLE and
REPAIR TABLE, and thus also
mysql_upgrade because that program invokes
mysqlcheck.
If your table was created by a different version of the
MySQL server than the one you are currently running,
CHECK TABLE ...
FOR UPGRADE indicates that the table has an
.frm file with an incompatible version.
In this case, the result set returned by
CHECK TABLE contains a line
with a Msg_type value of
error and a Msg_text
value of Table upgrade required. Please do "REPAIR
TABLE `
tbl_name`" to fix
it!
REPAIR TABLE without
USE_FRM upgrades the
.frm file to the current version.
If you use REPAIR TABLE ...USE_FRM and
your table was created by a different version of the MySQL
server than the one you are currently running,
REPAIR TABLE will not attempt
to repair the table. In this case, the result set returned
by REPAIR TABLE contains a
line with a Msg_type value of
error and a Msg_text
value of Failed repairing incompatible .FRM
file.
Previously, use of REPAIR TABLE
...USE_FRM with a table created by a different
version of the MySQL server risked the loss of all rows in
the table.
mysql_upgrade now has a
--tmpdir option to enable
the location of temporary files to be specified.
(Bug#36469)
Bugs fixed:
Important Change:
The server no longer issues warnings for truncation of excess
spaces for values inserted into
CHAR columns. This reverts a
change in the previous release that caused warnings to be
issued.
(Bug#30059)
Replication:
CREATE VIEW statements containing
extended comments were not written to the binary log correctly,
causing parse errors on the slave. Now, all comments are
stripped from such statements before being written to the binary
log.
(Bug#32575)
See also Bug#36570.
mysqltest ignored the value of
--tmpdir in one place.
(Bug#36465)
Conversion of a FLOAT ZEROFILL value to
string could cause a server crash if the value was
NULL.
(Bug#36139)
An error in calculation of the precision of zero-length items
(such as NULL) caused a server crash for
queries that employed temporary tables.
(Bug#36023)
The server crashed inside NOT IN subqueries
with an impossible WHERE or
HAVING clause, such as NOT IN
(SELECT ... FROM t1, t2, ... WHERE 0).
(Bug#36005)
Grouping or ordering of long values in unindexed
BLOB or
TEXT columns with the
gbk or big5 character set
crashed the server.
(Bug#35993)
SET GLOBAL debug='' resulted in a Valgrind
warning in DbugParse(), which was reading
beyond the end of the control string.
(Bug#35986)
The combination of
GROUP_CONCAT(),
DISTINCT, and LEFT JOIN
could crash the server when the right table is empty.
(Bug#35298)
Several additional configuration scripts in the
BUILD directory now are included in source
distributions. These may be useful for users who wish to build
MySQL from source. (See
Section 2.16.3, “Installing from the Development Source Tree”, for information about
what they do.)
(Bug#34291)
The internal init_time() library function
was renamed to my_init_time() to avoid
conflicts with external libraries.
(Bug#26294)
The parser used signed rather than unsigned values in some cases that caused legal lengths in column declarations to be rejected. (Bug#15776)
This is a Service Pack release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.60). For this release, there are no such changes or fixes.
If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.58). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Functionality added or changed:
Bugs fixed:
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 path
name is now disallowed.
Additional fixes were made in MySQL 5.0.70.
See also Bug#39277.
Incompatible Change:
It was possible to use FRAC_SECOND as a
synonym for MICROSECOND with
DATE_ADD(),
DATE_SUB(), and
INTERVAL; now, using
FRAC_SECOND with anything other than
TIMESTAMPADD() or
TIMESTAMPDIFF() produces a syntax
error.
It is now possible (and preferable) to use
MICROSECOND with
TIMESTAMPADD() and
TIMESTAMPDIFF(), and
FRAC_SECOND is now deprecated.
(Bug#33834)
Important Change:
The server handled truncation of values having excess trailing
spaces into CHAR,
VARCHAR, and
TEXT columns in different ways.
This behavior has now been made consistent for columns of all
three of these types, and now follows the existing behavior of
VARCHAR columns in this regard;
that is, a Note is always issued whenever
such truncation occurs.
This change does not affect columns of these three types when
using a binary encoding; BLOB
columns are also unaffected by the change, since they always use
a binary encoding.
(Bug#30059)
Replication:
insert_id was not written to
the binary log for inserts into BLACKHOLE
tables.
(Bug#35178)
Replication: The character sets and collations used for constant identifiers in stored procedures were not replicated correctly. (Bug#34289)
Replication:
An extraneous
ROLLBACK
statement was written to the binary log by a connection that did
not use any transactional tables.
(Bug#33329)
Replication:
When a stored routine or trigger, running on a master that used
MySQL 5.0 or MySQL 5.1.11 or earlier, performed an insert on an
AUTO_INCREMENT column, the
insert_id value was not
replicated correctly to a slave running MySQL 5.1.12 or later
(including any MySQL 6.0 release).
(Bug#33029)
See also Bug#19630.
Replication:
STOP SLAVE did not stop
connection attempts properly. If the IO slave thread was
attempting to connect, STOP SLAVE
waited for the attempt to finish, sometimes for a long period of
time, rather than stopping the slave immediately.
(Bug#31024)
See also Bug#30932.
Replication:
MASTER_POS_WAIT() did not return
NULL when the server was not a slave.
(Bug#26622)
Replication:
The nonspecific error message Wrong parameters to
function register_slave resulted when
START SLAVE failed to register on
the master due to excess length of any the slave server options
--report-host,
--report-user, or
--report-password. An error
message specific to each of these options is now returned in
such cases. The new error messages are:
Failed to register slave: too long 'report-host'
Failed to register slave: too long 'report-user'
Failed to register slave; too long 'report-password'
See also Bug#19328.
Replication:
PURGE BINARY LOGS TO and PURGE
BINARY LOGS BEFORE did not handle missing binary log
files correctly or in the same way. Now for both of these
statements, if any files listed in the
.index file are missing from the file
system, the statement fails with an error.
(Bug#18199, Bug#18453)
Replication:
START SLAVE UNTIL
MASTER_LOG_POS=
issued on a slave that was using
position--log-slave-updates and that was
involved in circular replication would cause the slave to run
and stop one event later than that specified by the value of
position.
(Bug#13861)
On Windows, the installer attempted to use JScript to determine whether the target data directory already existed. On Windows Vista x64, this resulted in an error because the installer was attempting to run the JScript in a 32-bit engine, which wasn't registered on Vista. The installer no longer uses JScript but instead relies on a native WiX command. (Bug#36103)
There was a memory leak when connecting to a
FEDERATED table using a connection string
that had a host value of localhost or omitted
the host and a port value of 0 or omitted the
port.
(Bug#35509)
Using LOAD DATA
INFILE with a view could crash the server.
(Bug#35469)
When a view containing a reference to DUAL
was created, the reference was removed when the definition was
stored, causing some queries against the view to fail with
invalid SQL syntax errors.
(Bug#35193)
Debugging symbols were missing for some executables in Windows binary distributions. (Bug#35104)
A query that performed a
ref_or_null join where the
second table used a key having one or columns that could be
NULL and had a column value that was
NULL caused the server to crash.
(Bug#34945)
This regression was introduced by Bug#12144.
Some binaries produced stack corruption messages due to being built with versions of bison older than 2.1. Builds are now created using bison 2.3. (Bug#34926)
mysqldump failed to return an error code when
using the --master-data option
without binary logging being enabled on the server.
(Bug#34909)
Under some circumstances, the value of
mysql_insert_id() following a
SELECT ... INSERT statement could return an
incorrect value. This could happen when the last SELECT
... INSERT did not involve an
AUTO_INCREMENT column, but the value of
mysql_insert_id() was changed by
some previous statements.
(Bug#34889)
Table and database names were mixed up in some places of the subquery transformation procedure. This could affect debugging trace output and further extensions of that procedure. (Bug#34830)
A malformed URL used for a FEDERATED
table's CONNECTION option value in a
CREATE TABLE statement was not
handled correctly and could crash the server.
(Bug#34788)
Queries such as SELECT ROW(1, 2) IN (SELECT t1.a, 2)
FROM t1 GROUP BY t1.a (combining row constructors and
subqueries in the FROM clause) could lead to
assertion failure or unexpected error messages.
(Bug#34763)
Using NAME_CONST() with a negative number and
an aggregate function caused MySQL to crash. This could also
have a negative impact on replication.
(Bug#34749)
A memory-handling error associated with use of
GROUP_CONCAT() in subqueries
could result in a server crash.
(Bug#34747)
For an indexed integer column
col_name and a value
N that is one greater than the
maximum value allowed for the data type of
col_name, conditions of the form
WHERE failed to return rows
where the value of col_name <
Ncol_name is
N - 1
Executing a TRUNCATE statement on
a table having both a foreign key reference and a
DELETE trigger crashed the
server.
(Bug#34643)
Some subqueries using an expression that included an aggregate function could fail or in some cases lead to a crash of the server. (Bug#34620)
A server crash could occur if
INFORMATION_SCHEMA tables built in memory
were swapped out to disk during query execution.
(Bug#34529)
CAST(AVG( produced incorrect results for
non-arg) AS
DECIMAL)DECIMAL arguments.
(Bug#34512)
Under some conditions, a SET GLOBAL
innodb_commit_concurrency or SET GLOBAL
innodb_autoextend_increment statement could fail.
(Bug#34223)
mysqldump attempts to set the
character_set_results system
variable after connecting to the server. This failed for pre-4.1
servers that have no such variable, but
mysqldump did not account for this and 1)
failed to dump database contents; 2) failed to produce any error
message alerting the user to the problem.
(Bug#34192)
For a FEDERATED table with an index on a
nullable column, accessing the table could crash a server,
return an incorrect result set, or return ERROR 1030
(HY000): Got error 1430 from storage engine.
(Bug#33946)
A query using WHERE
(column1=', where
string1' AND
column2=constant1) OR
(column1='string2' AND
column2=constant2)col1 used a binary collation and
string1 matched
string2 except for case, failed to
match any records even when matches were found by a query using
the equivalent clause WHERE
column2=.
(Bug#33833)constant1 OR
column2=constant2
Reuse of prepared statements could cause a memory leak in the embedded server. (Bug#33796)
Some queries using a combination of IN,
CONCAT(), and an implicit type
conversion could return an incorrect result.
(Bug#33764)
In some cases a query that produced a result set when using
ORDER BY ASC did not return any results when
this was changed to ORDER BY DESC.
(Bug#33758)
Disabling concurrent inserts caused some cacheable queries not to be saved in the query cache. (Bug#33756)
Certain combinations of views, subselects with outer references and stored routines or triggers could cause the server to crash. (Bug#33389)
SLEEP(0) failed to return on
64-bit Mac OS X due to a bug in
pthread_cond_timedwait().
(Bug#33304)
Granting the UPDATE privilege on
one column of a view caused the server to crash.
(Bug#33201)
Under some circumstances a combination of aggregate functions
and GROUP BY in a
SELECT query over a view could
lead to incorrect calculation of the result type of the
aggregate function. This in turn could lead to incorrect
results, or to crashes on debug builds of the server.
(Bug#33049)
For DISTINCT queries, MySQL 4.0 and 4.1
stopped reading joined tables as soon as the first matching row
was found. However, this optimization was lost in MySQL 5.0,
which instead read all matching rows. This fix for this
regression may result in a major improvement in performance for
DISTINCT queries in cases where many rows
match.
(Bug#32942)
Incorrect assertions could cause a server crash for
DELETE triggers for transactional
tables.
(Bug#32790)
Inserting strings with a common prefix into a table that used
the ucs2 character set corrupted the table.
(Bug#32705)
Queries using LIKE on tables having indexed
CHAR columns using either of the
eucjpms or ujis character
sets did not return correct results.
(Bug#32510)
Queries testing numeric constants containing leading zeroes
against ZEROFILL columns were not evaluated
correctly.
(Bug#31887)
If an error occurred during file creation, the server sometimes did not remove the file, resulting in an unused file in the file system. (Bug#31781)
The server returned the error message Out of memory; restart server and try again when the actual problem was that the sort buffer was too small. Now an appropriate error message is returned in such cases. (Bug#31590)
When sorting privilege table rows, the server treated escaped
wildcard characters (\% and
\_) the same as unescaped wildcard characters
(% and _), resulting in
incorrect row ordering.
(Bug#31194)
On Windows, SHOW PROCESSLIST
could display process entries with a State
value of *** DEAD ***.
(Bug#30960)
If an alias was used to refer to the value returned by a stored function within a subselect, the outer select recognized the alias but failed to retrieve the value assigned to it in the subselect. (Bug#30787)
Binary logging for a stored procedure differed depending on whether or not execution occurred in a prepared statement. (Bug#30604)
An orphaned PID file from a no-longer-running process could cause mysql.server to wait for that process to exit even though it does not exist. (Bug#30378)
The mysql_config command would output
CFLAGS values that were incompatible with C++
for the HP-UX platform.
(Bug#29645)
The SQL parser did not accept an empty
UNION=() clause. This meant that, when there
were no underlying tables specified for a
MERGE table, SHOW CREATE
TABLE and mysqldump both output
statements that could not be executed.
Now it is possible to execute a CREATE
TABLE or ALTER TABLE
statement with an empty UNION=() clause.
However, SHOW CREATE TABLE and
mysqldump do not output the
UNION=() clause if there are no underlying
tables specified for a MERGE table. This also
means it is now possible to remove the underlying tables for a
MERGE table using ALTER TABLE ...
UNION=().
(Bug#28248)
It was possible to exhaust memory by repeatedly running
index_merge queries and never
performing any FLUSH
TABLES statements.
(Bug#27732)
When utf8 was set as the connection character
set, using SPACE() with a
non-Unicode column produced an error.
(Bug#27580)
See also Bug#23637.
In ORDER BY clauses, mixing aggregate
functions and nongrouping columns is not allowed if the
ONLY_FULL_GROUP_BY SQL mode is
enabled. However, in some cases, no error was thrown because of
insufficient checking.
(Bug#27219)
For the --record_log_pos
option, mysqlhotcopy now determines the slave
status information from the result of SHOW
SLAVE STATUS by using the
Relay_Master_Log_File and
Exec_Master_Log_Pos values rather than the
Master_Log_File and
Read_Master_Log_Pos values. This provides a
more accurate indication of slave execution relative to the
master.
(Bug#27101)
The MySQL Instance Configuration Wizard would not allow you to choose a service name, even though the criteria for the service name were valid. The code that checks the name has been updated to support the correct criteria of any string less than 256 character and not containing either a forward or backward slash character. (Bug#27013)
config-win.h unconditionally defined
bool as BOOL,
causing problems on systems where bool is 1
byte and BOOL is 4 bytes.
(Bug#26461)
On Windows, for distributions built with debugging support, mysql could crash if the user typed Control-C. (Bug#26243)
On Windows, an error in configure.js caused
installation of source distributions to fail.
(Bug#25340)
Using mysqldump in MySQL 5.1 resulted in dump
files that could not be loaded in MySQL 5.0 because
USING
options in index definitions appeared after the index column
list, whereas 5.0 accepted only the old syntax that has
type_nameUSING before the column list. The parser in
5.0 now accepts USING following the column
list.
(Bug#25162)
The client library had no way to return an error if no
connection had been established. This caused problems such as
mysql_library_init() failing
silently if no errmsg.sys file was
available.
(Bug#25097)
On Mac OS X, the StartupItem for MySQL did not work. (Bug#25008)
For Windows 64-bit builds, enabling shared-memory support caused client connections to fail. (Bug#24992)
If a user installed MySQL Server and set a password for the
root user, and then uninstalled and
reinstalled MySQL Server to the same location, the user could
not use the MySQL Instance Config wizard to configure the server
because the uninstall operation left the previous data directory
intact. The config wizard assumed that any
new install (not an upgrade) would have the default data
directory where the root user has no
password. The installer now writes a registry key named
FoundExistingDataDir. If the installer finds
an existing data directory, the key will have a value of 1,
otherwise it will have a value of 0. When
MySQLInstanceConfig.exe is run, it will
attempt to read the key. If it can read the key, and the value
is 1 and there is no existing instance of the server (indicating
a new installation), the Config Wizard will allow the user to
input the old password so the server can be configured.
(Bug#24215)
The MySQL header files contained some duplicate macro definitions that could cause compilation problems. (Bug#23839)
SHOW COLUMNS on a
TEMPOARY table caused locking issues.
(Bug#23588)
For distributions compiled with the bundled
libedit library, there were difficulties
using the mysql client to enter input for
non-ASCII or multi-byte characters.
(Bug#23097)
On Mac OS X, mysqld did not react to Ctrl-C
when run under gdb, even when run with the
--gdb option.
(Bug#21567)
mysql-stress-test.pl and mysqld_multi.server.sh were missing from some binary distributions. (Bug#21023, Bug#25486)
A SET column whose definition specified 64
elements could not be updated using integer values.
(Bug#15409)
MySQLInstanceConfig.exe did not save the
innodb_data_home_dir value to
the my.ini file under certain
circumstances.
(Bug#6627)
This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.56). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Functionality added or changed:
Cluster API: Important Change:
Because NDB_LE_MemoryUsage.page_size_kb shows
memory page sizes in bytes rather than kilobytes, it has been
renamed to page_size_bytes. The name
page_size_kb is now deprecated and thus
subject to removal in a future release, although it currently
remains supported for reasons of backward compatibility. See
The Ndb_logevent_type Type, for more information about
NDB_LE_MemoryUsage.
(Bug#30271)
The ndbd and ndb_mgmd man pages have been reclassified from volume 1 to volume 8. (Bug#34642)
mysqltest now has mkdir
and rmdir commands for creating and removing
directories.
(Bug#31004)
Bugs fixed:
Performance:
InnoDB adaptive hash latches could be held
too long during filesort operations, resulting in a server
crash. Now the hash latch is released when a query on
InnoDB tables performs a filesort. This
eliminates the crash and may provide significant performance
improvements on systems on which many queries using filesorts
with temporary tables are being performed.
(Bug#32149)
MySQL Cluster:
When configured with NDB support,
MySQL failed to compile using gcc 4.3 on
64bit FreeBSD systems.
(Bug#34169)
MySQL Cluster: The failure of a DDL statement could sometimes lead to node failures when attempting to execute subsequent DDL statements. (Bug#34160)
MySQL Cluster:
Extremely long SELECT statements
(where the text of the statement was in excess of 50000
characters) against NDB tables
returned empty results.
(Bug#34107)
MySQL Cluster:
A periodic failure to flush the send buffer by the
NDB TCP transporter could cause a
unnecessary delay of 10 ms between operations.
(Bug#34005)
MySQL Cluster:
When all data and SQL nodes in the cluster were shut down
abnormally (that is, other than by using STOP
in the cluster management client), ndb_mgm
used excessive amounts of CPU.
(Bug#33237)
MySQL Cluster: Transaction atomicity was sometimes not preserved between reads and inserts under high loads. (Bug#31477)
MySQL Cluster:
Numerous NDBCLUSTER test failures
occurred in builds compiled using icc on IA64
platforms.
(Bug#31239)
MySQL Cluster: Having tables with a great many columns could cause Cluster backups to fail. (Bug#30172)
MySQL Cluster:
Issuing an
INSERT ...
ON DUPLICATE KEY UPDATE concurrently with or following
a TRUNCATE statement on an
NDB table failed with
NDB error 4350
Transaction already aborted.
(Bug#29851)
MySQL Cluster:
It was possible in config.ini to define
cluster nodes having node IDs greater than the maximum allowed
value.
(Bug#28298)
Cluster API:
When reading a BIT(64) value using
NdbOperation:getValue(), 12 bytes were
written to the buffer rather than the expected 8 bytes.
(Bug#33750)
mysql_explain_log concatenated multiple-line
statements, causing malformed results for statements that
contained SQL comments beginning with --.
(Bug#34339)
Executing an ALTER VIEW statement
on a table crashed the server.
(Bug#34337)
Passing anything other than an integer argument to a
LIMIT clause in a prepared statement would
fail. (This limitation was introduced to avoid replication
problems; for example, replicating the statement with a string
argument would cause a parse failure in the slave). Now,
arguments to the LIMIT clause are converted
to integer values, and these converted values are used when
logging the statement.
(Bug#33851)
An internal buffer in mysql was too short. Overextending it could cause stack problems or segmentation violations on some architectures. (This is not a problem that could be exploited to run arbitrary code.) (Bug#33841)
Large unsigned integers were improperly handled for prepared statements, resulting in truncation or conversion to negative numbers. (Bug#33798)
make_binary_distribution passed the
--print-libgcc-file option to the C compiler,
but this does not work with the ICC compiler.
(Bug#33536)
When MySQL was built with OpenSSL, the SSL library was not properly initialized with information of which endpoint it was (server or client), causing connection failures. (Bug#33050)
Repeated creation and deletion of views within prepared statements could eventually crash the server. (Bug#32890)
See also Bug#34587.
Executing a prepared statement associated with a materialized cursor sent to the client a metadata packet with incorrect table and database names. The problem occurred because the server sent the name of the temporary table used by the cursor instead of the table name of the original table.
The same problem occured when selecting from a view, in which case the name of the table name was sent, rather than the name of the view. (Bug#32265)
SHOW STATUS caused a server crash
if InnoDB had not been initialized.
(Bug#32083)
The MySQL preferences pane did not work to start or stop MySQL on Mac OS X 10.5 (Leopard). (Bug#28854)
For upgrading to a new major version using RPM packages (such as 4.1 to 5.0), if the installation procedure found an existing MySQL server running, it could fail to shut down the old server, but also erroneously removed the server's socket file. Now the procedure checks for an existing server package from a different vendor or major MySQL version. In such case, it refuses to install the server and recommends how to safely remove the old packages before installing the new ones. (Bug#28555)
mysqlhotcopy silently skipped databases with names consisting of two alphanumeric characters. (Bug#28460)
mysql did not use its completion table. Also, the table contained few entries. (Bug#24624)
mysql_config output did not include
-lmygcc on some platforms when it was needed.
(Bug#21158)
This is a Service Pack release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied in MySQL 5.0.56sp1 since the previous MySQL Enterprise Server Quarterly Service Pack release (5.0.50sp1a). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Functionality added or changed:
mysqldump produces a -- Dump
completed on comment
at the end of the dump if
DATE--comments is given. The date
causes dump files for identical data take at different times to
appear to be different. The new options
--dump-date and
--skip-dump-date
control whether the date is added to the comment.
--skip-dump-date
suppresses date printing. The default is
--dump-date (include the date
in the comment).
(Bug#31077)
The mysql_odbc_escape_string() C API
function has been removed. It has multi-byte character escaping
issues, doesn't honor the
NO_BACKSLASH_ESCAPES SQL mode
and is not needed anymore by Connector/ODBC as of 3.51.17.
(Bug#29592)
The default value of the
connect_timeout system variable
was increased from 5 to 10 seconds. This might help in cases
where clients frequently encounter errors of the form
Lost connection to MySQL server at
'.
(Bug#28359)XXX', system error:
errno
The use of InnoDB hash indexes now can be
controlled by setting the new
innodb_adaptive_hash_index
system variable at server startup. By default, this variable is
enabled. See Section 13.2.10.4, “Adaptive Hash Indexes”.
The argument for the mysql-test-run.pl
--do-test and --skip-test
options is now interpreted as a Perl regular expression if there
is a pattern metacharacter in the argument value. This allows
more flexible specification of which tests to perform or skip.
Bugs fixed:
Security Fix:
Using RENAME TABLE against a
table with explicit DATA DIRECTORY and
INDEX DIRECTORY options can be used to
overwrite system table information by replacing the symbolic
link points. the file to which the symlink points.
MySQL will now return an error when the file to which the symlink points already exists. (Bug#32111, CVE-2007-5969)
Security Fix:
ALTER VIEW retained the original
DEFINER value, even when altered by another
user, which could allow that user to gain the access rights of
the view. Now ALTER VIEW is
allowed only to the original definer or users with the
SUPER privilege.
(Bug#29908)
Security Fix:
When using a FEDERATED table, the local
server could be forced to crash if the remote server returned a
result with fewer columns than expected.
(Bug#29801)
Security Enhancement: It was possible to force an error message of excessive length which could lead to a buffer overflow. This has been made no longer possible as a security precaution. (Bug#32707)
Incompatible Change:
With ONLY_FULL_GROUP_BY SQL
mode enabled, queries such as SELECT a FROM t1 HAVING
COUNT(*)>2 were not being rejected as they should
have been.
This fix results in the following behavior:
There is a check against mixing group and nongroup columns
only when
ONLY_FULL_GROUP_BY is
enabled.
This check is done both for the select list and for the
HAVING clause if there is one.
This behavior differs from previous versions as follows:
Previously, the HAVING clause was not
checked when
ONLY_FULL_GROUP_BY was
enabled; now it is checked.
Previously, the select list was checked even when
ONLY_FULL_GROUP_BY was not
enabled; now it is checked only when
ONLY_FULL_GROUP_BY is
enabled.
Incompatible Change: The MySQL 5.0.50 patch for this bug was reverted because it changed the behavior of a General Availability MySQL release. (Bug#30234)
See also Bug#27525.
Incompatible Change: It was possible to create a view having a column whose name consisted of an empty string or space characters only.
One result of this bug fix is that aliases for columns in the
view SELECT statement are checked to ensure
that they are legal column names. In particular, the length must
be within the maximum column length of 64 characters, not the
maximum alias length of 256 characters. This can cause problems
for replication or loading dump files. For additional
information and workarounds, see
Section D.4, “Restrictions on Views”.
(Bug#27695)
See also Bug#31202.
Incompatible Change:
Several type-preserving functions and operators returned an
incorrect result type that does not match their argument types:
COALESCE(),
IF(),
IFNULL(),
LEAST(),
GREATEST(),
CASE. These now aggregate using the
precise SQL types of their arguments rather than the internal
type. In addition, the result type of the
STR_TO_DATE() function is now
DATETIME by default.
(Bug#27216)
Incompatible Change: It was possible for option files to be read twice at program startup, if some of the standard option file locations turned out to be the same directory. Now duplicates are removed from the list of files to be read.
Also, users could not override system-wide settings using
~/.my.cnf because
SYSCONFDIR/my.cnf~/.my.cnf can override system-wide
settings.
The fix for this problem had a side effect such that on Unix,
MySQL programs looked for options in
~/my.cnf rather than the standard location
of ~/.my.cnf. That problem was addressed as
Bug#38180.
(Bug#20748)
Important Change: MySQL Cluster:
AUTO_INCREMENT columns had the following
problems when used in NDB tables:
The AUTO_INCREMENT counter was not
updated correctly when such a column was updated.
AUTO_INCREMENT values were not
prefetched beyond statement boundaries.
AUTO_INCREMENT values were not handled
correctly with
INSERT
IGNORE statements.
After being set,
ndb_autoincrement_prefetch_sz
showed a value of 1, regardless of the value it had
actually been set to.
As part of this fix, the behavior of
ndb_autoincrement_prefetch_sz
has changed. Setting this to less than 32 no longer has any
effect on prefetching within statements (where IDs are now
always obtained in batches of 32 or more), but only between
statements. The default value for this variable has also
changed, and is now 1.
(Bug#25176, Bug#31956, Bug#32055)
Important Change: Replication:
When the master crashed during an update on a transactional
table while in autocommit mode,
the slave failed. This fix causes every transaction (including
autocommit transactions) to be
recorded in the binlog as starting with a
BEGIN and
ending with a COMMIT or
ROLLBACK.
(Bug#26395)
Replication: Important Note: Network timeouts between the master and the slave could result in corruption of the relay log. This fix rectifies a long-standing replication issue when using unreliable networks, including replication over wide area networks such as the Internet. If you experience reliability issues and see many You have an error in your SQL syntax errors on replication slaves, we strongly recommend that you upgrade to a MySQL version which includes this fix. (Bug#26489)
MySQL Cluster:
An improperly reset internal signal was observed as a hang when
using events in the NDB API but
could result in various errors.
(Bug#33206)
MySQL Cluster: Incorrectly handled parameters could lead to a crash in the Transaction Coordinator during a node failure, causing other data nodes to fail. (Bug#33168)
MySQL Cluster: The failure of a master node could lead to subsequent failures in local checkpointing. (Bug#32160)
MySQL Cluster:
An uninitialized variable in the
NDB storage engine code led to
AUTO_INCREMENT failures when the server was
compiled with gcc 4.2.1.
(Bug#31848)
This regression was introduced by Bug#27437.
MySQL Cluster:
An error with an if statement in
sql/ha_ndbcluster.cc could potentially lead
to an infinite loop in case of failure when working with
AUTO_INCREMENT columns in
NDB tables.
(Bug#31810)
MySQL Cluster:
The NDB storage engine code was not
safe for strict-alias optimization in gcc
4.2.1.
(Bug#31761)
MySQL Cluster:
Primary keys on variable-length columns (such as
VARCHAR) did not work correctly.
(Bug#31635)
MySQL Cluster: Transaction timeouts were not handled well in some circumstances, leading to excessive number of transactions being aborted unnecessarily. (Bug#30379)
MySQL Cluster: In some cases, the cluster managment server logged entries multiple times following a restart of mgmd. (Bug#29565)
MySQL Cluster: An interpreted program of sufficient size and complexity could cause all cluster data nodes to shut down due to buffer overruns. (Bug#29390)
MySQL Cluster:
UPDATE IGNORE could sometimes fail on
NDB tables due to the use of
unitialized data when checking for duplicate keys to be ignored.
(Bug#25817)
MySQL Cluster:
When inserting a row into an NDB
table with a duplicate value for a nonprimary unique key, the
error issued would reference the wrong key.
This improves on an initial fix for this issue made in MySQL 5.0.30 and MySQL 5.0.33 (Bug#21072)
Replication:
A CREATE USER,
DROP USER, or
RENAME USER statement that fails
on the master, or that is a duplicate of any of these
statements, is no longer written to the binlog; previously,
either of these occurrences could cause the slave to fail.
See also Bug#29749.
Replication:
SHOW BINLOG EVENTS could fail
when the binlog contained one or more events whose size was
close to the value of
max_allowed_packet.
(Bug#33413)
Replication:
SQL statements containing comments using --
syntax were not replayable by mysqlbinlog,
even though such statements replicated correctly.
(Bug#32205)
Replication: It was possible for the name of the relay log file to exceed the amount of memory reserved for it, possibly leading to a crash of the server. (Bug#31836)
See also Bug#28597.
Replication: Corruption of log events caused the server to crash on 64-bit Linux systems having 4 GB of memory or more. (Bug#31793)
Replication:
Use of the @@hostname system variable in
inserts in mysql_system_tables_data.sql did
not replicate. The workaround is to select its value into a user
variable (which does replicate) and insert that.
(Bug#31167)
Replication:
Issuing a DROP VIEW statement
caused replication to fail if the view did not actually exist.
(Bug#30998)
Replication: One thread could read uninitialized memory from the stack of another thread. This issue was only known to occur in a mysqld process acting as both a master and a slave. (Bug#30752)
Replication:
Replication of LOAD
DATA INFILE could fail when
read_buffer_size was larger
than max_allowed_packet.
(Bug#30435)
Replication:
Setting server_id did not
update its value for the current session.
(Bug#28908)
Replication: Due a previous change in how the default name and location of the binary log file were determined, replication failed following some upgrades. (Bug#28597, Bug#28603)
See also Bug#31836.
This regression was introduced by Bug#20166.
Replication:
Stored procedures having BIT
parameters were not replicated correctly.
(Bug#26199)
Replication:
Issuing SHOW SLAVE STATUS as
mysqld was shutting down could cause a crash.
(Bug#26000)
Replication:
An UPDATE statement using a
stored function that modified a nontransactional table was not
logged if it failed. This caused the copy of the
nontransactional table on the master have a row that the copy on
the slave did not.
In addition, when an
INSERT ...
ON DUPLICATE KEY UPDATE statement encountered a
duplicate key constraint, but the
UPDATE did not actually change
any data, the statement was not logged. As a result of this fix,
such statements are now treated the same for logging purposes as
other UPDATE statements, and so
are written to the binary log.
(Bug#23333)
See also Bug#12713.
Replication:
A replication slave sometimes failed to reconnect because it was
unable to run SHOW SLAVE HOSTS.
It was not necessary to run this statement on slaves (since the
master should track connection IDs), and the execution of this
statement by slaves was removed.
(Bug#21132)
The server crashed when executing a query that had a subquery
containing an equality X=Y where Y referred to a named select
list expression from the parent select. The server crashed when
trying to use the X=Y equality for
ref-based access.
(Bug#33794)
Use of uninitialized memory for filesort in a
subquery caused a server crash.
(Bug#33675)
The server could crash when
REPEAT
or another control instruction was used in conjunction with
labels and a
LEAVE
instruction.
(Bug#33618)
The parser allowed control structures in compound statements to have mismatched beginning and ending labels. (Bug#33618)
SET GLOBAL myisam_max_sort_file_size=DEFAULT
set myisam_max_sort_file_size
to an incorrect value.
(Bug#33382)
See also Bug#31177.
CREATE TABLE ...
SELECT created tables that for date columns used the
obsolete Field_date type instead of
Field_newdate.
(Bug#33256)
For DECIMAL columns used with the
ROUND(
or
X,D)TRUNCATE(
function with a nonconstant value of
X,D)D, adding an ORDER
BY for the function result produced misordered output.
(Bug#33143)
Some valid SELECT statements
could not be used as views due to incorrect column reference
resolution.
(Bug#33133)
The fix for Bug#11230 and Bug#26215 introduced a significant input-parsing slowdown for the mysql client. This has been corrected. (Bug#33057)
UNION constructs cannot contain
SELECT ... INTO except in the final
SELECT. However, if a
UNION was used in a subquery and
an INTO clause appeared in the top-level
query, the parser interpreted it as having appeared in the
UNION and raised an error.
(Bug#32858)
The correct data type for a NULL column
resulting from a UNION could be
determined incorrectly in some cases: 1) Not correctly inferred
as NULL depending on the number of selects;
2) Not inferred correctly as NULL if one
select used a subquery.
(Bug#32848)
An ORDER BY query using IS
NULL in the WHERE clause did not
return correct results.
(Bug#32815)
For queries containing GROUP_CONCAT(DISTINCT
, there was a
limitation that the col_list ORDER BY
col_list)DISTINCT columns had to
be the same as ORDER BY columns. Incorrect
results could be returned if this was not true.
(Bug#32798)
Use of the cp932 character set with
CAST() in an ORDER
BY clause could cause a server crash.
(Bug#32726)
A subquery using an IS NULL check of a column
defined as NOT NULL in a table used in the
FROM clause of the outer query produced an
invalid result.
(Bug#32694)
Specifying a nonexistent column for an
INSERT DELAYED statement caused a
server crash rather than producing an error.
(Bug#32676)
Use of CLIENT_MULTI_QUERIES caused
libmysqld to crash.
(Bug#32624)
The INTERVAL() function
incorrectly handled NULL values in the value
list.
(Bug#32560)
Use of a NULL-returning GROUP
BY expression in conjunction with WITH
ROLLUP could cause a server crash.
(Bug#32558)
See also Bug#31095.
A SELECT ... GROUP BY
query failed
with an assertion if the length of the
bit_columnBIT column used for the
GROUP BY was not an integer multiple of 8.
(Bug#32556)
Using SELECT INTO OUTFILE with 8-bit
ENCLOSED BY characters led to corrupted data
when the data was reloaded using LOAD DATA INFILE. This was
because SELECT INTO OUTFILE failed to escape
the 8-bit characters.
(Bug#32533)
For FLUSH TABLES WITH
READ LOCK, the server failed to properly detect
write-locked tables when running with low-priority updates,
resulting in a crash or deadlock.
(Bug#32528)
A build problem introduced in MySQL 5.0.52 was resolved: The x86 32-bit Intel icc-compiled server binary had unwanted dependences on Intel icc runtime libraries. (Bug#32514)
The rules for valid column names were being applied differently for base tables and views. (Bug#32496)
Sending several KILL
QUERY statements to target a connection running
SELECT SLEEP() could freeze the server.
(Bug#32436)
ssl-cipher values in option files were not
being read by libmysqlclient.
(Bug#32429)
Repeated execution of a query containing a
CASE
expression and numerous AND and
OR relations could crash the server. The root
cause of the issue was determined to be that the internal
SEL_ARG structure was not properly
initialized when created.
(Bug#32403)
Referencing within a subquery an alias used in the
SELECT list of the outer query
was incorrectly permitted.
(Bug#32400)
An ORDER BY query on a view created using a
FEDERATED table as a base table caused the
server to crash.
(Bug#32374)
Comparison of a BIGINT NOT NULL column with a
constant arithmetic expression that evaluated to NULL mistakenly
caused the error Column '...' cannot be
null (error 1048).
(Bug#32335)
Assigning a 65,536-byte string to a
TEXT column (which can hold a
maximum of 65,535 bytes) resulted in truncation without a
warning. Now a truncation warning is generated.
(Bug#32282)
The LAST_DAY() function returns a
DATE value, but internally the
value did not have the time fields zeroed and calculations
involving the value could return incorrect results.
(Bug#32270)
MIN() and
MAX() could return incorrect
results when an index was present if a loose index scan was
used.
(Bug#32268)
Memory corruption could occur due to large index map in
Range checked for each record status reported
by EXPLAIN
SELECT. The problem was based in an incorrectly
calculated length of the buffer used to store a hexadecimal
representation of an index map, which could result in buffer
overrun and stack corruption under some circumstances.
(Bug#32241)
Various test program cleanups were made: 1)
mytest and libmysqltest
were removed. 2) bug25714 displays an error
message when invoked with incorrect arguments or the
--help option. 3)
mysql_client_test exits cleanly with a proper
error status.
(Bug#32221)
The default grant tables on Windows contained information for
host production.mysql.com, which should not
be there.
(Bug#32219)
Under certain conditions, the presence of a GROUP
BY clause could cause an ORDER BY
clause to be ignored.
(Bug#32202)
For comparisons of the form date_col OP
datetime_const (where
OP is
=,
<,
>,
<=,
or
>=),
the comparison is done using
DATETIME values, per the fix for
Bug#27590. However that fix caused any index on
date_col not to be used and
compromised performance. Now the index is used again.
(Bug#32198)
DATETIME arguments specified in
numeric form were treated by
DATE_ADD() as
DATE values.
(Bug#32180)
InnoDB does not support
SPATIAL indexes, but could crash when asked
to handle one. Now an error is returned.
(Bug#32125)
The server crashed on optimizations involving a join of
INT and
MEDIUMINT columns and a system
variable in the WHERE clause.
(Bug#32103)
With lower_case_table_names
set, CREATE TABLE LIKE was treated
differently by libmysqld than by the
nonembedded server.
(Bug#32063)
Within a subquery, UNION was
handled differently than at the top level, which could result in
incorrect results or a server crash.
(Bug#32036, Bug#32051)
User-defined functions are not loaded if the server is started
with the --skip-grant-tables
option, but the server did not properly handle this case and
issued an Out of memory error message
instead.
(Bug#32020)
HOUR(),
MINUTE(), and
SECOND() could return nonzero
values for DATE arguments.
(Bug#31990)
A column with malformed multi-byte characters could cause the full-text parser to go into an infinite loop. (Bug#31950)
Changing the SQL mode to cause dates with “zero”
parts to be considered invalid (such as
'1000-00-00') could result in indexed and
nonindexed searches returning different results for a column
that contained such dates.
(Bug#31928)
In debug builds, testing the result of an IN
subquery against NULL caused an assertion
failure.
(Bug#31884)
mysql-test-run.pl sometimes set up test scenarios in which the same port number was passed to multiple servers, causing one of them to be unable to start. (Bug#31880)
Comparison results for BETWEEN were
different from those for operators like
< and
> for
DATETIME-like values with
trailing extra characters such as '2007-10-01 00:00:00
GMT-6'. BETWEEN treated
the values as DATETIME, whereas
the other operators performed a binary-string comparison. Now
they all uniformly use a DATETIME
comparison, but generate warnings for values with trailing
garbage.
(Bug#31800)
Name resolution for correlated subqueries and
HAVING clauses failed to distinguish which of
two was being performed when there was a reference to an outer
aliased field. This could result in error messages about a
HAVING clause for queries that had no such
clause.
(Bug#31797)
The server could crash during filesort for
ORDER BY based on expressions with
INET_NTOA() or
OCT() if those functions returned
NULL.
(Bug#31758)
For a fatal error during a filesort in
find_all_keys(), the error was returned
without the necessary handler uninitialization, causing an
assertion failure.
(Bug#31742)
The examined-rows count was not incremented for
const queries.
(Bug#31700)
The mysql_change_user() C API
function was subject to buffer overflow.
(Bug#31669)
For SELECT ... INTO
OUTFILE, if the ENCLOSED BY string
is empty and the FIELDS TERMINATED BY string
started with a special character (one of n,
t, r,
b, 0,
Z, or N), every occurrence
of the character within field values would be duplicated.
(Bug#31663)
SHOW COLUMNS and
DESCRIBE displayed
null as the column type for a view with no
valid definer. This caused mysqldump to
produce a nonreloadable dump file for the view.
(Bug#31662)
The mysqlbug script did not include the
correct values of CFLAGS and
CXXFLAGS that were used to configure the
distribution.
(Bug#31644)
ucs2 does not work as a client character set,
but attempts to use it as such were not rejected. Now
character_set_client cannot be
set to ucs2. This also affects statements
such as SET NAMES and SET CHARACTER
SET.
(Bug#31615)
A buffer used when setting variables was not dimensioned to
accommodate the trailing '\0' byte, so a
single-byte buffer overrun was possible.
(Bug#31588)
HAVING could treat lettercase of table
aliases incorrectly if
lower_case_table_names was
enabled.
(Bug#31562)
The fix for Bug#24989 introduced a problem such that a
NULL thread handler could be used during a
rollback operation. This problem is unlikely to be seen in
practice.
(Bug#31517)
Killing a CREATE TABLE ... LIKE statement
that was waiting for a name lock caused a server crash. When the
statement was killed, the server attempted to release locks that
were not held.
(Bug#31479)
The length of the result from
IFNULL() could be calculated
incorrectly because the sign of the result was not taken into
account.
(Bug#31471)
Queries that used the ref
access method or index-based subquery execution over indexes
that have DECIMAL columns could
fail with an error Column
.
(Bug#31450)col_name cannot be null
SELECT 1 REGEX NULL caused an assertion
failure for debug servers.
(Bug#31440)
Executing RENAME while tables were open for
use with HANDLER statements could
cause a server crash.
(Bug#31409)
mysql-test-run.pl tried to create files in a
directory where it could not be expected to have write
permission. mysqltest created
.reject files in a directory other than the
one where test results go.
(Bug#31398)
For an almost-full MyISAM table, an insert
that failed could leave the table in a corrupt state.
(Bug#31305)
myisamchk --unpack could corrupt a table that when unpacked has static (fixed-length) row format. (Bug#31277)
CONVERT( would fail on invalid input, but processing
was not aborted for the val,
DATETIME)WHERE clause, leading
to a server crash.
(Bug#31253)
Allocation of an insufficiently large group-by buffer following creation of a temporary table could lead to a server crash. (Bug#31249)
Use of DECIMAL( in
n,
n) ZEROFILLGROUP_CONCAT() could cause a
server crash.
(Bug#31227)
Server variables could not be set to their current values on Linux platforms. (Bug#31177)
See also Bug#6958.
WIth small values of
myisam_sort_buffer_size,
REPAIR TABLE for
MyISAM tables could cause a server crash.
(Bug#31174)
If MAKETIME() returned
NULL when used in an ORDER
BY that was evaluated using
filesort, a server crash could result.
(Bug#31160)
Full-text searches on ucs2 columns caused a
server crash. (FULLTEXT indexes on
ucs2 columns cannot be used, but it should be
possible to perform IN BOOLEAN MODE searches
on ucs2 columns without a crash.)
(Bug#31159)
Data in BLOB or
GEOMETRY columns could be cropped when
performing a UNION query.
(Bug#31158)
An assertion designed to detect a bug in the
ROLLUP implementation would incorrectly be
triggered when used in a subquery context with noncacheable
statements.
(Bug#31156)
Selecting spatial types in a
UNION could cause a server crash.
(Bug#31155)
Use of GROUP_CONCAT(DISTINCT
caused an
assertion failure.
(Bug#31154)bit_column)
The server crashed in the parser when running out of memory. Memory handling in the parser has been improved to gracefully return an error when out-of-memory conditions occur in the parser. (Bug#31153)
MySQL declares a UNIQUE key as a
PRIMARY key if it doesn't have
NULL columns and is not a partial key, and
the PRIMARY key must alway be the first key.
However, in some cases, a nonfirst key could be reported as
PRIMARY, leading to an assert failure by
InnoDB. This is fixed by correcting the key
sort order.
(Bug#31137)
GROUP BY NULL WITH ROLLUP could cause a
server crash.
(Bug#31095)
See also Bug#32558.
REGEXP operations could cause a
server crash for character sets such as ucs2.
Now the arguments are converted to utf8 if
possible, to allow correct results to be produced if the
resulting strings contain only 8-bit characters.
(Bug#31081)
Internal conversion routines could fail for several multi-byte
character sets (big5,
cp932, euckr,
gb2312, sjis) for empty
strings or during evaluation of SOUNDS
LIKE.
(Bug#31069, Bug#31070)
Many nested subqueries in a single query could led to excessive memory consumption and possibly a crash of the server. (Bug#31048)
The MOD() function and the
% operator crashed the server for a divisor
less than 1 with a very long fractional part.
(Bug#31019)
On Windows, the pthread_mutex_trylock()
implementation was incorrect.
(Bug#30992)
A character set introducer followed by a hexadecimal or bit-value literal did not check its argument and could return an ill-formed result for invalid input. (Bug#30986)
CHAR( did not check its
argument and could return an ill-formed result for invalid
input.
(Bug#30982)str USING
charset)
The result from
CHAR() did not add a leading 0x00 byte for input
strings with an odd number of bytes.
(Bug#30981)str USING
ucs2
The GeomFromText() function could
cause a server crash if the first argument was
NULL or the empty string.
(Bug#30955)
MAKEDATE() incorrectly moved year
values in the 100–200 range into the 1970–2069
range. (This is legitimate for 00–99, but three-digit
years should be used unchanged.)
(Bug#30951)
When invoked with constant arguments,
STR_TO_DATE() could use a cached
value for the format string and return incorrect results.
(Bug#30942)
GROUP_CONCAT() returned
',' rather than an empty string when the
argument column contained only empty strings.
(Bug#30897)
ROUND(
or
X,D)TRUNCATE(
for nonconstant values of X,D)D could
crash the server if these functions were used in an
ORDER BY that was resolved using
filesort.
(Bug#30889)
For MEMORY tables, lookups for
NULL values in BTREE
indexes could return incorrect results.
(Bug#30885)
Calling NAME_CONST() with
nonconstant arguments triggered an assertion failure.
Nonconstant arguments are now disallowed.
(Bug#30832)
For a spatial column with a regular
(non-SPATIAL) index, queries failed if the
optimizer tried to use the index.
(Bug#30825)
Values for the --tc-heuristic-recover option
incorrectly were treated as values for the
--myisam-stats-method option.
(Bug#30821)
The optimizer incorrectly optimized conditions out of the
WHERE clause in some queries involving
subqueries and indexed columns.
(Bug#30788)
Improper calculation of CASE
expression results could lead to value truncation.
(Bug#30782)
On Windows, the pthread_mutex_trylock()
implementation was incorrect. One symptom was that invalidating
the query cache could cause a server crash.
(Bug#30768)
A multiple-table UPDATE involving
transactional and nontransactional tables caused an assertion
failure.
(Bug#30763)
Under some circumstances,
CREATE TABLE ...
SELECT could crash the server or incorrectly report
that the table row size was too large.
(Bug#30736)
Using the MIN() or
MAX() function to select one part
of a multi-part key could cause a crash when the function result
was NULL.
(Bug#30715)
The optimizer could ignore ORDER BY in cases
when the result set is ordered by filesort,
resulting in rows being returned in incorrect order.
(Bug#30666)
MyISAM tables could not exceed 4294967295
(2^32 - 1) rows on Windows.
(Bug#30638)
mysql-test-run.pl could not run
mysqld with root
privileges.
(Bug#30630)
For MEMORY tables,
DELETE statements that remove
rows based on an index read could fail to remove all matching
rows.
(Bug#30590)
Using GROUP BY on an expression of the form
timestamp_col DIV
number
The options available to the CHECK
TABLE statement were also allowed in
OPTIMIZE TABLE and
ANALYZE TABLE statements, but
caused corruption during their execution. These options were
never supported for these statements, and an error is now raised
if you try to apply these options to these statements.
(Bug#30495)
When expanding a * in a
USING or NATURAL join, the
check for table access for both tables in the join was done
using only the grant information of the first table.
(Bug#30468)
When casting a string value to an integer, cases where the input
string contained a decimal point and was long enough to overrun
the unsigned long long type were not handled
correctly. The position of the decimal point was not taken into
account which resulted in miscalculated numbers and incorrect
truncation to appropriate SQL data type limits.
(Bug#30453)
Versions of mysqldump from MySQL 4.1 or
higher tried to use START TRANSACTION WITH CONSISTENT
SNAPSHOT if the
--single-transaction and
--master-data options were
given, even with servers older than 4.1 that do not support
consistent snapshots.
(Bug#30444)
For CREATE ... SELECT ... FROM, where the
resulting table contained indexes, adding
SQL_BUFFER_RESULT to the
SELECT part caused index
corruption in the table.
(Bug#30384)
The optimizer made incorrect assumptions about the value of the
is_member value for user-defined functions,
sometimes resulting in incorrect ordering of UDF results.
(Bug#30355)
Some valid euc-kr characters having the
second byte in the ranges [0x41..0x5A] and
[0x61..0x7A] were rejected.
(Bug#30315)
Simultaneous ALTER TABLE
statements for BLACKHOLE tables caused 100%
CPU use due to locking problems.
(Bug#30294)
Setting certain values on a table using a spatial index could cause the server to crash. (Bug#30286)
Tables with a GEOMETRY column could be marked
as corrupt if you added a non-SPATIAL index
on a GEOMETRY column.
(Bug#30284)
Some INFORMATION_SCHEMA tables are intended
for internal use, but could be accessed by using
SHOW statements.
(Bug#30079)
On some 64-bit systems, inserting the largest negative value
into a BIGINT column resulted in
incorrect data.
(Bug#30069)
Specifying the --without-geometry option for
configure caused server compilation to fail.
(Bug#29972)
Under some circumstances, a UDF initialization function could be passed incorrect argument lengths. (Bug#29804)
configure did not find nss
on some Linux platforms.
(Bug#29658)
InnoDB had a race condition for an adaptive
hash rw-lock waiting for an X-lock. This fix may also provide
significant speed improvements on systems experiencing problems
with contention for the adaptive hash index.
(Bug#29560)
Views were treated as insertable even if some base table columns with no default value were omitted from the view definition. (This is contrary to the condition for insertability that a view must contain all columns in the base table that do not have a default value.) (Bug#29477)
The mysql client program now ignores Unicode byte order mark (BOM) characters at the beginning of input files. Previously, it read them and sent them to the server, resulting in a syntax error.
Presence of a BOM does not cause mysql to
change its default character set. To do that, invoke
mysql with an option such as
--default-character-set=utf8.
(Bug#29323)
For transactional tables, an error during a multiple-table
DELETE statement did not roll
back the statement.
(Bug#29136)
The log and
log_slow_queries system
variables were displayed by SHOW
VARIABLES but could not be accessed in expressions as
@@log and
@@log_slow_queries. Also, attempting to set
them with SET produced an incorrect
Unknown system variable message. Now these
variables can be accessed in expressions and attempting to set
their values produces an error message that the variable is read
only.
(Bug#29131)
Denormalized double-precision numbers cannot be handled properly by old MIPS pocessors. For IRIX, this is now handled by enabling a mode to use a software workaround. (Bug#29085)
SHOW VARIABLES did not display
the relay_log,
relay_log_index, or
relay_log_info_file system variables.
(Bug#28893)
When doing a DELETE on a table
that involved a JOIN with
MyISAM or MERGE tables and
the JOIN referred to the same table, the
operation could fail reporting ERROR 1030 (HY000): Got
error 134 from storage engine. This was because scans
on the table contents would change because of rows that had
already been deleted.
(Bug#28837)
On Windows, mysql_upgrade created temporary
files in C:\ and did not clean them up.
(Bug#28774)
Index hints specified in view definitions were ignored when using the view to select from the base table. (Bug#28702)
Views do not have indexes, so index hints do not apply. Use of index hints when selecting from a view is now disallowed. (Bug#28701)
After changing the SQL mode to a restrictive value that would make already-inserted dates in a column be considered invalid, searches returned different results depending on whether the column was indexed. (Bug#28687)
The result from CHAR() was
incorrectly assumed in some contexts to return a single-byte
result.
(Bug#28550)
The parser confused user-defined function (UDF) and stored
function creation for CREATE
FUNCTION and required that there be a default database
when creating UDFs, although there is no such requirement.
(Bug#28318, Bug#29816)
The result of a comparison between
VARBINARY and
BINARY columns differed depending
on whether the VARBINARY column
was indexed.
(Bug#28076)
The metadata in some MYSQL_FIELD members
could be incorrect when a temporary table was used to evaluate a
query.
(Bug#27990)
An ORDER BY at the end of a
UNION affected individual
SELECT statements rather than the
overall query result.
(Bug#27848)
comp_err created files with permissions such that they might be inaccessible during make install operations. (Bug#27789)
The anonymous accounts were not being created during MySQL installation. (Bug#27692)
A race condition between killing a statement and the thread executing the statement could lead to a situation such that the binary log contained an event indicating that the statement was killed, whereas the statement actually executed to completion. (Bug#27571)
Some queries using the
NAME_CONST() function failed to
return either a result or an error to the client, causing it to
hang. This was due to the fact that there was no check to insure
that both arguments to this function were constant expressions.
(Bug#27545, Bug#32559)
With the read_only system
variable enabled, CREATE DATABASE
and DROP DATABASE were allowed to
users who did not have the SUPER
privilege.
(Bug#27440)
resolveip failed to produce correct results for host names that begin with a digit. (Bug#27427)
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.
mysqlcheck -A -r did not correctly identify all tables that needed repairing. (Bug#25347)
If the expected precision of an arithmetic expression exceeded the maximum precision supported by MySQL, the precision of the result was reduced by an unpredictable or arbitrary amount, rather than to the maximum precision. In some cases, exceeding the maximum supported precision could also lead to a crash of the server. (Bug#24907)
For Windows Vista, MySQLInstanceConfig.exe did not include a proper manifest enabling it to run with administrative privileges. (Bug#22563)
See also Bug#24732.
mysqldumpslow returned a confusing error message when no configuration file was found. (Bug#20455)
Host names sometimes were treated as case sensitive in
account-management statements (CREATE
USER, GRANT,
REVOKE, and so forth).
(Bug#19828)
The readline library has been updated to
version 5.2. This addresses issues in the
mysql client where history and editing within
the client would fail to work as expected.
(Bug#18431)
The Aborted_clients status
variable was incremented twice if a client exited without
calling mysql_close().
(Bug#16918)
Clients were ignoring the TCP/IP port number specified as the default port via the --with-tcp-port configuration option. (Bug#15327)
Zero-padding of exponent values was not the same across platforms. (Bug#12860)
Values of types REAL ZEROFILL,
DOUBLE ZEROFILL, FLOAT
ZEROFILL, were not zero-filled when converted to a
character representation in the C prepared statement API.
(Bug#11589)
mysql stripped comments from statements sent
to the server. Now the
--comments or
--skip-comments option can be
used to control whether to retain or strip comments. The default
is --skip-comments.
(Bug#11230, Bug#26215)
If an INSERT ...
SELECT statement is executed, and no automatically
generated value is successfully inserted, then
mysql_insert_id() returns the ID
of the last inserted row.
If no automatically generated value is successfully inserted,
then mysql_insert_id() returns
0.
(Bug#9481)
Several buffer-size system variables were either being handled incorrectly for large values (for settings larger than 4GB, they were truncated to values less than 4GB without a warning), or were limited unnecessarily to 4GB even on 64-bit systems. The following changes were made:
For key_buffer_size, values
larger than 4GB are allowed on 64-bit platforms (except
Windows, for which large values are truncated to 4GB with a
warning).
For join_buffer_size,
sort_buffer_size, and
myisam_sort_buffer_size,
values are limited to 4GB on all platforms. Larger values
are truncated to 4GB with a warning.
In addition, settings for
read_buffer_size and
read_rnd_buffer_size are
limited to 2GB on all platforms. Larger values are truncated to
2GB with a warning.
(Bug#5731, Bug#29419, Bug#29446)
Executing DISABLE KEYS and ENABLE
KEYS on a nonempty table would cause the size of the
index file for the table to grow considerable. This was because
the DISABLE KEYS operation would only mark
the existing index, without deleting the index blocks. The
ENABLE KEYS operation would re-create the
index, adding new blocks, while the previous index blocks would
remain. Existing indexes are now dropped and recreated when the
ENABLE KEYS statement is executed.
(Bug#4692)
This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.54). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Bugs fixed:
Important Change: MySQL Cluster:
AUTO_INCREMENT columns had the following
problems when used in NDB tables:
The AUTO_INCREMENT counter was not
updated correctly when such a column was updated.
AUTO_INCREMENT values were not
prefetched beyond statement boundaries.
AUTO_INCREMENT values were not handled
correctly with
INSERT
IGNORE statements.
After being set,
ndb_autoincrement_prefetch_sz
showed a value of 1, regardless of the value it had
actually been set to.
As part of this fix, the behavior of
ndb_autoincrement_prefetch_sz
has changed. Setting this to less than 32 no longer has any
effect on prefetching within statements (where IDs are now
always obtained in batches of 32 or more), but only between
statements. The default value for this variable has also
changed, and is now 1.
(Bug#25176, Bug#31956, Bug#32055)
Important Change: Replication:
When the master crashed during an update on a transactional
table while in autocommit mode,
the slave failed. This fix causes every transaction (including
autocommit transactions) to be
recorded in the binlog as starting with a
BEGIN and
ending with a COMMIT or
ROLLBACK.
(Bug#26395)
Replication: Important Note: Network timeouts between the master and the slave could result in corruption of the relay log. This fix rectifies a long-standing replication issue when using unreliable networks, including replication over wide area networks such as the Internet. If you experience reliability issues and see many You have an error in your SQL syntax errors on replication slaves, we strongly recommend that you upgrade to a MySQL version which includes this fix. (Bug#26489)
MySQL Cluster:
An improperly reset internal signal was observed as a hang when
using events in the NDB API but
could result in various errors.
(Bug#33206)
MySQL Cluster: Incorrectly handled parameters could lead to a crash in the Transaction Coordinator during a node failure, causing other data nodes to fail. (Bug#33168)
MySQL Cluster: The failure of a master node could lead to subsequent failures in local checkpointing. (Bug#32160)
MySQL Cluster:
Primary keys on variable-length columns (such as
VARCHAR) did not work correctly.
(Bug#31635)
MySQL Cluster:
When inserting a row into an NDB
table with a duplicate value for a nonprimary unique key, the
error issued would reference the wrong key.
This improves on an initial fix for this issue made in MySQL 5.0.30 and MySQL 5.0.33 (Bug#21072)
Replication:
A CREATE USER,
DROP USER, or
RENAME USER statement that fails
on the master, or that is a duplicate of any of these
statements, is no longer written to the binlog; previously,
either of these occurrences could cause the slave to fail.
See also Bug#29749.
Replication:
SHOW BINLOG EVENTS could fail
when the binlog contained one or more events whose size was
close to the value of
max_allowed_packet.
(Bug#33413)
Replication:
SQL statements containing comments using --
syntax were not replayable by mysqlbinlog,
even though such statements replicated correctly.
(Bug#32205)
Replication:
Issuing a DROP VIEW statement
caused replication to fail if the view did not actually exist.
(Bug#30998)
Replication:
Replication of LOAD
DATA INFILE could fail when
read_buffer_size was larger
than max_allowed_packet.
(Bug#30435)
Replication:
Setting server_id did not
update its value for the current session.
(Bug#28908)
The server crashed when executing a query that had a subquery
containing an equality X=Y where Y referred to a named select
list expression from the parent select. The server crashed when
trying to use the X=Y equality for
ref-based access.
(Bug#33794)
Use of uninitialized memory for filesort in a
subquery caused a server crash.
(Bug#33675)
The server could crash when
REPEAT
or another control instruction was used in conjunction with
labels and a
LEAVE
instruction.
(Bug#33618)
The parser allowed control structures in compound statements to have mismatched beginning and ending labels. (Bug#33618)
SET GLOBAL myisam_max_sort_file_size=DEFAULT
set myisam_max_sort_file_size
to an incorrect value.
(Bug#33382)
See also Bug#31177.
CREATE TABLE ...
SELECT created tables that for date columns used the
obsolete Field_date type instead of
Field_newdate.
(Bug#33256)
For DECIMAL columns used with the
ROUND(
or
X,D)TRUNCATE(
function with a nonconstant value of
X,D)D, adding an ORDER
BY for the function result produced misordered output.
(Bug#33143)
Some valid SELECT statements
could not be used as views due to incorrect column reference
resolution.
(Bug#33133)
The fix for Bug#11230 and Bug#26215 introduced a significant input-parsing slowdown for the mysql client. This has been corrected. (Bug#33057)
UNION constructs cannot contain
SELECT ... INTO except in the final
SELECT. However, if a
UNION was used in a subquery and
an INTO clause appeared in the top-level
query, the parser interpreted it as having appeared in the
UNION and raised an error.
(Bug#32858)
The correct data type for a NULL column
resulting from a UNION could be
determined incorrectly in some cases: 1) Not correctly inferred
as NULL depending on the number of selects;
2) Not inferred correctly as NULL if one
select used a subquery.
(Bug#32848)
For queries containing GROUP_CONCAT(DISTINCT
, there was a
limitation that the col_list ORDER BY
col_list)DISTINCT columns had to
be the same as ORDER BY columns. Incorrect
results could be returned if this was not true.
(Bug#32798)
HOUR(),
MINUTE(), and
SECOND() could return nonzero
values for DATE arguments.
(Bug#31990)
mysql-test-run.pl sometimes set up test scenarios in which the same port number was passed to multiple servers, causing one of them to be unable to start. (Bug#31880)
Name resolution for correlated subqueries and
HAVING clauses failed to distinguish which of
two was being performed when there was a reference to an outer
aliased field. This could result in error messages about a
HAVING clause for queries that had no such
clause.
(Bug#31797)
ROUND(
or
X,D)TRUNCATE(
for nonconstant values of X,D)D could
crash the server if these functions were used in an
ORDER BY that was resolved using
filesort.
(Bug#30889)
Views were treated as insertable even if some base table columns with no default value were omitted from the view definition. (This is contrary to the condition for insertability that a view must contain all columns in the base table that do not have a default value.) (Bug#29477)
An ORDER BY at the end of a
UNION affected individual
SELECT statements rather than the
overall query result.
(Bug#27848)
With the read_only system
variable enabled, CREATE DATABASE
and DROP DATABASE were allowed to
users who did not have the SUPER
privilege.
(Bug#27440)
resolveip failed to produce correct results for host names that begin with a digit. (Bug#27427)
mysqlcheck -A -r did not correctly identify all tables that needed repairing. (Bug#25347)
For Windows Vista, MySQLInstanceConfig.exe did not include a proper manifest enabling it to run with administrative privileges. (Bug#22563)
See also Bug#24732.
mysqldumpslow returned a confusing error message when no configuration file was found. (Bug#20455)
This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This is a bugfix release that replaces MySQL 5.0.54.
Bugs fixed:
Security Fix: Three vulnerabilities in yaSSL versions 1.7.5 and earlier were discovered that could lead to a server crash or execution of unauthorized code. The exploit requires a server with yaSSL enabled and TCP/IP connections enabled, but does not require valid MySQL account credentials. The exploit does not apply to OpenSSL.
The proof-of-concept exploit is freely available on the Internet. Everyone with a vulnerable MySQL configuration is advised to upgrade immediately.
This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.52). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Functionality added or changed:
The mysql_odbc_escape_string() C API
function has been removed. It has multi-byte character escaping
issues, doesn't honor the
NO_BACKSLASH_ESCAPES SQL mode
and is not needed anymore by Connector/ODBC as of 3.51.17.
(Bug#29592)
The argument for the mysql-test-run.pl
--do-test and --skip-test
options is now interpreted as a Perl regular expression if there
is a pattern metacharacter in the argument value. This allows
more flexible specification of which tests to perform or skip.
Bugs fixed:
Security Enhancement: It was possible to force an error message of excessive length which could lead to a buffer overflow. This has been made no longer possible as a security precaution. (Bug#32707)
Incompatible Change: The MySQL 5.0.50 patch for this bug was reverted because it changed the behavior of a General Availability MySQL release. (Bug#30234)
See also Bug#27525.
Incompatible Change: It was possible for option files to be read twice at program startup, if some of the standard option file locations turned out to be the same directory. Now duplicates are removed from the list of files to be read.
Also, users could not override system-wide settings using
~/.my.cnf because
SYSCONFDIR/my.cnf~/.my.cnf can override system-wide
settings.
The fix for this problem had a side effect such that on Unix,
MySQL programs looked for options in
~/my.cnf rather than the standard location
of ~/.my.cnf. That problem was addressed as
Bug#38180.
(Bug#20748)
Replication: It was possible for the name of the relay log file to exceed the amount of memory reserved for it, possibly leading to a crash of the server. (Bug#31836)
See also Bug#28597.
Replication: Corruption of log events caused the server to crash on 64-bit Linux systems having 4 GB of memory or more. (Bug#31793)
Replication: One thread could read uninitialized memory from the stack of another thread. This issue was only known to occur in a mysqld process acting as both a master and a slave. (Bug#30752)
Replication: Due a previous change in how the default name and location of the binary log file were determined, replication failed following some upgrades. (Bug#28597, Bug#28603)
See also Bug#31836.
This regression was introduced by Bug#20166.
Replication:
Stored procedures having BIT
parameters were not replicated correctly.
(Bug#26199)
Replication:
Issuing SHOW SLAVE STATUS as
mysqld was shutting down could cause a crash.
(Bug#26000)
Replication:
An UPDATE statement using a
stored function that modified a nontransactional table was not
logged if it failed. This caused the copy of the
nontransactional table on the master have a row that the copy on
the slave did not.
In addition, when an
INSERT ...
ON DUPLICATE KEY UPDATE statement encountered a
duplicate key constraint, but the
UPDATE did not actually change
any data, the statement was not logged. As a result of this fix,
such statements are now treated the same for logging purposes as
other UPDATE statements, and so
are written to the binary log.
(Bug#23333)
See also Bug#12713.
Replication:
A replication slave sometimes failed to reconnect because it was
unable to run SHOW SLAVE HOSTS.
It was not necessary to run this statement on slaves (since the
master should track connection IDs), and the execution of this
statement by slaves was removed.
(Bug#21132)
An ORDER BY query using IS
NULL in the WHERE clause did not
return correct results.
(Bug#32815)
Use of the cp932 character set with
CAST() in an ORDER
BY clause could cause a server crash.
(Bug#32726)
A subquery using an IS NULL check of a column
defined as NOT NULL in a table used in the
FROM clause of the outer query produced an
invalid result.
(Bug#32694)
Specifying a nonexistent column for an
INSERT DELAYED statement caused a
server crash rather than producing an error.
(Bug#32676)
Use of CLIENT_MULTI_QUERIES caused
libmysqld to crash.
(Bug#32624)
The INTERVAL() function
incorrectly handled NULL values in the value
list.
(Bug#32560)
Use of a NULL-returning GROUP
BY expression in conjunction with WITH
ROLLUP could cause a server crash.
(Bug#32558)
See also Bug#31095.
A SELECT ... GROUP BY
query failed
with an assertion if the length of the
bit_columnBIT column used for the
GROUP BY was not an integer multiple of 8.
(Bug#32556)
Using SELECT INTO OUTFILE with 8-bit
ENCLOSED BY characters led to corrupted data
when the data was reloaded using LOAD DATA INFILE. This was
because SELECT INTO OUTFILE failed to escape
the 8-bit characters.
(Bug#32533)
For FLUSH TABLES WITH
READ LOCK, the server failed to properly detect
write-locked tables when running with low-priority updates,
resulting in a crash or deadlock.
(Bug#32528)
Sending several KILL
QUERY statements to target a connection running
SELECT SLEEP() could freeze the server.
(Bug#32436)
ssl-cipher values in option files were not
being read by libmysqlclient.
(Bug#32429)
Repeated execution of a query containing a
CASE
expression and numerous AND and
OR relations could crash the server. The root
cause of the issue was determined to be that the internal
SEL_ARG structure was not properly
initialized when created.
(Bug#32403)
Referencing within a subquery an alias used in the
SELECT list of the outer query
was incorrectly permitted.
(Bug#32400)
An ORDER BY query on a view created using a
FEDERATED table as a base table caused the
server to crash.
(Bug#32374)
Comparison of a BIGINT NOT NULL column with a
constant arithmetic expression that evaluated to NULL mistakenly
caused the error Column '...' cannot be
null (error 1048).
(Bug#32335)
Assigning a 65,536-byte string to a
TEXT column (which can hold a
maximum of 65,535 bytes) resulted in truncation without a
warning. Now a truncation warning is generated.
(Bug#32282)
The LAST_DAY() function returns a
DATE value, but internally the
value did not have the time fields zeroed and calculations
involving the value could return incorrect results.
(Bug#32270)
MIN() and
MAX() could return incorrect
results when an index was present if a loose index scan was
used.
(Bug#32268)
Memory corruption could occur due to large index map in
Range checked for each record status reported
by EXPLAIN
SELECT. The problem was based in an incorrectly
calculated length of the buffer used to store a hexadecimal
representation of an index map, which could result in buffer
overrun and stack corruption under some circumstances.
(Bug#32241)
Various test program cleanups were made: 1)
mytest and libmysqltest
were removed. 2) bug25714 displays an error
message when invoked with incorrect arguments or the
--help option. 3)
mysql_client_test exits cleanly with a proper
error status.
(Bug#32221)
For comparisons of the form date_col OP
datetime_const (where
OP is
=,
<,
>,
<=,
or
>=),
the comparison is done using
DATETIME values, per the fix for
Bug#27590. However that fix caused any index on
date_col not to be used and
compromised performance. Now the index is used again.
(Bug#32198)
DATETIME arguments specified in
numeric form were treated by
DATE_ADD() as
DATE values.
(Bug#32180)
InnoDB does not support
SPATIAL indexes, but could crash when asked
to handle one. Now an error is returned.
(Bug#32125)
With lower_case_table_names
set, CREATE TABLE LIKE was treated
differently by libmysqld than by the
nonembedded server.
(Bug#32063)
Within a subquery, UNION was
handled differently than at the top level, which could result in
incorrect results or a server crash.
(Bug#32036, Bug#32051)
Changing the SQL mode to cause dates with “zero”
parts to be considered invalid (such as
'1000-00-00') could result in indexed and
nonindexed searches returning different results for a column
that contained such dates.
(Bug#31928)
ucs2 does not work as a client character set,
but attempts to use it as such were not rejected. Now
character_set_client cannot be
set to ucs2. This also affects statements
such as SET NAMES and SET CHARACTER
SET.
(Bug#31615)
Killing a CREATE TABLE ... LIKE statement
that was waiting for a name lock caused a server crash. When the
statement was killed, the server attempted to release locks that
were not held.
(Bug#31479)
myisamchk --unpack could corrupt a table that when unpacked has static (fixed-length) row format. (Bug#31277)
Server variables could not be set to their current values on Linux platforms. (Bug#31177)
See also Bug#6958.
Data in BLOB or
GEOMETRY columns could be cropped when
performing a UNION query.
(Bug#31158)
The server crashed in the parser when running out of memory. Memory handling in the parser has been improved to gracefully return an error when out-of-memory conditions occur in the parser. (Bug#31153)
MySQL declares a UNIQUE key as a
PRIMARY key if it doesn't have
NULL columns and is not a partial key, and
the PRIMARY key must alway be the first key.
However, in some cases, a nonfirst key could be reported as
PRIMARY, leading to an assert failure by
InnoDB. This is fixed by correcting the key
sort order.
(Bug#31137)
REGEXP operations could cause a
server crash for character sets such as ucs2.
Now the arguments are converted to utf8 if
possible, to allow correct results to be produced if the
resulting strings contain only 8-bit characters.
(Bug#31081)
Many nested subqueries in a single query could led to excessive memory consumption and possibly a crash of the server. (Bug#31048)
The optimizer incorrectly optimized conditions out of the
WHERE clause in some queries involving
subqueries and indexed columns.
(Bug#30788)
Improper calculation of CASE
expression results could lead to value truncation.
(Bug#30782)
A multiple-table UPDATE involving
transactional and nontransactional tables caused an assertion
failure.
(Bug#30763)
mysql-test-run.pl could not run
mysqld with root
privileges.
(Bug#30630)
The options available to the CHECK
TABLE statement were also allowed in
OPTIMIZE TABLE and
ANALYZE TABLE statements, but
caused corruption during their execution. These options were
never supported for these statements, and an error is now raised
if you try to apply these options to these statements.
(Bug#30495)
When casting a string value to an integer, cases where the input
string contained a decimal point and was long enough to overrun
the unsigned long long type were not handled
correctly. The position of the decimal point was not taken into
account which resulted in miscalculated numbers and incorrect
truncation to appropriate SQL data type limits.
(Bug#30453)
For CREATE ... SELECT ... FROM, where the
resulting table contained indexes, adding
SQL_BUFFER_RESULT to the
SELECT part caused index
corruption in the table.
(Bug#30384)
The optimizer made incorrect assumptions about the value of the
is_member value for user-defined functions,
sometimes resulting in incorrect ordering of UDF results.
(Bug#30355)
Some valid euc-kr characters having the
second byte in the ranges [0x41..0x5A] and
[0x61..0x7A] were rejected.
(Bug#30315)
Simultaneous ALTER TABLE
statements for BLACKHOLE tables caused 100%
CPU use due to locking problems.
(Bug#30294)
Tables with a GEOMETRY column could be marked
as corrupt if you added a non-SPATIAL index
on a GEOMETRY column.
(Bug#30284)
On some 64-bit systems, inserting the largest negative value
into a BIGINT column resulted in
incorrect data.
(Bug#30069)
InnoDB had a race condition for an adaptive
hash rw-lock waiting for an X-lock. This fix may also provide
significant speed improvements on systems experiencing problems
with contention for the adaptive hash index.
(Bug#29560)
The mysql client program now ignores Unicode byte order mark (BOM) characters at the beginning of input files. Previously, it read them and sent them to the server, resulting in a syntax error.
Presence of a BOM does not cause mysql to
change its default character set. To do that, invoke
mysql with an option such as
--default-character-set=utf8.
(Bug#29323)
For transactional tables, an error during a multiple-table
DELETE statement did not roll
back the statement.
(Bug#29136)
Denormalized double-precision numbers cannot be handled properly by old MIPS pocessors. For IRIX, this is now handled by enabling a mode to use a software workaround. (Bug#29085)
When doing a DELETE on a table
that involved a JOIN with
MyISAM or MERGE tables and
the JOIN referred to the same table, the
operation could fail reporting ERROR 1030 (HY000): Got
error 134 from storage engine. This was because scans
on the table contents would change because of rows that had
already been deleted.
(Bug#28837)
A race condition between killing a statement and the thread executing the statement could lead to a situation such that the binary log contained an event indicating that the statement was killed, whereas the statement actually executed to completion. (Bug#27571)
Some queries using the
NAME_CONST() function failed to
return either a result or an error to the client, causing it to
hang. This was due to the fact that there was no check to insure
that both arguments to this function were constant expressions.
(Bug#27545, Bug#32559)
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.
If the expected precision of an arithmetic expression exceeded the maximum precision supported by MySQL, the precision of the result was reduced by an unpredictable or arbitrary amount, rather than to the maximum precision. In some cases, exceeding the maximum supported precision could also lead to a crash of the server. (Bug#24907)
Zero-padding of exponent values was not the same across platforms. (Bug#12860)
If an INSERT ...
SELECT statement is executed, and no automatically
generated value is successfully inserted, then
mysql_insert_id() returns the ID
of the last inserted row.
If no automatically generated value is successfully inserted,
then mysql_insert_id() returns
0.
(Bug#9481)
This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.50). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Functionality added or changed:
mysqldump produces a -- Dump
completed on comment
at the end of the dump if
DATE--comments is given. The date
causes dump files for identical data take at different times to
appear to be different. The new options
--dump-date and
--skip-dump-date
control whether the date is added to the comment.
--skip-dump-date
suppresses date printing. The default is
--dump-date (include the date
in the comment).
(Bug#31077)
The default value of the
connect_timeout system variable
was increased from 5 to 10 seconds. This might help in cases
where clients frequently encounter errors of the form
Lost connection to MySQL server at
'.
(Bug#28359)XXX', system error:
errno
The use of InnoDB hash indexes now can be
controlled by setting the new
innodb_adaptive_hash_index
system variable at server startup. By default, this variable is
enabled. See Section 13.2.10.4, “Adaptive Hash Indexes”.
Bugs fixed:
Security Fix:
Using RENAME TABLE against a
table with explicit DATA DIRECTORY and
INDEX DIRECTORY options can be used to
overwrite system table information by replacing the symbolic
link points. the file to which the symlink points.
MySQL will now return an error when the file to which the symlink points already exists. (Bug#32111, CVE-2007-5969)
Security Fix:
ALTER VIEW retained the original
DEFINER value, even when altered by another
user, which could allow that user to gain the access rights of
the view. Now ALTER VIEW is
allowed only to the original definer or users with the
SUPER privilege.
(Bug#29908)
Security Fix:
When using a FEDERATED table, the local
server could be forced to crash if the remote server returned a
result with fewer columns than expected.
(Bug#29801)
Incompatible Change:
With ONLY_FULL_GROUP_BY SQL
mode enabled, queries such as SELECT a FROM t1 HAVING
COUNT(*)>2 were not being rejected as they should
have been.
This fix results in the following behavior:
There is a check against mixing group and nongroup columns
only when
ONLY_FULL_GROUP_BY is
enabled.
This check is done both for the select list and for the
HAVING clause if there is one.
This behavior differs from previous versions as follows:
Previously, the HAVING clause was not
checked when
ONLY_FULL_GROUP_BY was
enabled; now it is checked.
Previously, the select list was checked even when
ONLY_FULL_GROUP_BY was not
enabled; now it is checked only when
ONLY_FULL_GROUP_BY is
enabled.
Incompatible Change: It was possible to create a view having a column whose name consisted of an empty string or space characters only.
One result of this bug fix is that aliases for columns in the
view SELECT statement are checked to ensure
that they are legal column names. In particular, the length must
be within the maximum column length of 64 characters, not the
maximum alias length of 256 characters. This can cause problems
for replication or loading dump files. For additional
information and workarounds, see
Section D.4, “Restrictions on Views”.
(Bug#27695)
See also Bug#31202.
Incompatible Change:
Several type-preserving functions and operators returned an
incorrect result type that does not match their argument types:
COALESCE(),
IF(),
IFNULL(),
LEAST(),
GREATEST(),
CASE. These now aggregate using the
precise SQL types of their arguments rather than the internal
type. In addition, the result type of the
STR_TO_DATE() function is now
DATETIME by default.
(Bug#27216)
MySQL Cluster:
An uninitialized variable in the
NDB storage engine code led to
AUTO_INCREMENT failures when the server was
compiled with gcc 4.2.1.
(Bug#31848)
This regression was introduced by Bug#27437.
MySQL Cluster:
An error with an if statement in
sql/ha_ndbcluster.cc could potentially lead
to an infinite loop in case of failure when working with
AUTO_INCREMENT columns in
NDB tables.
(Bug#31810)
MySQL Cluster:
The NDB storage engine code was not
safe for strict-alias optimization in gcc
4.2.1.
(Bug#31761)
MySQL Cluster: Transaction timeouts were not handled well in some circumstances, leading to excessive number of transactions being aborted unnecessarily. (Bug#30379)
MySQL Cluster: In some cases, the cluster managment server logged entries multiple times following a restart of mgmd. (Bug#29565)
MySQL Cluster: An interpreted program of sufficient size and complexity could cause all cluster data nodes to shut down due to buffer overruns. (Bug#29390)
MySQL Cluster:
UPDATE IGNORE could sometimes fail on
NDB tables due to the use of
unitialized data when checking for duplicate keys to be ignored.
(Bug#25817)
Replication:
Use of the @@hostname system variable in
inserts in mysql_system_tables_data.sql did
not replicate. The workaround is to select its value into a user
variable (which does replicate) and insert that.
(Bug#31167)
A build problem introduced in MySQL 5.0.52 was resolved: The x86 32-bit Intel icc-compiled server binary had unwanted dependences on Intel icc runtime libraries. (Bug#32514)
The rules for valid column names were being applied differently for base tables and views. (Bug#32496)
The default grant tables on Windows contained information for
host production.mysql.com, which should not
be there.
(Bug#32219)
Under certain conditions, the presence of a GROUP
BY clause could cause an ORDER BY
clause to be ignored.
(Bug#32202)
The server crashed on optimizations involving a join of
INT and
MEDIUMINT columns and a system
variable in the WHERE clause.
(Bug#32103)
User-defined functions are not loaded if the server is started
with the --skip-grant-tables
option, but the server did not properly handle this case and
issued an Out of memory error message
instead.
(Bug#32020)
A column with malformed multi-byte characters could cause the full-text parser to go into an infinite loop. (Bug#31950)
In debug builds, testing the result of an IN
subquery against NULL caused an assertion
failure.
(Bug#31884)
Comparison results for BETWEEN were
different from those for operators like
< and
> for
DATETIME-like values with
trailing extra characters such as '2007-10-01 00:00:00
GMT-6'. BETWEEN treated
the values as DATETIME, whereas
the other operators performed a binary-string comparison. Now
they all uniformly use a DATETIME
comparison, but generate warnings for values with trailing
garbage.
(Bug#31800)
The server could crash during filesort for
ORDER BY based on expressions with
INET_NTOA() or
OCT() if those functions returned
NULL.
(Bug#31758)
For a fatal error during a filesort in
find_all_keys(), the error was returned
without the necessary handler uninitialization, causing an
assertion failure.
(Bug#31742)
The examined-rows count was not incremented for
const queries.
(Bug#31700)
The mysql_change_user() C API
function was subject to buffer overflow.
(Bug#31669)
For SELECT ... INTO
OUTFILE, if the ENCLOSED BY string
is empty and the FIELDS TERMINATED BY string
started with a special character (one of n,
t, r,
b, 0,
Z, or N), every occurrence
of the character within field values would be duplicated.
(Bug#31663)
SHOW COLUMNS and
DESCRIBE displayed
null as the column type for a view with no
valid definer. This caused mysqldump to
produce a nonreloadable dump file for the view.
(Bug#31662)
The mysqlbug script did not include the
correct values of CFLAGS and
CXXFLAGS that were used to configure the
distribution.
(Bug#31644)
A buffer used when setting variables was not dimensioned to
accommodate the trailing '\0' byte, so a
single-byte buffer overrun was possible.
(Bug#31588)
HAVING could treat lettercase of table
aliases incorrectly if
lower_case_table_names was
enabled.
(Bug#31562)
The fix for Bug#24989 introduced a problem such that a
NULL thread handler could be used during a
rollback operation. This problem is unlikely to be seen in
practice.
(Bug#31517)
The length of the result from
IFNULL() could be calculated
incorrectly because the sign of the result was not taken into
account.
(Bug#31471)
Queries that used the ref
access method or index-based subquery execution over indexes
that have DECIMAL columns could
fail with an error Column
.
(Bug#31450)col_name cannot be null
SELECT 1 REGEX NULL caused an assertion
failure for debug servers.
(Bug#31440)
Executing RENAME while tables were open for
use with HANDLER statements could
cause a server crash.
(Bug#31409)
mysql-test-run.pl tried to create files in a
directory where it could not be expected to have write
permission. mysqltest created
.reject files in a directory other than the
one where test results go.
(Bug#31398)
For an almost-full MyISAM table, an insert
that failed could leave the table in a corrupt state.
(Bug#31305)
CONVERT( would fail on invalid input, but processing
was not aborted for the val,
DATETIME)WHERE clause, leading
to a server crash.
(Bug#31253)
Allocation of an insufficiently large group-by buffer following creation of a temporary table could lead to a server crash. (Bug#31249)
Use of DECIMAL( in
n,
n) ZEROFILLGROUP_CONCAT() could cause a
server crash.
(Bug#31227)
WIth small values of
myisam_sort_buffer_size,
REPAIR TABLE for
MyISAM tables could cause a server crash.
(Bug#31174)
If MAKETIME() returned
NULL when used in an ORDER
BY that was evaluated using
filesort, a server crash could result.
(Bug#31160)
Full-text searches on ucs2 columns caused a
server crash. (FULLTEXT indexes on
ucs2 columns cannot be used, but it should be
possible to perform IN BOOLEAN MODE searches
on ucs2 columns without a crash.)
(Bug#31159)
An assertion designed to detect a bug in the
ROLLUP implementation would incorrectly be
triggered when used in a subquery context with noncacheable
statements.
(Bug#31156)
Selecting spatial types in a
UNION could cause a server crash.
(Bug#31155)
Use of GROUP_CONCAT(DISTINCT
caused an
assertion failure.
(Bug#31154)bit_column)
GROUP BY NULL WITH ROLLUP could cause a
server crash.
(Bug#31095)
See also Bug#32558.
Internal conversion routines could fail for several multi-byte
character sets (big5,
cp932, euckr,
gb2312, sjis) for empty
strings or during evaluation of SOUNDS
LIKE.
(Bug#31069, Bug#31070)
The MOD() function and the
% operator crashed the server for a divisor
less than 1 with a very long fractional part.
(Bug#31019)
On Windows, the pthread_mutex_trylock()
implementation was incorrect.
(Bug#30992)
A character set introducer followed by a hexadecimal or bit-value literal did not check its argument and could return an ill-formed result for invalid input. (Bug#30986)
CHAR( did not check its
argument and could return an ill-formed result for invalid
input.
(Bug#30982)str USING
charset)
The result from
CHAR() did not add a leading 0x00 byte for input
strings with an odd number of bytes.
(Bug#30981)str USING
ucs2
The GeomFromText() function could
cause a server crash if the first argument was
NULL or the empty string.
(Bug#30955)
MAKEDATE() incorrectly moved year
values in the 100–200 range into the 1970–2069
range. (This is legitimate for 00–99, but three-digit
years should be used unchanged.)
(Bug#30951)
When invoked with constant arguments,
STR_TO_DATE() could use a cached
value for the format string and return incorrect results.
(Bug#30942)
GROUP_CONCAT() returned
',' rather than an empty string when the
argument column contained only empty strings.
(Bug#30897)
For MEMORY tables, lookups for
NULL values in BTREE
indexes could return incorrect results.
(Bug#30885)
Calling NAME_CONST() with
nonconstant arguments triggered an assertion failure.
Nonconstant arguments are now disallowed.
(Bug#30832)
For a spatial column with a regular
(non-SPATIAL) index, queries failed if the
optimizer tried to use the index.
(Bug#30825)
Values for the --tc-heuristic-recover option
incorrectly were treated as values for the
--myisam-stats-method option.
(Bug#30821)
On Windows, the pthread_mutex_trylock()
implementation was incorrect. One symptom was that invalidating
the query cache could cause a server crash.
(Bug#30768)
Under some circumstances,
CREATE TABLE ...
SELECT could crash the server or incorrectly report
that the table row size was too large.
(Bug#30736)
Using the MIN() or
MAX() function to select one part
of a multi-part key could cause a crash when the function result
was NULL.
(Bug#30715)
The optimizer could ignore ORDER BY in cases
when the result set is ordered by filesort,
resulting in rows being returned in incorrect order.
(Bug#30666)
MyISAM tables could not exceed 4294967295
(2^32 - 1) rows on Windows.
(Bug#30638)
For MEMORY tables,
DELETE statements that remove
rows based on an index read could fail to remove all matching
rows.
(Bug#30590)
Using GROUP BY on an expression of the form
timestamp_col DIV
number
When expanding a * in a
USING or NATURAL join, the
check for table access for both tables in the join was done
using only the grant information of the first table.
(Bug#30468)
Versions of mysqldump from MySQL 4.1 or
higher tried to use START TRANSACTION WITH CONSISTENT
SNAPSHOT if the
--single-transaction and
--master-data options were
given, even with servers older than 4.1 that do not support
consistent snapshots.
(Bug#30444)
Setting certain values on a table using a spatial index could cause the server to crash. (Bug#30286)
Some INFORMATION_SCHEMA tables are intended
for internal use, but could be accessed by using
SHOW statements.
(Bug#30079)
Specifying the --without-geometry option for
configure caused server compilation to fail.
(Bug#29972)
Under some circumstances, a UDF initialization function could be passed incorrect argument lengths. (Bug#29804)
configure did not find nss
on some Linux platforms.
(Bug#29658)
The log and
log_slow_queries system
variables were displayed by SHOW
VARIABLES but could not be accessed in expressions as
@@log and
@@log_slow_queries. Also, attempting to set
them with SET produced an incorrect
Unknown system variable message. Now these
variables can be accessed in expressions and attempting to set
their values produces an error message that the variable is read
only.
(Bug#29131)
SHOW VARIABLES did not display
the relay_log,
relay_log_index, or
relay_log_info_file system variables.
(Bug#28893)
On Windows, mysql_upgrade created temporary
files in C:\ and did not clean them up.
(Bug#28774)
Index hints specified in view definitions were ignored when using the view to select from the base table. (Bug#28702)
Views do not have indexes, so index hints do not apply. Use of index hints when selecting from a view is now disallowed. (Bug#28701)
After changing the SQL mode to a restrictive value that would make already-inserted dates in a column be considered invalid, searches returned different results depending on whether the column was indexed. (Bug#28687)
The result from CHAR() was
incorrectly assumed in some contexts to return a single-byte
result.
(Bug#28550)
The parser confused user-defined function (UDF) and stored
function creation for CREATE
FUNCTION and required that there be a default database
when creating UDFs, although there is no such requirement.
(Bug#28318, Bug#29816)
The result of a comparison between
VARBINARY and
BINARY columns differed depending
on whether the VARBINARY column
was indexed.
(Bug#28076)
The metadata in some MYSQL_FIELD members
could be incorrect when a temporary table was used to evaluate a
query.
(Bug#27990)
comp_err created files with permissions such that they might be inaccessible during make install operations. (Bug#27789)
The anonymous accounts were not being created during MySQL installation. (Bug#27692)
Host names sometimes were treated as case sensitive in
account-management statements (CREATE
USER, GRANT,
REVOKE, and so forth).
(Bug#19828)
The readline library has been updated to
version 5.2. This addresses issues in the
mysql client where history and editing within
the client would fail to work as expected.
(Bug#18431)
The Aborted_clients status
variable was incremented twice if a client exited without
calling mysql_close().
(Bug#16918)
Clients were ignoring the TCP/IP port number specified as the default port via the --with-tcp-port configuration option. (Bug#15327)
Values of types REAL ZEROFILL,
DOUBLE ZEROFILL, FLOAT
ZEROFILL, were not zero-filled when converted to a
character representation in the C prepared statement API.
(Bug#11589)
mysql stripped comments from statements sent
to the server. Now the
--comments or
--skip-comments option can be
used to control whether to retain or strip comments. The default
is --skip-comments.
(Bug#11230, Bug#26215)
Several buffer-size system variables were either being handled incorrectly for large values (for settings larger than 4GB, they were truncated to values less than 4GB without a warning), or were limited unnecessarily to 4GB even on 64-bit systems. The following changes were made:
For key_buffer_size, values
larger than 4GB are allowed on 64-bit platforms (except
Windows, for which large values are truncated to 4GB with a
warning).
For join_buffer_size,
sort_buffer_size, and
myisam_sort_buffer_size,
values are limited to 4GB on all platforms. Larger values
are truncated to 4GB with a warning.
In addition, settings for
read_buffer_size and
read_rnd_buffer_size are
limited to 2GB on all platforms. Larger values are truncated to
2GB with a warning.
(Bug#5731, Bug#29419, Bug#29446)
Executing DISABLE KEYS and ENABLE
KEYS on a nonempty table would cause the size of the
index file for the table to grow considerable. This was because
the DISABLE KEYS operation would only mark
the existing index, without deleting the index blocks. The
ENABLE KEYS operation would re-create the
index, adding new blocks, while the previous index blocks would
remain. Existing indexes are now dropped and recreated when the
ENABLE KEYS statement is executed.
(Bug#4692)
This is a bugfix release for the current MySQL Community Server production release family. It replaces MySQL 5.0.51.
Bugs fixed:
On Windows, the installer attempted to use JScript to determine whether the target data directory already existed. On Windows Vista x64, this resulted in an error because the installer was attempting to run the JScript in a 32-bit engine, which wasn't registered on Vista. The installer no longer uses JScript but instead relies on a native WiX command. (Bug#36103)
The MySQL preferences pane did not work to start or stop MySQL on Mac OS X 10.5 (Leopard). (Bug#28854)
On Mac OS X, the StartupItem for MySQL did not work. (Bug#25008)
This is a bugfix release for the current MySQL Community Server production release family. It replaces MySQL 5.0.51.
Bugs fixed:
Security Fix: Three vulnerabilities in yaSSL versions 1.7.5 and earlier were discovered that could lead to a server crash or execution of unauthorized code. The exploit requires a server with yaSSL enabled and TCP/IP connections enabled, but does not require valid MySQL account credentials. The exploit does not apply to OpenSSL.
The proof-of-concept exploit is freely available on the Internet. Everyone with a vulnerable MySQL configuration is advised to upgrade immediately.
Security Fix:
ALTER VIEW retained the original
DEFINER value, even when altered by another
user, which could allow that user to gain the access rights of
the view. Now ALTER VIEW is
allowed only to the original definer or users with the
SUPER privilege.
(Bug#29908)
Security Fix:
When using a FEDERATED table, the local
server could be forced to crash if the remote server returned a
result with fewer columns than expected.
(Bug#29801)
When running the MySQL Instance Configuration Wizard, a race condition could exist that would fail to connect to a newly configured instance. This was because mysqld had not completed the startup process before the next stage of the installation process. (Bug#28628)
For Windows Vista, MySQLInstanceConfig.exe did not include a proper manifest enabling it to run with administrative privileges. (Bug#22563)
See also Bug#24732.
MySQLInstanceConfig.exe failed to grant
certain privileges to the 'root'@'%' account.
(Bug#17303)
This is a bugfix release for the current MySQL Community Server production release family. It replaces MySQL 5.0.45.
Functionality added or changed:
Incompatible Change:
The parser accepted statements that contained /* ...
*/ that were not properly closed with
*/, such as SELECT 1 /* +
2. Statements that contain unclosed
/*-comments now are rejected with a syntax
error.
This fix has the potential to cause incompatibilities. Because
of Bug#26302, which caused the trailing */ to
be truncated from comments in views, stored routines, triggers,
and events, it is possible that objects of those types may have
been stored with definitions that now will be rejected as
syntactically invalid. Such objects should be dropped and
re-created so that their definitions do not contain truncated
comments. If a stored object definition contains only a single
statement (does not use a BEGIN ... END
block) and contains a comment within the statement, the comment
should be moved to follow the statement or the object should be
rewritten to use a BEGIN ... END block. For
example, this statement:
CREATE PROCEDURE p() SELECT 1 /* my comment */ ;
Can be rewritten in either of these ways:
CREATE PROCEDURE p() SELECT 1; /* my comment */ CREATE PROCEDURE p() BEGIN SELECT 1 /* my comment */ ; END;
MySQL Cluster:
Mapping of NDB error codes to MySQL
storage engine error codes has been improved.
(Bug#28423)
MySQL Cluster:
auto_increment_increment and
auto_increment_offset are now
supported for NDB tables.
(Bug#26342)
MySQL Cluster: The output from the cluster management client showing the progress of data node starts has been improved. (Bug#23354)
Replication:
The sql_mode,
foreign_key_checks,
unique_checks, character
set/collations, and
sql_auto_is_null session
variables are written to the binary log and honored during
replication. See Section 5.2.3, “The Binary Log”.
Server parser performance was improved for expression parsing by lowering the number of state transitions and reductions needed. (Bug#30625)
Server parser performance was improved for boolean expressions. (Bug#30237)
If a MyISAM table is created with no
DATA DIRECTORY option, the
.MYD file is created in the database
directory. By default, if MyISAM finds an
existing .MYD file in this case, it
overwrites it. The same applies to .MYI
files for tables created with no INDEX
DIRECTORY option. To suppress this behavior, start the
server with the new --keep_files_on_create
option, in which case MyISAM will not
overwrite existing files and returns an error instead.
(Bug#29325)
MySQL source distributions are now available in Zip format. (Bug#27742)
If a MERGE table cannot be opened or used
because of a problem with an underlying table,
CHECK TABLE now displays
information about which table caused the problem.
(Bug#26976)
The EXAMPLE storage engine is now enabled by
default.
Bugs fixed:
Security Fix:
Using RENAME TABLE against a
table with explicit DATA DIRECTORY and
INDEX DIRECTORY options can be used to
overwrite system table information by replacing the symbolic
link points. the file to which the symlink points.
MySQL will now return an error when the file to which the symlink points already exists. (Bug#32111, CVE-2007-5969)
Incompatible Change:
The file mysqld.exe was mistakenly included
in binary distributions between MySQL 5.0.42 and 5.0.48. You
should use mysqld-nt.exe.
(Bug#32197)
Incompatible Change:
Multiple-table DELETE statements
containing ambiguous aliases could have unintended side effects
such as deleting rows from the wrong table. Example:
DELETE FROM t1 AS a2 USING t1 AS a1 INNER JOIN t2 AS a2;
This bug fix enables alias declarations to be declared only in
the table_references part. Elsewhere
in the statement, alias references are allowed but not alias
declarations.
(Bug#30234)
See also Bug#27525.
Incompatible Change:
Failure to consider collation when comparing space characters
could result in incorrect index entry order, leading to
incorrect comparisons, inability to find some index values,
misordered index entries, misordered ORDER BY
results, or tables that CHECK
TABLE reports as having corrupt indexes.
As a result of this bug fix, indexes must be rebuilt for columns
that use any of these character sets:
eucjpms, euc_kr,
gb2312, latin7,
macce, ujis. See
Section 2.18.3, “Checking Whether Table Indexes Must Be Rebuilt”.
(Bug#29461)
MySQL Cluster: Packaging:
Some commercial MySQL Cluster RPM packages included support for
the InnoDB storage engine.
(InnoDB is not part of the standard
commercial MySQL Cluster offering.)
(Bug#31989)
MySQL Cluster: Attempting to restore a backup made on a cluster host using one endian to a machine using the other endian could cause the cluster to fail. (Bug#29674)
MySQL Cluster: When restarting a data node, queries could hang during that node's start phase 5, and continue only after the node had entered phase 6. (Bug#29364)
MySQL Cluster: Replica redo logs were inconsistently handled during a system restart. (Bug#29354)
MySQL Cluster:
Reads on BLOB columns were not
locked when they needed to be to guarantee consistency.
(Bug#29102)
See also Bug#31482.
MySQL Cluster:
A query using joins between several large tables and requiring
unique index lookups failed to complete, eventually returning
Uknown Error after a very long period of
time. This occurred due to inadequate handling of instances
where the Transaction Coordinator ran out of
TransactionBufferMemory, when the cluster
should have returned NDB error code 4012 (Request
ndbd time-out).
(Bug#28804)
MySQL Cluster:
The description of the --print option provided
in the output from ndb_restore --help
was incorrect.
(Bug#27683)
MySQL Cluster:
The management client's response to START BACKUP
WAIT COMPLETED did not include the backup ID.
(Bug#27640)
MySQL Cluster:
An invalid subselect on an NDB
table could cause mysqld to crash.
(Bug#27494)
MySQL Cluster:
An attempt to perform a SELECT ... FROM
INFORMATION_SCHEMA.TABLES whose result included
information about NDB tables for
which the user had no privileges crashed the MySQL Server on
which the query was performed.
(Bug#26793)
MySQL Cluster:
Warnings and errors generated by ndb_config
--config-file=
were sent to filestdout, rather than to
stderr.
(Bug#25941)
MySQL Cluster: Large file support did not work in AIX server binaries. (Bug#10776)
Replication:
The thread ID was not reset properly after execution of
mysql_change_user(), which could
cause replication failure when replicating temporary tables.
(Bug#29734)
Replication: Operations that used the time zone replicated the time zone only for successful operations, but did not replicate the time zone for errors that need to know it. (Bug#29536)
Replication:
INSERT DELAYED statements on a
master server are replicated as non-DELAYED
inserts on slaves (which is normal, to preserve serialization),
but the inserts on the slave did not use concurrent inserts. Now
INSERT DELAYED on a slave is
converted to a concurrent insert when possible, and to a normal
insert otherwise.
(Bug#29152)
Replication:
DROP USER statements that named
multiple users, only some of which could be dropped, were
replicated incorrectly.
(Bug#29030)
Replication:
An error that happened inside
INSERT,
UPDATE, or
DELETE statements performed from
within a stored function or trigger could cause inconsistency
between master and slave servers.
(Bug#27417)
Replication: Slave servers could incorrectly interpret an out-of-memory error from the master and reconnect using the wrong binary log position. (Bug#24192)
When a TIMESTAMP with a nonzero
time part was converted to a DATE
value, no warning was generated. This caused index lookups to
assume that this is a valid conversion and was returning rows
that match a comparison between a
TIMESTAMP value and a
DATE keypart. Now a warning is
generated so that TIMESTAMP with
a nonzero time part will not match
DATE values.
(Bug#31221)
A server crash could occur when a
non-DETERMINISTIC stored function was used in
a GROUP BY clause.
(Bug#31035)
For an InnoDB table if a
SELECT was ordered by the primary
key and also had a WHERE field = value clause
on a different field that was indexed, a DESC
order instruction would be ignored.
(Bug#31001)
A failed HANDLER ... READ operation could
leave the table in a locked state.
(Bug#30632)
The optimization that uses a unique index to remove
GROUP BY did not ensure that the index was
actually used, thus violating the ORDER BY
that is implied by GROUP BY.
(Bug#30596)
SHOW STATUS LIKE 'Ssl_cipher_list' from a
MySQL client connected via SSL returned an empty string rather
than a list of available ciphers.
(Bug#30593)
Memory corruption occurred for some queries with a top-level
OR operation in the WHERE
condition if they contained equality predicates and other
sargable predicates in disjunctive parts of the condition.
(Bug#30396)
Issuing a DELETE statement having
both an ORDER BY clause and a
LIMIT clause could cause
mysqld to crash.
(Bug#30385)
The Last_query_cost status
variable value can be computed accurately only for simple
“flat” queries, not complex queries such as those
with subqueries or UNION.
However, the value was not consistently being set to 0 for
complex queries.
(Bug#30377)
Queries that had a GROUP BY clause and
selected COUNT(DISTINCT
returned
incorrect results.
(Bug#30324)bit_column)
The server created temporary tables for filesort operations in
the working directory, not in the directory specified by the
tmpdir system variable.
(Bug#30287)
The query cache does not support retrieval of statements for which column level access control applies, but the server was still caching such statements, thus wasting memory. (Bug#30269)
Using DISTINCT or GROUP BY
on a BIT column in a
SELECT statement caused the
column to be cast internally as an integer, with incorrect
results being returned from the query.
(Bug#30245)
GROUP BY on
BIT columns produced incorrect
results.
(Bug#30219)
Using KILL QUERY
or KILL
CONNECTION to kill a
SELECT statement caused a server
crash if the query cache was enabled.
(Bug#30201)
Prepared statements containing
CONNECTION_ID() could be written
improperly to the binary log.
(Bug#30200)
When a thread executing a DROP
TABLE statement was killed, the table name locks that
had been acquired were not released.
(Bug#30193)
Short-format mysql commands embedded within
/*! ... */ comments were parsed incorrectly
by mysql, which discarded the rest of the
comment including the terminating */
characters. The result was a malformed (unclosed) comment. Now
mysql does not discard the
*/ characters.
(Bug#30164)
When mysqldump wrote
DROP DATABASE statements within
version-specific comments, it included the terminating semicolon
in the wrong place, causing following statements to fail when
the dump file was reloaded.
(Bug#30126)
Use of local variables with non-ASCII names in stored procedures crashed the server. (Bug#30120)
On Windows, client libraries lacked symbols required for linking. (Bug#30118)
--myisam-recover='' (empty option value) did
not disable MyISAM recovery.
(Bug#30088)
The IS_UPDATABLE column in the
INFORMATION_SCHEMA.VIEWS table was
not always set correctly.
(Bug#30020)
Statements within stored procedures ignored the value of the
low_priority_updates system
variable.
(Bug#29963)
See also Bug#26162.
For MyISAM tables on Windows,
INSERT,
DELETE, or
UPDATE followed by
ALTER TABLE within
LOCK TABLES could cause table
corruption.
(Bug#29957)
With auto-reconnect enabled, row fetching for a prepared statement could crash after reconnect occurred because loss of the statement handler was not accounted for. (Bug#29948)
LOCK TABLES did not pre-lock
tables used in triggers of the locked tables. Unexpected locking
behavior and statement failures similar to failed:
1100: Table 'xx' was not locked with
LOCK TABLES could result.
(Bug#29929)
INSERT ... VALUES(CONNECTION_ID(), ...)
statements were written to the binary log in such a way that
they could not be properly restored.
(Bug#29928)
Adding DISTINCT could cause incorrect rows to
appear in a query result.
(Bug#29911)
Using the DATE() function in a
WHERE clause did not return any records after
encountering NULL. However, using
TRIM or CAST produced the
correct results.
(Bug#29898)
Very long prepared statements in stored procedures could cause a server crash. (Bug#29856)
If query execution involved a temporary table,
GROUP_CONCAT() could return a
result with an incorrect character set.
(Bug#29850)
If one thread was performing concurrent inserts, other threads reading from the same table using equality key searches could see the index values for new rows before the data values had been written, leading to reports of table corruption. (Bug#29838)
Repeatedly accessing a view in a stored procedure (for example, in a loop) caused a small amount of memory to be allocated per access. Although this memory is deallocated on disconnect, it could be a problem for a long running stored procedures that make repeated access of views. (Bug#29834)
mysqldump produced output that incorrectly
discarded the
NO_AUTO_VALUE_ON_ZERO value of
the sql_mode variable after
dumping triggers.
(Bug#29788)
An assertion failure occurred within yaSSL for very long keys. (Bug#29784)
For MEMORY tables, the
index_merge union access
method could return incorrect results.
(Bug#29740)
Comparison of TIME values using
the BETWEEN operator led to string
comparison, producing incorrect results in some cases. Now the
values are compared as integers.
(Bug#29739)
For a table with a DATE column
date_col such that selecting rows
with WHERE yielded
a nonempty result, adding date_col =
'date_val 00:00:00'GROUP BY
caused the result
to be empty.
(Bug#29729)date_col
In some cases, INSERT INTO ... SELECT ... GROUP
BY could insert rows even if the
SELECT by itself produced an
empty result.
(Bug#29717)
For the embedded server, the
mysql_stmt_store_result() C API
function caused a memory leak for empty result sets.
(Bug#29687)
EXPLAIN produced
Impossible where for statements of the form
SELECT ... FROM t WHERE c=0, where
c was an ENUM
column defined as a primary key.
(Bug#29661)
On Windows, ALTER TABLE hung if
records were locked in share mode by a long-running transaction.
(Bug#29644)
A left join between two views could produce incorrect results. (Bug#29604)
Certain statements with unions, subqueries, and joins could result in huge memory consumption. (Bug#29582)
Clients using SSL could hang the server. (Bug#29579)
A slave running with
--log-slave-updates would fail to
write INSERT DELAY IGNORE statements to its
binary log, resulting in different binary log contents on the
master and slave.
(Bug#29571)
An incorrect result was returned when comparing string values
that were converted to TIME
values with CAST().
(Bug#29555)
gcov coverage-testing information was not written if the server crashed. (Bug#29543)
In the ascii character set, conversion of DEL
(0x7F) to Unicode incorrectly resulted in
QUESTION MARK (0x3F) rather than DEL.
(Bug#29499)
A field packet with NULL fields caused a
libmysqlclient crash.
(Bug#29494)
When using a combination of HANDLER... READ
and DELETE on a table, MySQL
continued to open new copies of the table every time, leading to
an exhaustion of file descriptors.
(Bug#29474)
This regression was introduced by Bug#21587.
On Windows, the mysql client died if the user entered a statement and Return after entering Control-C. (Bug#29469)
Corrupt data resulted from use of SELECT ... INTO
OUTFILE ', where
file_name' FIELDS ENCLOSED
BY 'c'c is a digit or minus sign, followed
by LOAD DATA INFILE
'.
(Bug#29442)file_name' FIELDS ENCLOSED BY
'c'
Killing an INSERT DELAYED thread
caused a server crash.
(Bug#29431)
Use of SHOW BINLOG EVENTS for a
nonexistent log file followed by PURGE
BINARY LOGS caused a server crash.
(Bug#29420)
Assertion failure could occur for grouping queries that employed
DECIMAL user variables with
assignments to them.
(Bug#29417)
For CAST(,
the limits of 65 and 30 on the precision
(expr AS
DECIMAL(M,D))M) and scale
(D) were not enforced.
(Bug#29415)
If a view used a function in its
SELECT statement, the columns
from the view were not inserted into the
INFORMATION_SCHEMA.COLUMNS table.
(Bug#29408)
Results for a select query that aliases the column names against
a view could duplicate one column while omitting another. This
bug could occur for a query over a multiple-table view that
includes an ORDER BY clause in its
definition.
(Bug#29392)
mysqldump created a stray file when a given a too-long file name argument. (Bug#29361)
The special “zero”
ENUM value was coerced to the
normal empty string ENUM value
during a column-to-column copy. This affected CREATE
... SELECT statements and
SELECT statements with aggregate
functions on ENUM columns in the
GROUP BY clause.
(Bug#29360)
Optimization of queries with DETERMINISTIC
stored functions in the WHERE clause was
ineffective: A sequential scan was always used.
(Bug#29338)
MyISAM corruption could occur with the
cp932_japanese_ci collation for the
cp932 character set due to incorrect
comparison for trailing space.
(Bug#29333)
The mysql_list_fields() C API
function incorrectly set
MYSQL_FIELD::decimals for some view columns.
(Bug#29306)
FULLTEXT indexes could be corrupted by
certain gbk characters.
(Bug#29299)
SELECT ... INTO
OUTFILE followed by LOAD
DATA could result in garbled characters when the
FIELDS ENCLOSED BY clause named a delimiter
of '0', 'b',
'n', 'r',
't', 'N', or
'Z' due to an interaction of character
encoding and doubling for data values containing the enclosed-by
character.
(Bug#29294)
Sort order of the collation wasn't used when comparing trailing
spaces. This could lead to incorrect comparison results,
incorrectly created indexes, or incorrect result set order for
queries that include an ORDER BY clause.
(Bug#29261)
If an ENUM column contained
'' as one of its members (represented with
numeric value greater than 0), and the column contained error
values (represented as 0 and displayed as
''), using ALTER
TABLE to modify the column definition caused the 0
values to be given the numeric value of the nonzero
'' member.
(Bug#29251)
Calling mysql_options() after
mysql_real_connect() could cause
clients to crash.
(Bug#29247)
CHECK TABLE for
ARCHIVE tables could falsely report table
corruption or cause a server crash.
(Bug#29207)
Mixing binary and utf8 columns in a union
caused field lengths to be calculated incorrectly, resulting in
truncation.
(Bug#29205)
AsText() could fail with a buffer overrun.
(Bug#29166)
InnoDB refused to start on some versions of
FreeBSD with LinuxThreads. This is fixed by enabling file
locking on FreeBSD.
(Bug#29155)
LOCK TABLES was not atomic when
more than one InnoDB tables were locked.
(Bug#29154)
A network structure was initialized incorrectly, leading to embedded server crashes. (Bug#29117)
An assertion failure occurred if a query contained a conjunctive
predicate of the form
in
the view_column = constantWHERE clause and the GROUP
BY clause contained a reference to a different view
column. The fix also enables application of an optimization that
was being skipped if a query contained a conjunctive predicate
of the form view_column =
constantWHERE clause and
the GROUP BY clause contained a reference to
the same view column.
(Bug#29104)
A maximum of 4TB InnoDB free space was
reported by SHOW TABLE STATUS, which is
incorrect on systems with more than 4TB space.
(Bug#29097)
If an INSERT INTO
... SELECT statement inserted into the same table that
the SELECT retrieved from, and
the SELECT included
ORDER BY and LIMIT
clauses, different data was inserted than the data produced by
the SELECT executed by itself.
(Bug#29095)
Queries that performed a lookup into a
BINARY index containing key
values ending with spaces caused an assertion failure for debug
builds and incorrect results for nondebug builds.
(Bug#29087)
The semantics of BIGINT depended
on platform-specific characteristics.
(Bug#29079)
A byte-order issue in writing a spatial index to disk caused bad index files on some systems. (Bug#29070)
If one of the queries in a UNION
used the SQL_CACHE option and another query
in the UNION contained a
nondeterministic function, the result was still cached. For
example, this query was incorrectly cached:
SELECT NOW() FROM t1 UNION SELECT SQL_CACHE 1 FROM t1;
Creation of a legal stored procedure could fail if no default database had been selected. (Bug#29050)
REPLACE,
INSERT IGNORE,
and UPDATE IGNORE did not work for
FEDERATED tables.
(Bug#29019)
Inserting into InnoDB tables and executing
RESET MASTER in multiple threads
cause assertion failure in debug server binaries.
(Bug#28983)
For a ucs2 column,
GROUP_CONCAT() did not convert
separators to the result character set before inserting them,
producing a result containing a mixture of two different
character sets.
(Bug#28925)
Queries using UDFs or stored functions were cached. (Bug#28921)
For a join with GROUP BY and/or
ORDER BY and a view reference in the
FROM list, the query metadata erroneously
showed empty table aliases and database names for the view
columns.
(Bug#28898)
Coercion of ASCII values to character sets that are a superset of ASCII sometimes was not done, resulting in illegal mix of collations errors. These cases now are resolved using repertoire, a new string expression attribute (see Section 9.1.7, “String Repertoire”). (Bug#28875)
Non-utf8 characters could get mangled when
stored in CSV tables.
(Bug#28862)
ALTER VIEW is not supported as a
prepared statement but was not being rejected.
ALTER VIEW is now prohibited as a
prepared statement or when called within stored routines.
(Bug#28846)
In strict SQL mode, errors silently stopped the SQL thread even
for errors named using the --slave-skip-errors
option.
(Bug#28839)
Fast ALTER TABLE (that works
without rebuilding the table) acquired duplicate locks in the
storage engine. In MyISAM, if
ALTER TABLE was issued under
LOCK
TABLE, it caused all data inserted after
LOCK
TABLE to disappear.
(Bug#28838)
Killing an SSL connection on platforms where MySQL is compiled
with -DSIGNAL_WITH_VIO_CLOSE (Windows, Mac OS
X, and some others) could crash the server.
(Bug#28812)
Runtime changes to the
log_queries_not_using_indexes
system variable were ignored.
(Bug#28808)
Tables using the InnoDB storage engine
incremented AUTO_INCREMENT values incorrectly
with ON DUPLICATE KEY UPDATE.
(Bug#28781)
Selecting a column not present in the selected-from table caused
an extra error to be produced by SHOW
ERRORS.
(Bug#28677)
For a statement of the form CREATE t1 SELECT
, the
server created the column using the
integer_constantDECIMAL data type for large
negative values that are within the range of
BIGINT.
(Bug#28625)
For InnoDB tables, MySQL unnecessarily sorted
records in certain cases when the records were retrieved by
InnoDB in the proper order already.
(Bug#28591)
A SELECT in one connection could
be blocked by
INSERT ...
ON DUPLICATE KEY UPDATE in another connection even
when low_priority_updates is
set.
(Bug#28587)
mysql_install_db could fail to find script files that it needs. (Bug#28585)
When one thread attempts to lock two (or more) tables and
another thread executes a statement that aborts these locks
(such as REPAIR TABLE,
OPTIMIZE TABLE, or
CHECK TABLE), the thread might
get a table object with an incorrect lock type in the table
cache. The result is table corruption or a server crash.
(Bug#28574)
mysql_upgrade could run binaries dynamically linked against incorrect versions of shared libraries. (Bug#28560)
If a stored procedure was created and invoked prior to selecting
a default database with USE, a
No database selected error occurred.
(Bug#28551)
On Mac OS X, shared-library installation path names were incorrect. (Bug#28544)
Using the
--skip-add-drop-table
option with mysqldump generated
incorrect SQL if the database included any views. The recreation
of views requires the creation and removal of temporary tables.
This option suppressed the removal of those temporary tables.
The same applied to --compact
since this option also invokes
--skip-add-drop-table.
(Bug#28524)
mysqlbinlog --hexdump generated incorrect
output due to omission of the “ #
” comment character for some comment lines.
(Bug#28293)
A race condition in the interaction between
MyISAM and the query cache code caused the
query cache not to invalidate itself for concurrently inserted
data.
(Bug#28249)
Indexing column prefixes in InnoDB tables
could cause table corruption.
(Bug#28138)
Index creation could fail due to truncation of key values to the maximum key length rather than to a mulitiple of the maximum character length. (Bug#28125)
The LOCATE() function returned
NULL if any of its arguments evaluated to
NULL. Likewise, the predicate,
LOCATE(, erroneously evaluated to
str,NULL)
IS NULLFALSE.
(Bug#27932)
On Windows, symbols for yaSSL and taocrypt were missing from
mysqlclient.lib, resulting in unresolved
symbol errors for clients linked against that library.
(Bug#27861)
SHOW COLUMNS returned
NULL instead of the empty string for the
Default value of columns that had no default
specified.
(Bug#27747)
The modification of a table by a partially completed multi-column update was not recorded in the binlog, rather than being marked by an event and a corresponding error code. (Bug#27716)
With recent versions of DBD::mysql, mysqlhotcopy generated table names that were doubly qualified with the database name. (Bug#27694)
The anonymous accounts were not being created during MySQL installation. (Bug#27692)
Some SHOW statements and
INFORMATION_SCHEMA queries could expose
information not allowed by the user's access privileges.
(Bug#27629)
A stack overrun could occur when storing
DATETIME values using repeated
prepared statements.
(Bug#27592)
Dropping a user-defined function could cause a server crash if the function was still in use by another thread. (Bug#27564)
Some character mappings in the ascii.xml
file were incorrect.
As a result of this bug fix, indexes must be rebuilt for columns
that use the ascii_general_ci collation for
columns that contain any of these characters:
'`', '[',
'\', ']',
'~'. See
Section 2.18.3, “Checking Whether Table Indexes Must Be Rebuilt”.
(Bug#27562)
The parser rules for the SHOW
PROFILE statement were revised to work with older
versions of bison.
(Bug#27433)
Unsafe aliasing in the source caused a client library crash when compiled with gcc 4 at high optimization levels. (Bug#27383)
A SELECT with more than 31 nested
dependent subqueries returned an incorrect result.
(Bug#27352)
Index-based range reads could fail for comparisons that involved
contraction characters (such as ch in Czech
or ll in Spanish).
(Bug#27345)
Aggregations in subqueries that refer to outer query columns were not always correctly referenced to the proper outer query. (Bug#27333)
INSERT INTO ...
SELECT caused a crash if
innodb_locks_unsafe_for_binlog
was enabled.
(Bug#27294)
Error returns from the time() system call
were ignored.
(Bug#27198)
Phantom reads could occur under InnoDB
SERIALIZABLE isolation level.
(Bug#27197)
The SUBSTRING() function returned
the entire string instead of an empty string when it was called
from a stored procedure and when the length parameter was
specified by a variable with the value “
0 ”.
(Bug#27130)
ALTER TABLE ... ENABLE KEYS could cause
mysqld to crash when executed on a table
containing on a MyISAM table containing
billions of rows.
(Bug#27029)
FEDERATED tables had an artificially low
maximum of key length.
(Bug#26909)
Binary content 0x00 in a
BLOB column sometimes became
0x5C 0x00 following a dump and reload, which
could cause problems with data using multi-byte character sets
such as GBK (Chinese). This was due to a
problem with SELECT INTO OUTFILE whereby
LOAD DATA later incorrectly
interpreted 0x5C as the second byte of a
multi-byte sequence rather than as the
SOLIDUS (“\”) character, used by
MySQL as the escape character.
(Bug#26711)
Index creation could corrupt the table definition in the
.frm file: 1) A table with the maximum
number of key segments and maximum length key name would have a
corrupted .frm file, due to incorrect
calculation of the total key length. 2)
MyISAM would reject a table with the maximum
number of keys and the maximum number of key segments in all
keys. (It would allow one less than this total maximum.) Now
MyISAM accepts a table defined with the
maximum.
(Bug#26642)
After the first read of a TEMPORARY table,
CHECK TABLE could report the
table as being corrupt.
(Bug#26325)
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)
ALTER DATABASE did not require at
least one option.
(Bug#25859)
Using HANDLER to open a table
having a storage engine not supported by
HANDLER properly returned an
error, but also improperly prevented the table from being
dropped by other connections.
(Bug#25856)
The index merge union access algorithm could produce incorrect
results with InnoDB tables. The problem could
also occur for queries that used DISTINCT.
(Bug#25798)
When using a FEDERATED table, the value of
LAST_INSERT_ID() would not
correctly update the C API interface, which would affect the
autogenerated ID returned both through the C API and the MySQL
protocol, affecting Connectors that used the protocol and/or C
API.
(Bug#25714)
The server was blocked from opening other tables while the
FEDERATED engine was attempting to open a
remote table. Now the server does not check the correctness of a
FEDERATED table at
CREATE TABLE time, but waits
until the table actually is accessed.
(Bug#25679)
Under ActiveState Perl, mysql-test-run.pl
could kill itself when attempting to kill other processes.
(Bug#25657)
Several InnoDB assertion failures were
corrected.
(Bug#25645)
A query with DISTINCT in the select list to
which the loose-scan optimization for grouping queries was
applied returned an incorrect result set when the query was used
with the SQL_BIG_RESULT option.
(Bug#25602)
For a multiple-row insert into a FEDERATED
table that refers to a remote transactional table, if the insert
failed for a row due to constraint failure, the remote table
would contain a partial commit (the rows preceding the failed
one) instead of rolling back the statement completely. This
occurred because the rows were treated as individual inserts.
Now FEDERATED performs bulk-insert handling
such that multiple rows are sent to the remote table in a batch.
This provides a performance improvement and enables the remote
table to perform statement rollback properly should an error
occur. This capability has the following limitations:
The size of the insert cannot exceed the maximum packet size between servers. If the insert exceeds this size, it is broken into multiple packets and the rollback problem can occur.
Bulk-insert handling does not occur for
INSERT
... ON DUPLICATE KEY UPDATE.
The FEDERATED storage engine failed silently
for INSERT
... ON DUPLICATE KEY UPDATE if a duplicate key
violation occurred. FEDERATED does not
support ON DUPLICATE KEY UPDATE, so now it
correctly returns an ER_DUP_KEY
error if a duplicate key violation occurs.
(Bug#25511)
For InnoDB tables, CREATE TABLE a AS
SELECT * FROM A would fail.
(Bug#25164)
In a stored function or trigger, when InnoDB
detected deadlock, it attempted rollback and displayed an
incorrect error message (Explicit or implicit commit
is not allowed in stored function or trigger). Now
InnoDB returns an error under these
conditions and does not attempt rollback. Rollback is handled
outside of InnoDB above the function/trigger
level.
(Bug#24989)
A too-long shared-memory-base-name value
could cause a buffer overflow and crash the server or clients.
(Bug#24924)
Dropping a temporary InnoDB table that had
been locked with LOCK TABLES
caused a server crash.
(Bug#24918)
On Windows, executables did not include Vista manifests. (Bug#24732)
See also Bug#22563.
If MySQL/InnoDB crashed very quickly after
starting up, it would not force a checkpoint. In this case,
InnoDB would skip crash recovery at next
startup, and the database would become corrupt. Now, if the redo
log scan at InnoDB startup goes past the last
checkpoint, crash recovery is forced.
(Bug#23710)
The server deducted some bytes from the
key_cache_block_size option
value and reduced it to the next lower 512 byte boundary. The
resulting block size was not a power of two. Setting the
key_cache_block_size system
variable to a value that is not a power of two resulted in
MyISAM table corruption.
(Bug#23068, Bug#28478, Bug#25853)
SHOW INNODB STATUS caused an
assertion failure under high load.
(Bug#22819)
SHOW BINLOG EVENTS displayed
incorrect values of End_log_pos for events
associated with transactional storage engines.
(Bug#22540)
A statement of the form CREATE TABLE IF NOT EXISTS t1
SELECT f1() AS i failed with a deadlock error if the
stored function f1() referred to a table with
the same name as the to-be-created table. Now it correctly
produces a message that the table already exists.
(Bug#22427)
Read lock requests that were blocked by a pending write lock request were not allowed to proceed if the statement requesting the write lock was killed. (Bug#21281)
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)
mysql-stress-test.pl and mysqld_multi.server.sh were missing from some binary distributions. (Bug#21023, Bug#25486)
On Windows, the server used 10MB of memory for each connection thread, resulting in memory exhaustion. Now each thread uses 1MB. (Bug#20815)
Worked around an icc problem with an incorrect machine instruction being generated in the context of software pre-fetching after a subroutine got in-lined. (Upgrading to icc 10.0.026 makes the workaround unnecessary.) (Bug#20803)
InnoDB produced an unnecessary (and harmless)
warning: InnoDB: Error: trying to
declare trx to enter InnoDB, but
InnoDB: it already is declared
Under ActiveState Perl, mysql-test-run.pl
would not run.
(Bug#18415)
The server crashed when the size of an
ARCHIVE table grew larger than 2GB.
(Bug#15787)
SQL_BIG_RESULT had no effect for
CREATE TABLE ... SELECT SQL_BIG_RESULT ...
statements.
(Bug#15130)
On 64-bit Windows systems, the Config Wizard failed to complete
the setup because 64-bit Windows does not resolve dynamic
linking of the 64-bit libmysql.dll to a
32-bit application like the Config Wizard.
(Bug#14649)
mysql_setpermission tried to grant global-only privileges at the database level. (Bug#14618)
Parameters of type DATETIME or
DATE in stored procedures were
silently converted to VARBINARY.
(Bug#13675)
For the general query log, logging of prepared statements
executed via the C API differed from logging of prepared
statements performed with PREPARE
and EXECUTE. Logging for the
latter was missing the Prepare and
Execute lines.
(Bug#13326)
The server returned data from SHOW CREATE
TABLE statement or a
SELECT statement on an
INFORMATION_SCHEMA table using the binary
character set.
(Bug#10491)
Backup software can cause
ERROR_SHARING_VIOLATION or
ERROR_LOCK_VIOLATION conditions during file
operations. InnoDB now retries forever until
the condition goes away.
(Bug#9709)
This is a Service Pack release of the MySQL Enterprise Server 5.0.
This is a bugfix release that replaces MySQL 5.0.50sp1.
Bugs fixed:
Security Fix: Three vulnerabilities in yaSSL versions 1.7.5 and earlier were discovered that could lead to a server crash or execution of unauthorized code. The exploit requires a server with yaSSL enabled and TCP/IP connections enabled, but does not require valid MySQL account credentials. The exploit does not apply to OpenSSL.
The proof-of-concept exploit is freely available on the Internet. Everyone with a vulnerable MySQL configuration is advised to upgrade immediately.
This is a Service Pack release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.50). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Bugs fixed:
Security Fix:
Using RENAME TABLE against a
table with explicit DATA DIRECTORY and
INDEX DIRECTORY options can be used to
overwrite system table information by replacing the symbolic
link points. the file to which the symlink points.
MySQL will now return an error when the file to which the symlink points already exists. (Bug#32111, CVE-2007-5969)
Security Fix:
ALTER VIEW retained the original
DEFINER value, even when altered by another
user, which could allow that user to gain the access rights of
the view. Now ALTER VIEW is
allowed only to the original definer or users with the
SUPER privilege.
(Bug#29908)
Security Fix:
When using a FEDERATED table, the local
server could be forced to crash if the remote server returned a
result with fewer columns than expected.
(Bug#29801)
A build problem introduced in MySQL 5.0.52 was resolved: The x86 32-bit Intel icc-compiled server binary had unwanted dependences on Intel icc runtime libraries. (Bug#32514)
InnoDB does not support
SPATIAL indexes, but could crash when asked
to handle one. Now an error is returned.
(Bug#32125)
mysql-test-run.pl could not run
mysqld with root
privileges.
(Bug#30630)
InnoDB had a race condition for an adaptive
hash rw-lock waiting for an X-lock. This fix may also provide
significant speed improvements on systems experiencing problems
with contention for the adaptive hash index.
(Bug#29560)
This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.48). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Functionality added or changed:
Incompatible Change:
The parser accepted statements that contained /* ...
*/ that were not properly closed with
*/, such as SELECT 1 /* +
2. Statements that contain unclosed
/*-comments now are rejected with a syntax
error.
This fix has the potential to cause incompatibilities. Because
of Bug#26302, which caused the trailing */ to
be truncated from comments in views, stored routines, triggers,
and events, it is possible that objects of those types may have
been stored with definitions that now will be rejected as
syntactically invalid. Such objects should be dropped and
re-created so that their definitions do not contain truncated
comments. If a stored object definition contains only a single
statement (does not use a BEGIN ... END
block) and contains a comment within the statement, the comment
should be moved to follow the statement or the object should be
rewritten to use a BEGIN ... END block. For
example, this statement:
CREATE PROCEDURE p() SELECT 1 /* my comment */ ;
Can be rewritten in either of these ways:
CREATE PROCEDURE p() SELECT 1; /* my comment */ CREATE PROCEDURE p() BEGIN SELECT 1 /* my comment */ ; END;
MySQL Cluster:
Mapping of NDB error codes to MySQL
storage engine error codes has been improved.
(Bug#28423)
MySQL Cluster: The output from the cluster management client showing the progress of data node starts has been improved. (Bug#23354)
Server parser performance was improved for expression parsing by lowering the number of state transitions and reductions needed. (Bug#30625)
Server parser performance was improved for boolean expressions. (Bug#30237)
Bugs fixed:
Incompatible Change:
The file mysqld.exe was mistakenly included
in binary distributions between MySQL 5.0.42 and 5.0.48. You
should use mysqld-nt.exe.
(Bug#32197)
Incompatible Change:
Multiple-table DELETE statements
containing ambiguous aliases could have unintended side effects
such as deleting rows from the wrong table. Example:
DELETE FROM t1 AS a2 USING t1 AS a1 INNER JOIN t2 AS a2;
This fix enables alias declarations to be made only in the
table_references part. Elsewhere in
the statement, alias references are allowed but not alias
declarations. However, this patch was reverted in MySQL 5.0.54
because it changed the behavior of a General Availability MySQL
release.
(Bug#30234)
See also Bug#27525.
MySQL Cluster: Packaging:
Some commercial MySQL Cluster RPM packages included support for
the InnoDB storage engine.
(InnoDB is not part of the standard
commercial MySQL Cluster offering.)
(Bug#31989)
MySQL Cluster: Attempting to restore a backup made on a cluster host using one endian to a machine using the other endian could cause the cluster to fail. (Bug#29674)
MySQL Cluster:
Reads on BLOB columns were not
locked when they needed to be to guarantee consistency.
(Bug#29102)
See also Bug#31482.
MySQL Cluster:
A query using joins between several large tables and requiring
unique index lookups failed to complete, eventually returning
Uknown Error after a very long period of
time. This occurred due to inadequate handling of instances
where the Transaction Coordinator ran out of
TransactionBufferMemory, when the cluster
should have returned NDB error code 4012 (Request
ndbd time-out).
(Bug#28804)
MySQL Cluster:
The description of the --print option provided
in the output from ndb_restore --help
was incorrect.
(Bug#27683)
MySQL Cluster:
An invalid subselect on an NDB
table could cause mysqld to crash.
(Bug#27494)
MySQL Cluster:
An attempt to perform a SELECT ... FROM
INFORMATION_SCHEMA.TABLES whose result included
information about NDB tables for
which the user had no privileges crashed the MySQL Server on
which the query was performed.
(Bug#26793)
When a TIMESTAMP with a nonzero
time part was converted to a DATE
value, no warning was generated. This caused index lookups to
assume that this is a valid conversion and was returning rows
that match a comparison between a
TIMESTAMP value and a
DATE keypart. Now a warning is
generated so that TIMESTAMP with
a nonzero time part will not match
DATE values.
(Bug#31221)
A server crash could occur when a
non-DETERMINISTIC stored function was used in
a GROUP BY clause.
(Bug#31035)
For an InnoDB table if a
SELECT was ordered by the primary
key and also had a WHERE field = value clause
on a different field that was indexed, a DESC
order instruction would be ignored.
(Bug#31001)
A failed HANDLER ... READ operation could
leave the table in a locked state.
(Bug#30632)
The optimization that uses a unique index to remove
GROUP BY did not ensure that the index was
actually used, thus violating the ORDER BY
that is implied by GROUP BY.
(Bug#30596)
SHOW STATUS LIKE 'Ssl_cipher_list' from a
MySQL client connected via SSL returned an empty string rather
than a list of available ciphers.
(Bug#30593)
Issuing a DELETE statement having
both an ORDER BY clause and a
LIMIT clause could cause
mysqld to crash.
(Bug#30385)
The Last_query_cost status
variable value can be computed accurately only for simple
“flat” queries, not complex queries such as those
with subqueries or UNION.
However, the value was not consistently being set to 0 for
complex queries.
(Bug#30377)
Queries that had a GROUP BY clause and
selected COUNT(DISTINCT
returned
incorrect results.
(Bug#30324)bit_column)
Using DISTINCT or GROUP BY
on a BIT column in a
SELECT statement caused the
column to be cast internally as an integer, with incorrect
results being returned from the query.
(Bug#30245)
Short-format mysql commands embedded within
/*! ... */ comments were parsed incorrectly
by mysql, which discarded the rest of the
comment including the terminating */
characters. The result was a malformed (unclosed) comment. Now
mysql does not discard the
*/ characters.
(Bug#30164)
When mysqldump wrote
DROP DATABASE statements within
version-specific comments, it included the terminating semicolon
in the wrong place, causing following statements to fail when
the dump file was reloaded.
(Bug#30126)
If a view used a function in its
SELECT statement, the columns
from the view were not inserted into the
INFORMATION_SCHEMA.COLUMNS table.
(Bug#29408)
Killing an SSL connection on platforms where MySQL is compiled
with -DSIGNAL_WITH_VIO_CLOSE (Windows, Mac OS
X, and some others) could crash the server.
(Bug#28812)
A SELECT in one connection could
be blocked by
INSERT ...
ON DUPLICATE KEY UPDATE in another connection even
when low_priority_updates is
set.
(Bug#28587)
mysql_upgrade could run binaries dynamically linked against incorrect versions of shared libraries. (Bug#28560)
SHOW COLUMNS returned
NULL instead of the empty string for the
Default value of columns that had no default
specified.
(Bug#27747)
With recent versions of DBD::mysql, mysqlhotcopy generated table names that were doubly qualified with the database name. (Bug#27694)
For InnoDB tables, CREATE TABLE a AS
SELECT * FROM A would fail.
(Bug#25164)
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)
Worked around an icc problem with an incorrect machine instruction being generated in the context of software pre-fetching after a subroutine got in-lined. (Upgrading to icc 10.0.026 makes the workaround unnecessary.) (Bug#20803)
Parameters of type DATETIME or
DATE in stored procedures were
silently converted to VARBINARY.
(Bug#13675)
This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This release was withdrawn from production and is no longer available.
This section documents all changes and bugfixes that have been applied since the last last MySQL Enterprise Server release (5.0.46). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Functionality added or changed:
If a MyISAM table is created with no
DATA DIRECTORY option, the
.MYD file is created in the database
directory. By default, if MyISAM finds an
existing .MYD file in this case, it
overwrites it. The same applies to .MYI
files for tables created with no INDEX
DIRECTORY option. To suppress this behavior, start the
server with the new --keep_files_on_create
option, in which case MyISAM will not
overwrite existing files and returns an error instead.
(Bug#29325)
MySQL source distributions are now available in Zip format. (Bug#27742)
The EXAMPLE storage engine is now enabled by
default.
Bugs fixed:
Incompatible Change:
Failure to consider collation when comparing space characters
could result in incorrect index entry order, leading to
incorrect comparisons, inability to find some index values,
misordered index entries, misordered ORDER BY
results, or tables that CHECK
TABLE reports as having corrupt indexes.
As a result of this bug fix, indexes must be rebuilt for columns
that use any of these character sets:
eucjpms, euc_kr,
gb2312, latin7,
macce, ujis. See
Section 2.18.3, “Checking Whether Table Indexes Must Be Rebuilt”.
(Bug#29461)
MySQL Cluster:
Warnings and errors generated by ndb_config
--config-file=
were sent to filestdout, rather than to
stderr.
(Bug#25941)
MySQL Cluster:
When a cluster backup was terminated using the ABORT
BACKUP command in the management client, a misleading
error message Backup aborted by application:
Permanent error: Internal error was returned. The
error message returned in such cases now reads Backup
aborted by user request.
(Bug#21052)
MySQL Cluster: Large file support did not work in AIX server binaries. (Bug#10776)
Replication:
SHOW SLAVE STATUS failed when
slave I/O was about to terminate.
(Bug#34305)
Replication:
The thread ID was not reset properly after execution of
mysql_change_user(), which could
cause replication failure when replicating temporary tables.
(Bug#29734)
Replication: Operations that used the time zone replicated the time zone only for successful operations, but did not replicate the time zone for errors that need to know it. (Bug#29536)
Replication:
INSERT DELAYED statements on a
master server are replicated as non-DELAYED
inserts on slaves (which is normal, to preserve serialization),
but the inserts on the slave did not use concurrent inserts. Now
INSERT DELAYED on a slave is
converted to a concurrent insert when possible, and to a normal
insert otherwise.
(Bug#29152)
Replication:
An error that happened inside
INSERT,
UPDATE, or
DELETE statements performed from
within a stored function or trigger could cause inconsistency
between master and slave servers.
(Bug#27417)
Replication: Slave servers could incorrectly interpret an out-of-memory error from the master and reconnect using the wrong binary log position. (Bug#24192)
Memory corruption occurred for some queries with a top-level
OR operation in the WHERE
condition if they contained equality predicates and other
sargable predicates in disjunctive parts of the condition.
(Bug#30396)
The server created temporary tables for filesort operations in
the working directory, not in the directory specified by the
tmpdir system variable.
(Bug#30287)
The query cache does not support retrieval of statements for which column level access control applies, but the server was still caching such statements, thus wasting memory. (Bug#30269)
GROUP BY on
BIT columns produced incorrect
results.
(Bug#30219)
Using KILL QUERY
or KILL
CONNECTION to kill a
SELECT statement caused a server
crash if the query cache was enabled.
(Bug#30201)
Prepared statements containing
CONNECTION_ID() could be written
improperly to the binary log.
(Bug#30200)
When a thread executing a DROP
TABLE statement was killed, the table name locks that
had been acquired were not released.
(Bug#30193)
Use of local variables with non-ASCII names in stored procedures crashed the server. (Bug#30120)
On Windows, client libraries lacked symbols required for linking. (Bug#30118)
--myisam-recover='' (empty option value) did
not disable MyISAM recovery.
(Bug#30088)
The IS_UPDATABLE column in the
INFORMATION_SCHEMA.VIEWS table was
not always set correctly.
(Bug#30020)
Statements within stored procedures ignored the value of the
low_priority_updates system
variable.
(Bug#29963)
See also Bug#26162.
For MyISAM tables on Windows,
INSERT,
DELETE, or
UPDATE followed by
ALTER TABLE within
LOCK TABLES could cause table
corruption.
(Bug#29957)
With auto-reconnect enabled, row fetching for a prepared statement could crash after reconnect occurred because loss of the statement handler was not accounted for. (Bug#29948)
LOCK TABLES did not pre-lock
tables used in triggers of the locked tables. Unexpected locking
behavior and statement failures similar to failed:
1100: Table 'xx' was not locked with
LOCK TABLES could result.
(Bug#29929)
INSERT ... VALUES(CONNECTION_ID(), ...)
statements were written to the binary log in such a way that
they could not be properly restored.
(Bug#29928)
Adding DISTINCT could cause incorrect rows to
appear in a query result.
(Bug#29911)
Using the DATE() function in a
WHERE clause did not return any records after
encountering NULL. However, using
TRIM or CAST produced the
correct results.
(Bug#29898)
Very long prepared statements in stored procedures could cause a server crash. (Bug#29856)
If query execution involved a temporary table,
GROUP_CONCAT() could return a
result with an incorrect character set.
(Bug#29850)
If one thread was performing concurrent inserts, other threads reading from the same table using equality key searches could see the index values for new rows before the data values had been written, leading to reports of table corruption. (Bug#29838)
Repeatedly accessing a view in a stored procedure (for example, in a loop) caused a small amount of memory to be allocated per access. Although this memory is deallocated on disconnect, it could be a problem for a long running stored procedures that make repeated access of views. (Bug#29834)
mysqldump produced output that incorrectly
discarded the
NO_AUTO_VALUE_ON_ZERO value of
the sql_mode variable after
dumping triggers.
(Bug#29788)
An assertion failure occurred within yaSSL for very long keys. (Bug#29784)
For MEMORY tables, the
index_merge union access
method could return incorrect results.
(Bug#29740)
Comparison of TIME values using
the BETWEEN operator led to string
comparison, producing incorrect results in some cases. Now the
values are compared as integers.
(Bug#29739)
For a table with a DATE column
date_col such that selecting rows
with WHERE yielded
a nonempty result, adding date_col =
'date_val 00:00:00'GROUP BY
caused the result
to be empty.
(Bug#29729)date_col
In some cases, INSERT INTO ... SELECT ... GROUP
BY could insert rows even if the
SELECT by itself produced an
empty result.
(Bug#29717)
For the embedded server, the
mysql_stmt_store_result() C API
function caused a memory leak for empty result sets.
(Bug#29687)
EXPLAIN produced
Impossible where for statements of the form
SELECT ... FROM t WHERE c=0, where
c was an ENUM
column defined as a primary key.
(Bug#29661)
On Windows, ALTER TABLE hung if
records were locked in share mode by a long-running transaction.
(Bug#29644)
A left join between two views could produce incorrect results. (Bug#29604)
Certain statements with unions, subqueries, and joins could result in huge memory consumption. (Bug#29582)
Clients using SSL could hang the server. (Bug#29579)
A slave running with
--log-slave-updates would fail to
write INSERT DELAY IGNORE statements to its
binary log, resulting in different binary log contents on the
master and slave.
(Bug#29571)
An incorrect result was returned when comparing string values
that were converted to TIME
values with CAST().
(Bug#29555)
In the ascii character set, conversion of DEL
(0x7F) to Unicode incorrectly resulted in
QUESTION MARK (0x3F) rather than DEL.
(Bug#29499)
A field packet with NULL fields caused a
libmysqlclient crash.
(Bug#29494)
When using a combination of HANDLER... READ
and DELETE on a table, MySQL
continued to open new copies of the table every time, leading to
an exhaustion of file descriptors.
(Bug#29474)
This regression was introduced by Bug#21587.
On Windows, the mysql client died if the user entered a statement and Return after entering Control-C. (Bug#29469)
Killing an INSERT DELAYED thread
caused a server crash.
(Bug#29431)
The special “zero”
ENUM value was coerced to the
normal empty string ENUM value
during a column-to-column copy. This affected CREATE
... SELECT statements and
SELECT statements with aggregate
functions on ENUM columns in the
GROUP BY clause.
(Bug#29360)
Optimization of queries with DETERMINISTIC
stored functions in the WHERE clause was
ineffective: A sequential scan was always used.
(Bug#29338)
MyISAM corruption could occur with the
cp932_japanese_ci collation for the
cp932 character set due to incorrect
comparison for trailing space.
(Bug#29333)
The mysql_list_fields() C API
function incorrectly set
MYSQL_FIELD::decimals for some view columns.
(Bug#29306)
InnoDB refused to start on some versions of
FreeBSD with LinuxThreads. This is fixed by enabling file
locking on FreeBSD.
(Bug#29155)
A maximum of 4TB InnoDB free space was
reported by SHOW TABLE STATUS, which is
incorrect on systems with more than 4TB space.
(Bug#29097)
A byte-order issue in writing a spatial index to disk caused bad index files on some systems. (Bug#29070)
Creation of a legal stored procedure could fail if no default database had been selected. (Bug#29050)
Coercion of ASCII values to character sets that are a superset of ASCII sometimes was not done, resulting in illegal mix of collations errors. These cases now are resolved using repertoire, a new string expression attribute (see Section 9.1.7, “String Repertoire”). (Bug#28875)
Fast ALTER TABLE (that works
without rebuilding the table) acquired duplicate locks in the
storage engine. In MyISAM, if
ALTER TABLE was issued under
LOCK
TABLE, it caused all data inserted after
LOCK
TABLE to disappear.
(Bug#28838)
Tables using the InnoDB storage engine
incremented AUTO_INCREMENT values incorrectly
with ON DUPLICATE KEY UPDATE.
(Bug#28781)
Starting the server with an
innodb_force_recovery value of
4 did not work.
(Bug#28604)
For InnoDB tables, MySQL unnecessarily sorted
records in certain cases when the records were retrieved by
InnoDB in the proper order already.
(Bug#28591)
mysql_install_db could fail to find script files that it needs. (Bug#28585)
If a stored procedure was created and invoked prior to selecting
a default database with USE, a
No database selected error occurred.
(Bug#28551)
On Mac OS X, shared-library installation path names were incorrect. (Bug#28544)
Using the
--skip-add-drop-table
option with mysqldump generated
incorrect SQL if the database included any views. The recreation
of views requires the creation and removal of temporary tables.
This option suppressed the removal of those temporary tables.
The same applied to --compact
since this option also invokes
--skip-add-drop-table.
(Bug#28524)
A race condition in the interaction between
MyISAM and the query cache code caused the
query cache not to invalidate itself for concurrently inserted
data.
(Bug#28249)
Indexing column prefixes in InnoDB tables
could cause table corruption.
(Bug#28138)
Index creation could fail due to truncation of key values to the maximum key length rather than to a mulitiple of the maximum character length. (Bug#28125)
On Windows, symbols for yaSSL and taocrypt were missing from
mysqlclient.lib, resulting in unresolved
symbol errors for clients linked against that library.
(Bug#27861)
Some SHOW statements and
INFORMATION_SCHEMA queries could expose
information not allowed by the user's access privileges.
(Bug#27629)
Some character mappings in the ascii.xml
file were incorrect.
As a result of this bug fix, indexes must be rebuilt for columns
that use the ascii_general_ci collation for
columns that contain any of these characters:
'`', '[',
'\', ']',
'~'. See
Section 2.18.3, “Checking Whether Table Indexes Must Be Rebuilt”.
(Bug#27562)
A SELECT with more than 31 nested
dependent subqueries returned an incorrect result.
(Bug#27352)
INSERT INTO ...
SELECT caused a crash if
innodb_locks_unsafe_for_binlog
was enabled.
(Bug#27294)
FEDERATED tables had an artificially low
maximum of key length.
(Bug#26909)
After the first read of a TEMPORARY table,
CHECK TABLE could report the
table as being corrupt.
(Bug#26325)
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)
ALTER DATABASE did not require at
least one option.
(Bug#25859)
Using HANDLER to open a table
having a storage engine not supported by
HANDLER properly returned an
error, but also improperly prevented the table from being
dropped by other connections.
(Bug#25856)
When using a FEDERATED table, the value of
LAST_INSERT_ID() would not
correctly update the C API interface, which would affect the
autogenerated ID returned both through the C API and the MySQL
protocol, affecting Connectors that used the protocol and/or C
API.
(Bug#25714)
The server was blocked from opening other tables while the
FEDERATED engine was attempting to open a
remote table. Now the server does not check the correctness of a
FEDERATED table at
CREATE TABLE time, but waits
until the table actually is accessed.
(Bug#25679)
Several InnoDB assertion failures were
corrected.
(Bug#25645)
In a stored function or trigger, when InnoDB
detected deadlock, it attempted rollback and displayed an
incorrect error message (Explicit or implicit commit
is not allowed in stored function or trigger). Now
InnoDB returns an error under these
conditions and does not attempt rollback. Rollback is handled
outside of InnoDB above the function/trigger
level.
(Bug#24989)
Dropping a temporary InnoDB table that had
been locked with LOCK TABLES
caused a server crash.
(Bug#24918)
On Windows, executables did not include Vista manifests. (Bug#24732)
See also Bug#22563.
If MySQL/InnoDB crashed very quickly after
starting up, it would not force a checkpoint. In this case,
InnoDB would skip crash recovery at next
startup, and the database would become corrupt. Now, if the redo
log scan at InnoDB startup goes past the last
checkpoint, crash recovery is forced.
(Bug#23710)
SHOW INNODB STATUS caused an
assertion failure under high load.
(Bug#22819)
A statement of the form CREATE TABLE IF NOT EXISTS t1
SELECT f1() AS i failed with a deadlock error if the
stored function f1() referred to a table with
the same name as the to-be-created table. Now it correctly
produces a message that the table already exists.
(Bug#22427)
Read lock requests that were blocked by a pending write lock request were not allowed to proceed if the statement requesting the write lock was killed. (Bug#21281)
On Windows, the server used 10MB of memory for each connection thread, resulting in memory exhaustion. Now each thread uses 1MB. (Bug#20815)
InnoDB produced an unnecessary (and harmless)
warning: InnoDB: Error: trying to
declare trx to enter InnoDB, but
InnoDB: it already is declared
SQL_BIG_RESULT had no effect for
CREATE TABLE ... SELECT SQL_BIG_RESULT ...
statements.
(Bug#15130)
mysql_setpermission tried to grant global-only privileges at the database level. (Bug#14618)
For the general query log, logging of prepared statements
executed via the C API differed from logging of prepared
statements performed with PREPARE
and EXECUTE. Logging for the
latter was missing the Prepare and
Execute lines.
(Bug#13326)
Backup software can cause
ERROR_SHARING_VIOLATION or
ERROR_LOCK_VIOLATION conditions during file
operations. InnoDB now retries forever until
the condition goes away.
(Bug#9709)
This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.44). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Functionality added or changed:
MySQL Cluster:
auto_increment_increment and
auto_increment_offset are now
supported for NDB tables.
(Bug#26342)
Replication:
The sql_mode,
foreign_key_checks,
unique_checks, character
set/collations, and
sql_auto_is_null session
variables are written to the binary log and honored during
replication. See Section 5.2.3, “The Binary Log”.
If a MERGE table cannot be opened or used
because of a problem with an underlying table,
CHECK TABLE now displays
information about which table caused the problem.
(Bug#26976)
Bugs fixed:
MySQL Cluster: When restarting a data node, queries could hang during that node's start phase 5, and continue only after the node had entered phase 6. (Bug#29364)
MySQL Cluster: Replica redo logs were inconsistently handled during a system restart. (Bug#29354)
MySQL Cluster:
The management client's response to START BACKUP
WAIT COMPLETED did not include the backup ID.
(Bug#27640)
Replication:
DROP USER statements that named
multiple users, only some of which could be dropped, were
replicated incorrectly.
(Bug#29030)
On the IBM i5 platform, the installation script in the
.savf binaries unconditionally executed the
mysql_install_db script.
(Bug#30084)
gcov coverage-testing information was not written if the server crashed. (Bug#29543)
Corrupt data resulted from use of SELECT ... INTO
OUTFILE ', where
file_name' FIELDS ENCLOSED
BY 'c'c is a digit or minus sign, followed
by LOAD DATA INFILE
'.
(Bug#29442)file_name' FIELDS ENCLOSED BY
'c'
Use of SHOW BINLOG EVENTS for a
nonexistent log file followed by PURGE
BINARY LOGS caused a server crash.
(Bug#29420)
Assertion failure could occur for grouping queries that employed
DECIMAL user variables with
assignments to them.
(Bug#29417)
For CAST(,
the limits of 65 and 30 on the precision
(expr AS
DECIMAL(M,D))M) and scale
(D) were not enforced.
(Bug#29415)
Results for a select query that aliases the column names against
a view could duplicate one column while omitting another. This
bug could occur for a query over a multiple-table view that
includes an ORDER BY clause in its
definition.
(Bug#29392)
mysqldump created a stray file when a given a too-long file name argument. (Bug#29361)
FULLTEXT indexes could be corrupted by
certain gbk characters.
(Bug#29299)
SELECT ... INTO
OUTFILE followed by LOAD
DATA could result in garbled characters when the
FIELDS ENCLOSED BY clause named a delimiter
of '0', 'b',
'n', 'r',
't', 'N', or
'Z' due to an interaction of character
encoding and doubling for data values containing the enclosed-by
character.
(Bug#29294)
Sort order of the collation wasn't used when comparing trailing
spaces. This could lead to incorrect comparison results,
incorrectly created indexes, or incorrect result set order for
queries that include an ORDER BY clause.
(Bug#29261)
If an ENUM column contained
'' as one of its members (represented with
numeric value greater than 0), and the column contained error
values (represented as 0 and displayed as
''), using ALTER
TABLE to modify the column definition caused the 0
values to be given the numeric value of the nonzero
'' member.
(Bug#29251)
Calling mysql_options() after
mysql_real_connect() could cause
clients to crash.
(Bug#29247)
CHECK TABLE for
ARCHIVE tables could falsely report table
corruption or cause a server crash.
(Bug#29207)
Mixing binary and utf8 columns in a union
caused field lengths to be calculated incorrectly, resulting in
truncation.
(Bug#29205)
AsText() could fail with a buffer overrun.
(Bug#29166)
LOCK TABLES was not atomic when
more than one InnoDB tables were locked.
(Bug#29154)
A network structure was initialized incorrectly, leading to embedded server crashes. (Bug#29117)
An assertion failure occurred if a query contained a conjunctive
predicate of the form
in
the view_column = constantWHERE clause and the GROUP
BY clause contained a reference to a different view
column. The fix also enables application of an optimization that
was being skipped if a query contained a conjunctive predicate
of the form view_column =
constantWHERE clause and
the GROUP BY clause contained a reference to
the same view column.
(Bug#29104)
If an INSERT INTO
... SELECT statement inserted into the same table that
the SELECT retrieved from, and
the SELECT included
ORDER BY and LIMIT
clauses, different data was inserted than the data produced by
the SELECT executed by itself.
(Bug#29095)
Queries that performed a lookup into a
BINARY index containing key
values ending with spaces caused an assertion failure for debug
builds and incorrect results for nondebug builds.
(Bug#29087)
The semantics of BIGINT depended
on platform-specific characteristics.
(Bug#29079)
If one of the queries in a UNION
used the SQL_CACHE option and another query
in the UNION contained a
nondeterministic function, the result was still cached. For
example, this query was incorrectly cached:
SELECT NOW() FROM t1 UNION SELECT SQL_CACHE 1 FROM t1;
REPLACE,
INSERT IGNORE,
and UPDATE IGNORE did not work for
FEDERATED tables.
(Bug#29019)
Inserting into InnoDB tables and executing
RESET MASTER in multiple threads
cause assertion failure in debug server binaries.
(Bug#28983)
For a ucs2 column,
GROUP_CONCAT() did not convert
separators to the result character set before inserting them,
producing a result containing a mixture of two different
character sets.
(Bug#28925)
Queries using UDFs or stored functions were cached. (Bug#28921)
For a join with GROUP BY and/or
ORDER BY and a view reference in the
FROM list, the query metadata erroneously
showed empty table aliases and database names for the view
columns.
(Bug#28898)
Non-utf8 characters could get mangled when
stored in CSV tables.
(Bug#28862)
ALTER VIEW is not supported as a
prepared statement but was not being rejected.
ALTER VIEW is now prohibited as a
prepared statement or when called within stored routines.
(Bug#28846)
In strict SQL mode, errors silently stopped the SQL thread even
for errors named using the --slave-skip-errors
option.
(Bug#28839)
Runtime changes to the
log_queries_not_using_indexes
system variable were ignored.
(Bug#28808)
Selecting a column not present in the selected-from table caused
an extra error to be produced by SHOW
ERRORS.
(Bug#28677)
For a statement of the form CREATE t1 SELECT
, the
server created the column using the
integer_constantDECIMAL data type for large
negative values that are within the range of
BIGINT.
(Bug#28625)
When one thread attempts to lock two (or more) tables and
another thread executes a statement that aborts these locks
(such as REPAIR TABLE,
OPTIMIZE TABLE, or
CHECK TABLE), the thread might
get a table object with an incorrect lock type in the table
cache. The result is table corruption or a server crash.
(Bug#28574)
mysqlbinlog --hexdump generated incorrect
output due to omission of the “ #
” comment character for some comment lines.
(Bug#28293)
The LOCATE() function returned
NULL if any of its arguments evaluated to
NULL. Likewise, the predicate,
LOCATE(, erroneously evaluated to
str,NULL)
IS NULLFALSE.
(Bug#27932)
The modification of a table by a partially completed multi-column update was not recorded in the binlog, rather than being marked by an event and a corresponding error code. (Bug#27716)
A stack overrun could occur when storing
DATETIME values using repeated
prepared statements.
(Bug#27592)
Dropping a user-defined function could cause a server crash if the function was still in use by another thread. (Bug#27564)
Unsafe aliasing in the source caused a client library crash when compiled with gcc 4 at high optimization levels. (Bug#27383)
Index-based range reads could fail for comparisons that involved
contraction characters (such as ch in Czech
or ll in Spanish).
(Bug#27345)
Aggregations in subqueries that refer to outer query columns were not always correctly referenced to the proper outer query. (Bug#27333)
Error returns from the time() system call
were ignored.
(Bug#27198)
Phantom reads could occur under InnoDB
SERIALIZABLE isolation level.
(Bug#27197)
The SUBSTRING() function returned
the entire string instead of an empty string when it was called
from a stored procedure and when the length parameter was
specified by a variable with the value “
0 ”.
(Bug#27130)
ALTER TABLE ... ENABLE KEYS could cause
mysqld to crash when executed on a table
containing on a MyISAM table containing
billions of rows.
(Bug#27029)
Binary content 0x00 in a
BLOB column sometimes became
0x5C 0x00 following a dump and reload, which
could cause problems with data using multi-byte character sets
such as GBK (Chinese). This was due to a
problem with SELECT INTO OUTFILE whereby
LOAD DATA later incorrectly
interpreted 0x5C as the second byte of a
multi-byte sequence rather than as the
SOLIDUS (“\”) character, used by
MySQL as the escape character.
(Bug#26711)
Index creation could corrupt the table definition in the
.frm file: 1) A table with the maximum
number of key segments and maximum length key name would have a
corrupted .frm file, due to incorrect
calculation of the total key length. 2)
MyISAM would reject a table with the maximum
number of keys and the maximum number of key segments in all
keys. (It would allow one less than this total maximum.) Now
MyISAM accepts a table defined with the
maximum.
(Bug#26642)
The index merge union access algorithm could produce incorrect
results with InnoDB tables. The problem could
also occur for queries that used DISTINCT.
(Bug#25798)
Under ActiveState Perl, mysql-test-run.pl
could kill itself when attempting to kill other processes.
(Bug#25657)
A query with DISTINCT in the select list to
which the loose-scan optimization for grouping queries was
applied returned an incorrect result set when the query was used
with the SQL_BIG_RESULT option.
(Bug#25602)
For a multiple-row insert into a FEDERATED
table that refers to a remote transactional table, if the insert
failed for a row due to constraint failure, the remote table
would contain a partial commit (the rows preceding the failed
one) instead of rolling back the statement completely. This
occurred because the rows were treated as individual inserts.
Now FEDERATED performs bulk-insert handling
such that multiple rows are sent to the remote table in a batch.
This provides a performance improvement and enables the remote
table to perform statement rollback properly should an error
occur. This capability has the following limitations:
The size of the insert cannot exceed the maximum packet size between servers. If the insert exceeds this size, it is broken into multiple packets and the rollback problem can occur.
Bulk-insert handling does not occur for
INSERT
... ON DUPLICATE KEY UPDATE.
The FEDERATED storage engine failed silently
for INSERT
... ON DUPLICATE KEY UPDATE if a duplicate key
violation occurred. FEDERATED does not
support ON DUPLICATE KEY UPDATE, so now it
correctly returns an ER_DUP_KEY
error if a duplicate key violation occurs.
(Bug#25511)
A too-long shared-memory-base-name value
could cause a buffer overflow and crash the server or clients.
(Bug#24924)
The server deducted some bytes from the
key_cache_block_size option
value and reduced it to the next lower 512 byte boundary. The
resulting block size was not a power of two. Setting the
key_cache_block_size system
variable to a value that is not a power of two resulted in
MyISAM table corruption.
(Bug#23068, Bug#28478, Bug#25853)
SHOW BINLOG EVENTS displayed
incorrect values of End_log_pos for events
associated with transactional storage engines.
(Bug#22540)
Under ActiveState Perl, mysql-test-run.pl
would not run.
(Bug#18415)
The server crashed when the size of an
ARCHIVE table grew larger than 2GB.
(Bug#15787)
On 64-bit Windows systems, the Config Wizard failed to complete
the setup because 64-bit Windows does not resolve dynamic
linking of the 64-bit libmysql.dll to a
32-bit application like the Config Wizard.
(Bug#14649)
The server returned data from SHOW CREATE
TABLE statement or a
SELECT statement on an
INFORMATION_SCHEMA table using the binary
character set.
(Bug#10491)
This is a bugfix release for the current MySQL Community Server production release family. It replaces MySQL 5.0.41.
Functionality added or changed:
Incompatible Change:
Prior to this release, when DATE
values were compared with
DATETIME values, the time portion
of the DATETIME value was
ignored, or the comparison could be performed as a string
compare. Now a DATE value is
coerced to the DATETIME type by
adding the time portion as 00:00:00. To mimic
the old behavior, use the CAST()
function as shown in this example: SELECT
.
(Bug#28929)date_col = CAST(NOW() AS DATE) FROM
table;
Incompatible Change:
INSERT DELAYED is now downgraded
to a normal INSERT if the
statement uses functions that access tables or triggers, or that
is called from a function or a trigger.
This was done to resolve the following interrelated issues:
The server could abort or deadlock for
INSERT DELAYED statements for
which another insert was performed implicitly (for example,
via a stored function that inserted a row).
A trigger using an INSERT
DELAYED caused the error INSERT DELAYED
can't be used with table ... because it is locked with LOCK
TABLES although the target table was not
actually locked.
INSERT DELAYED into a table
with a BEFORE INSERT or AFTER
INSERT trigger gave an incorrect
NEW pseudocolumn value and caused the
server to deadlock or abort.
MySQL Cluster: The server source tree now includes scripts to simplify building MySQL with SCI support. For more information about SCI interconnects and these build scripts, see Section 17.9.1, “Configuring MySQL Cluster to use SCI Sockets”. (Bug#25470)
Binaries for the Linux x86 statically linked
tar.gz Community package were linked
dynamically, not statically. Static linking has been re-enabled.
(Bug#29617)
INSERT DELAYED statements on
BLACKHOLE tables are now rejected, due to the
fact that the BLACKHOLE storage engine does
not support them.
(Bug#27998)
A new status variable, Com_call_procedure,
indicates the number of calls to stored procedures.
(Bug#27994)
Potential memory leaks in SHOW
PROFILE were eliminated.
(Bug#24795)
Bugs fixed:
Security Fix: A malformed password packet in the connection protocol could cause the server to crash. Thanks for Dormando for reporting this bug, and for providing details and a proof of concept. (Bug#28984, CVE-2007-3780)
Security Fix: Use of a view could allow a user to gain update privileges for tables in other databases. (Bug#27878, CVE-2007-3782)
Security Fix:
The requirement of the DROP
privilege for RENAME TABLE was
not enforced.
(Bug#27515, CVE-2007-2691)
Security Fix:
If a stored routine was declared using SQL SECURITY
INVOKER, a user who invoked the routine could gain
privileges.
(Bug#27337, CVE-2007-2692)
Security Fix:
CREATE TABLE LIKE did not require any
privileges on the source table. Now it requires the
SELECT privilege.
In addition, CREATE TABLE LIKE was not
isolated from alteration by other connections, which resulted in
various errors and incorrect binary log order when trying to
execute concurrently a CREATE TABLE LIKE
statement and either DDL statements on the source table or DML
or DDL statements on the target table.
(Bug#23667, Bug#25578, CVE-2007-3781)
Incompatible Change:
When mysqldump was run with the
--delete-master-logs option,
binary log files were deleted before it was known that the dump
had succeeded, not after. (The method for removing log files
used RESET MASTER prior to the
dump. This also reset the binary log sequence numbering to
.000001.) Now mysqldump
flushes the logs (which creates a new binary log number with the
next sequence number), performs the dump, and then uses
PURGE BINARY LOGS to remove the
log files older than the new one. This also preserves log
numbering because the new log with the next number is generated
and only the preceding logs are removed. However, this may
affect applications if they rely on the log numbering sequence
being reset.
(Bug#24733)
Incompatible Change:
The use of an ORDER BY or
DISTINCT clause with a query containing a
call to the GROUP_CONCAT()
function caused results from previous queries to be redisplayed
in the current result. The fix for this includes replacing a
BLOB value used internally for
sorting with a VARCHAR. This
means that for long results (more than 65,535 bytes), it is
possible for truncation to occur; if so, an appropriate warning
is issued.
(Bug#23856, Bug#28273)
MySQL Cluster: A corrupt schema file could cause a File already open error. (Bug#28770)
MySQL Cluster:
Setting InitialNoOpenFiles equal to
MaxNoOfOpenFiles caused an error. This was
due to the fact that the actual value of
MaxNoOfOpenFiles as used by the cluster was
offset by 1 from the value set in
config.ini.
(Bug#28749)
MySQL Cluster:
UPDATE IGNORE statements involving the
primary keys of multiple tables could result in data corruption.
(Bug#28719)
MySQL Cluster:
A race condition could result when nonmaster nodes (in addition
to the master node) tried to update active status due to a local
checkpoint (that is, between NODE_FAILREP and
COPY_GCIREQ events). Now only the master
updates the active status.
(Bug#28717)
MySQL Cluster: A fast global checkpoint under high load with high usage of the redo buffer caused data nodes to fail. (Bug#28653)
MySQL Cluster:
When an API node sent more than 1024 signals in a single batch,
NDB would process only the first
1024 of these, and then hang.
(Bug#28443)
MySQL Cluster:
A delay in obtaining AUTO_INCREMENT IDs could
lead to excess temporary errors.
(Bug#28410)
MySQL Cluster: The cluster waited 30 seconds instead of 30 milliseconds before reading table statistics. (Bug#28093)
MySQL Cluster:
INSERT IGNORE
wrongly ignored NULL values in unique
indexes.
(Bug#27980)
MySQL Cluster: The name of the month “March” was given incorrectly in the cluster error log. (Bug#27926)
MySQL Cluster:
It was not possible to add a unique index to an
NDB table while in single user
mode.
(Bug#27710)
MySQL Cluster:
Repeated insertion of data generated by
mysqldump into
NDB tables could eventually lead to
failure of the cluster.
(Bug#27437)
MySQL Cluster:
ndb_connectstring did not appear in the
output of SHOW VARIABLES.
(Bug#26675)
MySQL Cluster: A failure to release internal resources following an error could lead to problems with single user mode. (Bug#25818)
Replication:
The result of executing of a prepared statement created with
PREPARE s FROM "SELECT 1 LIMIT ?" was not
replicated correctly.
(Bug#28464)
Replication: Recreating a view that already exists on the master would cause a replicating slave to terminate replication with a 'different error message on slave and master' error. (Bug#28244)
Replication: Binary logging of prepared statements could produce syntactically incorrect queries in the binary log, replacing some parameters with variable names rather than variable values. This could lead to incorrect results on replication slaves. (Bug#26842, Bug#12826)
Replication:
Connections from one mysqld server to another
failed on Mac OS X, affecting replication and
FEDERATED tables.
(Bug#26664)
See also Bug#29083.
Replication: Aborting a statement on the master that applied to a nontransactional statement broke replication. The statement was written to the binary log but not completely executed on the master. Slaves receiving the statement executed it completely, resulting in loss of data synchrony. Now an error code is written to the error log so that the slaves stop without executing the aborted statement. (That is, replication stops, but synchrony to the point of the stop is preserved and you can investigate the problem.) (Bug#26551)
Replication: Restoration of the default database after stored routine or trigger execution on a slave could cause replication to stop if the database no longer existed. (Bug#25082)
Replication: When using transactions and replication, shutting down the master in the middle of a transaction would cause all slaves to stop replicating. (Bug#22725)
Replication:
Using CREATE TABLE LIKE ... would raise an
assertion when replicated to a slave.
(Bug#18950)
Cluster API:
For BLOB reads on operations with
lock mode LM_CommittedRead, the lock mode was
not upgraded to LM_Read before the state of
the BLOB had already been
calculated. The NDB API methods
affected by this problem included the following:
NdbOperation::readTuple()
NdbScanOperation::readTuples()
NdbIndexScanOperation::readTuples()
On the IBM i5 platform, the installation script in the
.savf binaries unconditionally executed the
mysql_install_db script. This problem was
fixed in a repackaged distribution numbered 5.0.45b.
(Bug#30084)
Long path names for internal temporary tables could cause stack overflows. (Bug#29015)
Using an INTEGER column from a
table to ROUND() a number
produced different results than using a constant with the same
value as the INTEGER column.
(Bug#28980)
If a program binds a given number of parameters to a prepared
statement handle and then somehow changes
stmt->param_count to a different number,
mysql_stmt_execute() could crash
the client or server.
(Bug#28934)
INSERT .. ON DUPLICATE KEY UPDATE could under
some circumstances silently update rows when it should not have.
(Bug#28904)
Queries that used UUID() were
incorrectly allowed into the query cache. (This should not
happen because UUID() is
nondeterministic.)
(Bug#28897)
Using a VIEW created with a nonexisting
DEFINER could lead to incorrect results under
some circumstances.
(Bug#28895)
On Windows, USE_TLS was not defined for
mysqlclient.lib.
(Bug#28860)
A subquery with ORDER BY and LIMIT
1 could cause a server crash.
(Bug#28811)
Using BETWEEN with nonindexed date
columns and short formats of the date string could return
incorrect results.
(Bug#28778)
Selecting GEOMETRY columns in a
UNION caused a server crash.
(Bug#28763)
When constructing the path to the original
.frm file, ALTER ..
RENAME was unnecessarily (and incorrectly) lowercasing
the entire path when not on a case-insensitive file system,
causing the statement to fail.
(Bug#28754)
Searches on indexed and nonindexed
ENUM columns could return
different results for empty strings.
(Bug#28729)
Executing EXPLAIN EXTENDED on a query using a
derived table over a grouping subselect could lead to a server
crash. This occurred only when materialization of the derived
tables required creation of an auxiliary temporary table, an
example being when a grouping operation was carried out with
usage of a temporary table.
(Bug#28728)
The result of evaluation for a view's CHECK
OPTION option over an updated record and records of
merged tables was arbitrary and dependant on the order of
records in the merged tables during the execution of the
SELECT statement.
(Bug#28716)
The “manager thread” of the LinuxThreads implementation was unintentionally started before mysqld had dropped privileges (to run as an unprivileged user). This caused signaling between threads in mysqld to fail when the privileges were finally dropped. (Bug#28690)
For debug builds, ALTER TABLE
could trigger an assertion failure due to occurrence of a
deadlock when committing changes.
(Bug#28652)
After an upgrade, the names of stored routines referenced by
views were no longer displayed by SHOW
CREATE VIEW.
(Bug#28605)
This regression was introduced by Bug#23491.
Killing from one connection a long-running EXPLAIN
QUERY started from another connection caused
mysqld to crash.
(Bug#28598)
Outer join queries with ON conditions over
constant outer tables did not return
NULL-complemented rows when conditions were
evaluated to FALSE.
(Bug#28571)
An update on a multiple-table view with the CHECK OPTION clause and a subquery in the WHERE condition could cause an assertion failure. (Bug#28561)
PURGE MASTER LOGS BEFORE
( caused a server
crash. Subqueries are forbidden in the subquery)BEFORE
clause now.
(Bug#28553)
mysqldump calculated the required memory for a hex-blob string incorrectly causing a buffer overrun. This in turn caused mysqldump to crash silently and produce incomplete output. (Bug#28522)
Passing a DECIMAL value as a
parameter of a statement prepared with
PREPARE resulted in an error.
(Bug#28509)
mysql_affected_rows() could
return an incorrect result for
INSERT ...
ON DUPLICATE KEY UPDATE if the
CLIENT_FOUND_ROWS flag was set.
(Bug#28505)
A query that grouped by the result of an expression returned a different result when the expression was assigned to a user variable. (Bug#28494)
Subselects returning LONG values in MySQL
versions later than 5.0.24a returned LONGLONG
prior to this. The previous behavior was restored.
(Bug#28492)
This regression was introduced by Bug#19714.
Forcing the use of an index on a
SELECT query when the index had
been disabled would raise an error without running the query.
The query now executes, with a warning generated noting that the
use of a disabled index has been ignored.
(Bug#28476)
The query SELECT '2007-01-01' + INTERVAL
caused
mysqld to fail.
(Bug#28450)column_name DAY FROM
table_name
A server crash could happen under rare conditions such that a
temporary table outgrew heap memory reserved for it and the
remaining disk space was not big enough to store the table as a
MyISAM table.
(Bug#28449)
mysql_upgrade failed if certain SQL modes were set. Now it sets the mode itself to avoid this problem. (Bug#28401)
A query with a NOT IN subquery predicate
could cause a crash when the left operand of the predicate
evaluated to NULL.
(Bug#28375)
The test case for mysqldump failed with
bin-log disabled.
(Bug#28372)
Attempting to LOAD_FILE from an empty floppy
drive under Windows, caused the server to hang. For example, if
you opened a connection to the server and then issued the
command SELECT LOAD_FILE('a:test');, with no
floppy in the drive, the server was inaccessible until the modal
pop-up dialog box was dismissed.
(Bug#28366)
A buffer overflow could occur when using
DECIMAL columns on Windows
operating systems.
(Bug#28361)
libmysql.dll could not be dynamically loaded
on Windows.
(Bug#28358)
Grouping queries with correlated subqueries in
WHERE conditions could produce incorrect
results.
(Bug#28337)
mysqltest used a too-large stack size on PPC/Debian Linux, causing thread-creation failure for tests that use many threads. (Bug#28333)
EXPLAIN for a query on an empty
table immediately after its creation could result in a server
crash.
(Bug#28272)
The IS_UPDATABLE column in the
INFORMATION_SCHEMA.VIEWS table was
not always set correctly.
(Bug#28266)
Comparing a DATETIME column value
with a user variable yielded incorrect results.
(Bug#28261)
For CAST() of a
NULL value with type
DECIMAL, the return value was
incorrectly initialized, producing a runtime error for binaries
built using Visual C++ 2005.
(Bug#28250)
Portability problems caused by use of isinf()
were corrected.
(Bug#28240)
When dumping procedures, mysqldump
--compact generated
output that restored the session variable
sql_mode without first
capturing it. When dumping routines, mysqldump
--compact neither
set nor retrieved the value of
sql_mode.
(Bug#28223)
Comparison of the string value of a date showed as unequal to
CURTIME(). Similar behavior was
exhibited for DATETIME values.
(Bug#28208)
For InnoDB, in some rare cases the optimizer
preferred a more expensive
ref access to a less
expensive range access.
(Bug#28189)
A performance degradation was observed for outer join queries to which a not-exists optimization was applied. (Bug#28188)
SELECT * INTO OUTFILE ... FROM
INFORMATION_SCHEMA.SCHEMATA failed with an
Access denied error, even for a user who
had the FILE privilege.
(Bug#28181)
The Bytes_received and
Bytes_sent status variables
could hold only 32-bit values (not 64-bit values) on some
platforms.
(Bug#28149)
Comparisons of DATE or
DATETIME values for the
IN() function could yield
incorrect results.
(Bug#28133)
Storing a large number into a
FLOAT or
DOUBLE column with a fixed length
could result in incorrect truncation of the number if the
column's length was greater than 31.
(Bug#28121)
The server could hang for INSERT IGNORE ... ON
DUPLICATE KEY UPDATE if an update failed.
(Bug#28000)
DECIMAL values beginning with
nine 9 digits could be incorrectly rounded.
(Bug#27984)
For INSERT
... ON DUPLICATE KEY UPDATE statements that affected
many rows, updates could be applied to the wrong rows.
(Bug#27954)
Early NULL-filtering optimization did not
work for eq_ref table access.
(Bug#27939)
The second execution of a prepared statement from a
UNION query with ORDER
BY RAND() caused the server to crash. This problem
could also occur when invoking a stored procedure containing
such a query.
(Bug#27937)
For attempts to open a nonexistent table, the server should
report ER_NO_SUCH_TABLE but
sometimes reported
ER_TABLE_NOT_LOCKED.
(Bug#27907)
A stored program that uses a variable name containing multibyte characters could fail to execute. (Bug#27876)
Nongrouped columns were allowed by * in
ONLY_FULL_GROUP_BY SQL mode.
(Bug#27874)
ON conditions from JOIN
expressions were ignored when checking the CHECK
OPTION clause while updating a multiple-table view
that included such a clause.
(Bug#27827)
Debug builds on Windows generated false alarms about uninitialized variables with some Visual Studio runtime libraries. (Bug#27811)
Certain queries that used uncorrelated scalar subqueries caused
EXPLAIN to crash.
(Bug#27807)
Changes to some system variables should invalidate statements in the query cache, but invalidation did not happen. (Bug#27792)
Performing a UNION on two views
that had ORDER BY clauses resulted in an
Unknown column error.
(Bug#27786)
mysql_install_db is supposed to detect existing system tables and create only those that do not exist. Instead, it was exiting with an error if tables already existed. (Bug#27783)
On some systems, udf_example.c returned an
incorrect result length. Also on some systems,
mysql-test-run.pl could not find the shared
object built from udf_example.c.
(Bug#27741)
mysqld did not check the length of option values and could crash with a buffer overflow for long values. (Bug#27715)
Comparisons using row constructors could fail for rows
containing NULL values.
(Bug#27704)
LOAD DATA did not use
CURRENT_TIMESTAMP as the default value for a
TIMESTAMP column for which no
value was provided.
(Bug#27670)
On Linux, the server could not create temporary tables if
lower_case_table_names was set
to 1 and the value of tmpdir was a directory
name containing any uppercase letters.
(Bug#27653)
For InnoDB tables, a multiple-row
INSERT of the form
INSERT INTO t (id...) VALUES (NULL...) ON DUPLICATE KEY
UPDATE id=VALUES(id), where id is
an AUTO_INCREMENT column, could cause
ERROR 1062 (23000): Duplicate entry... errors
or lost rows.
(Bug#27650)
HASH indexes on
VARCHAR columns with binary
collations did not ignore trailing spaces from strings before
comparisons. This could result in duplicate records being
successfully inserted into a MEMORY table
with unique key constraints. A consequence was that internal
MEMORY tables used for GROUP
BY calculation contained duplicate rows that resulted
in duplicate-key errors when converting those temporary tables
to MyISAM, and that error was incorrectly
reported as a table is full error.
(Bug#27643)
The XML output representing an empty result was an empty string
rather than an empty <resultset/>
element.
(Bug#27608)
An error occurred trying to connect to mysqld-debug.exe. (Bug#27597)
Comparison of a DATE with a
DATETIME did not treat the
DATE as having a time part of
00:00:00.
(Bug#27590)
See also Bug#32198.
Selecting MIN() on an indexed
column that contained only NULL values caused
NULL to be returned for other result columns.
(Bug#27573)
If a stored function or trigger was killed, it aborted but no error was thrown, allowing the calling statement to continue without noticing the problem. This could lead to incorrect results. (Bug#27563)
The fix for Bug#17212 provided correct sort order for misordered output of certain queries, but caused significant overall query performance degradation. (Results were correct (good), but returned much more slowly (bad).) The fix also affected performance of queries for which results were correct. The performance degradation has been addressed. (Bug#27531)
The CRC32() function returns an
unsigned integer, but the metadata was signed, which could cause
certain queries to return incorrect results. (For example,
queries that selected a CRC32()
value and used that value in the GROUP BY
clause.)
(Bug#27530)
An interaction between SHOW TABLE
STATUS and other concurrent statements that modify the
table could result in a divide-by-zero error and a server crash.
(Bug#27516)
When ALTER TABLE was used to add
a new DATE column with no
explicit default value, '0000-00-00' was used
as the default even if the SQL mode included the
NO_ZERO_DATE mode to prohibit
that value. A similar problem occurred for
DATETIME columns.
(Bug#27507)
A race condition between DROP
TABLE and SHOW TABLE
STATUS could cause the latter to display incorrect
information.
(Bug#27499)
Using a TEXT local variable in a
stored routine in an expression such as SET
produced
an incorrect result.
(Bug#27415)var =
SUBSTRING(var, 3)
Nested aggregate functions could be improperly evaluated. (Bug#27363)
A stored function invocation in the WHERE
clause was treated as a constant.
(Bug#27354)
Failure to allocate memory associated with
transaction_prealloc_size could
cause a server crash.
(Bug#27322)
mysqldump crashed if it got no data from
SHOW CREATE PROCEDURE (for
example, when trying to dump a routine defined by a different
user and for which the current user had no privileges). Now it
prints a comment to indicate the problem. It also returns an
error, or continues if the --force option is
given.
(Bug#27293)
The error message for error number 137 did
not report which database/table combination reported the
problem.
(Bug#27173)
mysqlbinlog produced different output with
the -R option than without it.
(Bug#27171)
A large filesort could result in a division by zero error and a server crash. (Bug#27119)
Times displayed by SHOW PROFILE
were incorrectly associated with the profile entry one later
than the corrrect one.
(Bug#27060)
Flow control optimization in stored routines could cause exception handlers to never return or execute incorrect logic. (Bug#26977)
SHOW PROFILE hung if executed
before enabling the @@profiling session
variable.
(Bug#26938)
mysqldump would not dump a view for which the
DEFINER no longer exists.
(Bug#26817)
Creating a temporary table with InnoDB when
using the one-file-per-table setting, and when the host file
system for temporary tables was tmpfs, would
cause an assertion within mysqld. This was
due to the use of O_DIRECT when opening the
temporary table file.
(Bug#26662)
mysql_upgrade did not detect failure of external commands that it runs. (Bug#26639)
Some test suite files were missing from some MySQL-test packages. (Bug#26609)
Statements within triggers ignored the value of the
low_priority_updates system
variable.
(Bug#26162)
See also Bug#29963.
Index hints (USE INDEX, IGNORE
INDEX, FORCE INDEX) cannot be used
with FULLTEXT indexes, but were not being
ignored.
(Bug#25951)
If CREATE TABLE t1 LIKE t2 failed due to a
full disk, an empty t2.frm file could be
created but not removed. This file then caused subsequent
attempts to create a table named t2 to fail.
This is easily corrected at the file system level by removing
the t2.frm file manually, but now the
server removes the file if the create operation does not
complete successfully.
(Bug#25761)
Running CHECK TABLE concurrently
with a SELECT,
INSERT or other statement on
Windows could corrupt a MyISAM table.
(Bug#25712)
On Windows, connection handlers did not properly decrement the server's thread count when exiting. (Bug#25621)
mysql_upgrade did not pass a password to mysqlcheck if one was given. (Bug#25452)
On Windows, mysql_upgrade was sensitive to lettercase of the names of some required components. (Bug#25405)
For storage engines that allow the current auto-increment value
to be set, using ALTER TABLE ... ENGINE to
convert a table from one such storage engine to another caused
loss of the current value. (For storage engines that do not
support setting the value, it cannot be retained anyway when
changing the storage engine.)
(Bug#25262)
Due to a race condition, executing
FLUSH
PRIVILEGES in one thread could cause brief table
unavailability in other threads.
(Bug#24988)
Several math functions produced incorrect results for large
unsigned values. ROUND() produced
incorrect results or a crash for a large number-of-decimals
argument.
(Bug#24912)
The result set of a query that used WITH
ROLLUP and DISTINCT could lack some
rollup rows (rows with NULL values for
grouping attributes) if the GROUP BY list
contained constant expressions.
(Bug#24856)
For queries that used ORDER BY with
InnoDB tables, if the optimizer chose an
index for accessing the table but found a covering index that
enabled the ORDER BY to be skipped, no
results were returned.
(Bug#24778)
Concurrent execution of
CREATE TABLE ...
SELECT and other statements involving the target table
suffered from various race conditions, some of which might have
led to deadlocks.
(Bug#24738)
On some Linux distributions where LinuxThreads and NPTL
glibc versions both are available, statically
built binaries can crash because the linker defaults to
LinuxThreads when linking statically, but calls to external
libraries (such as libnss) are resolved to
NPTL versions. This cannot be worked around in the code, so
instead if a crash occurs on such a binary/OS combination, print
an error message that provides advice about how to fix the
problem.
(Bug#24611)
An attempt to execute
CREATE TABLE ...
SELECT when a temporary table with the same name
already existed led to the insertion of data into the temporary
table and creation of an empty nontemporary table.
(Bug#24508)
The MERGE storage engine could return
incorrect results when several index values that compare
equality were present in an index (for example,
'gross' and 'gross ',
which are considered equal but have different lengths).
(Bug#24342)
Some upgrade problems are detected and better error messages suggesting that mysql_upgrade be run are produced. (Bug#24248)
Some views could not be created even when the user had the requisite privileges. (Bug#24040)
Using CAST() to convert
DATETIME values to numeric values
did not work.
(Bug#23656)
The AUTO_INCREMENT value would not be
correctly reported for InnoDB tables when
using SHOW CREATE TABLE statement
or mysqldump command.
(Bug#23313)
Implicit conversion of 9912101 to
DATE did not match
CAST(9912101 AS DATE).
(Bug#23093)
Conversion errors could occur when constructing the condition
for an IN predicate. The predicate was
treated as if the affected column contains
NULL, but if the IN
predicate is inside NOT, incorrect results
could be returned.
(Bug#22855)
SELECT COUNT(*) from a table containing a
DATETIME NOT NULL column could produce
spurious warnings with the
NO_ZERO_DATE SQL mode enabled.
(Bug#22824)
Using SET
GLOBAL to change the
lc_time_names system variable
had no effect on new connections.
(Bug#22648)
A multiple-table UPDATE could
return an incorrect rows-matched value if, during insertion of
rows into a temporary table, the table had to be converted from
a MEMORY table to a MyISAM
table.
(Bug#22364)
yaSSL crashed on pre-Pentium Intel CPUs. (Bug#21765)
Linux binaries were unable to dump core after executing a
setuid() call.
(Bug#21723)
A slave that used
--master-ssl-cipher
could not connect to the master.
(Bug#21611)
Quoted labels in stored routines were mishandled, rendering the routines unusable. (Bug#21513)
Stack overflow caused server crashes. (Bug#21476)
CURDATE() is less than
NOW(), either when comparing
CURDATE() directly
(CURDATE() < NOW() is true) or when
casting CURDATE() to
DATE (CAST(CURDATE() AS
DATE) < NOW() is true). However, storing
CURDATE() in a
DATE column and comparing
incorrectly yielded false. This is fixed by
comparing a col_name <
NOW()DATE column as
DATETIME for comparisons to a
DATETIME constant.
(Bug#21103)
CREATE TABLE IF NOT EXISTS ... SELECT caused
a server crash if the target table already existed and had a
BEFORE INSERT trigger.
(Bug#20903)
Deadlock occurred for attempts to execute CREATE TABLE
IF NOT EXISTS ... SELECT when
LOCK TABLES had been used to
acquire a read lock on the target table.
(Bug#20662, Bug#15522)
Changing a utf8 column in an
InnoDB table to a shorter length did not
shorten the data values.
(Bug#20095)
For dates with 4-digit year parts less than 200, an incorrect
implicit conversion to add a century was applied for date
arithmetic performed with
DATE_ADD(),
DATE_SUB(), +
INTERVAL, and - INTERVAL. (For
example, DATE_ADD('0050-01-01 00:00:00',
INTERVAL 0 SECOND) became '2050-01-01
00:00:00'.)
(Bug#18997)
Granting access privileges to an individual table where the database or table name contained an underscore would fail. (Bug#18660)
The -lmtmalloc library was removed from the
output of mysql_config on Solaris, as it
caused problems when building DBD::mysql (and
possibly other applications) on that platform that tried to use
dlopen() to access the client library.
(Bug#18322)
The check-cpu script failed to detect AMD64 Turion processors correctly. (Bug#17707)
Trying to shut down the server following a failed
LOAD DATA
INFILE caused mysqld to crash.
(Bug#17233)
The omission of leading zeros in dates could lead to erroneous results when these were compared with the output of certain date and time functions. (Bug#16377)
INSERT...ON DUPLICATE KEY UPDATE could cause
Error 1032: Can't find record in ... for
inserts into an InnoDB table unique index
using key column prefixes with an underlying
utf8 string column.
(Bug#13191)
Having the EXECUTE privilege for
a routine in a database should make it possible to
USE that database, but the server
returned an error instead. This has been corrected. As a result
of the change, SHOW TABLES for a
database in which you have only the
EXECUTE privilege returns an
empty set rather than an error.
(Bug#9504)
This is a Service Pack release of the MySQL Enterprise Server 5.0.
This section documents all changes and bug fixes that have been applied since the last MySQL Enterprise Server release (5.0.44).
Bugs fixed:
Using the DATE() function in a
WHERE clause did not return any records after
encountering NULL. However, using
TRIM or CAST produced the
correct results.
(Bug#29898)
For a table with a DATE column
date_col such that selecting rows
with WHERE yielded
a nonempty result, adding date_col =
'date_val 00:00:00'GROUP BY
caused the result
to be empty.
(Bug#29729)date_col
Optimization of queries with DETERMINISTIC
stored functions in the WHERE clause was
ineffective: A sequential scan was always used.
(Bug#29338)
Creation of a legal stored procedure could fail if no default database had been selected. (Bug#29050)
If a stored procedure was created and invoked prior to selecting
a default database with USE, a
No database selected error occurred.
(Bug#28551)
This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This section documents all changes and bug fixes that have been applied since the last MySQL Enterprise Server release (5.0.42).
Functionality added or changed:
MySQL Cluster: The server source tree now includes scripts to simplify building MySQL with SCI support. For more information about SCI interconnects and these build scripts, see Section 17.9.1, “Configuring MySQL Cluster to use SCI Sockets”. (Bug#25470)
Enterprise builds did not include the CSV
storage engine. CSV is now included in
Enterprise builds for all platforms except Windows, QNX, and
NetWare.
(Bug#28844)
INSERT DELAYED statements on
BLACKHOLE tables are now rejected, due to the
fact that the BLACKHOLE storage engine does
not support them.
(Bug#27998)
A new status variable, Com_call_procedure,
indicates the number of calls to stored procedures.
(Bug#27994)
Bugs fixed:
Security Fix: A malformed password packet in the connection protocol could cause the server to crash. Thanks for Dormando for reporting this bug, and for providing details and a proof of concept. (Bug#28984, CVE-2007-3780)
Security Fix:
CREATE TABLE LIKE did not require any
privileges on the source table. Now it requires the
SELECT privilege.
In addition, CREATE TABLE LIKE was not
isolated from alteration by other connections, which resulted in
various errors and incorrect binary log order when trying to
execute concurrently a CREATE TABLE LIKE
statement and either DDL statements on the source table or DML
or DDL statements on the target table.
(Bug#23667, Bug#25578, CVE-2007-3781)
Incompatible Change:
When mysqldump was run with the
--delete-master-logs option,
binary log files were deleted before it was known that the dump
had succeeded, not after. (The method for removing log files
used RESET MASTER prior to the
dump. This also reset the binary log sequence numbering to
.000001.) Now mysqldump
flushes the logs (which creates a new binary log number with the
next sequence number), performs the dump, and then uses
PURGE BINARY LOGS to remove the
log files older than the new one. This also preserves log
numbering because the new log with the next number is generated
and only the preceding logs are removed. However, this may
affect applications if they rely on the log numbering sequence
being reset.
(Bug#24733)
Incompatible Change:
The use of an ORDER BY or
DISTINCT clause with a query containing a
call to the GROUP_CONCAT()
function caused results from previous queries to be redisplayed
in the current result. The fix for this includes