Dear MySQL users,
We are proud to present to you the MySQL Server 5.1.14 Beta
release, a new Beta version of the popular open source database.
Bear in mind that this is a beta release, and as any other pre-production
release, caution should be taken when installing on production level
systems or systems with critical data. For production level systems
using 5.0, pay attention to the product description of MySQL Enterprise
at:
http://mysql.com/products/enterprise/
The MySQL 5.1.14 Beta release is now available in source and binary form
for a number of platforms from our download pages at
http://dev.mysql.com/downloads/
and mirror sites. Note that not all mirror sites may be up to date at
this point in time, so if you can't find this version on some mirror,
please try again later or choose another download site.
We welcome and appreciate your feedback, bug reports, bug fixes,
patches etc.:
http://forge.mysql.com/wiki/Contributing
The following section lists the changes from version to version in the
MySQL source code through the latest released version of MySQL 5.1, the
MySQL 5.1.12-beta. It can also be viewed online at
http://dev.mysql.com/doc/refman/5.1/en/news-5-1-14.html
NOTE: Embedded is only enabled in the rpm packages, due to problems
on other platforms.
Functionality added or changed:
* Incompatible change: Previously, you could create a
user-defined function (UDF) or stored function with the same
name as a built-in function, but could not invoke the UDF. Now
an error occurs if you try to create such a UDF. The server
also now generates a warning if you create a stored function
with the same name as a built-in function. It is not
considered an error to create a stored function with the same
name as a built-in function because you can invoke the
function using db_name.func_name() syntax. However, the server
now generates a warning in this case.
(Bug#22619: http://bugs.mysql.com/22619)
See Section 9.2.4, Function Name Resolution, for the rules
describing how the server interprets references to different
kinds of functions.
* NDB Cluster (Replication): ndb_restore now creates the
apply_status and schema tables if they do not already exist on
the slave cluster. (Bug#14612: http://bugs.mysql.com/14612)
* NDB Cluster: Backup messages are now printed to the Cluster
log. (Bug#24544: http://bugs.mysql.com/24544)
* NDB Cluster: The error message Management server closed
connection, when recorded in the MySQL error log, now includes
a timestamp indicating when the error took place.
(Bug#21519: http://bugs.mysql.com/21519)
* NDB Cluster (Disk Data): The output of mysqldump now includes
by default all tablespace and logfile group definitions used
by any tables or databases that are dumped.
(Bug#20839: http://bugs.mysql.com/20839)
Note: The working of the --all-tablespaces or -Y option for
mysqldump remains unaffected by this change.
* Direct and indirect usage of stored routines, user-defined
functions, and table references is now prohibited in CREATE
EVENT and ALTER EVENT statements.
(Bug#22830: http://bugs.mysql.com/22830)
See Section 20.2.1, CREATE EVENT Syntax, and Section 20.2.2,
ALTER EVENT Syntax, for more specific information.
* DROP TRIGGER now supports an IF EXISTS clause.
(Bug#23703: http://bugs.mysql.com/23703)
Bugs fixed:
* NDB Cluster (Replication): If errors occurred during purging
of the binary logs, extraneous rows could remain left in the
binlog_index table. (Bug#15021: http://bugs.mysql.com/15021)
* NDB Cluster (Disk Data): ndb_restore could sometimes fail when
attempting to restore Disk Data tables due to data node
failure caused by accessing unitialized memory.
(Bug#24331: http://bugs.mysql.com/24331)
* NDB Cluster (Disk Data): Excessive fragmentation of Disk Data
files (including log files and data files) could occur during
the course of normal use.
(Bug#24143: http://bugs.mysql.com/24143)
* NDB Cluster (Disk Data): It was possible to execute a
statement for creating a Disk Data table that referred to a
nonexistent tablespace, in which case the table was an
in-memory NDB table. Such a statement instead now fails with
an appropriate error message.
(Bug#23576: http://bugs.mysql.com/23576)
* NDB Cluster (Disk Data): Under some circumstances, a DELETE
from a Disk Data table could cause mysqld to crash.
(Bug#23542: http://bugs.mysql.com/23542)
* NDB Cluster (Cluster APIs): Using BIT values with any of the
comparison methods of the NdbScanFilter class caused the
cluster's data nodes to fail.
(Bug#24503: http://bugs.mysql.com/24503)
* NDB Cluster: A value equal to or greater than the allowed
maximum for LongMessageBuffer caused all data nodes to crash.
(Bug#22547: http://bugs.mysql.com/22547)
* NDB Cluster: The failure of a data node failure during a
schema operation could lead to additional node
