Table of Contents
This appendix lists the enhancements and changes from version to version in MySQL Community Server. This information is updated as bugs are fixed and features are incorporated, so that everybody can follow the development process.
Note that we tend to update the manual at the same time we make changes to MySQL. If you find a recent version of MySQL listed here that you can't find on our download page (http://dev.mysql.com/downloads/), it means that the version has not yet been released (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 change done internally at MySQL AB (the BitKeeper ChangeSet) on which the release was based, not the date when the packages were made available. The binaries are usually made available a few days after the date of the tagged ChangeSet, because building and testing all packages takes some time.
For information on how to determine your current version and release type, see Section 2.2, “Determining your current MySQL version”.
This section documents all enhancements, changes, and bug fixes made to MySQL Community Server from 5.0.27 on. For changes and bug fixes to earlier versions, see Appendix E, MySQL Change History.
This is a bugfix release for the current 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 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)
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)
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 SQL_MODE
,
FOREIGN_KEY_CHECKS
,
UNIQUE_CHECKS
, character set/collations, and
SQL_AUTO_IS_NULL
sesstion variables are
written to the binary log and honoured during replication. See
Section 5.2.3, “The Binary Log”.
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)
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 file
stdout
, rather than to
stderr
.
(Bug#25941)
MySQL Cluster: Large file support did not work in AIX server binaries. (Bug#10776)
When a TIMESTAMP
with a non-zero 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 non-zero 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)
Multiple-table DELETE
statements could delete
rows from the wrong table.
(Bug#30234)
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)
The thread ID was not reset properly after execution of
mysql_change_user()
, which
could cause replication failure when replicating temporary
tables.
(Bug#29734)
For a table with a DATE
column
date_col
such that selecting rows
with WHERE
yielded
a non-empty 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)
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)
Conversion of ASCII 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)
Failure to consider collation when comparing space characters could lead to incorrect index entry order, making it impossible to find some index values. (Bug#29461)
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 non-existent
log file followed by PURGE MASTER 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 filename 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 non-zero ''
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)
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)
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
in the 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
non-debug 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)
DROP USER
statements that named multiple
users, only some of which could be dropped, were replicated
incorrectly.
(Bug#29030)
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.6, “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_constant
DECIMAL
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 pathnames 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.
(Bug#27562)
The parser rules for the SHOW PROFILE
statement were revised to work with older versions of
bison.
(Bug#27433)
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)
Fixed a case of unsafe aliasing in the source that 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
Slave servers could incorrectly interpret an out-of-memory error from the master and reconnect using the wrong binary log position. (Bug#24192)
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. Fix: If the redo
log scan at InnoDB
startup goes past the last
checkpoint, force crash recovery.
(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
.
(Bug#20090)
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)
Bulk-insert handling does not occur for INSERT ... ON
DUPLICATE KEY UPDATE
.
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.
This is a bugfix release for the current production release family. It replaces MySQL 5.0.41.
Functionality added or changed:
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 16.11.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)
Prior to this release, when DATE
values were
compared with DATETIME
values the time
portion of the DATETIME
value was ignored.
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 in the following way: SELECT
.
(Bug#28929)date_field
= CAST(NOW() as
DATE);
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 MASTER 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 non-master 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)
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 pathnames 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
non-deterministic.)
(Bug#28897)
Using a VIEW
created with a non-existing
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 non-indexed
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 filesystem,
causing the statement to fail.
(Bug#28754)
Searches on indexed and non-indexed 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 result of executing of a prepared statement created with
PREPARE s FROM "SELECT 1 LIMIT ?"
was not replicated correctly.
(Bug#28464)
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)
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)
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 non-existent 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)
Non-grouped 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)
mysqldump could not connect using SSL. (Bug#27669)
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)
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)
mysqldump would not dump a view for which the
DEFINER
no longer exists.
(Bug#26817)
Connections from one mysqld server to another
failed on Mac OS X, affecting replication and
FEDERATED
tables.
(Bug#26664)
See also Bug#29083
Creating a temporary table with InnoDB when using the
one-file-per-table setting, and when the host filesystem 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)
Aborting a statement on the master that applied to a non-transactional 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)
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 filesystem 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)
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)
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 non-temporary 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)
When using transactions and replication, shutting down the master in the middle of a transaction would cause all slaves to stop replicating. (Bug#22725)
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)
Using CREATE TABLE LIKE ...
would raise an
assertion when replicated to a slave.
(Bug#18950)
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 bugfix release for the current production release family. It replaces MySQL 5.0.37.
Functionality added or changed:
If a set function S
with an outer
reference
cannot be aggregated in the outer query against which the outer
reference has been resolved, MySQL interprets S
(outer_ref
)
the same way that it would interpret S
(outer_ref
)
.
However, standard SQL requires throwing an error in this
situation. An error now is thrown for such queries if the
S
(const
)ANSI
SQL mode is enabled.
(Bug#27348)
Prefix lengths for columns in SPATIAL
indexes
are no longer displayed in SHOW CREATE TABLE
output. mysqldump uses that statement, so if
a table with SPATIAL
indexes containing
prefixed columns is dumped and reloaded, the index is created
with no prefixes. (The full column width of each column is
indexed.)
(Bug#26794)
The output of mysql --xml
and mysqldump --xml
now
includes a valid XML namespace.
(Bug#25946)
If you use SSL for a client connection, you can tell the client
not to authenticate the server certificate by specifying neither
--ssl-ca
nor --ssl-capath
. The
server still verifies the client according to any applicable
requirements established via GRANT
statements
for the client, and it still uses any
--ssl-ca
/--ssl-capath
values
that were passed to server at startup time.
(Bug#25309)
The server now includes a timestamp in error messages that are
logged as a result of unhandled signals (such as mysqld
got signal 11
messages).
(Bug#24878)
The syntax for index hints has been extended to enable explicit specification that the hint applies only to join processing. See Section 12.2.7.2, “Index Hint Syntax”.
This is a new fix for this issue, and replaces the fix made in MySQL 5.0.25 and reverted in 5.0.26. (Bug#21174)
Added the --secure-file-priv
option for
mysqld, which limits the effect of the
LOAD_FILE()
function and the
LOAD DATA
and SELECT ... INTO
OUTFILE
statements to work only with files in a given
directory.
(Bug#18628)
Binary distributions for some platforms did not include shared
libraries; now shared libraries are shipped for all platforms
except AIX 5.2 64-bit. Exception: The
library for the libmysqld
embedded server is
not shared except on Windows.
(Bug#16520, Bug#26767, Bug#13450)
Added the hostname
system variable, which the
server sets at startup to the server hostname.
The mysql_create_system_tables script was removed because mysql_install_db no longer uses it in MySQL 5.0.
To satisfy different user requirements, we provide several servers. mysqld is an optimized server that is a smaller, faster binary. Each package now also includes mysqld-debug, which is compiled with debugging support but is otherwise configured identically to the non-debug server.
Bugs fixed:
Incompatible Change:
INSERT DELAYED
statements are not supported
for MERGE
tables, but the
MERGE
storage engine was not rejecting such
statements, resulting in table corruption. Applications
previously using INSERT DELAYED
into
MERGE
table will break when upgrading to
versions with this fix. To avoid the problem, remove
DELAYED
from such statements.
(Bug#26464)
MySQL Cluster:
NDB
tables having MEDIUMINT
AUTO_INCREMENT
columns were not restored correctly by
ndb_restore, causing spurious duplicate key
errors. This issue did not affect TINYINT
,
INT
, or BIGINT
columns
with AUTO_INCREMENT
.
(Bug#27775)
MySQL Cluster:
NDB
tables with indexes whose names contained
space characters were not restored correctly by
ndb_restore (the index names were truncated).
(Bug#27758)
MySQL Cluster:
Under certain rare circumstances performing a DROP
TABLE
or TRUNCATE
on an
NDB
table could cause a node failure or
forced cluster shutdown.
(Bug#27581)
MySQL Cluster: Memory usage of a mysqld process grew even while idle. (Bug#27560)
MySQL Cluster:
It was not possible to set
LockPagesInMainMemory
equal to
0
.
(Bug#27291)
MySQL Cluster: A race condition could sometimes occur if the node acting as master failed while node IDs were still being allocated during startup. (Bug#27286)
MySQL Cluster: When a data node was taking over as the master node, a race condition could sometimes occur as the node was assuming responsibility for handling of global checkpoints. (Bug#27283)
MySQL Cluster: Error messages displayed when running in single user mode were inconsistent. (Bug#27021)
MySQL Cluster: The failure of a data node while restarting could cause other data nodes to hang or crash. (Bug#27003)
MySQL Cluster:
On Solaris, the value of an NDB
table column
declared as BIT(33)
was always displayed as
0
.
(Bug#26986)
MySQL Cluster: mysqld processes would sometimes crash under high load. (Bug#26825)
MySQL Cluster:
The output from ndb_restore
--print_data
was incorrect for a
backup made of a database containing tables with
TINYINT
or SMALLINT
columns.
(Bug#26740)
MySQL Cluster: An inadvertent use of unaligned data caused ndb_restore to fail on some 64-bit platforms, including Sparc and Itanium-2. (Bug#26739)
MySQL Cluster:
An invalid pointer was returned following a
FSCLOSECONF
signal when accessing the REDO
logs during a node restart or system restart.
(Bug#26515)
MySQL Cluster:
The failure of a data node when restarting it with
--initial
could lead to failures of subsequent
data node restarts.
(Bug#26481)
MySQL Cluster: Takeover for local checkpointing due to multiple failures of master nodes was sometimes incorrectly handled. (Bug#26457)
MySQL Cluster:
The LockPagesInMemory
parameter was not read
until after distributed communication had already started
between cluster nodes. When the value of this parameter was
1
, this could sometimes result in data node
failure due to missed heartbeats.
(Bug#26454)
MySQL Cluster: Under some circumstances, following the restart of a management node, all data nodes would connect to it normally, but some of them subsequently failed to log any events to the management node. (Bug#26293)
MySQL Cluster:
In some cases, AFTER UPDATE
and
AFTER DELETE
triggers on
NDB
tables that referenced subject table did
not see the results of operation which caused invocation of the
trigger, but rather saw the row as it was prior to the update or
delete operation.
This was most noticeable when an update operation used a
subquery to obtain the rows to be updated. An example would be
UPDATE tbl1 SET col2 = val1 WHERE tbl1.col1 IN (SELECT
col3 FROM tbl2 WHERE c4 = val2)
where there was an
AFTER UPDATE
trigger on table
tbl1
. In such cases, the trigger would fail
to execute.
The problem occurred because the actual update or delete
operations were deferred to be able to perform them later as one
batch. The fix for this bug solves the problem by disabling this
optimization for a given update or delete if the table has an
AFTER
trigger defined for this operation.
(Bug#26242)
MySQL Cluster: Condition pushdown did not work with prepared statements. (Bug#26225)
MySQL Cluster:
Joins on multiple tables containing BLOB
columns could cause data nodes run out of memory, and to crash
with the error NdbObjectIdMap::expand unable to
expand.
(Bug#26176)
MySQL Cluster:
After entering single user mode it was not possible to alter
non-NDB
tables on any SQL nodes other than
the one having sole access to the cluster.
(Bug#25275)
MySQL Cluster:
The management client command
displayed
the message node_id
STATUSNode
when node_id
:
not connectednode_id
was not the node ID of a data node.
The ALL STATUS
command in the cluster
management client still displays status information for data
nodes only. This is by design. See
Section 16.7.2, “Commands in the MySQL Cluster Management Client”, for more
information.
MySQL Cluster:
The message Error 0 in readAutoIncrementValue(): no
Error was written to the error log whenever
SHOW TABLE STATUS
was performed on a Cluster
table that did not have an AUTO_INCREMENT
column.
(Bug#21033)
MySQL Cluster:
Some values of MaxNoOfTables
caused the error
Job buffer congestion to occur.
(Bug#19378)
MySQL Cluster:
When trying to create tables on an SQL node not connected to the
cluster, a misleading error message Table
'tbl_name
' already exists
was generated. The error now generated is Could not
connect to storage engine.
(Bug#18676)
Replication: Some queries that updated multiple tables were not backed up correctly. (Bug#27748)
Replication: Out-of-memory errors were not reported. Now they are written to the error log. (Bug#26844)
Cluster API:
Using NdbBlob::writeData()
to write data in
the middle of an existing blob value (that is, updating the
value) could overwrite some data past the end of the data to be
changed.
(Bug#27018)
Some equi-joins containing a WHERE
clause
that included a NOT IN
subquery caused a
server crash.
(Bug#27870)
SELECT DISTINCT
could return incorrect
results if the select list contained duplicated columns.
(Bug#27659)
With NO_AUTO_VALUE_ON_ZERO
SQL mode enabled,
LOAD DATA
operations could assign incorrect
AUTO_INCREMENT
values.
(Bug#27586)
Incorrect results could be returned for some queries that
contained a select list expression with IN
or
BETWEEN
together with an
ORDER BY
or GROUP BY
on
the same expression using NOT IN
or
NOT BETWEEN
.
(Bug#27532)
Evaluation of an IN()
predicate containing a
decimal-valued argument caused a server crash.
(Bug#27513, Bug#27362, CVE-2007-2583)
Profiling overhead was incurred even with profiling disabled. (Bug#27501)
In out-of-memory conditions, the server might crash or otherwise not report an error to the Windows event log. (Bug#27490)
Passing nested row expressions with different structures to an
IN
predicate caused a server crash.
(Bug#27484)
The decimal.h
header file was incorrectly
omitted from binary distributions.
(Bug#27456)
With innodb_file_per_table
enabled,
attempting to rename an InnoDB
table to a
non-existent database caused the server to exit.
(Bug#27381)
A subquery could get incorrect values for references to outer query columns when it contained aggregate functions that were aggregated in outer context. (Bug#27321)
In a view, a column that was defined using a
GEOMETRY
function was treated as having the
LONGBLOB
data type rather than the
GEOMETRY
type.
(Bug#27300)
Queries containing subqueries with
COUNT(*)
aggregated in an outer
context returned incorrect results. This happened only if the
subquery did not contain any references to outer columns.
(Bug#27257)
SELECT ... INTO OUTFILE
with a long
FIELDS ENCLOSED BY
value could crash the
server.
(Bug#27231)
Use of an aggregate function from an outer context as an
argument to GROUP_CONCAT()
caused a server crash.
(Bug#27229)
String truncation upon insertion into an integer or year column did not generate a warning (or an error in strict mode). (Bug#27176, Bug#26359)
Storing NULL
values in spatial fields caused
excessive memory allocation and crashes on some systems.
(Bug#27164)
Row equalities in WHERE
clauses could cause
memory corruption.
(Bug#27154)
GROUP BY
on a ucs2
column
caused a server crash when there was at least one empty string
in the column.
(Bug#27079)
Duplicate members in SET
definitions were not
detected. Now they result in a warning; if strict SQL mode is
enabled, an error occurs instead.
(Bug#27069)
For INSERT ... ON DUPLICATE KEY UPDATE
statements on tables containing
AUTO_INCREMENT
columns,
LAST_INSERT_ID()
was reset to 0
if no rows were successfully inserted or changed. “Not
changed” includes the case where a row was updated to its
current values, but in that case,
LAST_INSERT_ID()
should not be
reset to 0. Now LAST_INSERT_ID()
is reset to 0 only if no rows were successfully inserted or
touched, whether or not touched rows were changed.
(Bug#27033)
This regression was introduced by Bug#19978
mysql_install_db could terminate with an error after failing to determine that a system table already existed. (Bug#27022)
AFTER UPDATE
triggers were not activated by
the update part of INSERT ... ON DUPLICATE KEY
UPDATE
statements.
(Bug#27006)
This regression was introduced by Bug#19978
In a MEMORY
table, using a
BTREE
index to scan for updatable rows could
lead to an infinite loop.
(Bug#26996)
Invalid optimization of pushdown conditions for queries where an outer join was guaranteed to read only one row from the outer table led to results with too few rows. (Bug#26963)
Windows binaries contained no debug symbol file. Now
.map
and .pdb
files are
included in 32-bit builds for mysqld-nt.exe,
mysqld-debug.exe, and
mysqlmanager.exe.
(Bug#26893)
For MERGE
tables defined on underlying tables
that contained a short VARCHAR
column
(shorter than four characters), using ALTER
TABLE
on at least one but not all of the underlying
tables caused the table definitions to be considered different
from that of the MERGE
table, even if the
ALTER TABLE
did not change the definition.
(Bug#26881)
Improved out-of-memory detection when sending logs from a master server to slaves, and log a message when allocation fails. (Bug#26837)
For InnoDB
tables having a clustered index
that began with a CHAR
or
VARCHAR
column, deleting a record and then
inserting another before the deleted record was purged could
result in table corruption.
(Bug#26835)
Use of a subquery containing GROUP BY
and
WITH ROLLUP
caused a server crash.
(Bug#26830)
Duplicates were not properly identified among (potentially) long
strings used as arguments for
GROUP_CONCAT(DISTINCT)
.
(Bug#26815)
ALTER VIEW
requires the CREATE
VIEW
and DROP
privileges for the
view. However, if the view was created by another user, the
server erroneously required the SUPER
privilege.
(Bug#26813)
Added support for --debugger=dbx
for
mysql-test-run.pl and fixed support for
--debugger=devenv
,
--debugger=DevEnv
, and
--debugger=
.
(Bug#26792)/path/to
/devenv
A result set column formed by concatention of string literals
was incomplete when the column was produced by a subquery in the
FROM
clause.
(Bug#26738)
SSL connections failed on Windows. (Bug#26678)
When using the result of
SEC_TO_TIME()
for time value
greater than 24 hours in an ORDER BY
clause,
either directly or through a column alias, the rows were sorted
incorrectly as strings.
(Bug#26672)
Use of a subquery containing a UNION
with an
invalid ORDER BY
clause caused a server
crash.
(Bug#26661)
The range optimizer could cause the server to run out of memory. (Bug#26625)
The range optimizer could consume a combinatorial amount of
memory for certain classes of WHERE
clauses.
(Bug#26624)
In some error messages, inconsistent format specifiers were used for the translations in different languages. comp_err (the error message compiler) now checks for mismatches. (Bug#26571)
Views that used a scalar correlated subquery returned incorrect results. (Bug#26560)
UNHEX() IS NULL
comparisons failed when
UNHEX()
returned
NULL
.
(Bug#26537)
On 64-bit Windows, large timestamp values could be handled incorrectly. (Bug#26536)
mysqldump
could crash or exhibit incorrect
behavior when some options were given very long values, such as
--fields-terminated-by="
. The code has been cleaned
up to remove a number of fixed-sized buffers and to be more
careful about error conditions in memory allocation.
(Bug#26346)some very long
string
"
If the server was started with
--skip-grant-tables
, Selecting from
INFORMATION_SCHEMA
tables causes a server
crash.
(Bug#26285)
For some values of the position argument, the
INSERT()
function could insert a
NUL byte into the result.
(Bug#26281)
For an INSERT
statement that should fail due
to a column with no default value not being assigned a value,
the statement succeeded with no error if the column was assigned
a value in an ON DUPLICATE KEY UPDATE
clause,
even if that clause was not used.
(Bug#26261)
INSERT DELAYED
statements inserted incorrect
values into BIT
columns.
(Bug#26238)
The temporary file-creation code was cleaned up on Windows to improve server stability. (Bug#26233)
For MyISAM
tables,
COUNT(*)
could return an
incorrect value if the WHERE
clause compared
an indexed TEXT
column to the empty string
(''
). This happened if the column contained
empty strings and also strings starting with control characters
such as tab or newline.
(Bug#26231)
For INSERT INTO ... SELECT
where index
searches used column prefixes, insert errors could occur when
key value type conversion was done.
(Bug#26207)
For DELETE FROM
(with no
tbl_name
ORDER BY
col_name
WHERE
or LIMIT
clause),
the server did not check whether
col_name
was a valid column in the
table.
(Bug#26186)
REPAIR TABLE ... USE_FRM
with an
ARCHIVE
table deleted all records from the
table.
(Bug#26138)
A multiple-row delayed insert with an auto-increment column could cause duplicate entries to be created on the slave in a replication environment. (Bug#26116, Bug#25507)
BENCHMARK()
did not work
correctly for expressions that produced a
DECIMAL
result.
(Bug#26093)
LOAD DATA INFILE
sent an okay to the client
before writing the binary log and committing the changes to the
table had finished, thus violating ACID requirements.
(Bug#26050)
X() IS NULL
and Y() IS
NULL
comparisons failed when
X()
and
Y()
returned
NULL
.
(Bug#26038)
mysqldump crashed for
MERGE
tables if the
--complete-insert
(-c
) option
was given.
(Bug#25993)
Indexes on TEXT
columns were ignored when
ref
accesses were evaluated.
(Bug#25971)
If a thread previously serviced a connection that was killed, excessive memory and CPU use by the thread occurred if it later serviced a connection that had to wait for a table lock. (Bug#25966)
Setting a column to NOT NULL
with an
ON DELETE SET NULL
clause foreign key crashes
the server.
(Bug#25927)
VIEW
restrictions were applied to
SELECT
statements after a CREATE
VIEW
statement failed, as though the
CREATE
had succeeded.
(Bug#25897)
Several deficiencies in resolution of column names for
INSERT ... SELECT
statements were corrected.
(Bug#25831)
Inserting utf8
data into a
TEXT
column that used a single-byte character
set could result in spurious warnings about truncated data.
(Bug#25815)
On Windows, debug builds of mysqld could fail with heap assertions. (Bug#25765)
In certain situations, MATCH ... AGAINST
returned false hits for NULL
values produced
by LEFT JOIN
when no full-text index was
available.
(Bug#25729)
In certain cases it could happen that deleting a row corrupted
an RTREE
index. This affected indexes on
spatial columns.
(Bug#25673)
When RAND()
was called multiple
times inside a stored procedure, the server did not write the
correct random seed values to the binary log, resulting in
incorrect replication.
(Bug#25543)
OPTIMIZE TABLE
might fail on Windows when it
attempts to rename a temporary file to the original name if the
original file had been opened, resulting in loss of the
.MYD
file.
(Bug#25521)
For SHOW ENGINE INNODB STATUS
, the
LATEST DEADLOCK INFORMATION
was not always
cleared properly.
(Bug#25494)
mysql_stmt_fetch()
did an
invalid memory deallocation when used with the embedded server.
(Bug#25492)
GRANT
statements were not replicated if the
server was started with the
--replicate-ignore-table
or
--replicate-wild-ignore-table
option.
(Bug#25482)
Expressions involving SUM()
,
when used in an ORDER BY
clause, could lead
to out-of-order results.
(Bug#25376)
Use of a GROUP BY
clause that referred to a
stored function result together with WITH
ROLLUP
caused incorrect results.
(Bug#25373)
A stored procedure that made use of cursors failed when the procedure was invoked from a stored function. (Bug#25345)
Difficult repair or optimization operations could cause an assertion failure, resulting in a server crash. (Bug#25289)
On Windows, the server exhibited a file-handle leak after reaching the limit on the number of open file descriptors. (Bug#25222)
The REPEAT()
function did not
allow a column name as the count
parameter.
(Bug#25197)
Duplicating the usage of a user variable in a stored procedure or trigger would not be replicated correctly to the slave. (Bug#25167)
A reference to a non-existent column in the ORDER
BY
clause of an UPDATE ... ORDER BY
statement could cause a server crash.
(Bug#25126)
A view on a join is insertable for INSERT
statements that store values into only one table of the join.
However, inserts were being rejected if the inserted-into table
was used in a self-join because MySQL incorrectly was
considering the insert to modify multiple tables of the view.
(Bug#25122)
MySQL would not compile when configured using
--without-query-cache
.
(Bug#25075)
Duplicate entries were not assessed correctly in a
MEMORY
table with a BTREE
primary key on a utf8
ENUM
column.
(Bug#24985)
Selecting the result of AVG()
within a UNION
could produce incorrect
values.
(Bug#24791)
MBROverlaps()
returned incorrect values in
some cases.
(Bug#24563)
Increasing the width of a DECIMAL
column
could cause column values to be changed.
(Bug#24558)
IF(expr
,
unsigned_expr
,
unsigned_expr
) was evaluated to a
signed result, not unsigned. This has been corrected. The fix
also affects constructs of the form IS [NOT]
{TRUE|FALSE}
, which were transformed internally into
IF()
expressions that evaluated
to a signed result.
For existing views that were defined using IS [NOT]
{TRUE|FALSE}
constructs, there is a related
implication. The definitions of such views were stored using the
IF()
expression, not the
original construct. This is manifest in that SHOW
CREATE VIEW
shows the transformed
IF()
expression, not the
original one. Existing views will evaluate correctly after the
fix, but if you want SHOW CREATE VIEW
to
display the original construct, you must drop the view and
re-create it using its original definition. New views will
retain the construct in their definition.
(Bug#24532)
A problem in handling of aggregate functions in subqueries caused predicates containing aggregate functions to be ignored during query execution. (Bug#24484)
DROP TRIGGER
statements would not be filtered
on the slave when using the
replication-wild-do-table
option.
(Bug#24478)
For INSERT ... ON DUPLICATE KEY UPDATE
statements where some AUTO_INCREMENT
values
were generated automatically for inserts and some rows were
updated, one auto-generated value was lost per updated row,
leading to faster exhaustion of the range of the
AUTO_INCREMENT
column.
Because the original problem can affect replication (different values on master and slave), it is recommended that the master and its slaves be upgraded to the current version. (Bug#24432)
The test for the
MYSQL_OPT_SSL_VERIFY_SERVER_CERT
option for
mysql_options()
was performed
incorrectly. Also changed as a result of this bugfix: The
arg
option for the
mysql_options()
C API function
was changed from char *
to void
*
.
(Bug#24121)
A user-defined variable could be assigned an incorrect value if a temporary table was employed in obtaining the result of the query used to determine its value. (Bug#24010)
Queries that used a temporary table for the outer query when evaluating a correlated subquery could return incorrect results. (Bug#23800)
Replication between master and slave would infinitely retry
binary log transmission where the
max_allowed_packet
on the master was larger
than that on the slave if the size of the transfer was between
these two values.
(Bug#23775)
On Windows, debug builds of mysqlbinlog could fail with a memory error. (Bug#23736)
When using certain server SQL modes, the
mysql.proc
table was not created by
mysql_install_db.
(Bug#23669)
The values displayed for the
Innodb_row_lock_time
,
Innodb_row_lock_time_avg
, and
Innodb_row_lock_time_max
status variables
were incorrect.
(Bug#23666)
DOUBLE
values such as
20070202191048.000000
were being treated as
illegal arguments by WEEK()
.
(Bug#23616)
The server could crash if two or more threads initiated query cache resize operation at moments very close in time. (Bug#23527)
SHOW CREATE VIEW
qualified references to
stored functions in the view definition with the function's
database name, even when the database was the default database.
This affected mysqldump (which uses
SHOW CREATE VIEW
to dump views) because the
resulting dump file could not be used to reload the database
into a different database. SHOW CREATE VIEW
now suppresses the database name for references to functions in
the default database.
(Bug#23491)
An INTO OUTFILE
clause is allowed only for
the final SELECT
of a
UNION
, but this restriction was not being
enforced correctly.
(Bug#23345)
NOW()
returned the wrong value
in statements executed at server startup with the
--init-file
option.
(Bug#23240)
With the NO_AUTO_VALUE_ON_ZERO
SQL mode
enabled, LAST_INSERT_ID()
could
return 0 after INSERT ... ON DUPLICATE KEY
UPDATE
. Additionally, the next rows inserted (by the
same INSERT
, or the following
INSERT
with or without ON DUPLICATE
KEY UPDATE
), would insert 0 for the auto-generated
value if the value for the AUTO_INCREMENT
column was NULL
or missing.
(Bug#23233)
SOUNDEX()
returned an invalid
string for international characters in multi-byte character
sets.
(Bug#22638)
When nesting stored procedures within a trigger on a table, a
false dependency error was thrown when one of the nested
procedures contained a DROP TABLE
statement.
(Bug#22580)
Instance Manager did not remove the angel PID file on a clean shutdown. (Bug#22511)
EXPLAIN EXTENDED
did not show
WHERE
conditions that were optimized away.
(Bug#22331)
COUNT(
sometimes generated a spurious truncation warning.
(Bug#21976)decimal_expr
)
IN ((
,
subquery
))IN (((
,
and so forth, are equivalent to subquery
)))IN
(
, which is always
interpreted as a table subquery (so that it is allowed to return
more than one row). MySQL was treating the
“over-parenthesized” subquery as a single-row
subquery and rejecting it if it returned more than one row. This
bug primarily affected automatically generated code (such as
queries generated by Hibernate), because humans rarely write the
over-parenthesized forms.
(Bug#21904)subquery
)
An INSERT
trigger invoking a stored routine
that inserted into a table other than the one on which the
trigger was defined would fail with a Table '...'
doesn't exist referring to the second table when
attempting to delete records from the first table.
(Bug#21825)
For InnoDB
, fixed consistent-read behavior of
the first read statement, if the read was served from the query
cache, for the READ COMMITTED
isolation
level.
(Bug#21409)
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)
When a stored routine attempted to execute a statement accessing a nonexistent table, the error was not caught by the routine's exception handler. (Bug#20713, Bug#8407)
For a stored procedure containing a SELECT
statement that used a complicated join with an
ON
expression, the expression could be
ignored during re-execution of the procedure, yielding an
incorrect result.
(Bug#20492)
The conditions checked by the optimizer to allow use of indexes
in IN
predicate calculations were
unnecessarily tight and were relaxed.
(Bug#20420)
When a TIME_FORMAT()
expression
was used as a column in a GROUP BY
clause,
the expression result was truncated.
(Bug#20293)
The creation of MySQL system tables was not checked for by mysql-test-run.pl. (Bug#20166)
For index reads, the BLACKHOLE
engine did not
return end-of-file (which it must because
BLACKHOLE
tables contain no rows), causing
some queries to crash.
(Bug#19717)
In some cases, the optimizer preferred a range or full index scan access method over lookup access methods when the latter were much cheaper. (Bug#19372)
For
, the result
could be incorrect if expr
IN(value_list
)BIGINT UNSIGNED
values
were used for expr
or in the value
list.
(Bug#19342)
When attempting to call a stored procedure creating a table from
a trigger on a table tbl
in a database
db
, the trigger failed with ERROR
1146 (42S02): Table 'db.tbl' doesn't exist. However,
the actual reason that such a trigger fails is due to the fact
that CREATE TABLE
causes an implicit
COMMIT
, and so a trigger cannot invoke a
stored routine containing this statement. A trigger which does
so now fails with ERROR 1422 (HY000): Explicit or
implicit commit is not allowed in stored function or
trigger, which makes clear the reason for the
trigger's failure.
(Bug#18914)
The update columns for INSERT ... SELECT ... ON
DUPLICATE KEY UPDATE
could be assigned incorrect
values if a temporary table was used to evaluate the
SELECT
.
(Bug#16630)
Conversion of DATETIME
values in numeric
contexts sometimes did not produce a double
(YYYYMMDDHHMMSS.uuuuuu
) value.
(Bug#16546)
For SUBSTRING()
evaluation using
a temporary table, when
SUBSTRING()
was used on a
LONGTEXT column, the max_length
metadata
value of the result was incorrectly calculated and set to 0.
Consequently, an empty string was returned instead of the
correct result.
(Bug#15757)
Loading data using LOAD DATA INFILE
may not
replicate correctly (due to character set incompatibilities) if
the character_set_database
variable is set
before the data is loaded.
(Bug#15126)
User defined variables used within stored procedures and triggers are not replicated correctly when operating in statement-based replication mode. (Bug#14914, Bug#20141)
Local variables in stored routines or triggers, when declared as
the BIT
type, were interpreted as strings.
(Bug#12976)
CONNECTION
is no longer treated as a reserved
word.
(Bug#12204)
This is a bugfix release for the current production release family. It replaces MySQL 5.0.33.
Functionality added or changed:
Incompatible Change: MySQL Cluster:
The LockPagesInMainMemory
configuration
parameter has changed its type and possible values. For more
information, see
LockPagesInMainMemory
.
The values true
and
false
are no longer accepted for this
parameter. If you were using this parameter and had it set to
false
in a previous release, you must
change it to 0
. If you had this parameter
set to true
, you should instead use
1
to obtain the same behavior as
previously, or 2
to take advantage of new
functionality introduced with this release, as described in
the section cited above.
Incompatible Change:
Previously, the DATE_FORMAT()
function returned a binary string. Now it returns a string with
a character set and collation given by
character_set_connection
and
collation_connection
so that it can return
month and weekday names containing non-ASCII characters.
(Bug#22646)
Added the Uptime_since_flush_status
status
variable, which indicates the number of seconds since the most
recent FLUSH STATUS
statement. (From Jeremy
Cole)
(Bug#24822)
Added the SHOW PROFILES
and SHOW
PROFILE
statements to display statement profile data,
and the accompanying
INFORMATION_SCHEMA.PROFILING
table. Profiling
is controlled via the profiling
and
profiling_history_size
session variables. see
Section 12.5.4.22, “SHOW PROFILES
and SHOW PROFILE
Syntax”, and
Section 21.17, “The INFORMATION_SCHEMA PROFILING
Table”. (From Jeremy Cole)
(Bug#24795)
The localhost
anonymous user account created
during MySQL installation on Windows now has no global
privileges. Formerly this account had all global privileges. For
operations that require global privileges, the
root
account can be used instead.
(Bug#24496)
The --skip-thread-priority
option now is
enabled by default for binary Mac OS X distributions. Use of
thread priorities degrades performance on Mac OS X.
(Bug#18526)
When using MERGE
tables the definition of
the MERGE
table and the
MyISAM
tables are checked each time the
tables are opened for access (including any
SELECT
or INSERT
statement. Each table is compared for column order, types,
sizes and associated. If there is a difference in any one of
the tables then the statement will fail.
This is the last version for which MySQL-Max RPM distributions are available. (This change was already made for non-RPM binary distributions in 5.0.27.)
The bundled yaSSL library was upgraded to version 1.5.8.
Added the --disable-grant-options
option to
configure. If configure is
run with this option, the --bootstrap
,
--skip-grant-tables
, and
--init-file
options for
mysqld are disabled and cannot be used. For
Windows, the configure.js script recognizes
the DISABLE_GRANT_OPTIONS
flag, which has the
same effect.
Bugs fixed:
Security Fix:
Using an INFORMATION_SCHEMA
table with
ORDER BY
in a subquery could cause a server
crash.
We would like to thank Oren Isacson of Flowgate Security Consulting and Stefan Streichsbier of SEC Consult for informing us of this problem. (Bug#24630, Bug#26556, CVE-2007-1420)
Incompatible Change:
For ENUM
columns that had enumeration values
containing commas, the commas were mapped to
0xff
internally. However, this rendered the
commas indistinguishable from true 0xff
characters in the values. This no longer occurs. However, the
fix requires that you dump and reload any tables that have
ENUM
columns containing any true
0xff
values. Dump the tables using
mysqldump with the current server before
upgrading from a version of MySQL 5.0 older than 5.0.36 to
version 5.0.36 or newer.
(Bug#24660)
MySQL Cluster:
A query with an IN
clause against an
NDB
table employing explicit user-defined
partitioning did not always return all matching rows.
(Bug#25821)
MySQL Cluster:
It was not possible to create an NDB
table
with a key on two VARCHAR
columns where both
columns had a storage length in excess of 256.
(Bug#25746)
MySQL Cluster: Hosts in clusters with large numbers of nodes could experience excessive CPU usage while obtaining configuration data. (Bug#25711)
MySQL Cluster: In some circumstances, shutting down the cluster could cause connected mysqld processes to crash. (Bug#25668)
MySQL Cluster:
Memory allocations for TEXT
columns were
calculated incorrectly, resulting in space being wasted and
other issues.
(Bug#25562)
MySQL Cluster: The failure of a master node during a node restart could lead to a resource leak, causing later node failures. (Bug#25554)
MySQL Cluster:
An UPDATE
using an IN
clause on an NDB
table on which there was a
trigger caused mysqld to crash.
(Bug#25522)
MySQL Cluster: A node shutdown occurred if the master failed during a commit. (Bug#25364)
MySQL Cluster:
Creating a non-unique index with the USING
HASH
clause silently created an ordered index instead
of issuing a warning.
(Bug#24820)
MySQL Cluster:
The ndb_size.tmpl
file (necessary for using
the ndb_size.pl
script) was missing from
binary distributions.
(Bug#24191)
MySQL Cluster:
When a data node was shut down using the management client
STOP
command, a connection event
(NDB_LE_Connected
) was logged instead of a
disconnection event (NDB_LE_Disconnected
).
(Bug#22773)
MySQL Cluster: The management server did not handle logging of node shutdown events correctly in certain cases. (Bug#22013)
MySQL Cluster:
SELECT
statements with a
BLOB
or TEXT
column in the
selected column list and a WHERE
condition
including a primary key lookup on a VARCHAR
primary key produced empty result sets.
(Bug#19956)
Cluster API:
Deletion of an Ndb_cluster_connection
object
took a very long time.
(Bug#25487)
Cluster API:
Invoking the NdbTransaction::execute()
method
using execution type Commit
and abort option
AO_IgnoreError
could lead to a crash of the
transaction coordinator (DBTC
).
(Bug#25090)
Cluster API: A unique index lookup on a non-existent tuple could lead to a data node timeout (error 4012). (Bug#25059)
Cluster API:
libndbclient.so
was not versioned.
(Bug#13522)
Using ORDER BY
or GROUP BY
could yield different results when selecting from a view and
selecting from the underlying table.
(Bug#26209)
DISTINCT
queries that were executed using a
loose scan for an InnoDB
table that had been
emptied caused a server crash.
(Bug#26159)
A WHERE
clause that used
BETWEEN
for
DATETIME
values could be treated differently
for a SELECT
and a view defined as that
SELECT
.
(Bug#26124)
Collation for LEFT JOIN
comparisons could be
evaluated incorrectly, leading to improper query results.
(Bug#26017)
The WITH CHECK OPTION
clause for views was
ignored for updates of multiple-table views when the updates
could not be performed on fly and the rows to update had to be
put into temporary tables first.
(Bug#25931)
LOAD DATA INFILE
did not work with pipes.
(Bug#25807)
The SEC_TO_TIME()
and
QUARTER()
functions sometimes
did not handle NULL
values correctly.
(Bug#25643)
The InnoDB
parser sometimes did not account
for null bytes, causing spurious failure of some queries.
(Bug#25596)
View definitions that used the !
operator
were treated as containing the NOT
operator,
which has a different precedence and can produce different
results. .
(Bug#25580)
An error in the name resolution of nested JOIN ...
USING
constructs was corrected.
(Bug#25575)
GROUP BY
and DISTINCT
did
not group NULL
values for columns that have a
UNIQUE
index. .
(Bug#25551)
The --with-readline
option for
configure did not work for commercial source
packages, but no error message was printed to that effect. Now a
message is printed.
(Bug#25530)
mysql_stmt_fetch()
did an
invalid memory deallocation when used with the embedded server.
(Bug#25492)
Referencing an ambiguous column alias in an expression in the
ORDER BY
clause of a query caused the server
to crash.
(Bug#25427)
A yaSSL program named test was installed, causing conflicts with the test system utility. It is no longer installed. (Bug#25417)
For a UNIQUE
index containing many
NULL
values, the optimizer would prefer the
index for
conditions over other more selective indexes. .
(Bug#25407)col
IS
NULL
An AFTER UPDATE
trigger on an
InnoDB
table with a composite primary key
caused the server to crash.
(Bug#25398)
Passing a NULL
value to a user-defined
function from within a stored procedure crashes the server.
(Bug#25382)
perror crashed on some platforms due to
failure to handle a NULL
pointer.
(Bug#25344)
mysql.server stop timed out too quickly (35 seconds) waiting for the server to exit. Now it waits up to 15 minutes, to ensure that the server exits. (Bug#25341)
A query that contained an EXIST
subquery with
a UNION
over correlated and uncorrelated
SELECT
queries could cause the server to
crash.
(Bug#25219)
mysql_kill()
caused a server
crash when used on an SSL connection.
(Bug#25203)
yaSSL was sensitive to the presence of whitespace at the ends of lines in PEM-encoded certificates, causing a server crash. (Bug#25189)
A query with ORDER BY
and GROUP
BY
clauses where the ORDER BY
clause had more elements than the GROUP BY
clause caused a memory overrun leading to a crash of the server.
(Bug#25172)
Use of ON DUPLICATE KEY UPDATE
defeated the
usual restriction against inserting into a join-based view
unless only one of the underlying tables is used.
(Bug#25123)
Using a view in combination with a USING
clause caused column aliases to be ignored.
(Bug#25106)
A multiple-table DELETE QUICK
could sometimes
cause one of the affected tables to become corrupted.
(Bug#25048)
ALTER TABLE ... ENABLE KEYS
acquired a global
lock, preventing concurrent execution of other statements that
use tables. .
(Bug#25044)
An assertion failed incorrectly for prepared statements that
contained a single-row uncorrelated subquery that was used as an
argument of the IS NULL
predicate.
(Bug#25027)
A return value of -1
from user-defined
handlers was not handled well and could result in conflicts with
server code.
(Bug#24987)
Accessing a fixed record format table with a crashed key definition results in server/myisamchk segmentation fault. (Bug#24855)
mysqld_multi and
mysqlaccess looked for option files in
/etc
even if the
--sysconfdir
option for
configure had been given to specify a
different directory.
(Bug#24780)
If there was insufficient memory available to mysqld, this could sometimes cause the server to hang during startup. (Bug#24751)
Optimizations that are legal only for subqueries without tables
and WHERE
conditions were applied for any
subquery without tables.
(Bug#24670)
If an ORDER BY
or GROUP BY
list included a constant expression being optimized away and, at
the same time, containing single-row subselects that returned
more that one row, no error was reported. If a query required
sorting by expressions containing single-row subselects that
returned more than one row, execution of the query could cause a
server crash.
(Bug#24653)
For ALTER TABLE
, using ORDER BY
could cause a
server crash. Now the expression
ORDER BY
clause allows
only column names to be specified as sort criteria (which was
the only documented syntax, anyway).
(Bug#24562)
A workaround was implemented to avoid a race condition in the
NPTL pthread_exit()
implementation.
(Bug#24507)
mysqltest crashed with a stack overflow. (Bug#24498)
Within stored routines or prepared statements, inconsistent
results occurred with multiple use of INSERT ... SELECT
... ON DUPLICATE KEY UPDATE
when the ON
DUPLICATE KEY UPDATE
clause erroneously tried to
assign a value to a column mentioned only in its
SELECT
part.
(Bug#24491)
Expressions of the form (a, b) IN (SELECT a, MIN(b)
FROM t GROUP BY a)
could produce incorrect results
when column a
of table t
contained NULL
values while column
b
did not.
(Bug#24420)
If a prepared statement accessed a view, access to the tables listed in the query after that view was checked in the security context of the view. (Bug#24404)
Attempts to access a MyISAM
table with a
corrupt column definition caused a server crash.
(Bug#24401)
When opening a corrupted .frm
file during a
query, the server crashes.
(Bug#24358)
Some joins in which one of the joined tables was a view could return erroneous results or crash the server. (Bug#24345)
A view was not handled correctly if the
SELECT
part contained “
\Z
”.
(Bug#24293)
A query using WHERE
could
cause the server to crash.
(Bug#24261)unsigned_column
NOT IN
('negative_value
')
When SET PASSWORD
was written to the binary
log double quotes were included in the statement. If the slave
was running in with the server SQL mode set to
ANSI_QUOTES
, then the event failed, which
halted the replication process.
(Bug#24158)
Expressions of the form (a, b) IN (SELECT c, d
...)
could produce incorrect results if
a
, b
, or both were
NULL
.
(Bug#24127)
A FETCH
statement using a cursor on a table
which was not in the table cache could sometimes cause the
server to crash.
(Bug#24117)
Queries that evaluate NULL IN (SELECT ... UNION SELECT
...)
could produce an incorrect result
(FALSE
instead of NULL
).
(Bug#24085)
Hebrew-to-Unicode conversion failed for some characters. Definitions for the following Hebrew characters (as specified by the ISO/IEC 8859-8:1999) were added: LEFT-TO-RIGHT MARK (LRM), RIGHT-TO-LEFT MARK (RLM) (Bug#24037)
Some UPDATE
statements were slower than in
previous versions when the search key could not be converted to
a valid value for the type of the search column.
(Bug#24035)
ISNULL(DATE(NULL))
and
ISNULL(CAST(NULL AS DATE))
erroneously returned false.
(Bug#23938)
Within a stored routine, accessing a declared routine variable
with PROCEDURE ANALYSE()
caused a server
crash.
(Bug#23782)
When reading from the standard input on Windows, mysqlbinlog opened the input in text mode rather than binary mode and consequently misinterpreted some characters such as Control-Z. (Bug#23735)
A stored procedure, executed from a connection using a binary character set, and which wrote multibyte data, would write incorrectly escaped entries to the binary log. This caused syntax errors, and caused replication to fail. (Bug#23619, Bug#24492)
OPTIMIZE TABLE
tried to sort R-tree indexes
such as spatial indexes, although this is not possible (see
Section 12.5.2.5, “OPTIMIZE TABLE
Syntax”).
(Bug#23578)
For an InnoDB
table with any ON
DELETE
trigger, TRUNCATE TABLE
mapped to DELETE
and activated triggers. Now
a fast truncation occurs and triggers are not activated. .
(Bug#23556)
The row count for MyISAM
tables was not
updated properly, causing SHOW TABLE STATUS
to report incorrect values.
(Bug#23526)
User-defined variables could consume excess memory, leading to a
crash caused by the exhaustion of resources available to the
MEMORY
storage engine, due to the fact that
this engine is used by MySQL for variable storage and
intermediate results of GROUP BY
queries.
Where SET
had been used, such a condition
could instead give rise to the misleading error message
You may only use constant expressions with
SET, rather than Out of memory (Needed
NNNNNN bytes).
(Bug#23443)
With ONLY_FULL_GROUP_BY
enables, the server
was too strict: Some expressions involving only aggregate values
were rejected as non-aggregate (for example,
MAX(a)
–
MIN(a)
).
(Bug#23417)
The arguments to the ENCODE()
and the DECODE()
functions were
not printed correctly, causing problems in the output of
EXPLAIN EXTENDED
and in view definitions.
(Bug#23409)
A table created with the ROW_FORMAT = FIXED
table option lost the option if an index was added or dropped
with CREATE INDEX
or DROP
INDEX
.
(Bug#23404)
A deadlock could occur, with the server hanging on
Closing tables
, with a sufficient number of
concurrent INSERT DELAYED
, FLUSH
TABLES
, and ALTER TABLE
operations.
(Bug#23312)
Some queries against INFORMATION_SCHEMA
that
used subqueries failed. .
(Bug#23299)
readline
detection did not work correctly on
NetBSD.
(Bug#23293)
If there was insufficient memory to store or update a blob
record in a MyISAM
table then the table will
marked as crashed.
(Bug#23196)
LAST_INSERT_ID()
was not reset
to 0 if INSERT ... SELECT
inserted no rows.
(Bug#23170)
A compressed MyISAM
table that became
corrupted could crash myisamchk and possibly
the MySQL Server.
(Bug#23139)
The number of setsockopt()
calls performed
for reads and writes to the network socket was reduced to
decrease system call overhead.
(Bug#22943)
mysql_upgrade failed when called with a
basedir
pathname containing spaces.
(Bug#22801)
SET lc_time_names =
allowed only exact literal values, not expression
values.
(Bug#22647)value
Changes to the lc_time_names
system variable
were not replicated.
(Bug#22645)
The STDDEV()
function returned a
positive value for data sets consisting of a single value.
(Bug#22555)
Storing values specified as hexadecimal values 64 or more bits
long in BIT(64)
, BIGINT
,
or BIGINT UNSIGNED
columns did not raise any
warning or error if the value was out of range.
(Bug#22533)
SHOW COLUMNS
reported some NOT
NULL
columns as NULL
.
(Bug#22377)
Type conversion errors during formation of index search conditions were not correctly checked, leading to incorrect query results. (Bug#22344)
Changing the value of MI_KEY_BLOCK_LENGTH
in
myisam.h
and recompiling MySQL resulted in
a myisamchk that saw existing
MyISAM
tables as corrupt.
(Bug#22119)
A crash of the MySQL Server could occur when unpacking a
BLOB
column from a row in a corrupted MyISAM
table. This could happen when trying to repair a table using
either REPAIR TABLE
or
myisamchk; it could also happen when trying
to access such a “broken” row using statements like
SELECT
if the table was not marked as
crashed.
(Bug#22053)
The code for generating USE
statements for
binary logging of CREATE PROCEDURE
statements
resulted in confusing output from mysqlbinlog
for DROP PROCEDURE
statements.
(Bug#22043)
For the IF()
and
COALESCE()
function and
CASE
expressions, large
unsigned integer values could be mishandled and result in
warnings.
(Bug#22026)
SSL connections could hang at connection shutdown. (Bug#21781, Bug#24148)
The FEDERATED
storage engine did not support
the euckr
character set.
(Bug#21556)
When updating a table that used a JOIN
of the
table itself (for example, when building trees) and the table
was modified on one side of the expression, the table would
either be reported as crashed or the wrong rows in the table
would be updated.
(Bug#21310)
mysqld_error.h
was not installed when only
the client libraries were built.
(Bug#21265)
InnoDB
: During a restart of the MySQL Server
that followed the creation of a temporary table using the
InnoDB
storage engine, MySQL failed to clean
up in such a way that InnoDB
still attempted
to find the files associated with such tables.
(Bug#20867)
Inserting DEFAULT
into a column with no
default value could result in garbage in the column. Now the
same result occurs as when inserting NULL
into a NOT NULL
column.
(Bug#20691)
A stored routine containing semicolon in its body could not be reloaded from a dump of a binary log. (Bug#20396)
SELECT ... FOR UPDATE
, SELECT ...
LOCK IN SHARE MODE
, DELETE
, and
UPDATE
statements executed using a full table
scan were not releasing locks on rows that did not satisfy the
WHERE
condition.
(Bug#20390)
On Windows, if the server was installed as a service, it did not auto-detect the location of the data directory. (Bug#20376)
The BUILD/check-cpu script did not recognize Celeron processors. (Bug#20061)
If a duplicate key value was present in the table,
INSERT ... ON DUPLICATE KEY UPDATE
reported a
row count indicating that a record was updated, even when no
record actually changed due to the old and new values being the
same. Now it reports a row count of zero.
(Bug#19978)
For SET
, SELECT
, and
DO
statements that invoked a stored function
from a database other than the default database, the function
invocation could fail to be replicated.
(Bug#19725)
ORDER BY
values of the
DOUBLE
or DECIMAL
types
could change the result returned by a query.
(Bug#19690)
The readline
library wrote to uninitialized
memory, causing mysql to crash.
(Bug#19474)
mysqltest incorrectly tried to retrieve result sets for some queries where no result set was available. (Bug#19410)
Use of already freed memory caused SSL connections to hang forever. (Bug#19209)
Some CASE
statements inside stored routines
could lead to excessive resource usage or a crash of the server.
(Bug#19194, Bug#24854)
Instance Manager could crash during shutdown. (Bug#19044)
The server might fail to use an appropriate index for
DELETE
when ORDER BY
,
LIMIT
, and a non-restricting
WHERE
are present.
(Bug#17711)
No warning was issued for use of the DATA
DIRECTORY
or INDEX DIRECTORY
table
options on a platform that does not support them.
(Bug#17498)
The FEDERATED
storage engine did not support
the utf8
character set.
(Bug#17044)
The optimizer removes expressions from GROUP
BY
and DISTINCT
clauses if they
happen to participate in
predicates of the
expression
=
constant
WHERE
clause, the idea being that, if the
expression is equal to a constant, then it cannot take on
multiple values. However, for predicates where the expression
and the constant item are of different result types (for
example, when a string column is compared to 0), this is not
valid, and can lead to invalid results in such cases. The
optimizer now performs an additional check of the result types
of the expression and the constant; if their types differ, then
the expression is not removed from the GROUP
BY
list.
(Bug#15881)
When a prepared statement failed during the prepare operation, the error code was not cleared when it was reused, even if the subsequent use was successful. (Bug#15518)
Dropping a user-defined function sometimes did not remove the
UDF entry from the mysql.proc
table.
(Bug#15439)
Inserting a row into a table without specifying a value for a
BINARY(
column caused the column to be set to spaces, not zeroes.
(Bug#14171)N
) NOT NULL
On Windows, the SLEEP()
function
could sleep too long, especially after a change to the system
clock.
(Bug#14094, Bug#24686, Bug#17635)
mysqldump --order-by-primary failed if the primary key name was an identifier that required quoting. (Bug#13926)
To enable installation of MySQL RPMs on Linux systems running RHEL 4 (which includes SE-Linux) additional information was provided to specify some actions that are allowed to the MySQL binaries. (Bug#12676)
The presence of ORDER BY
in a view definition
prevented the MERGE
algorithm from being used
to resolve the view even if nothing else in the definition
required the TEMPTABLE
algorithm.
(Bug#12122)
If a slave server closed its relay log (for example, due to an error during log rotation), the I/O thread did not recognize this and still tried to write to the log, causing a server crash. (Bug#10798)
The internal functions for table preparation, creation, and
alteration were not re-execution friendly, causing problems in
code that: repeatedly altered a table; repeatedly created and
dropped a table; opened and closed a cursor on a table, altered
the table, and then reopened the cursor; used ALTER
TABLE
to change a table's current
AUTO_INCREMENT
value; created indexes on
utf8
columns.
Re-execution of CREATE DATABASE
,
CREATE TABLE
, and ALTER
TABLE
statements in stored routines or as prepared
statements also caused incorrect results or crashes.
(Bug#4968, Bug#6895, Bug#19182, Bug#19733, Bug#22060, Bug#24879)
This is a bugfix release for the current production release family. It replaces MySQL 5.0.27.
This version of MySQL Community Server has been released as a source tarball only; there are no binaries built by MySQL.
Functionality added or changed:
Incompatible Change:
InnoDB
rolls back only the last statement on
a transaction timeout. A new option,
--innodb_rollback_on_timeout
, causes
InnoDB
to abort and roll back the entire
transaction if a transaction timeout occurs (the same behavior
as in MySQL 5.0.13 and earlier).
(Bug#24200)
Incompatible Change:
The prepared_stmt_count
system variable has
been converted to the Prepared_stmt_count
global status variable (viewable with the SHOW GLOBAL
STATUS
statement).
(Bug#23159)
MySQL Cluster:
Setting the configuration parameter
LockPagesInMainMemory
had no effect.
(Bug#24461)
MySQL Cluster:
The ndb_config utility now accepts
-c
as a short form of the
--ndb-connectstring
option.
(Bug#22295)
MySQL Cluster: Added the --bind-address option for ndbd. This allows a data node process to be bound to a specific network interface. (Bug#22195)
MySQL Cluster:
It is now possible to create a unique hashed index on a column
that is not defined as NOT NULL
.
This change applies only to tables using the
NDB
storage engine.
Unique indexes on columns in NDB
tables do
not store null values because they are mapped to primary keys in
an internal index table (and primary keys cannot contain nulls).
Normally, an additional ordered index is created when one
creates unique indexes on NDB
table columns;
this can be used to search for NULL
values.
However, if USING HASH
is specified when such
an index is created, no ordered index is created.
The reason for permitting unique hash indexes with null values
is that, in some cases, the user wants to save space if a large
number of records are pre-allocated but not fully initialized.
This also assumes that the user will not
try to search for null values. Since MySQL does not support
indexes that are not allowed to be searched in some cases, the
NDB
storage engine uses a full table scan
with pushed conditions for the referenced index columns to
return the correct result.
A warning is returned if one creates a unique nullable hash
index, since the query optimizer should be provided a hint not
to use it with NULL
values if this can be
avoided.
(Bug#21507)
MySQL Cluster:
The Ndb_number_of_storage_nodes
system
variable was renamed to
Ndb_number_of_data_nodes
.
(Bug#20848)
MySQL Cluster:
The HELP
command in the Cluster management
client now provides command-specific help. For example,
HELP RESTART
in ndb_mgm
provides detailed information about the
RESTART
command.
(Bug#19620)
DROP TRIGGER
now supports an IF
EXISTS
clause.
(Bug#23703)
The Com_create_user
status variable was added
(for counting CREATE USER
statements).
(Bug#22958)
The --memlock
option relies on system calls
that are unreliable on some operating systems. If a crash
occurs, the server now checks whether --memlock
was specified and if so issues some information about possible
workarounds.
(Bug#22860)
If the user specified the server options
--max-connections=
or N
--table-open-cache=
, a warning would be given in some cases that some
values were recalculated, with the result that
M
--table-open-cache
could be assigned greater
value.
It should be noted that, in such cases, both the warning and the
increase in the --table-open-cache
value were
completely harmless. Note also that it is not possible for the
MySQL Server to predict or to control limitations on the maximum
number of open files, since this is determined by the operating
system.
The recalculation code has now been fixed to ensure that the
value of --table-open-cache
is no longer
increased automatically, and that a warning is now given only if
some values had to be decreased due to operating system limits.
(Bug#21915)
For the CALL
statement, stored procedures
that take no arguments now can be invoked without parentheses.
That is, CALL p()
and CALL
p
are equivalent.
(Bug#21462)
mysql_upgrade
now passes all the parameters
specified on the command line to both
mysqlcheck
and mysql
using
the upgrade_defaults
file.
(Bug#20100)
SHOW STATUS
is no longer logged to the slow
query log.
(Bug#19764)
mysqldump --single-transaction now uses
START TRANSACTION /*!40100 WITH CONSISTENT SNAPSHOT
*/
rather than BEGIN
to start a
transaction, so that a consistent snapshot will be used on those
servers that support it.
(Bug#19660)
The bundled yaSSL library was upgraded to version 1.5.0.
Bugs fixed:
MySQL Cluster: The failure of a data node failure during a schema operation could lead to additional node failures. (Bug#24752)
MySQL Cluster: A committed read could be attempted before a data node had time to connect, causing a timeout error. (Bug#24717)
MySQL Cluster: Sudden disconnection of an SQL or data node could lead to shutdown of data nodes with the error failed ndbrequire. (Bug#24447)
MySQL Cluster: ndb_config failed when trying to use 2 management servers and node IDs. (Bug#23887)
MySQL Cluster: Backup of a cluster failed if there were any tables with 128 or more columns. (Bug#23502)
MySQL Cluster: Cluster backups failed when there were more than 2048 schema objects in the cluster. (Bug#23499)
MySQL Cluster:
The management client command ALL DUMP 1000
would cause the cluster to crash if data nodes were connected to
the cluster but not yret fully started.
(Bug#23203)
MySQL Cluster:
INSERT ... ON DUPLICATE KEY UPDATE
on an
NDB
table could lead to deadlocks and memory
leaks.
(Bug#23200)
MySQL Cluster: (NDB API): Inacivity timeouts for scans were not correctly handled. (Bug#23107)
MySQL Cluster: If a node restart could not be performed from the REDO log, no node takeover took place. This could cause partitions to be left empty during a system restart. (Bug#22893)
MySQL Cluster: Multiple node restarts in rapid succession could cause a system restart to fail , or induce a race condition. (Bug#22892, Bug#23210)
MySQL Cluster:
(NDB API): Attempting to read a nonexistent tuple using
Commit
mode for
NdbTransaction::execute()
caused node
failures.
(Bug#22672)
MySQL Cluster:
The --help
output from NDB
binaries did not include file-related options.
(Bug#21994)
MySQL Cluster: (NDB API): Scans closed before being executed were still placed in the send queue. (Bug#21941)
MySQL Cluster: A scan timeout returned Error 4028 (Node failure caused abort of transaction) instead of Error 4008 (Node failure caused abort of transaction...). (Bug#21799)
MySQL Cluster:
The node recovery algorithm was missing a version check for
tables in the ALTER_TABLE_COMMITTED
state (as
opposed to the TABLE_ADD_COMMITTED
state,
which has the version check). This could cause inconsistent
schemas across nodes following node recovery.
(Bug#21756)
MySQL Cluster:
The output for the --help
option used with
NDB
executable programs (such as
ndbd, ndb_mgm,
ndb_restore, ndb_config,
and others mentioned in
Section 16.10, “Cluster Utility Programs”) referred to the
Ndb.cfg
file, instead of to
my.cnf
.
(Bug#21585)
MySQL Cluster: Partition distribution keys were updated only for the primary and starting replicas during node recovery. This could lead to node failure recovery for clusters having an odd number of replicas.
We recommend values for NumberOfReplicas
that are even powers of 2, for best results.
MySQL Cluster: The ndb_mgm management client did not set the exit status on errors, always returning 0 instead. (Bug#21530)
MySQL Cluster: Cluster logs were not rotated following the first rotation cycle. (Bug#21345)
MySQL Cluster:
When inserting a row into an NDB
table with a
duplicate value for a non-primary unique key, the error issued
would reference the wrong key.
(Bug#21072)
MySQL Cluster:
Condition pushdown did not work correctly with
DATETIME
columns.
(Bug#21056)
MySQL Cluster: Under some circumstances, local checkpointing would hang, keeping any unstarted nodes from being started. (Bug#20895)
MySQL Cluster:
Using an invalid node ID with the management client
STOP
command could cause
ndb_mgm to hang.
(Bug#20575)
MySQL Cluster: Data nodes added while the cluster was running in single user mode were all assigned node ID 0, which could later cause multiple node failures. Adding nodes while in single user mode is no longer possible. (Bug#20395)
MySQL Cluster:
In some cases where SELECT COUNT(*)
from an
NDB
table should have yielded an error,
MAX_INT
was returned instead.
(Bug#19914)
MySQL Cluster: Following the restart of a management node, the Cluster management client did not automatically reconnect. (Bug#19873)
MySQL Cluster:
Error messages given when trying to make online changes
parameters such as NoOfReplicas
thast can
only be changed via a complete shutdown and restart of the
cluster did not indicate the true nature of the problem.
(Bug#19787)
MySQL Cluster: ndb_restore did not always make clear that it had recovered successfully from temporary errors while restoring a cluster backup. (Bug#19651)
MySQL Cluster:
In rare situations with resource shortages, a crash could result
from insufficient IndexScanOperations
.
(Bug#19198)
MySQL Cluster: ndb_mgm -e show | head would hang after displaying the first 10 lines of output. (Bug#19047)
MySQL Cluster: The error returned by the cluster when too many nodes were defined did not make clear the nature of the problem. (Bug#19045)
MySQL Cluster:
A unique constraint violation was not ignored by an
UPDATE IGNORE
statement when the constraint
violation occurred on a non-primary key.
(Bug#18487, Bug#24303)
MySQL Cluster:
The ndb_config utility did not perform host
lookups correctly when using the --host
option
(Bug#17582)
MySQL Cluster: A problem with takeover during a system restart caused ordered indexes to be rebuilt incorrectly. (Bug#15303)
Cluster API:
Using BIT
values with any of the comparison
methods of the NdbScanFilter
class caused
data nodes to fail.
(Bug#24503)
Cluster API: Some MGM API function calls could yield incorrect return values in certain cases where the cluster was operating under a very high load, or experienced timeouts in inter-node communications. (Bug#24011)
Cluster API:
The NdbOperation::getBlobHandle()
method,
when called with the name of a nonexistent column, caused a
segmentation fault.
(Bug#21036)
Cluster API: When multiple processes or threads in parallel performed the same ordered scan with exclusive lock and updated the retrieved records, the scan could skip some records, which as a result were not updated. (Bug#20446)
The REPEAT()
function could
return NULL
when passed a column for the
count argument.
(Bug#24947)
mysql_upgrade failed if the
--password
(or -p
) option
was given.
(Bug#24896)
With innodb_file_per_table
enabled,
InnoDB
displayed incorrect file times in the
output from SHOW TABLE STATUS
.
(Bug#24712)
ALTER ENABLE KEYS
or ALTER TABLE
DISABLE KEYS
combined with another ALTER
TABLE
option other than RENAME TO
did nothing. In addition, if ALTER TABLE was used on a table
having disabled keys, the keys of the resulting table were
enabled.
(Bug#24395)
The InnoDB
mutex structure was simplified to
reduce memory load.
(Bug#24386)
The --extern
option for
mysql-test-run.pl did not function correctly.
(Bug#24354)
Foreign key identifiers for InnoDB
tables
could not contain certain characters.
(Bug#24299)
The mysql.server script used the source command, which is less portable than the . command; it now uses . instead. (Bug#24294)
ALTER TABLE
statements that performed both
RENAME TO
and {ENABLE|DISABLE}
KEYS
operations caused a server crash.
(Bug#24219)
The loose index scan optimization for GROUP
BY
with MIN
or
MAX
was not applied within other queries,
such as CREATE TABLE ... SELECT ...
,
INSERT ... SELECT ...
, or in the
FROM
clauses of subqueries.
(Bug#24156)
There was a race condition in the InnoDB
fil_flush_file_spaces()
function.
(Bug#24089)
This regression was introduced by Bug#15653
Subqueries for which a pushed-down condition did not produce exactly one key field could cause a server crash. (Bug#24056)
The size of MEMORY
tables and internal
temporary tables was limited to 4GB on 64-bit Windows systems.
(Bug#24052)
Some yaSSL-related memory leaks detected by Valgrind were fixed. (Bug#23981)
The internal SQL interpreter of InnoDB
placed
an unnecessary lock on the supremum record when
innodb_locks_unsafe_for_binlog=1
. This caused
an assertion failure when InnoDB
was built
with debugging enabled.
(Bug#23769)
ROW_COUNT()
did not work
properly as an argument to a stored procedure.
(Bug#23760)
LAST_DAY('0000-00-00')
could
cause a server crash.
(Bug#23653)
A trigger that invoked a stored function could cause a server crash when activated by different client connections. (Bug#23651)
The stack size for NetWare binaries was increased to 128KB to prevent problems caused by insufficient stack size. (Bug#23504)
If elements in a non-top-level IN
subquery
were accessed by an index and the subquery result set included a
NULL
value, the quantified predicate that
contained the subquery was evaluated to NULL
when it should return a non-NULL
value.
(Bug#23478)
When applying the group_concat_max_len
limit,
GROUP_CONCAT()
could truncate
multi-byte characters in the middle.
(Bug#23451)
MySQL 5.0.26 introduced an ABI incompatibility, which this release reverts. Programs compiled against 5.0.26 are not compatible with any other version and must be recompiled. (Bug#23427)
returns
M
% 0NULL
, but (
evaluated to
false.
(Bug#23411)M
% 0) IS NULL
mysql_affected_rows()
could
return values different from
mysql_stmt_affected_rows()
for
the same sequence of statements.
(Bug#23383)
For not-yet-authenticated connections, the
Time
column in SHOW
PROCESSLIST
was a random value rather than
NULL
.
(Bug#23379)
Accuracy was improved for comparisons between
DECIMAL
columns and numbers represented as
strings.
(Bug#23260)
MySQL failed to build on Linux/Alpha. (Bug#23256)
This regression was introduced by Bug#21250
If COMPRESS()
returned
NULL
, subsequent invocations of
COMPRESS()
within a result set
or within a trigger also returned NULL
.
(Bug#23254)
Calculation of COUNT(DISTINCT)
,
AVG(DISTINCT)
, or
SUM(DISTINCT)
when they are
referenced more than once in a single query with GROUP
BY
could cause a server crash.
(Bug#23184)
Insufficient memory (myisam_sort_buffer_size
)
could cause a server crash for several operations on
MyISAM
tables: repair table, create index by
sort, repair by sort, parallel repair, bulk insert.
(Bug#23175)
The column default value in the output from SHOW
COLUMNS
or SELECT FROM
INFORMATION_SCHEMA.COLUMNS
was truncated to 64
characters.
(Bug#23037)
mysql did not check for errors when fetching data during result set printing. (Bug#22913)
Changes to character set variables prior to an action on a replication-ignored table were forgotten by slave servers. (Bug#22877)
InnoDB
exhibited thread thrashing with more
than 50 concurrent connections under an update-intensive
workload.
(Bug#22868)
The return value from my_seek()
was ignored.
(Bug#22828)
The optimizer failed to use equality propagation for
BETWEEN
and
IN
predicates with string arguments.
(Bug#22753)
The Handler_rollback
status variable
sometimes was incremented when no rollback had taken place.
(Bug#22728)
The Host
column in SHOW
PROCESSLIST
output was blank when the server was
started with the --skip-grant-tables
option.
(Bug#22723)
If a table contains an AUTO_INCREMENT
column,
inserting into an insertable view on the table that does not
include the AUTO_INCREMENT
column should not
change the value of
LAST_INSERT_ID()
, because the
side effects of inserting default values into columns not part
of the view should not be visible. MySQL was incorrectly setting
LAST_INSERT_ID()
to zero.
(Bug#22584)
Queries using a column alias in an expression as part of an
ORDER BY
clause failed, an example of such a
query being SELECT mycol + 1 AS mynum FROM mytable
ORDER BY 30 - mynum
.
(Bug#22457)
Using EXPLAIN
caused a server crash for
queries that selected from INFORMATION_SCHEMA
in a subquery in the FROM
clause.
(Bug#22413)
Instance Manager had a race condition involving mysqld PID file removal. (Bug#22379)
A server crash occurred when using LOAD DATA
to load a table containing a NOT NULL
spatial
column, when the statement did not load the spatial column. Now
a NULL supplied to NOT NULL column
error
occurs.
(Bug#22372)
The optimizer used the ref
join type rather
than eq_ref
for a simple join on strings.
(Bug#22367)
Some queries that used MAX()
and
GROUP BY
could incorrectly return an empty
result.
(Bug#22342)
DATE_ADD()
requires complete
dates with no “zero” parts, but sometimes did not
return NULL
when given such a date.
(Bug#22229)
If an init_connect
SQL statement produced an
error, the connection was silently terminated with no error
message. Now the server writes a warning to the error log.
(Bug#22158)
Some small double precision numbers (such as
1.00000001e-300
) that should have been
accepted were truncated to zero.
(Bug#22129)
For a nonexistent table, DROP TEMPORARY TABLE
failed with an incorrect error message if
read_only
was enabled.
(Bug#22077)
Trailing spaces were not removed from Unicode
CHAR
column values when used in indexes. This
resulted in excessive usage of storage space, and could affect
the results of some ORDER BY
queries that
made use of such indexes.
When upgrading, it is necessary to re-create any existing
indexes on Unicode CHAR
columns in order to
take advantage of the fix. This can be done by using a
REPAIR TABLE
statement on each affected
table.
The code for generating USE
statements for
binary logging of CREATE PROCEDURE
statements
resulted in confusing output from mysqlbinlog
for DROP PROCEDURE
statements.
(Bug#22043)
STR_TO_DATE()
returned
NULL
if the format string contained a space
following a non-format character.
(Bug#22029)
Use of a DES-encrypted SSL certificate file caused a server crash. (Bug#21868)
Use of PREPARE
with a CREATE
PROCEDURE
statement that contained a syntax error
caused a server crash.
(Bug#21856)
Adding a day, month, or year interval to a
DATE
value produced a
DATE
, but adding a week interval produced a
DATETIME
value. Now all produce a
DATE
value.
(Bug#21811)
In some cases, the parser failed to distinguish a user-defined function from a stored function. (Bug#21809)
Use of a subquery that invoked a function in the column list of the outer query resulted in a memory leak. (Bug#21798)
Inserting a default or invalid value into a spatial column could
fail with Unknown error
rather than a more
appropriate error.
(Bug#21790)
It was possible to use DATETIME
values whose
year, month, and day parts were all zeroes but whose hour,
minute, and second parts contained nonzero values, an example of
such an illegal DATETIME
being
'0000-00-00 11:23:45'
.
This fix was reverted in MySQL 5.0.40.
See also Bug#25301
yaSSL crashed on pre-Pentium Intel CPUs. (Bug#21765)
Evaluation of subqueries that require the filesort algorithm
were allocating and freeing the
sort_buffer_size
buffer many times, resulting
in slow performance. Now the buffer is allocated once and
reused.
(Bug#21727)
Through the C API, the member strings in
MYSQL_FIELD
for a query that contains
expressions may return incorrect results.
(Bug#21635)
Selecting from a MERGE
table could result in
a server crash if the underlying tables had fewer indexes than
the MERGE
table itself.
(Bug#21617, Bug#22937)
View columns were always handled as having implicit derivation,
leading to illegal mix of collation errors
for some views in UNION
operations. Now view
column derivation comes from the original expression given in
the view definition.
(Bug#21505)
InnoDB
crashed while performing XA recovery
of prepared transactions.
(Bug#21468)
INET_ATON()
returned a signed
BIGINT
value, not an unsigned value.
(Bug#21466)
After FLUSH TABLES WITH READ LOCK
followed by
UNLOCK TABLES
, attempts to drop or alter a
stored routine failed with an error that the routine did not
exist, and attempts to execute the routine failed with a lock
conflict error.
(Bug#21414)
It was possible to set the backslash character (“
\
”) as the delimiter character using
DELIMITER
, but not actually possible to use
it as the delimiter.
(Bug#21412)
For multiple-table UPDATE
statements, storage
engines were not notified of duplicate-key errors.
(Bug#21381)
Within a prepared statement, SELECT (COUNT(*) =
1)
(or similar use of other aggregate functions) did
not return the correct result for statement re-execution.
(Bug#21354)
It was possible for a stored routine with a
non-latin1
name to cause a stack overrun.
(Bug#21311)
Certain malformed INSERT
statements could
crash the mysql client.
(Bug#21142)
Creating a TEMPORARY
table with the same name
as an existing table that was locked by another client could
result in a lock conflict for DROP TEMPORARY
TABLE
because the server unnecessarily tried to
acquire a name lock.
(Bug#21096)
Incorrect results could be obtained from re-execution of a
parametrized prepared statement or a stored routine with a
SELECT
that uses LEFT JOIN
with a second table having only one row.
(Bug#21081)
Within a stored routine, a view definition cannot refer to routine parameters or local variables. However, an error did not occur until the routine was called. Now it occurs during parsing of the routine creation statement.
A side effect of this fix is that if you have already created
such routines, and error will occur if you execute
SHOW CREATE PROCEDURE
or SHOW
CREATE FUNCTION
. You should drop these routines
because they are erroneous.
In mysql, invoking connect
or \r
with very long
db_name
or
host_name
parameters caused buffer
overflow.
(Bug#20894)
SHOW VARIABLES
truncated the
Value
field to 256 characters.
(Bug#20862)
Selecting into variables sometimes returned incorrect wrong results. (Bug#20836)
WITH ROLLUP
could group unequal values.
(Bug#20825)
Range searches on columns with an index prefix could miss records. (Bug#20732)
On slave servers, transactions that exceeded the lock wait timeout failed to roll back properly. (Bug#20697)
Inserting DEFAULT
into a column with no
default value could result in garbage in the column. Now the
same result occurs as when inserting NULL
into a NOT NULL
column.
(Bug#20691)
An UPDATE
that referred to a key column in
the WHERE
clause and activated a trigger that
modified the column resulted in a loop.
(Bug#20670)
CONCURRENT
did not work correctly for
LOAD DATA INFILE
.
(Bug#20637)
mysql_fix_privilege_tables.sql
altered the
table_privs.table_priv
column to contain too
few privileges, causing loss of the CREATE
VIEW
and SHOW VIEW
privileges.
(Bug#20589)
LIKE
searches failed for indexed
utf8
character columns.
(Bug#20471)
With lower_case_table_names
set to 1,
SHOW CREATE TABLE
printed incorrect output
for table names containing Turkish I (LATIN CAPITAL LETTER I
WITH DOT ABOVE).
(Bug#20404)
A query with a subquery that references columns of a view from
the outer SELECT
could return an incorrect
result if used from a prepared statement.
(Bug#20327)
For queries that select from a view, the server was returning
MYSQL_FIELD
metadata inconsistently for view
names and table names. For view columns, the server now returns
the view name in the table
field and, if the
column selects from an underlying table, the table name in the
org_table
field.
(Bug#20191)
Invalidating the query cache caused a server crash for
INSERT INTO ... SELECT
statements that
selected from a view.
(Bug#20045)
With SQL_MODE=TRADITIONAL
, MySQL incorrectly
aborted on warnings within stored routines and triggers.
(Bug#20028)
Unsigned BIGINT
values treated as signed
values by the MOD()
function.
(Bug#19955)
Compiling PHP 5.1 with the MySQL static libraries failed on some versions of Linux. (Bug#19817)
The DELIMITER
statement did not work
correctly when used in an SQL file run using the
SOURCE
statement.
(Bug#19799)
mysqldump --xml produced invalid XML for
BLOB
data.
(Bug#19745)
Column names were not quoted properly for replicated views. (Bug#19736)
For a cast of a DATETIME
value containing
microseconds to DECIMAL
, the microseconds
part was truncated without generating a warning. Now the
microseconds part is preserved.
(Bug#19491)
InnoDB
: Reduced optimization level for
Windows 64 builds to handle possible memory overrun.
(Bug#19424)
SQL statements close to the size of
max_allowed_packet
could produce binary log
events larger than max_allowed_packet
that
could not be read by slave servers.
(Bug#19402)
VARBINARY
column values inserted on a MySQL
4.1 server had trailing zeroes following upgrade to MySQL 5.0 or
later.
(Bug#19371)
FLUSH INSTANCES
in Instance Manager triggered
an assertion failure.
(Bug#19368)
For a debug server, a reference to an undefined user variable in
a prepared statment executed with EXECUTE
caused an assertion failure.
(Bug#19356)
The server could send incorrect column count information to the client for queries that produce a larger number of columns than can fit in a two-byte number. (Bug#19216)
Within a trigger for a base table, selecting from a view on that base table failed. (Bug#19111)
The value of the warning_count
system
variable was not being calculated correctly (also affecting
SHOW COUNT(*) WARNINGS
).
(Bug#19024)
For some problems relating to character set conversion or
incorrect string values for INSERT
or
UPDATE
, the server was reporting truncation
or length errors instead.
(Bug#18908)
DELETE IGNORE
could hang for foreign key
parent deletes.
(Bug#18819)
Constant expressions and some numeric constants used as input parameters to user-defined functions were not treated as constants. (Bug#18761)
InnoDB
used table locks (not row locks)
within stored functions.
(Bug#18077)
myisampack wrote to unallocated memory, causing a crash. (Bug#17951)
FLUSH LOGS
or mysqladmin
flush-logs caused a server crash if the binary log was
not open.
(Bug#17733)
mysql_fix_privilege_tables did not handle a password containing embedded space or apostrophe characters. (Bug#17700)
mysql would lose its connection to the server if its standard output was not writable. (Bug#17583)
Attempting to use a view containing DEFINER
information for a non-existent user resulted in an error message
that revealed the definer account. Now the definer is revealed
only to superusers. Other users receive only an access
denied
message.
(Bug#17254)
mysql-test-run did not work correctly for RPM-based installations. (Bug#17194)
IN()
and
CHAR()
can return
NULL
, but did not signal that to the query
processor, causing incorrect results for
IS NULL
operations.
(Bug#17047)
A client library crash was caused by executing a statement such
as SELECT * FROM t1 PROCEDURE ANALYSE()
using
a server side cursor on a table t1
that does
not have the same number of columns as the output from
PROCEDURE ANALYSE()
.
(Bug#17039)
The WITH CHECK OPTION
for a view failed to
prevent storing invalid column values for
UPDATE
statements.
(Bug#16813)
Slave servers would retry the execution of a SQL statement an
infinite number of times, ignoring the value
SLAVE_TRANSACTION_RETRIES
when using the NDB
engine.
(Bug#16228)
InnoDB
showed substandard performance with
multiple queries running concurrently.
(Bug#15815)
ALTER TABLE
was not able to rename a view.
(Bug#14959)
Statements such as DROP PROCEDURE
and
DROP VIEW
were written to the binary log too
late due to a race condition.
(Bug#14262)
A literal string in a GROUP BY
clause could
be interpreted as a column name.
(Bug#14019)
Instance Manager didn't close the client socket file when starting a new mysqld instance. mysqld inherited the socket, causing clients connected to Instance Manager to hang. (Bug#12751)
Entries in the slow query log could have an incorrect
Rows_examined
value.
(Bug#12240)
Warnings were generated when explicitly casting a character to a
number (for example, CAST('x' AS
SIGNED)
), but not for implicit conversions in simple
arithmetic operations (such as 'x' + 0
). Now
warnings are generated in all cases.
(Bug#11927)
Lack of validation for input and output TIME
values resulted in several problems:
SEC_TO_TIME()
in some cases did
not clip large values to the TIME
range
appropriately; SEC_TO_TIME()
treated BIGINT UNSIGNED
values as signed;
only truncation warnings were produced when both truncation and
out-of-range TIME
values occurred.
(Bug#11655, Bug#20927)
Metadata for columns calculated from scalar subqueries was limited to integer, double, or string, even if the actual type of the column was different. (Bug#11032)
Several string functions could return incorrect results when given very large length arguments. (Bug#10963)
FROM_UNIXTIME()
did not accept
arguments up to POWER(2,31)-1
,
which it had previously.
(Bug#9191)
Subqueries of the form NULL IN (SELECT ...)
returned invalid results.
(Bug#8804, Bug#23485)
OPTIMIZE TABLE
with
myisam_repair_threads
> 1 could result in
MyISAM
table corruption.
(Bug#8283)
Transient errors in replication from master to slave may trigger
multiple Got fatal error 1236: 'binlog truncated in the
middle of event'
errors on the slave.
(Bug#4053)
This is a bugfix release for the current production release family. It replaces MySQL 5.0.26.
Functionality added or changed:
This is the last version for which binary MySQL-Max distributions are available, except for RPM distributions. (For RPM distributions, the last version is 5.0.37.)
Bugs fixed:
MySQL 5.0.26 introduced an ABI incompatibility, which this release reverts. Programs compiled against 5.0.26 are not compatible with any other version and must be recompiled. (Bug#23427)