Fixed problem in alarm handling that could cause problems when getting a packet that is too large.
Fixed problem when installing MySQL as a service on Windows
when one gave 2 arguments (option file group name and
service name) to
kill pid-of-mysqld to work on Mac
SHOW TABLE STATUS displayed incorrect
Row_format value for tables that have
been compressed with
SHOW VARIABLES LIKE
'innodb_data_file_path' displayed only the name of
the first datafile. (Bug#468)
Fixed security problem where
didn't allow one to
UPDATE rows in a
table even if one had a global
privilege and a database
Fixed a security problem with
wildcarded select list, when user only had partial column
SELECT privileges on the table.
Fixed unlikely problem in optimizing
WHERE clause with a constant expression
such as in
WHERE 1 AND (a=1 AND b=1).
Fixed problem on IA-64 with timestamps that caused
mysqlbinlog to fail.
The default option for
changed from 0 to 1 to make
ACID by default. See 項7.5.3. 「InnoDB 起動オプション」.
Fixed problem with too many allocated alarms on slave when connecting to master many times (normally not a very critical error).
Fixed a bug in replication of temporary tables. (Bug#183)
Fixed 64-bit bug that affected at least AMD hammer systems.
Fixed a bug when doing
LOAD DATA INFILE
IGNORE: When reading the binary log,
mysqlbinlog and the replication code read
REPLACE instead of
IGNORE. This could make the slave's table
become different from the master's table. (Bug#218)
Fixed overflow bug in
MyISAM when a row
is inserted into a table with a large number of columns and
at least one
BLOB/TEXT column. Bug was
caused by incorrect calculation of the needed buffer to pack
The binary log was not locked during
table_name statements, which could cause an
to be written to the log before the
Fixed rare bug in
InnoDB tables where one row could be
updated multiple times.
Produce an error for empty table and column names.
PROCEDURE ANALYSE() to report
DATE instead of
PROCEDURE ANALYSE(#) to restrict
the number of values in an
ENUM column to
# also for string values.
mysqldump no longer silently deletes the
binary logs when invoked with the
--first-slave option; while this behavior
was convenient for some users, others may suffer from it.
Now one has to explicitly ask for binary logs to be deleted
by using the new
Fixed a bug in
mysqldump when it was
invoked with the
--master-data option: The
CHANGE MASTER TO statements that were
appended to the SQL dump had incorrect coordinates. (Bug#159)
This is a translation of the MySQL Reference Manual that can be found at dev.mysql.com. The original Reference Manual is in English, and this translation is not necessarily as up to date as the English version.