MySQL 5.0.83 がリリースされました。
これは MySQL 5.0 シリーズの最新バージョンです。MySQL Enterprise Server と MySQL Community Server のバージョン番号が統合(share)されてから２度目のリリースです。

前回の 5.0.82のリリースからわずか２週間ほど。驚くべき早さですね。
ソースコードを見たところ、日本MySQLユーザ会のMLでの質問に端を発した、「cp932 の UPPER() 化け問題」の修正はまだこのバージョンには取り入れられていないようです。

　ダウンロードはこちら：
http://dev.mysql.com/downloads/mysql/5.0.html


---------------------
　以下、チェンジログ



■機能の追加と変更(5.0.83):
* 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)


■バグ修正(5.0.83):
* 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)