Functionality added or changed:
It is now possible to build the server such that
MyISAM tables can support up to 128 keys
rather than the standard 64. This can be done by configuring the
build using the option
N≤128 is the
maximum number of indexes to permit per table.
--bdb-log-direct server options.
Added the mysqlslap program, which is designed to emulate client load for a MySQL server and report the timing of each stage. It works as if multiple clients are accessing the server.
BDB library was upgraded to
cp1250_polish_ci collation for the
cp1250 character set.
selecting from a table having the primary key on a
VARCHAR column caused a forced
shutdown of the cluster.
(Bug#15240, Bug#15682, Bug#14828, Bug#15517)
Server could not be built on default Debian systems with BDB enabled. (Bug#15734)
It was not possible to reorganize a partition reusing a discarded partition name.
Now, for example, you can create a table such as this one:
CREATE TABLE t1 (a INT) PARTITION BY RANGE (a) ( PARTITION p0 VALUES LESS THAN (10), PARTITION p1 VALUES LESS THAN (20), PARTITION p2 VALUES LESS THAN MAXVALUE );
and then repartition it as shown here:
ALTER TABLE t1 REORGANIZE PARTITION p2 INTO ( PARTITION p2 VALUES LESS THAN (30) );
Previously, attempting to do so would produce the error All partitions must have unique names in the table . (Bug#15521)
BLACKHOLE storage engine did not handle
transactions properly: Rolled-back transactions were written to
the binary log. Now they ae not.
A left join on a column that having a
value could cause the server to crash.
Selecting from a view processed with the temptable algorithm caused a server crash if the query cache was enabled. (Bug#15119)
Creating a view that referenced a stored function that selected from a view caused a crash upon selection from the view. (Bug#15096)
Multiple-table update operations were counting updates and not updated rows. As a result, if a row had several updates it was counted several times for the “rows matched” value but updated only once. (Bug#15028)
ANALYZE TABLE did not properly
update table statistics for a
FULLTEXT index containing stopwords,
so a subsequent
would not recognize the table as having already been analyzed.
Creating a view within a stored procedure could result in an out of memory error or a server crash. (Bug#14885)
The maximum value of
MAX_ROWS was handled
incorrectly on 64-bit systems.
Attempts to assign
NULL to a
NULL column in strict mode now result in a message of
Column ', rather than
col_name' cannot be
Column set to default
value; NULL supplied to NOT NULL column
col_name' at row