This is a Service Pack release of the MySQL Enterprise Server 5.0.
This section documents all changes and bug fixes that have been applied since the last MySQL Enterprise Server release (5.0.30).
Functionality Added or Changed
InnoDB rolls back only the last statement on
a transaction timeout. A new option,
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).
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.
Replication: A stored procedure, executed from a connection using a binary character set, and which wrote multi-byte data, would write incorrectly escaped entries to the binary log. This caused syntax errors, and caused replication to fail. (Bug #23619, Bug #24492)
Several string functions could return incorrect results when given very large length arguments. (Bug #10963)
statements could crash the mysql client.
InnoDB crashed while performing XA recovery
of prepared transactions.
CONCURRENT did not work correctly for
The size of
MEMORY tables and internal
temporary tables was limited to 4GB on 64-bit Windows systems.
The loose index scan optimization for
MAX was not applied within other queries,
TABLE ... SELECT ...,
INSERT ... SELECT
..., or in the
FROM clauses of
Accuracy was improved for comparisons between
DECIMAL columns and numbers
represented as strings.