Replication: The way the time zone information is stored in the binary log was changed, so that it is now possible to have a replication master and slave running with different global time zones. A disadvantage is that replication from 5.0.4 masters to pre-5.0.4 slaves is impossible.
ENGINE=MyISAM table option when
mysql.proc table in
mysql_create_system_tables script to make
sure the table is created as a
even if the default storage engine has been changed.
SHOW CREATE TABLE for an
INFORMATION_SCHEMA table no longer prints a
MAX_ROWS value because the value has no
DEFAULT values for
CREATE TABLE now generate errors.
Support for MIT-pthreads was removed.
compilation option to configure. (Previously
it was necessary to pass
-DBIG_TABLES to the
compiler manually to enable large table support.) See
MySQL Source-Configuration Options, for details.
New configuration directives
!includedir implemented for including option
files and searching directories for option files. See
Using Option Files, for usage.
INFORMATION_SCHEMA could be
exposed to a user with insufficient privileges.
The commit count cache for
not properly invalidated when deleting a record using a cursor.
If, on a replication master, a
INFILE operation was interrupted (by, for example, an
integrity constraint violation or killed connection), the slave
INFILE entirely, thus missing changes if this command
permanently inserted or updated table records before being
mysql.server no longer uses nonportable alias command or LSB functions. (Bug #9852)
A server installed as a Windows service and started with
--shared-memory could not be
BIT column failed if
the binary client/server protocol was used.
PRIMARY KEY on a table having a
BIT column caused the server to
SET columns in
InnoDB tables were treated incorrectly as
character strings. This bug did not manifest itself with
latin1 collations, but it caused malfunction
utf8. Old tables will continue to work.
In new tables,
SET will be stored internally as
An error in division of floating point numbers could cause nine
000000000) to be inserted in the
middle of the quotient.
Some user variables were not being handled with “implicit” coercibility. (Bug #9425)
Multiple executions of a prepared statement involving a join of
INFORMATION_SCHEMA table with another
table could lead to a crash of the server.
InnoDB test suite failure was caused by a
locking conflict between two server instances at server shutdown
or startup. This conflict on advisory locks appears to be the
result of a bug in the operating system; these locks should be
released when the files are closed, but somehow that does not
always happen immediately in Linux.
Permit extra HKSCS and cp950 characters (
extension characters) to be accepted in
The value of the
CHARACTER_OCTET_LENGTH columns of the
NULL for numeric columns, but were
INFORMATION_SCHEMA tables had an implicit
upper limit for the number of rows. As a result, not all data
could be returned for some queries.
InnoDB stored the 'position' of a row wrong
in a column prefix primary key index; this could cause MySQL to
ERROR 1032: Can't find record … in
an update of the primary key, and also some
ORDER BY sometimes caused incorrect sorting
ucs2_spanish2_ci collations no longer
r equal to
If you upgrade to this version from an earlier version, you
should rebuild the indexes of any affected tables.
GROUP BY on a decimal expression caused
the server to crash.
mysqldump dumped core when invoked with
and a nonexistent table name.
mysql_stmt_close() for a
single-row result set could cause the server to crash.
system variable to 0 resulted in a setting of 1.
The use of
XOR together with
ISNULL() erroneously resulted in some outer joins
being converted to inner joins by the optimizer.
Two prepared statements for single-row result sets being open simultaneously caused a Commands out of sync error error. (Bug #8880)
Extraneous comparisons between
NULL values in
indexed columns were performed by the optimzer for operators
= that are never true for
In the client/server protocol for prepared statements, reconnection failed when the connection was killed with reconnection enabled. (Bug #8866)
In prepared statements, subqueries containing parameters were
erroneously treated as
tables during preparation, resulting in a server crash.
Do not try to space-pad
References: This bug was introduced by Bug #7350.
The warning message from
GROUP_CONCAT() did not always
indicate the correct number of lines.
InnoDB: SQL statements were not rolled back
Too many rows were returned from queries that combined
SQL_CALC_FOUND_ROWS was given.
Incorrect results were returned from queries that combined
GROUP BY , and
tee command could sometimes cause the
mysql client to crash.
Added linking with
libsupc++ on Fedora Core 3
to get language support functions.
Unions between binary and nonbinary columns failed due to a collation coercibility problem. (Bug #6519)
TRADITIONAL SQL mode should
prevent inserts where a column with no default value is omitted
or set to a value of
DEFAULT; however, in
some cases, this restriction was not enforced.
An error now occurs if you try to insert an invalid value using
a stored procedure in
STR_TO_DATE() now produces errors
in strict mode (and warnings otherwise) when given an illegal
ALTER TABLE now fails in
STRICT mode if the alteration generates