Support Ending for AIX 5.2: Per the http://www.mysql.com/about/legal/lifecycle/ regarding ending support for OS versions that have reached vendor end of life, we plan to discontinue building or supporting MySQL binaries for AIX 5.2 as of April 30, 2009. This release of MySQL 5.1 (5.1.34) is the last MySQL 5.1 release with support for AIX 5.2. For more information, see the March 24, 2009 note at MySQL Product Support EOL Announcements.
Functionality Added or Changed
Important Note; Replication:
Binary logging with
--binlog-format=ROW failed when a
change to be logged included more than 251 columns. This issue
was not known to occur with mixed-format or statement-based
References: See also Bug #42914.
Assigning an invalid directory for the
--slave-load-tmpdir caused the
replication slave to crash.
mysql.procs_priv system table was not
DELAYED into a
TIMESTAMP column issued
concurrently with an insert on the same column not using
DELAYED, but applied after the other insert,
was logged using the same timestamp as generated by the other
MIXED binary logging format did not
switch to row-based mode for statements containing the
When the server SQL mode included
DATA INFILE ... INTO
failed because the
statement was read incorrectly from the binary log; a trailing
space was omitted, causing the statement to fail with a syntax
error when run on the slave.
References: See also Bug #43746.
The MySQL Instance Configuration Wizard would fail to start correctly on Windows Vista. (Bug #42386)
When running the MySQL Instance Configuration Wizard in
command-line only mode, the service name would be ignored
(effectively creating all instances with the default
MySQL service name), irrespective of the name
specified on the command line. However, the wizard would attempt
to start the service with the specified name, and would fail.
An attempt to check or repair an
ARCHIVE table that had been
subjected to a server crash returned a 144 internal error. The
data appeared to be irrecoverable.
variable to its minimum value produced spurious warnings.
my_print_default_files() functions in the C
client library were subject to a race condition in
Queries of the following form returned an empty result:
SELECT ... WHERE ... (
col) OR ... (
strings/CHARSET_INFO.txt file was not
included in source distributions.
On Windows, incorrectly specified link dependencies in
CMakeLists.txt resulted in link errors for
When MySQL was configured with the
--basedir was specified,
mysqld_safe did not use it when attempting to
help command output displayed by
mysql, the description for the
clear) command was
A dangling pointer in
could lead to client crashes.
An attempt by a user who did not have the
SUPER privilege to kill a system
thread could cause a server crash.
mysql crashed if a request for the current
database name returned an empty result, such as after the client
has executed a preceding
Passing an unknown time zone specification to
CONVERT_TZ() resulted in a memory
The use of
result in a problem for
CREATE TABLE ...
SELECT statements when the source column expressions
refer to local variables. Converting these references to
NAME_CONST() expressions can
result in column names that are different on the master and
slave servers, or names that are too long to be legal column
identifiers. A workaround is to supply aliases for columns that
refer to local variables.
Now a warning is issued in such cases that indicate possible problems. (Bug #35383)
The mysql client could misinterpret its input if a line was longer than an internal buffer. (Bug #41486)
If the value of the
variable was too long, the mysql client
displayed a truncated startup message.
Time column for
PROCESSLIST output and the value of the
TIME column of the
table now can have negative values. Previously, the column was
unsigned and negative values were displayed incorrectly as large
positive values. Negative values can occur if a thread alters
the time into the future with
SET TIMESTAMP =
or the thread is
executing on a slave and processing events from a master that
has its clock set ahead of the slave.
Restoring a mysqldump dump file containing
FEDERATED tables failed because the file
contained the data for the table. Now only the table definition
is dumped (because the data is located elsewhere).