Functionality added or changed:
MySQL Cluster:
Improved handling of the configuration variables
NoOfPagesToDiskDuringRestartACC
,
NoOfPagesToDiskAfterRestartACC
,
NoOfPagesToDiskDuringRestartTUP
, and
NoOfPagesToDiskAfterRestartTUP
should result
in noticeably faster startup times for MySQL Cluster.
(Bug#12149)
Added an optimization that avoids key access with
NULL
keys for the
ref
method when used in outer
joins.
(Bug#12144)
Added support of where clause for queries with FROM
DUAL
.
(Bug#11745)
Maximum size of stored procedures increased from 64k to 4Gb. (Bug#11602)
SHOW CHARACTER SET
and
INFORMATION_SCHEMA
now properly report the
Latin1
character set as
cp1252
.
(Bug#11216)
Added new
ER_STACK_OVERRUN_NEED_MORE
error
message to indicate that, while the stack is not completely
full, more stack space is required.
(Bug#11213)
mysqldump now dumps triggers for each dumped
table. This can be suppressed with the
--skip-triggers
option.
(Bug#10431)
Added error message for users who attempt CREATE TABLE
... LIKE
and specify a nontable in the
LIKE
clause.
(Bug#6859)
Security improvement: Applied a patch that addresses a potential
zlib
data vulnerability that could result in
an application crash. This only affects the binaries for
platforms that are linked statically against the bundled zlib
(most notably Microsoft Windows and HP-UX).
(CVE-2005-1849)
Bugs fixed:
MySQL Cluster: The MySQL Cluster backup log was invalid where the number of Cluster nodes was not equal to a power of 2. (Bug#11675)
Creation of the mysql
group account failed
during the RPM installation.
(Bug#12348)
Updated dependency list for RPM builds to include missing
dependencies such as useradd
and
groupadd
.
(Bug#12233)
A delayed insert that would duplicate an existing record crashed the server instead. (Bug#12226)
When DROP DATABASE
was called
concurrently with a DROP TABLE
of
any table, the MySQL Server crashed.
(Bug#12212)
InnoDB
: True
VARCHAR
: Return
NULL
columns in the format expected by MySQL.
(Bug#12186)
Information about a trigger was not displayed in the output of
SELECT ... FROM INFORMATION_SCHEMA.TRIGGERS
when the selected database was
INFORMATION_SCHEMA
, prior to the trigger's
first invocation.
(Bug#12127)
InnoDB
: Do not flush after each write, not
even before setting up the doublewrite buffer. Flushing can be
extremely slow on some systems.
(Bug#12125)
Two threads could potentially initialize different characters sets and overwrite each other. (Bug#12109)
big5
strings were not being stored in
FULLTEXT
index.
(Bug#12075)
Character data truncated when GBK characters
0xA3A0
and 0xA1
are
present.
(Bug#11987)
ALTER TABLE
when
sql_mode = 'TRADITIONAL'
gave rise to an
invalid error message.
(Bug#11964)
Issuing successive FLUSH
TABLES WITH READ LOCK
would cause the
mysql
client to hang.
(Bug#11934)
mysql_install_db
used static
localhost
value in
GRANT
tables even when server
host name is not localhost
, such as
localhost.localdomain
. This change is applied
to version 5.0.10b on Windows.
(Bug#11822)
Comparisons like SELECT "A\\" LIKE "A\\";
fail when using SET NAMES utf8;
.
(Bug#11754)
Attempting to repair a table having a full-text index on a
column containing words whose length exceeded 21 characters and
where myisam_repair_threads
was
greater than 1 would crash the server.
(Bug#11684)
When used in a SELECT
query
against a view, the
GROUP_CONCAT()
function returned
only a single row.
(Bug#11412)
Multiplying ABS()
output by a
negative number would return incorrect results.
(Bug#11402)
The LPAD()
and
RPAD()
functions returned the
wrong length to
mysql_fetch_fields()
.
(Bug#11311)
A UNIQUE VARCHAR
column would be
mis-identified as MUL
in table descriptions.
(Bug#11227)
DDL statements are now allowed in stored procedures if the
procedure is not invoked from a stored function or a trigger.
This fix also resolves a problem where a
TEMPORARY
statement created by one stored
routine was inaccessible to another routine invoked during the
same connection.
(Bug#11126)
Calling the C API function
mysql_stmt_fetch()
after all
rows of a result set were exhausted would return an error
instead of MYSQL_NO_DATA
.
(Bug#11037)
SELECT @@local...
returned
@@session...
in the column header.
(Bug#10724)
Incorrect error message displayed if user attempted to create a
table in a nonexisting database using CREATE
syntax.
(Bug#10407)database_name
.table_name
Unsigned LONG
system variables may return
incorrect value when retrieved with a
SELECT
for certain values.
(Bug#10351)
GROUP_CONCAT()
sometimes returned
a result with a different collation from that of its arguments.
(Bug#10201)
Prepared statements were not being written to the Slow Query log. (Bug#9968)
The value of max_connections_per_hour
was
capped by the unrelated max_user_connections
setting.
(Bug#9947)
In stored procedures, a cursor that fetched an empty string into
a variable would set the variable to NULL
instead.
(Bug#8692)
Added checks to prevent error when allocating memory when there was insufficient memory available. (Bug#7003)
Multiple SELECT SQL_CACHE
queries in a stored
procedure causes error and client hang.
(Bug#6897)
A trigger dependent on a feature of one
sql_mode
setting would cause an
error when invoked after the
sql_mode
was changed.
(Bug#5891)
User Comments
Add your own comment.