2010年4月27日

[installer 2348] mysql-5.1.46

mysql-5.1.46 出ています。

☆ mysql-5.1.46
http://www.mysql.com/
http://dev.mysql.com/downloads/mysql/5.1.html
http://mirror.mysql-partners-jp.biz/Downloads/MySQL-5.1/mysql-5.1.46.tar.gz

C.1.1 Changes in MySQL 5.1.46 (Not yet released)

------------------------------------------------

Bugs fixed:

* *Partitioning*: Partition pruning on `RANGE' partitioned tables
did not always work correctly; the last partition partition was
not excluded if the range was beyond it (when not using
`MAXVALUE').Now the last partition is not included if the
partitioning function value is not within the range. (Bug#51830
http://bugs.mysql.com/bug.php?id=51830))

* *Partitioning*: The `insert_id' server system variable was not
reset following an insert that failed on a partitioned `MyISAM'
table having an `AUTO_INCREMENT' column. (Bug#50392
http://bugs.mysql.com/bug.php?id=50392))

* *Partitioning*: Foreign keys are not supported on partitioned
tables. However, it was possible via an *note `ALTER TABLE':
alter-table. statement to set a foreign key on a partitioned
table; it was also possible to partition a table with a single
foreign key. (Bug#50104 http://bugs.mysql.com/bug.php?id=50104))

* *Partitioning*: `GROUP BY' queries performed poorly for some
partitioned tables. This was due to the block size not being set
for partitioned tables, thus the keys per block was not correct,
which could cause such queries to be optimized incorrectly.
(Bug#48229 http://bugs.mysql.com/bug.php?id=48229)) See also
Bug#37252 http://bugs.mysql.com/bug.php?id=37252).

* *Replication*: `TRUNCATE' performed on a temporary table using the
`InnoDB' storage engine was logged even when using row-based mode.
(Bug#51251 http://bugs.mysql.com/bug.php?id=51251))

* *Replication*: When using temporary tables the binary log needs to
insert a pseudo-thread ID for threads that are using temporary
tables, each time a switch happens between two threads, both of
which are using temporary tables. However, if a thread issued a
failing statement before exit, its ID was not recorded in the
binary log, and this in turn caused the ID for the next thread
that tried to do something with a temporary table not to be logged
as well. Subsequent replays of the binary log failed with the
error `Table ... doesn't exist'. (Bug#51226
http://bugs.mysql.com/bug.php?id=51226))

* *Replication*: If the master was using `sql_mode='TRADITIONAL'',
duplicate key errors were not sent to the slave, which received
`0' rather than the expected error code. This caused replication
to fail even when such an error was expected. (Bug#51055
http://bugs.mysql.com/bug.php?id=51055))

* *Replication*: When run with the `--database' option, *note
`mysqlbinlog': mysqlbinlog. printed `ROLLBACK' statements but did
not print any corresponding *note `SAVEPOINT': savepoint.
statements. (Bug#50407 http://bugs.mysql.com/bug.php?id=50407))

* *Replication*: *note `CREATE EVENT': create-event. statements were
padded with `garbage' characters when written to the binary log,
which caused a syntax error when trying to read back from the log.
(Bug#50095 http://bugs.mysql.com/bug.php?id=50095))

* *Replication*: Column length information generated by `InnoDB' did
not match that generated by `MyISAM', which caused invalid
metadata to be written to the binary log when trying to replicate
*note `BIT': numeric-types. columns. (Bug#49618
http://bugs.mysql.com/bug.php?id=49618))

* *Replication*: The value of `Slave_IO_running' in the output of
*note `SHOW SLAVE STATUS': show-slave-status. did not distinguish
between all 3 possible states of the slave I/O thread (not
running; running but not connected; connected). Now the value
`Connecting' (rather than `No') is shown when the slave I/O thread
is running but the slave is not connected to a replication master.

The server system variable `Slave_running' also reflects this
change, and is now consistent with what is shown for
`Slave_IO_running'. (Bug#30703
http://bugs.mysql.com/bug.php?id=30703), Bug#41613
http://bugs.mysql.com/bug.php?id=41613), Bug#51089
http://bugs.mysql.com/bug.php?id=51089))

* The type inference used for view columns caused some columns in
views to be handled as the wrong type, as compared to the same
columns in base tables. *note `DATE': datetime. columns in base
tables were treated as *note `TIME': time. columns in views, and
base table *note `TIME': time. columns as view *note `DATETIME':
datetime. columns. (Bug#50918
http://bugs.mysql.com/bug.php?id=50918))

* If a stored function contained a *note `RETURN': return. statement
with an `ENUM' value in the `ucs2' character set, *note `SHOW
CREATE FUNCTION': show-create-function. and `SELECT DTD_IDENTIFIER
FROM INFORMATION_SCHEMA.ROUTINES' returned incorrect values.
(Bug#48766 http://bugs.mysql.com/bug.php?id=48766))

* *note `SHOW CREATE VIEW': show-create-view. returned invalid SQL
if the definition contained a `SELECT 'STRING'' statement where
the STRING was longer than the maximum length of a column name,
due to the fact that this text was also used as an alias (in the
`AS' clause).

Because not all names retrieved from arbitrary *note `SELECT':
select. statements can be used as view column names due to length
and format restrictions, the server now checks the conformity of
automatically generated column names and rewrites according to a
predefined format any names that are not acceptable as view column
names before storing the final view definition on disk.

In such cases, the name is now rewritten as `Name_exp_POS', where
POS is the position of the column. To avoid this conversion
scheme, define explicit, valid names for view columns using the
COLUMN_LIST clause of the *note `CREATE VIEW': create-view.
statement.

As part of this fix, aliases are now generated only for top-level
statements. (Bug#40277 http://bugs.mysql.com/bug.php?id=40277))

* *note `mysqlbinlog': mysqlbinlog. had a memory leak in its
option-processing code. (Bug#38468
http://bugs.mysql.com/bug.php?id=38468))

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


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




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