2009年9月30日

[installer 2084] mysql-5.0.86,

mysql-5.0.86, 5.1.39 出ています。

☆ mysql-5.0.86
http://www.mysql.com/
http://dev.mysql.com/downloads/mysql/5.0.html
ftp://ftp.iij.ad.jp/pub/db/mysql/Downloads/MySQL-5.0/mysql-5.0.86.tar.gz
http://ftp.iij.ad.jp/pub/db/mysql/Downloads/MySQL-5.0/mysql-5.0.86.tar.gz
http://mirror.mysql-partners-jp.biz/Downloads/MySQL-5.0/mysql-5.0.86.tar.gz


C.1.1 Changes in MySQL 5.0.86 (Not yet released)
------------------------------------------------

This section documents all changes and bugfixes that have been applied
since the last MySQL Enterprise Server and MySQL Community Server
release (5.0.85). 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'.

Bugs fixed:

* *Replication*: When using the `--replicate-rewrite-db' option and
the database referenced by this option on the master was the
current database when the connection to the slave was closed, any
temporary tables existing in this database were not properly
dropped. (Bug#46861 http://bugs.mysql.com/46861))

* *Replication*: In some cases, a *Note `STOP SLAVE': stop-slave.
statement could cause the replication slave to crash. This issue
was specific to MySQL on Windows or Macintosh platforms.
(Bug#45238 http://bugs.mysql.com/45238), Bug#45242
http://bugs.mysql.com/45242), Bug#45243
http://bugs.mysql.com/45243), Bug#46013
http://bugs.mysql.com/46013), Bug#46014
http://bugs.mysql.com/46014), Bug#46030
http://bugs.mysql.com/46030))

* If `--basedir' was specified, *Note `mysqld_safe': mysqld-safe.
did not use it when attempting to locate *Note
`my_print_defaults': my-print-defaults. (Bug#39326
http://bugs.mysql.com/39326))

* *Note `mysqladmin --wait ping': mysqladmin. crashed on Windows
systems. (Bug#35132 http://bugs.mysql.com/35132))

☆ mysql-5.1.39
http://www.mysql.com/
http://dev.mysql.com/downloads/mysql/5.1.html
ftp://ftp.iij.ad.jp/pub/db/mysql/Downloads/MySQL-5.1/mysql-5.1.39.tar.gz
http://ftp.iij.ad.jp/pub/db/mysql/Downloads/MySQL-5.1/mysql-5.1.39.tar.gz
http://mirror.mysql-partners-jp.biz/Downloads/MySQL-5.1/mysql-5.1.39.tar.gz

C.1.1 Changes in MySQL 5.1.39 (Not yet released)
------------------------------------------------

Bugs fixed:

* *Partitioning*: An *Note `INSERT ... SELECT': insert-select.
statement on an empty partition of a user-partitioned table failed
with `ERROR 1030 (HY000): Got error 124 from storage engine'.
(Bug#46639 http://bugs.mysql.com/46639)) See also Bug#35845
http://bugs.mysql.com/35845), Bug#44657
http://bugs.mysql.com/44657), Bug#45840
http://bugs.mysql.com/45840).

* *Partitioning*: A partitioned table having a *Note `TIMESTAMP':
datetime. column with a default value of `CURRENT_TIMESTAMP' and
this column was not defined using an `ON UPDATE' option, an *Note
`ALTER TABLE ... REORGANIZE PARTITION': alter-table. statement on
the table caused the *Note `TIMESTAMP': datetime. column value to
be set to `CURRENT_TIMESTAMP' regardless. (Bug#46478
http://bugs.mysql.com/46478))

* *Partitioning*: Attempting to access a partitioned table when
partitioning support was disabled in a MySQL server binary that
had been compiled with partitioning support caused the server to
crash. (Bug#39893 http://bugs.mysql.com/39893))

* *Partitioning*: The use of `TO_DAYS()' in the partitioning
expression led to selection failures when the column having the
date value contained invalid dates. This occurred because the
function returns `NULL' in such cases, and the partition
containing NULL values was pruned away. For example, this problem
occurred if `'2001-02-00'' was inserted into a *Note `DATE':
datetime. column of such a table, and a subsequent query on this
table used `WHERE DATE_COL < '2001-02-00'' -- while `'2001-01-01''
is less than `'2001-02-00'', `TO_DAYS('2001-02-00')' evaluates as
`NULL', and so the row containing `'2001-01-01'' was not returned.
Now, for tables using `RANGE' or `LIST' partitioning and having
`TO_DAYS()' in the partitioning expression, the `NULL' partition
is also scanned instead of being ignored.

The fix for this issue also corrects misbehavior such that a query
of the form `SELECT * FROM TABLE WHERE DATE_COL < DATE_VAL' on a
table partitioned by `RANGE' or `LIST' was handled as though the
server SQL mode included `ALLOW_INVALID_DATES' even if this was
not actually part of the server SQL mode at the time the query was
issued. (Bug#20577 http://bugs.mysql.com/20577)) See also
Bug#18198 http://bugs.mysql.com/18198), Bug#32021
http://bugs.mysql.com/32021), Bug#46362
http://bugs.mysql.com/46362).

* *Replication*: In some cases, a *Note `STOP SLAVE': stop-slave.
statement could cause the replication slave to crash. This issue
was specific to MySQL on Windows or Macintosh platforms.
(Bug#45238 http://bugs.mysql.com/45238), Bug#45242
http://bugs.mysql.com/45242), Bug#45243
http://bugs.mysql.com/45243), Bug#46013
http://bugs.mysql.com/46013), Bug#46014
http://bugs.mysql.com/46014), Bug#46030
http://bugs.mysql.com/46030))

* *Note `mysqladmin --wait ping': mysqladmin. crashed on Windows
systems. (Bug#35132 http://bugs.mysql.com/35132))

----
こがよういちろう


投稿者 xml-rpc : 2009年9月30日 10:26
役に立ちました?:
過去のフィードバック 平均:(0) 総合:(0) 投票回数:(0)
本記事へのTrackback: http://hoop.euqset.org/blog/mt-tb2006.cgi/89017
トラックバック
コメント
コメントする




画像の中に見える文字を入力してください。