MySQL Lists are EOL. Please join:

List:Announcements« Previous MessageNext Message »
From:Brian Pontz Date:April 26 2006 7:44am
Subject:MySQL 5.1.9-beta has been released
View as plain text  

MySQL 5.1.9-beta, a new version of the popular Open Source Database 
Management System, has been released. The Community Edition is now
available in source and binary form for a number of platforms from our
download pages at and mirror sites.

Note that not all mirror sites may be up to date at this point in time -
if you can't find this version on some mirror, please try again later or
choose another download site.

This is a new Beta development release, fixing recently discovered bugs.

NOTE: This Beta release, as any other pre-production release,
should not be installed on production-level systems or systems
with critical data. It is good practice to back up your data
before installing any new version of software. Although MySQL has
worked very hard to ensure a high level of quality, protect your
data by making a backup as you would for any software beta
release. Please refer to our bug database at for
more details about the individual bugs fixed in this version.

Please refer to our bug database at for more
details about the individual bugs fixed in this version.

This section documents all changes and bug fixes that have been applied
since the last official MySQL release. If you would like to receive
more fine-grained and personalised update alerts about fixes that are
relevant to the version and features you use, please consider
subscribing to MySQL Network (a commercial MySQL offering). For more
details please see

We welcome and appreciate your feedback!

   Functionality added or changed:
     * SHOW PLUGIN was renamed to SHOW PLUGINS. SHOW PLUGIN now is
       deprecated and generates a warning.
     * mysqld_safe no longer checks for a mysqld-max binary. Instead,
       mysqld_safe nows checks only for the standard mysqld server
       unless another server binary is specified explicitly.
     * For partitioned tables, the output of SHOW TABLE STATUS now
       shows in the Engine column the name of the storage engine used
       by all partitions for the table; in the Create_options column,
       the output now shows "partitioned" for a partitioned table. This
       change also affects the values shown in the corresponding
       columns of the INFORMATION_SCHEMA.TABLES table.
     * The NDBCluster storage engine now supports CREATE TABLE
       statements of arbitrary length. (Previously, CREATE TABLE
       statements for MySQL Cluster tables could contain a maximum of
       4096 characters only.)
     * Large file support was re-enabled for the MySQL server binary
       for the AIX 5.2 platform.

   Bugs fixed:
     * NDB Cluster: BLOB columns did not work correctly with
       user-partitioned NDB tables.
     * mysql_config returned incorrect libraries on x86_64 systems.
     * mysql_reconnect() sent a SET NAMES statement to the server,
       even for pre-4.1 servers that do not understand the statement.
     * COUNT(*) on a MyISAM table could return different results for
       the base table and a view on the base table.
     * For mysql.server, if the basedir option was specified after
       datadir in an option file, the setting for datadir was ignored
       and assumed to be located under basedir.
     * For full-text searches in boolean mode, and when a full-text
       parser plugin was used, a MYSQL_FTPARSER_PARAM::ftparser_state
       could have been corrupted by recursive calls to the plugin.
     * EXTRACT(QUARTER FROM date) returned unexpected results.
     * TRUNCATE did not reset the AUTO_INCREMENT counter for MyISAM
       tables when issued inside a stored procedure.
       Note: This bug did not affect InnoDB tables. Also, TRUNCATE
       does not reset the AUTO_INCREMENT counter for NDBCluster
       tables regardless of when it is called (see
     * The server was always built as though
       --with-extra-charsets=complex had been specified.
     * Partition pruning did not work properly for some kinds of
       partitioning and subpartitioning, with certain WHERE clauses.
       (Partitions and subpartitions that should have been marked as
       used were not so marked.) The error could manifest as
       incorrect content in EXPLAIN PARTITIONS output as well as
       missing rows in the results of affected queries.
     * NDB Cluster: An unitialised internal variable could lead to
       unexpected results. (Bug#18831:
     * For tables created in a MySQL 4.1 installation upgraded to
       MySQL 5.0 and up, multiple-table updates could update only the
       first matching row. (Bug#16281:
     * Complex queries with nested joins could cause a server crash.
     * A query against a partitioned table using WHERE col IS NULL
       could produce incorrect results given the following
          + The table had partitions and subpartitions
          + The partitioning function depended on a single column col
            of one of the MySQL integer types
          + The partitioning function was not monotonically
       The same issue could cause the server to crash when run in
       debug mode. (Bug#18659:
     * CAST(double AS SIGNED INT) for large double values outside the
       signed integer range truncates the result to be within range,
       but the result sometimes had the wrong sign, and no warning
       was generated. (Bug#15098:
     * MEDIUMINT columns were not handled in the same way as other
       column types by partition pruning.
       Partition pruning would sometimes use inappropriate columns in
       preforming queries.
       Both of these issues were rectified as part of the same
       bugfix. (Bug#18025:
     * Quoted values could not be used for partition option values.
     * Delimited identifiers could not be used in defining
       partitions. (Bug#13433:
     * Building the server using --with-example-storage-engine failed
       to enable the EXAMPLE storage engine in the server.
     * Triggers created in one version of the server could not be
       dropped after upgrading to a newer version.
     * Queries using WHERE ... IS NULL returned incorrect results
       from partitioned tables.
     * Partition pruning did not perform correctly with partitions on
       NULL, and could potentially crash the server.
     * If InnoDB encountered a HA_ERR_LOCK_TABLE_FULL error and
       rolled back a transaction, the transaction was still written
       to the binary log. (Bug#18283:


Brian Pontz, Senior Product Engineer
MySQL Inc., USA,

MySQL 5.1.9-beta has been releasedBrian Pontz26 Apr