Functionality added or changed:
variable that controls whether to use row-based or
statement-based binary logging. Added the
server options for binary logging control. See
Section 16.1.2, “Replication Formats”.
A new statement,
generated by mysqlbinlog to represent
row-based events in binary log files. The statement argument, a
base 64-encoded string, is decoded by the server to determine
the data change indicated by the corresponding event.
options for mysqlslap.
is enabled or if the transaction isolation mode is
InnoDB can use
“semi-consistent” reads. This affects treatment by
UPDATE statements for rows that
are already locked by another transaction. If a row is locked,
InnoDB returns the latest committed
version to MySQL so that MySQL can determine whether the row
WHERE condition of the
UPDATE. If the row matches (must
be updated), MySQL reads the row again and this time
InnoDB either locks it or waits for
a lock on it.
See also Bug#3300.
option to mysqlbinlog to print all binary log
entries using base64 encoding. This is for debugging only. Logs
produced using this option should not be applied on production
INFORMATION_SCHEMA PLUGINS table
SHOW PLUGIN statement.
Two new Hungarian collations are included:
ucs2_hungarian_ci. These support the correct
sort order for Hungarian vowels. However, they do not support
the correct order for sorting Hungarian consonant contractions;
we expect to fix this issue in a future release.
INFORMATION_SCHEMA ENGINES table.
Added the XML functions
ExtractValue() returns the
content of a fragment of XML matching a given XPath expression.
UpdateXML() replaces the element
selected from a fragment of XML by an XPath expression supplied
by the user with a second XML fragment (also user-supplied), and
returns the modified XML. See Section 11.10, “XML Functions”.
Attempting to insert into a table partitioned by
LIST a value less than any specified in one
of the table's partition definitions resulted in a server crash.
In such cases, mysqld now returns
ERROR 1500 (HY000): Table has no partition for value
v , where
v is the out-of-range value.
Creating a trigger caused a server crash if the table or trigger database was not known because no default database had been selected. (Bug#14863)
InnoDB: Comparison of indexed
VARCHAR CHARACTER SET ucs2 COLLATE ucs2_bin
LIKE could fail.