Dear MySQL users,
We are proud to present to you the MySQL Server 5.1.26-rc release,
a new "release candidate" version of the popular open source database.
MySQL 5.1.26-rc is slated to be the last release candidate before we
declare MySQL 5.1 as "production ready" (GA). We therefore appreciate
any feedback and community testing of this release, to ensure that we
have ironed out any remaining critical issues.
This one is still labeled a "candidate" release, so the usual hints
about a pre-production release apply.
For production level systems using 5.0, we would like to direct your
attention to the product description of MySQL Enterprise at:
http://mysql.com/products/enterprise/
The MySQL 5.1.26-rc 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.
Please also note that some of our mirrors are currently experiencing
problems that may result in serving corrupted files. We are working with
the mirror maintainers to resolve this.
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 since the latest released version of MySQL 5.1, the
MySQL 5.1.25-rc release. It can also be viewed online at
http://dev.mysql.com/doc/refman/5.1/en/news-5-1-26.html
Sincerely,
Jörg Brühe
The MySQL build team at Sun Microsystems
=======================================================================
News from the Changelog:
Functionality added or changed:
* The FEDERATED storage engine now is disabled by default in
binary distributions. The engine is still available and can be
enabled by starting the server with the --federated option.
(Bug#37069: http://bugs.mysql.com/37069)
Bugs fixed:
* An empty bit-string literal (b'') caused a server crash.
Now the expression is accepted as an empty binary string
(which has a value of 0 in numeric context).
(Bug#35658: http://bugs.mysql.com/35658)
* Replication: Performing an insert on a table having an
AUTO_INCREMENT column and an INSERT trigger that was being
replicated from a master running MySQL 5.0 or any version of
MySQL 5.1 up to and including MySQL 5.1.11 to a slave running
MySQL 5.1.12 or later caused the replication slave to crash.
(Bug#36443: http://bugs.mysql.com/36443)
See also Bug#33029: http://bugs.mysql.com/33029
* Row-based replication broke for utf8 CHAR columns longer than
85 characters. (Bug#37426: http://bugs.mysql.com/37426)
* NOT IN subqueries that selected MIN() or MAX() values but
produced an empty result could cause a server crash.
(Bug#37004: http://bugs.mysql.com/37004)
* ha_innodb.so was incorrectly installed in the lib/mysql
directory rather than in lib/mysql/plugin.
(Bug#36434: http://bugs.mysql.com/36434)
* The code for detecting a byte order mark (BOM) caused mysql to
crash for empty input.
(Bug#35480: http://bugs.mysql.com/35480)
* The mysql client incorrectly parsed statements containing the
word "delimiter" in mid-statement.
(Bug#33812: http://bugs.mysql.com/33812)
Jörg Brühe
--
Joerg Bruehe, MySQL Build Team, [EMAIL PROTECTED]
Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten
Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Dr. Roland Boemer
Vorsitzender des Aufsichtsrates: Martin Haering Muenchen: HRB161028
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
