MySQL Community Server 5.0.83 has been released

Dear MySQL users,

MySQL Community Server 5.0.83, a new version of the popular Open Source
Database Management System, has been released. This and future releases
in the MySQL Community Server 5.0 series share version numbers with
their MySQL Enterprise Server counterparts.

The release is now available in source and binary form for a number of
platforms from our download pages at

http://dev.mysql.com/downloads/

and mirror sites. Note that not all mirror sites may be up to date at
this point in time, so if you can't find this version on some mirror,
please try again later or choose another download site.

We welcome and appreciate your feedback, bug reports, bug fixes,
patches etc.:

http://forge.mysql.com/wiki/Contributing

Please note that we have dropped support for AIX 5.2 as of April 30th
as the platform has reached vendor EOL, and this is the second release
of MySQL 5.0 which does not include binaries for that platform.

http://dev.mysql.com/doc/refman/5.0/en/releasenotes-cs-5-0-8 3.html

This section documents all changes and bugfixes that have been
applied since the last MySQL Community Server release (5.0.82).
If you would like to receive more fine-grained and personalized
update alerts about fixes that are relevant to the version and
features you use, please consider subscribing to MySQL Enterprise
(a commercial MySQL offering). For more details please see
http://www.mysql.com/products/enterprise/advisors.html.

Functionality added or changed:

* The time zone tables for Windows available at
http://dev.mysql.com/downloads/timezones.html have been
updated. (Bug#39923: http://bugs.mysql.com/39923)

Bugs fixed:

* Replication: When stopping and restarting the slave while it
was replicating temporary tables, the slave server could crash
or raise an assertion failure. This was due to the fact that,
although temporary tables were saved between slave thread
restarts, the reference to the thread being used
(table->in_use) was not being properly updated when
restarting, continuing to reference the old thread instead of
the new one. This issue affected statement-based replication
only. (Bug#41725: http://bugs.mysql.com/41725)

* UNCOMPRESSED_LENGTH() returned a garbage result when passed a
string shorter than 5 bytes. Now UNCOMPRESSED_LENGTH() returns
NULL and generates a warning.
(Bug#44796: http://bugs.mysql.com/44796)

* Several Valgrind warnings were silenced.
(Bug#44774: http://bugs.mysql.com/44774,
Bug#44792: http://bugs.mysql.com/44792)

* Incorrect time was reported at the end of mysqldump output.
(Bug#44424: http://bugs.mysql.com/44424)

* EXPLAIN EXTENDED could crash for UNION queries in which the
last SELECT was not parenthesized and included an ORDER BY
clause. (Bug#43612: http://bugs.mysql.com/43612)

* SELECT ... INTO @var could produce values different from
SELECT ... without the INTO clause.
(Bug#42009: http://bugs.mysql.com/42009)

* Using --hexdump together with --read-from-remote-server caused
mysqlbinlog to crash. (Bug#41943: http://bugs.mysql.com/41943)

* For views created with a column list clause, column aliases
were not substituted when selecting through the view using a
HAVING clause. (Bug#40825: http://bugs.mysql.com/40825)

* A multiple-table DELETE involving a table self-join could
cause a server crash. (Bug#39918: http://bugs.mysql.com/39918)

* Creating an InnoDB table with a comment containing a '#'
character caused foreign key constraints to be omitted.
(Bug#39793: http://bugs.mysql.com/39793)

* The mysql option --ignore-spaces was nonfunctional.
(Bug#39101: http://bugs.mysql.com/39101)

* If a query was such as to produce the error 1054 Unknown
column '...' in 'field list', using EXPLAIN EXTENDED with the
query could cause a server crash.
(Bug#37362: http://bugs.mysql.com/37362)

Thanks,
Hery

Hery Ramilison, MySQL Release Engineer
Database Group, Sun Microsystem Inc.


--
MySQL Announce Mailing List
For list archives: http://lists.mysql.com/announce
To unsubscribe: http://lists.mysql.com/announce?unsub=gcdma-announce@m.gmane .org