Functionality added or changed:
Incompatible change: This
release introduced the TRIGGER
privilege.
Previously, the SUPER
privilege was needed
to create or drop triggers. Now those operations require the
TRIGGER
privilege. This is a security
improvement because you no longer need to grant users the
SUPER
privilege to enable them to create
triggers. However, the requirement that the account named in a
trigger's DEFINER
clause must have the
SUPER
privilege has changed to a
requirement for the TRIGGER
privilege. You
should check which accounts are named in the
DEFINER
clause of existing triggers and
make sure that those accounts have the
TRIGGER
privilege. Otherwise, they will
fail when activated. (Bug#9142)
Incompatible change: Due to a
change in the naming scheme for partitioning and
subpartitioning files, it is not possible for the server to
read partitioned tables created in previous MySQL versions. A
suggested workaround is (1) to create a non-partitioned table
with the same table schema using a standard CREATE
TABLE
statement (that is, with no partitioning
clauses) and then (2) to issue aSELECT INTO
to copy the data into the non-partitioned table before the
upgrade; following the upgrade, you can partition the new
table using ALTER TABLE ... PARTITION BY
...
. Alternatively, you can dump the table using
mysqldump prior to upgrading and reload it
afterwards with LOAD DATA
. In either case,
you should drop the pre-5.1.6 partitioned tables before
upgrading to 5.1.6 or later. (Bug#13437)
Important: If any partitioned
tables that were created prior to MySQL 5.1.6 are present
following an upgrade to MySQL 5.1.6 or later, it is also not
possible to read from the
INFORMATION_SCHEMA.PARTITIONS
table, nor
will you be able to drop those tables or the database or
databases in which they are located. In this event, you must:
(1) shut down mysqld; (2) manually delete
the table, partition, and (if any) subpartition files; and
then (3) restart the MySQL Server. (Bug#16695)
Incompatible change: Words
with apostrophes are now matched in a FULLTEXT search against
non-apostrophe words (for example, a search for
Jerry
will match against the term
Jerry's
). Users upgrading to this version
must issue REPAIR TABLE
statements for
tables containing FULLTEXT
indexes. (Bug#14194)
The mysqldump utility now supports an
option for dumping tablespaces. Use -Y
or
--all-tablespaces
to enable this
functionality. (Bug#16753)
Partition support is not an „engine“, but it was
included in the output of SHOW ENGINES
. Now
it is not. (Bug#14355) The
have_partition_engine
was renamed to
have_partitioning
. (Bug#16718)
ANALYZE TABLE
is now supported for
partitioned tables. (Bug#13441)
Added the --both-log-formats
and
--old-log-format
options for controlling
whether log files or log tables are used. variable.
Added the character_set_filesystem
system
variable.
Added the event_scheduler
system variable.
Added the ndb_extra_logging
system
variable.
Added the EVENTS
table to
INFORMATION_SCHEMA
.
Added the PARTITIONS
table to
INFORMATION_SCHEMA
.
The ARCHIVE
storage engine supports the
AUTO_INCREMENT
column attribute and the
AUTO_INCREMENT
table option.
Abschnitt 14.8, „Die ARCHIVE
-Speicher-Engine“.
Fixed a crash when fulltext search parser plugin returned more words than half of the length (in bytes) of the query string. (Bug#16722)
Bugs fixed:
MYSQL_OPT_RECONNECT
option was modified by
calls to the mysql_real_connect()
function. (Bug#15719)
Specifying a value for --tmptable
without a
trailing slash had unpredictable results. (Bug#15904)
Attempting to insert data into a partitioned table that used
the BLACKHOLE
storage engine caused
mysqld to crash. (Bug#14524)
Using RANGE
partitioning with a
CASE
statement as the partitioning function
would cause records to be placed in the wrong partition. (Bug#15393)
ALTER TABLE ... ADD PARTITIONS
on a table
with one partition crashed the server. (Bug#15820)
NDB Cluster returned incorrect Can't find
file
error for OS error 24, changed to Too
many open files
. (Bug#15020)
Multi-byte path names for LOAD DATA
and
SELECT ... INTO OUTFILE
caused errors. (Bug#12448)
Certain subqueries where the inner query is the result of a aggregate function would return different results on MySQL 5.0 than on MySQL 4.1. (Bug#15347)
Error message for specifying value for which no partition exists returned wrong values on certain platforms. (Bug#15910)
Certain Japanese table names were not properly saved during a
CREATE TABLE
statement. (Bug#3906)
NDB Cluster leaked disk space when performing INSERTS/DELETES in a loop. (Bug#16771)
NDB Cluster returned wrong error when tablespace on disk was full. (Bug#16738)
The DATA DIRECTORY
and INDEX
DIRECTORY
clauses of a CREATE
TABLE
statement involving partitions did not work.
(Bug#14354)
Subselect could return wrong results when records cache and grouping was involved. (Bug#15347)
In some cases the query optimizer did not properly perform multiple joins where inner joins followed left joins, resulting in corrupted result sets. (Bug#15633)
The absence of a table in the left part of a left or right join was not checked prior to name resolution, which resulted in a server crash. (Bug#15538)
NDB Cluster
: Trying to import too many
dumped tables requiring resources beyond those allocated in
the cluster configuration would cause the server to crash
instead of reporting an insufficient resources error. (Bug#16455)
NDB Cluster
(Disk Data): Tablespaces
created using parameters with relatively low values (< 10
MB) produced filesizes much smaller than expected. (Bug#16742)
NDB Cluster
: CREATE
TABLESPACE
statements were incorrectly parsed on
64-bit platforms. (INITIAL SIZE
worked, but
size
INITIAL SIZE =
failed.) (Bug#13556)
size
Trying to add more than one partition in a single
ALTER TABLE ... ADD PARTITION
statement
caused the server to crash. (Bug#16534)
Creating a partitioned table using a storage engine other than the session default storage engine caused the server to crash. (Bug#15966)
An ALTER TABLE ... PARTITION BY ...
statement did not have any effect. (Bug#15523)
NDBCluster
(Disk Data): The error message
generated by a failed ADD UNDOFILE
did not
provide any reasons for the failure. (Bug#16267)
NDBCluster
(Disk Data): DROP
LOGFILE GROUP
corrupted the cluster file system and
caused ndbd to fail when running more than
one node on the same system. (Bug#16193)
NDBCluster
: A bitfield whose offset and
length totaled 32 would crash the cluster. (Bug#16125)
NDBCluster
: Upon the completion of a scan
where a key request remained outstanding on the primary
replica and a starting node died, the scan did not terminate.
This caused incompleted error handling of the failed node.
(Bug#15908)
NDBCluster
: The
ndb_autodiscover
test failed sporadically
due to a node not being permitted to connect to the cluster.
(Bug#15619)
Using mysqldump to obtain a dump of a
partitioned table employing the NDB
storage
engine produced a non-functional table creation statement.
(Bug#13155)
SHOW CREATE TABLE
did not display the
PARTITIONS
clause for tables partitioned by
HASH
or KEY
. (Bug#14327)
Inserting a negative value into an integer column used as the
partitioning key for a table partitioned by
HASH
could cause the server to crash. (Bug#15968)
With a table partitioned by LIST
, inserting
a value which was smaller than any value shown in the
partitioning value-lists could cause the server to crash. (Bug#14365)
ALTER TABLE ... DROP PARTITION
would
truncate all DATE
column values in the
table's remaining partitions to NULL
. (Bug#13644)
ALTER TABLE ... ADD PARTITION
could crash
the server or cause an Out of memory
error in some circumstances. (Bug#13447)
The server would allow foreign keys to be declared in the definition of a partitioned table despite the fact that partitioned tables do not support foreign keys (see Abschnitt 17.4, „Beschränkungen und Grenzen der Partitionierung“). (Bug#13446)
A SELECT
from a key-partitioned table with
a multi-column key could cause the server to crash. (Bug#13445)
Issuing a TRUNCATE
statement twice in
succession on the same partitioned table would cause the
server to crash. (Bug#13442)
Using a REPLACE
statement on a partitioned
table caused the server to crash. (Bug#13440)
Using an identifier rather than a literal integer value in the
LESS THAN
clause of a range-partitioned
table could cause the server to crash and corruption of
tables. (Bug#13439)
Using ENGINE=...
within a
PARTITION
clause could cause the server to
crash. (Bug#13438)
CREATE TABLE ... LIKE
did not work if the
table whose schema was to be copied was a partitoned table.
(Bug#13435)
SHOW CREATE TABLE
did not display the
PARTITIONS
clause for tables partitioned by
HASH
or KEY
. (Bug#14327)
Certain permission management statements could create a
NULL
hostname for a user, resulting in a
server crash. (Bug#15598)
Temporary table aliasing did not work inside stored functions. (Bug#12198)
Parallel builds occasionally failed on Solaris. (Bug#16282)
Dies ist eine Übersetzung des MySQL-Referenzhandbuchs, das sich auf dev.mysql.com befindet. Das ursprüngliche Referenzhandbuch ist auf Englisch, und diese Übersetzung ist nicht notwendigerweise so aktuell wie die englische Ausgabe. Das vorliegende deutschsprachige Handbuch behandelt MySQL bis zur Version 5.1.