Table of Contents
This section does not apply to MySQL Community Server users.
This appendix lists the changes from version to version in MySQL Enterprise, including MySQL Enterprise Server. Releases in MySQL Enterprise Server are divided into the following release packs:
Rapid Update Service Packs are issued once a month and incorporate all the bug fixes and security updates introduced since the previous MySQL Enterprise Server release. A single Service Pack can be used to update MySQL Enterprise Server; it is not necessary to install intervening service packs to bring your system up to date.
Quarterly Service Packs are issued each quarter and incorporate all the bug fixes and security updates introduced since the previous MySQL Enterprise Server release. A single Service Pack can be used to update MySQL Enterprise Server; it is not necessary to install intervening service packs to bring your system up to date.
Hot-fix releases incorporate fixes for bugs that caused significant issues that are not released as part of a Service Pack.
The Release Notes are updated as new bugs 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.
This section does not apply to MySQL Community Server users.
This section documents all changes and bug fixes made available through the first MySQL Enterprise Server release (5.0.28), through hot-fixes, and through service packs.
This is the first 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.28).
Bugs fixed:
The optimizer failed to use equality propagation for
BETWEEN and IN
predicates with string arguments. (Bug#22753)
The optimizer used the ref join type rather
than eq_ref for a simple join on strings.
(Bug#22367)
The WITH CHECK OPTION for a view failed to
prevent storing invalid column values for
UPDATE statements. (Bug#16813)
A literal string in a GROUP BY clause could
be interpreted as a column name. (Bug#14019)
Some queries that used MAX() and
GROUP BY could incorrectly return an empty
result. (Bug#22342)
WITH ROLLUP could group unequal values.
(Bug#20825)
Use of a subquery that invoked a function in the column list of the outer query resulted in a memory leak. (Bug#21798)
LIKE searches failed for indexed
utf8 character columns. (Bug#20471)
FLUSH INSTANCES in Instance Manager
triggered an assertion failure. (Bug#19368)
ALTER TABLE was not able to rename a view.
(Bug#14959)
Entries in the slow query log could have an incorrect
Rows_examined value. (Bug#12240)
Insufficient memory
(myisam_sort_buffer_size) could cause a
server crash for several operations: repair table, create
index by sort, repair by sort, parallel repair, bulk insert.
(Bug#23175)
OPTIMIZE TABLE with
myisam_repair_threads > 1 could result
in table corruption. (Bug#8283)
Selecting from a MERGE table could result
in a server crash if the underlying tables had fewer indexes
than the MERGE table itself. (Bug#22937)
For multiple-table UPDATE statements,
storage engines were not notified of duplicate-key errors.
(Bug#21381)
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)
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)
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)
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)
SHOW VARIABLES truncated the
Value field to 256 characters. (Bug#20862)
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)
Instance Manager had a race condition involving mysqld PID file removal. (Bug#22379)
It was possible for a stored routine with a
non-latin1 name to cause a stack overrun.
(Bug#21311)
This is the first MySQL Enterprise Server release, following the last Community Server release (5.0.27).
Bugs fixed: