Fixed a bug: If you created a column prefix secondary index
and updated it so that the last characters in the column
prefix were spaces, InnoDB
would assert in
row0upd.c
, line 713. The same assertion
failed if you updated a column in an ordinary secondary index
so that the new value was alphabetically equivalent, but had a
different length. This could happen, for example, in the UTF8
character set if you updated a letter to its accented or
umlaut form.
Fixed a bug: InnoDB
could think that a
secondary index record was not locked though it had been
updated to an alphabetically equivalent value, for example,
'abc' -> 'aBc'.
Fixed a bug: If you updated a secondary index column to an
alphabetically equivalent value, and rolled back your update,
InnoDB
failed to restore the field in the
secondary index to its original value.
There are still several outstanding noncritical bugs reported in the MySQL bugs database. Their fixing has been delayed, because resources were allocated to the 4.1.1 release.
User Comments
Add your own comment.