gmane.comp.db.mysql.announce

MySQL Connector/Net 6.4.5 has been released!

Reggie Burnett — 2012-05-21T20:41:09

MySQL Connector/Net 6.4.5 has been released!  This is an update to our 
6.4 driver and brings several bug fixes.  It is appropriate for 
production use with MySQL server versions 5.0-5.5

It is now available in source and binary form from 
http://dev.mysql.com/downloads/connector/net/#downloads and mirror sites 
(note that not all mirror sites may be up to date at this point-if you 
can't find this version on some mirror, please try again later or choose 
another download site.)

You can read about the changes in this version at 
http://dev.mysql.com/doc/refman/5.5/en/connector-net-news-6-4-5.html

You can find our team blog at http://blogs.oracle.com/MySQLOnWindows.  
You can also post questions on our forums at http://forums.mysql.com/.

Enjoy and thanks for the support!

MySQL Workbench 5.2.40 GA Released

Alfredo Kojima — 2012-05-21T18:26:08

The MySQL Developer Tools team is announcing the next maintenance release of its flagship product, MySQL Workbench, version 5.2.40. 
This version contains more than 28 bug fixes applied over version 5.2.39

MySQL Workbench 5.2 GA

       • Data Modeling
       • Query 
       • Administration 
Please get your copy from our Download site. Sources and binary packages are available for several platforms, including Windows, Mac OS X and Linux.

http://dev.mysql.com/downloads/workbench/

Workbench Documentation can be found here.

http://dev.mysql.com/doc/workbench/en/index.html

Utilities Documentation can be found here.
http://dev.mysql.com/doc/workbench/en/mysql-utilities.html

In addition to the new Query/SQL Development and Administration modules, version 5.2 features improved stability and performance – especially in Windows, where OpenGL support has been enhanced and the UI was optimized to offer better responsiveness. This release also includes improvements to the scripting capabilities of the SQL Editor. You can read more about it in

http://wb.mysql.com/workbench/doc/

For a detailed list of resolved issues, see the change log.

http://dev.mysql.com/doc/workbench/en/wb-change-history.html


If you need any additional info or help please get in touch with us.

Post in our forums, leave comments on our blog pages or if you want to talk to us directly you can visit us on our IRC channel #workbenchonirc.freenode.net.

- The MySQL Workbench Team

MySQL Community Server 5.5.24 has been released

Joerg Bruehe — 2012-05-08T10:11:17

Dear MySQL users,


MySQL 5.5.24 is a new version of the 5.5 production release of the
world's most popular open source database. MySQL 5.5.24 is recommended
for use on production systems.

MySQL 5.5 includes several high-impact enhancements to improve the
performance and scalability of the MySQL Database, taking advantage of
the latest multi-CPU and multi-core hardware and operating systems. In
addition, with release 5.5, InnoDB is now the default storage engine for
the MySQL Database, delivering ACID transactions, referential integrity
and crash recovery by default.

MySQL 5.5 also provides a number of additional enhancements including:

    - Significantly improved performance on Windows, with various
      Windows specific features and improvements
    - Higher availability, with new semi-synchronous replication and
      Replication Heart Beat
    - Improved usability, with Improved index and table partitioning,
      SIGNAL/RESIGNAL support and enhanced diagnostics, including a new
      Performance Schema monitoring capability.

For a more complete look at what's new in MySQL 5.5, please see the
following resources:

MySQL 5.5 is GA, Interview with Tomas Ulin:
http://dev.mysql.com/tech-resources/interviews/thomas-ulin-mysql-55.html

Documentation:
    http://dev.mysql.com/doc/refman/5.5/en/mysql-nutshell.html

Whitepaper: What's New in MySQL 5.5:
http://dev.mysql.com/why-mysql/white-papers/mysql-wp-whatsnew-mysql-55.php

If you are running a MySQL production level system, we would like to
direct your attention to MySQL Enterprise Edition, which includes the
most comprehensive set of MySQL production, backup, monitoring,
modeling, development, and administration tools so businesses can
achieve the highest levels of MySQL performance, security and uptime.
    http://mysql.com/products/enterprise/

For information on installing MySQL 5.5.24 on new servers, please see
the MySQL installation documentation at
    http://dev.mysql.com/doc/refman/5.5/en/installing.html

For upgrading from previous MySQL releases, please see the important
upgrade considerations at:
    http://dev.mysql.com/doc/refman/5.5/en/upgrading.html

MySQL Database 5.5.24 is available in source and binary form for a
number of platforms from our download pages at:
    http://dev.mysql.com/downloads/mysql/

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 in the MySQL source code since
the previous released version of MySQL 5.5. It may also be viewed
online at:
    http://dev.mysql.com/doc/refman/5.5/en/news-5-5-24.html

Enjoy!

On behalf of the MySQL Build Team,
Joerg Bruehe


Changes in MySQL 5.5.24 (2012-May-7)

Functionality Added or Changed

  * Important Change: Replication: INSERT ON DUPLICATE KEY UPDATE
    is now marked as unsafe for statement-based replication if the
    target table has more than one primary or unique key. For more
    information, see Section 16.1.2.3, "Determination of Safe and
    Unsafe Statements in Binary Logging."

Bugs Fixed

  * Security Fix: Bug #64884 was fixed.

  * InnoDB: Replication: When binary log statements were replayed
    on the slave, the Com_insert, Com_update, and Com_delete
    counters were incremented by BEGIN statements initiating
    transactions affecting InnoDB tables but not by COMMIT
    statements ending such transactions. This affected these
    statements whether they were replicated or they were run using
    mysqlbinlog. (Bug #12662190)

  * If the --bind-address option was given a host name value and
    the host name resolved to more than one IP address, the server
    failed to start. For example, with --bind-address=localhost,
    if localhost resolved to both 127.0.0.1 and ::1, startup
    failed. Now the server prefers the IPv4 address in such cases.
    (Bug #61713, Bug #12762885)

  * mysql_store_result() and mysql_use_result() are not for use
    with prepared statements and are not intended to be called
    following mysql_stmt_execute(), but failed to return an error
    when invoked that way in libmysqld. (Bug #62136, Bug
    #13738989)
    References: See also Bug #47485.

  * On Windows, mysqlslap crashed for attempts to connect using
    shared memory. (Bug #31173, Bug #11747181, Bug #59107, Bug
    #11766072)

MySQL Community Server 5.1.63 has been released

Sunanda Menon — 2012-05-07T11:09:15

Dear MySQL users,

MySQL Server 5.1.63, a new version of the popular Open Source
Database Management System, has been released. MySQL 5.1.63 is
recommended for use on production systems.

For an overview of what's new in MySQL 5.1, please see

http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html

For information on installing MySQL 5.1.63 on new servers or upgrading
to MySQL 5.1.63 from previous MySQL releases, please see

http://dev.mysql.com/doc/refman/5.1/en/installing.html

MySQL Server is available in source and binary form for a number of
platforms from our download pages at

http://dev.mysql.com/downloads/

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

For information on open issues in MySQL 5.1, please see the errata
list at

http://dev.mysql.com/doc/refman/5.1/en/bugs.html

The following section lists the changes in the MySQL source code since
the previous released version of MySQL 5.1. It may also be viewed
online at

http://dev.mysql.com/doc/refman/5.1/en/news-5-1-63.html

Enjoy!

=======================================================================
D.1.1. Changes in MySQL 5.1.63 (7th May, 2012)

    Bugs Fixed

      * Security Fix: Bug #64884 was fixed.

      * Security Fix: Bug #59387 was fixed.

      * InnoDB: Deleting a huge amount of data from InnoDB tables
        within a short time could cause the purge operation that
        flushes data from the buffer pool to stall. If this issue
        occurs, restart the server to work around it. This issue is
        only likely to occur on 32-bit platforms. (Bug #13847885)

      * InnoDB: If the server crashed during a TRUNCATE TABLE or
        CREATE INDEX statement for an InnoDB table, or a DROP DATABASE
        statement for a database containing InnoDB tables, an index
        could be corrupted, causing an error message when accessing
        the table after restart:
        InnoDB: Error: trying to load index index_name for table
        table_name
        InnoDB: but the index tree has been freed!
        In MySQL 5.1, this fix applies to the InnoDB Plugin, but not
        the built-in InnoDB storage engine. (Bug #12861864, Bug
        #11766019)

      * InnoDB: When data was removed from an InnoDB table, newly
        inserted data might not reuse the freed disk blocks, leading
        to an unexpected size increase for the system tablespace or
        .ibd file (depending on the setting of innodb_file_per_table.
        The OPTIMIZE TABLE could compact a .ibd file in some cases but
        not others. The freed disk blocks would eventually be reused
        as additional data was inserted. (Bug #11766634, Bug #59783)

      * Partitioning: After updating a row of a partitioned table and
        selecting that row within the same transaction with the query
        cache enabled, then performing a ROLLBACK, the same result was
        returned by an identical SELECT issued in a new transaction.
        (Bug #11761296, Bug #53775)

      * Replication: The --relay-log-space-limit option was sometimes
        ignored.
        More specifically, when the SQL thread went to sleep, it
        allowed the I/O thread to queue additional events in such a
        way that the relay log space limit was bypassed, and the
        number of events in the queue could grow well past the point
        where the relay logs needed to be rotated. Now in such cases,
        the SQL thread checks to see whether the I/O thread should
        rotate and provide the SQL thread a chance to purge the logs
        (thus freeing space).
        Note that, when the SQL thread is in the middle of a
        transaction, it cannot purge the logs; it can only ask for
        more events until the transaction is complete. Once the
        transaction is finished, the SQL thread can immediately
        instruct the I/O thread to rotate. (Bug #12400313, Bug #64503)
        References: See also Bug #13806492.

      * Mishandling of NO_BACKSLASH_ESCAPES SQL mode within stored
        procedures on slave servers could cause replication failures.
        (Bug #12601974)

      * If the system time was adjusted backward during query
        execution, the apparent execution time could be negative. But
        in some cases these queries would be written to the slow query
        log, with the negative execution time written as a large
        unsigned number. Now statements with apparent negative
        execution time are not written to the slow query log. (Bug
        #63524, Bug #13454045) References: See also Bug #27208.

      * mysql_store_result() and mysql_use_result() are not for use
        with prepared statements and are not intended to be called
        following mysql_stmt_execute(), but failed to return an error
        when invoked that way in libmysqld. (Bug #62136, Bug
        #13738989) References: See also Bug #47485.

      * SHOW statements treated stored procedure, stored function, and
        event names as case sensitive. (Bug #56224, Bug #11763507)

      * On Windows, mysqlslap crashed for attempts to connect using
        shared memory. (Bug #31173, Bug #11747181, Bug #59107, Bug
        #11766072)

Thanks,
On Behalf of, Oracle MySQL RE Team

Sunanda Menon
MySQL Release Engineer

MySQL Enterprise Monitor 2.3.10 Is Now GA!

Andy Bang — 2012-04-28T00:50:35

We are pleased to announce that MySQL Enterprise Monitor 2.3.10 is now
available for download on the My Oracle Support (MOS) web site as our
latest GA release.  It will also be available via the Oracle Software
Delivery Cloud in approximately 1-2 weeks.  This is a maintenance
release that contains several new features and fixes a number of bugs.
You can find more information on the contents of this release in the
changelog:

     http://dev.mysql.com/doc/mysql-monitor/2.3/en/mem-news-2-3-10.html

You will find binaries for the new release on My Oracle Support:

     https://support.oracle.com

Choose the "Patches & Updates" tab, and then use the "Product or
Family (Advanced Search)" feature.

You will also find the binaries on the Oracle Software Delivery Cloud
in approximately 1-2 weeks:

     http://edelivery.oracle.com/

Choose "MySQL Database" as the Product Pack and you will find the
Enterprise Monitor along with other MySQL products.

More information on MySQL Enterprise and the Enterprise Monitor can be
found here:

     http://www.mysql.com/products/enterprise/
     http://www.mysql.com/products/enterprise/advisors.html
     http://www.mysql.com/products/enterprise/query.html
     http://forums.mysql.com/index.php?137

If you are not a MySQL Enterprise customer and want try the Monitor
and Query Analyzer using our 30-day free customer trial, go to
http://www.mysql.com/trials, or contact Sales at
http://www.mysql.com/about/contact/sales.html?s=corporate.

If you haven't looked at 2.3 recently, please do so now and let us
know what you think.

Thanks and Happy Monitoring!

   - The MySQL Enterprise Tools Development Team

MySQL Connector/Net 6.3.9 has been released

Reggie Burnett — 2012-04-24T15:36:07

MySQL Connector/Net 6.3.9, the latest maintenance release of our 6.3 
version series, has been released.  Connector/Net is our all-managed 
.NET driver for MySQL.  This release will be the last release of our 
6.3.x series and contains more than 25 fixes from the 6.3.8 base.  Users 
looking for additional fixes or features should upgrade to our most 
recent version.

Version 6.3.9 is appropriate for use with versions of MySQL 5.0-5.5.

It is now available in source and binary form from 
http://dev.mysql.com/downloads/connector/net/6.3.html#downloads and 
mirror sites (note that not all mirror sites may be up to date at this 
point-if you can't find this version on some mirror, please try again 
later or choose another download site.)

The release is also available for download on My Oracle Support (MOS).

Enjoy and thanks for the support!

MySQL Community Server 5.5.23 has been released

Hery Ramilison — 2012-04-13T16:24:16

Dear MySQL users,

MySQL 5.5.23 is a new version of the 5.5 production release of the
world's most popular open source database. MySQL 5.5.23 is recommended
for use on production systems.

MySQL 5.5 includes several high-impact enhancements to improve the
performance and scalability of the MySQL Database, taking advantage of
the latest multi-CPU and multi-core hardware and operating systems. In
addition, with release 5.5, InnoDB is now the default storage engine for
the MySQL Database, delivering ACID transactions, referential integrity
and crash recovery by default.

MySQL 5.5 also provides a number of additional enhancements including:

     - Significantly improved performance on Windows, with various
       Windows specific features and improvements
     - Higher availability, with new semi-synchronous replication and
       Replication Heart Beat
     - Improved usability, with Improved index and table partitioning,
       SIGNAL/RESIGNAL support and enhanced diagnostics, including a new
       Performance Schema monitoring capability.

For a more complete look at what's new in MySQL 5.5, please see the
following resources:

MySQL 5.5 is GA, Interview with Tomas Ulin:
http://dev.mysql.com/tech-resources/interviews/thomas-ulin-mysql-55.html

Documentation:
     http://dev.mysql.com/doc/refman/5.5/en/mysql-nutshell.html

Whitepaper: What's New in MySQL 5.5:
http://dev.mysql.com/why-mysql/white-papers/mysql-wp-whatsnew-mysql-55.php

If you are running a MySQL production level system, we would like to
direct your attention to MySQL Enterprise Edition, which includes the
most comprehensive set of MySQL production, backup, monitoring,
modeling, development, and administration tools so businesses can
achieve the highest levels of MySQL performance, security and uptime.
     http://mysql.com/products/enterprise/

For information on installing MySQL 5.5.23 on new servers, please see
the MySQL installation documentation at
     http://dev.mysql.com/doc/refman/5.5/en/installing.html

For upgrading from previous MySQL releases, please see the important
upgrade considerations at:
     http://dev.mysql.com/doc/refman/5.5/en/upgrading.html

MySQL Database 5.5.23 is available in source and binary form for a
number of platforms from our download pages at:
     http://dev.mysql.com/downloads/mysql/

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 in the MySQL source code since
the previous released version of MySQL 5.5. It may also be viewed
online at:
     http://dev.mysql.com/doc/refman/5.5/en/news-5-5-23.html

Enjoy!


Changes in MySQL 5.5.23 (12 April 2012)

Functionality Added or Changed

   * The MySQL-shared-compat RPM package enables users of Red
     Hat-privided mysql-*-5.1 RPM packages to migrate to
     Oracle-provided MySQL-*-5.5 packages. MySQL-shared-compat now
     replaces the Red Hat mysql-libs package by replacing
     libmysqlclient.so files of the latter package, thus satisfying
     dependencies of other packages on mysql-libs. This change
     affects only users of Red Hat (or Red Hat-compatible) RPM
     packages. Nothing is different for users of Oracle RPM
     packages. (Bug #13867506)

Bugs Fixed

   * Security Fix: Bug #59533 was fixed.

   * Performance: Partitioning: InnoDB Storage Engine: The
     statistics used by the optimizer for queries against
     partitioned InnoDB tables were based only on the first
     partition of each such table, leading to use of the wrong
     execution plan. (Bug #13694811)
     References: This bug was introduced by Bug #11756867.

   * Performance: InnoDB Storage Engine: Improved the performance
     of the DROP TABLE statement for InnoDB tables, especially on
     systems with a large buffer pool. The fix speeds up the
     processing for freeing entries in the adaptive hash index.
     (Bug #13704145, Bug #64284)

   * InnoDB Storage Engine: Deleting a huge amount of data from
     InnoDB tables within a short time could cause the purge
     operation that flushes data from the buffer pool to stall. If
     this issue occurs, restart the server to work around it. This
     issue is only likely to occur on 32-bit platforms. (Bug
     #13847885)

   * InnoDB Storage Engine: If the server crashed during a TRUNCATE
     TABLE or CREATE INDEX statement for an InnoDB table, or a DROP
     DATABASE statement for a database containing InnoDB tables, an
     index could be corrupted, causing an error message when
     accessing the table after restart:
      InnoDB: Error: trying to load index index_name for table
      InnoDB: table_name but the index tree has been freed!
     In MySQL 5.1, this fix applies to the InnoDB Plugin, but not
     the built-in InnoDB storage engine. (Bug #12861864, Bug
     #11766019)

   * InnoDB Storage Engine: When data was removed from an InnoDB
     table, newly inserted data might not reuse the freed disk
     blocks, leading to an unexpected size increase for the system
     tablespace or .ibd file (depending on the setting of
     innodb_file_per_table. The OPTIMIZE TABLE could compact a .ibd
     file in some cases but not others. The freed disk blocks would
     eventually be reused as additional data was inserted. (Bug
     #11766634, Bug #59783)

   * Partitioning: After updating a row of a partitioned table and
     selecting that row within the same transaction with the query
     cache enabled, then performing a ROLLBACK, the same result was
     returned by an identical SELECT issued in a new transaction.
     (Bug #11761296, Bug #53775)

   * Replication: Formerly, the default value shown for the Port
     column in the output of SHOW SLAVE HOSTS was 3306 whether the
     port had been set incorrectly or not set at all. Now, when the
     slave port is not set, 0 is used as the default. This change
     also affects the default used for the --report-port server
     option. (Bug #13333431)

   * Replication: The --relay-log-space-limit option was sometimes
     ignored.
     More specifically, when the SQL thread went to sleep, it
     allowed the I/O thread to queue additional events in such a
     way that the relay log space limit was bypassed, and the
     number of events in the queue could grow well past the point
     where the relay logs needed to be rotated. Now in such cases,
     the SQL thread checks to see whether the I/O thread should
     rotate and provide the SQL thread a chance to purge the logs
     (thus freeing space).
     Note that, when the SQL thread is in the middle of a
     transaction, it cannot purge the logs; it can only ask for
     more events until the transaction is complete. Once the
     transaction is finished, the SQL thread can immediately
     instruct the I/O thread to rotate. (Bug #12400313, Bug #64503)
     References: See also Bug #13806492.

   * An infinite thread loop could develop within Performance
     Schema, causing the server to become unresponsive. (Bug
     #13898343)

   * Incorrect stored program caching could cause statements within
     a stored program that included a GROUP BY clause to return
     different results across multiple program invocations. (Bug
     #13805127)

   * Mishandling of NO_BACKSLASH_ESCAPES SQL mode within stored
     procedures on slave servers could cause replication failures.
     (Bug #12601974)

   * SAVEPOINT statements were incorrectly disallowed within XA
     transactions. (Bug #64374, Bug #13737343)
     References: See also Bug #11766752.

   * The Performance Schema incorrectly displayed some backslashes
     in Windows file names (by doubling them). (Bug #63339, Bug
     #13417446)

   * SHOW statements treated stored procedure, stored function, and
     event names as case sensitive. (Bug #56224, Bug #11763507)

On behalf of the MySQL Build Team,

Hery Ramilison
MySQL/ORACLE Release Engineering Team

MySQL Workbench 5.2.39 GA released

Alfredo Kojima — 2012-04-10T20:36:50

The MySQL Developer Tools team is announcing the next maintenance release of it’s flagship product, MySQL Workbench, version 5.2.39.
This version contains MySQL Utilities 1.0.5, a set of command line Python utilities for helping performing and scripting
various administration tasks for MySQL. A complete list of changes in this release of the Utilities can be found at:
http://dev.mysql.com/doc/workbench/en/wb-utils-news-1-0-5.html

MySQL Workbench 5.2 GA

• Data Modeling
• Query (replaces the old MySQL Query Browser)
• Administration (replaces the old MySQL Administrator)
Please get your copy from our Download site. Sources and binary packages are available for several platforms, including Windows, Mac OS X and Linux.

http://dev.mysql.com/downloads/workbench/

Workbench Documentation can be found here.

http://dev.mysql.com/doc/workbench/en/index.html

Utilities Documentation can be found here.
http://dev.mysql.com/doc/workbench/en/mysql-utilities.html

In addition to the new Query/SQL Development and Administration modules, version 5.2 features improved stability and performance – especially in Windows, where OpenGL support has been enhanced and the UI was optimized to offer better responsiveness. This release also includes improvements to the scripting capabilities of the SQL Editor. You can read more about it in

http://wb.mysql.com/workbench/doc/

For a detailed list of resolved issues, see the change log.

http://dev.mysql.com/doc/workbench/en/wb-change-history.html

If you need any additional info or help please get in touch with us.

Post in our forums, leave comments on our blog pages or if you want to talk to us directly you can visit us on our IRC channel #workbench onirc.freenode.net.

- The MySQL Workbench Team

Alfredo Kojima

MySQL Community Server 5.6.5 has been released

Joerg Bruehe — 2012-04-10T11:57:37

Dear MySQL users,

MySQL Server 5.6.5 (Milestone Release) is a new version of the world's
most popular open source database.

The new features in these releases are of beta quality. As with any
other pre-production release, caution should be taken when installing on
production level systems or systems with critical data.

Note that 5.6.5 includes all features in MySQL 5.5. For an overview of
what's new in MySQL 5.6, please see the section "What Is New in MySQL
5.6" below, or view it online at

http://dev.mysql.com/doc/refman/5.6/en/mysql-nutshell.html

For information on installing MySQL 5.6.5 on new servers, please see the
MySQL installation documentation at

http://dev.mysql.com/doc/refman/5.6/en/installing.html

For upgrading from previous MySQL releases, please see the important
upgrade considerations at

http://dev.mysql.com/doc/refman/5.6/en/upgrading-from-previous-series.html

Please note that **downgrading** from these releases to a previous
release series is not supported.

MySQL Server 5.6 is available in source and binary form for a number of
platforms from the "Development Releases" selection of our download
pages at

http://dev.mysql.com/downloads/mysql/

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

Below, you find a list of selected changes in 5.6.5. You can view the
full list of all "Bugs Fixed" for 5.6.5 online at

http://dev.mysql.com/doc/refman/5.6/en/news-5-6-5.html

If you are running a MySQL production level system, we would like to
direct your attention to MySQL Enterprise Edition, which includes the
most comprehensive set of MySQL production, backup, monitoring,
modeling, development, and administration tools so businesses can
achieve the highest levels of MySQL performance, security and uptime.

http://mysql.com/products/enterprise/

Enjoy!


On behalf of the MySQL Build Team at Oracle,
Joerg Bruehe


=====

D.1.2. Changes in MySQL 5.6.5 (2012-April-10, Milestone 8)

Platform Notes

  * Beginning with MySQL 5.6.5 Oracle will no longer provide binaries
    for Mac OS X 10.5.  This aligns with Apple no longer providing
    updates or support for this platform.

Data Type Notes

  * Previously, at most one TIMESTAMP column per table could be
    automatically initialized or updated to the current date and
    time. This restriction has been lifted. Any TIMESTAMP column
    definition can have any combination of DEFAULT
    CURRENT_TIMESTAMP and ON UPDATE CURRENT_TIMESTAMP clauses. In
    addition, these clauses now can be used with DATETIME column
    definitions. For more information, see Section 11.3.4,
    "Automatic Initialization and Updating for TIMESTAMP and
    DATETIME."

Replication with GTIDs

  * Important Change: Replication: This release introduces global
    transaction identifiers (GTIDs) for MySQL Replication. A GTID
    is a unique identifier that is assigned to each transaction as
    it is committed; this identifier is unique on the MySQL Server
    where the transaction originated, as well as across all MySQL
    Servers in a given replication setup. Because GTID-based
    replication depends on tracking transactions, it cannot be
    employed with tables that employ a nontransactional storage
    engine such as MyISAM; thus, it is currently supported only
    with InnoDB tables.
    Because each transaction is uniquely identified, it is not
    necessary when using GTIDs to specify positions in the
    master's binary log when starting a new slave or failing over
    to a new master. This is reflected in the addition of a new
    MASTER_AUTO_POSITION option for the CHANGE MASTER TO statement
    which takes the place of the MASTER_LOG_FILE and
    MASTER_LOG_POS options when when executing this statement to
    prepare a MySQL Server to act as a replication slave.
    To enable GTIDs on a MySQL Server, the server must be started
    with the options
      --gtid-mode=ON --disable-gtid-unsafe-statements --log-bin
      --log-slave-updates
    These options are needed whether the server acts as a replication
    master or as a replication slave; the --gtid-mode and
    --disable-gtid-unsafe-statements options are new in this release.
    Once the master and slave have each been started with these options,
    it is necessary only to issue a CHANGE MASTER TO ...
    MASTER_AUTO_POSITION=1 followed by START SLAVE on the slave to start
    replication.
    A number of new server system variables have also been added
    for monitoring GTID usage. For more information about these
    options and variables, see Section 16.1.4.5, "Global
    Transaction ID Options and Variables."
    As part of these changes, three new mysqlbinlog options
        --include-gtids, --exclude-gtids, and --skip-gtids
    have been added for reading binary logs produced when the server
    participates in replication with GTIDs.

    Important
    Due to an issue discovered just prior to release, you cannot
    import a dump made using mysqldump from a MySQL 5.5 server to
    a MySQL 5.6.5 server and then use mysqlupgrade on the MySQL
    5.6.5 server while GTIDs are enabled; doing so makes it
    impossible to connect to the server normally following the
    upgrade. Instead, you should import the dump and run
    mysqlupgrade while the MySQL 5.6.5 server is running with
    --gtid-mode=OFF, then restart it with --gtid-mode=ON. (Bug
    #13833710.)
    For additional information about GTIDs and setting up
    GTID-based replication, see Section 16.1.3, "Replication with
    Global Transaction Identifiers."

Host Cache Notes

  * MySQL now provides more information about the causes of errors
    that occur when clients connect to the server, as well as
    improved access to the host cache, which contains client IP
    address and host name information and is used to avoid DNS
    lookups. These changes have been implemented:

       + New Connection_errors_xxx status variables provide
         information about connection errors that do not apply to
         specific client IP addresses.

       + Counters have been added to the host cache to track
         errors that do apply to specific IP addresses.

       + A new host_cache Performance Schema table exposes the
         contents of the host cache so that it can be examined
         using SELECT statements. Access to host cache contents
         makes it possible to answer questions such as how many
         hosts are cached, what kinds of connection errors are
         occurring for which hosts, or how close host error counts
         are to reaching the max_connect_errors system variable
         limit. The Performance Schema must be enabled or this
         table is empty.
         If you upgrade to this release of MySQL from an earlier
         version, you must run mysql_upgrade (and restart the
         server) to incorporate this change into the
         performance_schema database.

       + The host cache size now is configurable using the
         host_cache_size system variable. Setting the size to 0
         disables the host cache.This is similar to starting the
         server with --skip-host-cache, but host_cache_size is
         more flexible because it can also be used to resize,
         enable, or disable the host cache at runtime, not just at
         server startup. If you start the server with
         --skip-host-cache, the host cache cannot be re-enabled at
         runtime.

    For more information, see Section 8.11.5.2, "DNS Lookup
    Optimization and the Host Cache," and Section 20.9.8.1, "The
    host_cache Table." (Bug #22821, Bug #24906, Bug #45817, Bug
    #59404, Bug #11746048, Bug #11746269, Bug #11754244, Bug
    #11766316)

Optimizer Features

  * These query optimizer improvements were implemented:

       + The EXPLAIN statement now can produce output in JSON
         format. To select this, use EXPLAIN FORMAT = JSON
         explainable_stmt syntax. With FORMAT = JSON, the output
         includes regular EXPLAIN information, as well as extended
         and partition information.
         Traditional EXPLAIN output has also changed so that empty
         columns contain NULL rather the empty string. In
         addition, UNION RESULT rows have Using filesort in the
         Extra column because a temporary table is used to buffer
         UNION results.
         To work for both Optimizer Trace and JSON-format EXPLAIN
         output, the end_marker parameter for the optimizer_trace
         system variable has been moved to a separate
         end_markers_in_json system variable. This is an
         incompatible change to the optimizer_trace variable. For
         more information, see MySQL Internals: Optimizer tracing
         (http://forge.mysql.com/wiki/MySQL_Internals_Optimizer_tr
         acing).

       + The optimizer tries to find the best query execution plan
         by beginning with the most promising table and
         recursively adding to the plan the most promising of the
         remaining tables. Partial execution plans with a higher
         cost than an already found plan are pruned. The optimizer
         now attempts to improve the order in which it adds tables
         to the plan, resulting in a reduction of the number of
         partial plans considered.
         Queries that are likely to have improved performance are
         joins of many tables, where most tables use eq_ref or ref
         join types (as indicated by EXPLAIN output).
         A new status variable, Last_query_partial_plans, counts
         the number of iterations the optimizer makes in execution
         plan construction for the previous query.

       + The optimizer uses semi-join and materialization
         strategies to optimize subquery execution. See Section
         8.13.15.1, "Optimizing Subqueries with Semi-Join
         Transformations," and Section 8.13.15.2, "Optimizing
         Subqueries with Subquery Materialization." In addition,
         the Batched Key Access (BKA) Join and Block Nested-Loop
         (BNL) Join algorithms used for inner join and outer join
         operations have been extended to support semi-join
         operations. For more information, see Section 8.13.11,
         "Block Nested-Loop and Batched Key Access Joins."
         Several flags have been added to the optimizer_switch
         system variable to enable control over semi-join and
         subquery materialization strategies. See Section 8.8.4.2,
         "Controlling Switchable Optimizations."

       + For expressions such as col_name IN(values) that compare
         a column to a list of values, the optimizer previously
         made row estimates using index dives for each value in
         the list. This becomes inefficient as the number of
         values becomes large. The optimizer now can make row
         estimates for such expressions using index statistics
         instead, which is less accurate but quicker for a large
         number of values. The point at which the optimizer
         switches from index dives to index statistics is
         configurable using the new eq_range_index_dive_limit
         system variable. For more information, see Section
         8.13.1.3, "Equality Range Optimization of Many-Valued
         Comparisons."

Performance Schema Notes

  * The Performance Schema has these additions:

       + The Performance Schema now has a host_cache table that
         exposes the contents of the host cache so that it can be
         examined using SELECT statements. See Host Cache Notes
         above.

       + The Performance Schema now maintains statement digest
         information. This normalizes and groups statements with
         the same "signature" and permits questions to be answered
         about the types of statements the server is executing and
         how often they occur.
            o A statement_digest consumer in the setup_consumers
              table controls whether the Performance Schema
              maintains digest information.
            o The statement event tables
              (events_statements_current,
              events_statements_history, and
              events_statements_history_long) have DIGEST and
              DIGEST_TEXT columns that contain digest MD5 values
              and the corresponding normalized statement text
              strings.
            o A events_statements_summary_by_digest table provides
              aggregated statement digest information.

    If you upgrade to this release of MySQL from an earlier
    version, you must run mysql_upgrade (and restart the server)
    to incorporate these changes into the performance_schema
    database.
    For more information, see Chapter 20, "MySQL Performance
    Schema."

Functionality Added or Changed

  * Security Fix: Passwords stored in the older format used before
    MySQL 4.1 are now deprecated, and the secure_auth system
    variable is enabled by default to prevent connections using
    accounts that have passwords stored in the old format. To
    permit such connections, start the server with
    --skip-secure-auth. (Bug #13586336)

  * Security Fix: MySQL client programs now issue a warning if a
    password is given on the command line that this can be
    insecure.

  * Incompatible Change: The obsolete OPTION modifier for the SET
    statement has been removed.

  * InnoDB Storage Engine: --ignore-builtin-innodb is now ignored
    if used. (Bug #13586262)

  * The MySQL-shared-compat RPM package enables users of Red
    Hat-provided mysql-*-5.1 RPM packages to migrate to
    Oracle-provided MySQL-*-5.5 packages. MySQL-shared-compat now
    replaces the Red Hat mysql-libs package by replacing
    libmysqlclient.so files of the latter package, thus satisfying
    dependencies of other packages on mysql-libs. This change
    affects only users of Red Hat (or Red Hat-compatible) RPM
    packages. Nothing is different for users of Oracle RPM
    packages. (Bug #13867506)

  * Temporary tables for INFORMATION_SCHEMA queries now use packed
    MyISAM format if they contain sufficiently large VARCHAR
    columns, resulting in space savings. (Bug #13627632)

  * As of MySQL 5.5.3, the LOW_PRIORITY modifier for LOCK TABLES
    ... LOW_PRIORITY WRITE has no effect. This modifier is now
    deprecated. Its use should be avoided and now produces a
    warning. Use LOCK TABLES ... WRITE instead. (Bug #13586314)

  * A new CMake option, MYSQL_PROJECT_NAME, can be set on Windows
    or Mac OS X to be used in the project name. (Bug #13551687)

  * If the log_queries_not_using_indexes system variable is
    enabled, slow queries that do not use indexes are written to
    the slow query log. In this case, it is now possible to put a
    logging rate limit on these queries by setting the new
    log_throttle_queries_not_using_indexes system variable, so
    that the slow query log does not grow too quickly. By default,
    this variable is 0, which means there is no limit. Positive
    values impose a per-minute limit on logging of queries that do
    not use indexes. (Bug #55323, Bug #11762697)

  * A new server option, --slow-start-timeout, controls the
    Windows service control manager's service start timeout. The
    value is the maximum number of milliseconds that the service
    control manager waits before trying to kill the MySQL service
    during startup. The default value is 15000 (15 seconds). If
    the MySQL service takes too long to start, you may need to
    increase this value. A value of 0 means there is no timeout.
    (Bug #45546, Bug #11754011)

  * The mysql client now supports an --init-command=str option.
    The option value is an SQL statement to execute after
    connecting to the server. If auto-reconnect is enabled, the
    statement is executed again after reconnection occurs. (Bug
    #45634, Bug #11754087)

  * Several subquery performance issues were resolved through the
    implementation of semi-join subquery optimization strategies.
    See Section 8.13.15.1, "Optimizing Subqueries with Semi-Join
    Transformations." (Bug #47914, Bug #11756048, Bug #58660, Bug
    #11765671, Bug #10815, Bug #11745162, Bug #9021, Bug
    #13519134, Bug #48763, Bug #11756798, Bug #25130, Bug
    #11746289)

  * New utf8_general_mysql500_ci and ucs2_general_mysql500_ci
    collations have been added that preserve the behavior of
    utf8_general_ci and ucs2_general_ci from versions of MySQL
    previous to 5.1.24. Bug #27877 corrected an error in the
    original collations but introduced an incompatibility for
    columns that contain German 'ß' LATIN SMALL LETTER SHARP S.
    (As a result of the fix, that character compares equal to
    characters with which it previously compared different.) A
    symptom of the problem after upgrading to MySQL 5.1.24 or
    newer from a version older than 5.1.24 is that CHECK TABLE
    produces this error:
Table upgrade required.
Please do "REPAIR TABLE `t`" or dump/reload to fix it!
    Unfortunately, REPAIR TABLE could not fix the problem. The new
    collations permit older tables created before MySQL 5.1.24 to
    be upgraded to current versions of MySQL.
    To convert an affected table after a binary upgrade that
    leaves the table files in place, alter the table to use the
    new collation. Suppose that the table t1 contains one or more
    problematic utf8 columns. To convert the table at the table
    level, use a statement like this:
ALTER TABLE t1
CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_mysql500_ci;
    To apply the change on a column-specific basis, use a
    statement like this (be sure to repeat the column definition
    as originally specified except for the COLLATE clause):
ALTER TABLE t1
MODIFY c1 CHAR(N) CHARACTER SET utf8 COLLATE utf8_general_mysql500_ci;
    To upgrade the table using a dump and reload procedure, dump
    the table using mysqldump, modify the CREATE TABLE statement
    in the dump file to use the new collation, and reload the
    table.
    After making the appropriate changes, CHECK TABLE should
    report no error.
    For more information, see Section 2.11.3, "Checking Whether
    Tables or Indexes Must Be Rebuilt," and Section 2.11.4,
    "Rebuilding or Repairing Tables or Indexes." (Bug #43593, Bug
    #11752408)

  * MySQL distributions no longer include the GPL readline
    input-editing library. This results in simpler maintenance and
    support, and simplifies licensing considerations.

  * The SET TRANSACTION and START TRANSACTION statements now
    support READ WRITE and READ ONLY modifiers to set the
    transaction access mode for tables used in transactions. The
    default mode is read/write, which is the same mode as
    previously. Read/write mode now may be specified explicitly
    with the READ WRITE modifier. Using READ ONLY prohibits table
    changes and may enable storage engines to make performance
    improvements that are possible when changes are not permitted.
    In addition, the new --transaction-read-only option and
    tx_read_only system variable permit the default transaction
    access mode to be set at server startup and runtime.
    For more information, see Section 13.3.6, "SET TRANSACTION
    Syntax," and Section 13.3.1, "START TRANSACTION, COMMIT, and
    ROLLBACK Syntax."

Bugs Fixed

  * Performance: InnoDB Storage Engine: The optimizer now takes
    into account InnoDB page sizes other than 16KB, which can be
    configured with the innodb_page_size option when creating a
    MySQL instance. This change improves the estimates of I/O
    costs for queries on systems with non-default InnoDB page
    sizes. (Bug #13623078)

  * Performance: InnoDB Storage Engine: Memory allocation for
    InnoDB tables was reorganized to reduce the memory overhead
    for large numbers of tables or partitions, avoiding situations
    where the "resident set size" could grow regardless of FLUSH
    TABLES statements. (Bug #11764622, Bug #57480)

  * Incompatible Change: Replication: CHANGE MASTER TO statements
    were written into the error log using quoted numeric values,
    although the syntax for this statement does not allow such
    option values to be quoted. This meant that such statements
    could not be copied from the error log and re-run verbatim.
    Now CHANGE MASTER TO statements are written to the error log
    without the extraneous quotation marks, and so are
    syntactically correct as logged.

  * Incompatible Change: A change in MySQL 5.6.3 caused LAST_DAY()
    to be more strict and reject incomplete dates with a day part
    of zero. For this function, a nonzero day part is not
    necessary, so the change has been reverted. (Bug #13458237)

  * Important Change: InnoDB Storage Engine: When a row grew in
    size due to an UPDATE operation, other (non-updated) columns
    could be moved to off-page storage so that information about
    the row still fit within the constraints of the InnoDB page
    size. The pointer to the new allocated off-page data was not
    set up until the pages were allocated and written, potentially
    leading to lost data if the system crashed while the column
    was being moved out of the page.
    A related issue was that during such an UPDATE operation, or
    an INSERT operation that reused a delete-marked record, other
    transactions could see invalid data for the affected column,
    regardless of isolation level.
    The fix corrects the order of operations for moving the column
    data off the original page and replacing it with a pointer.
    (Bug #13721257, Bug #12612184, Bug #12704861)

  * Important Change: Replication: The CHANGE MASTER TO statement
    was not checked for invalid characters in values for options
    such as MASTER_HOST and MASTER_USER. In addition, when the
    server was restarted, a value containing certain characters
    was trimmed, causing the loss of its original value. Now such
    values are validated, and in cases where the value contains
    invalid characters, including linefeed (\n or 0x0A)
    characters, the statement fails with an error
    (ER_MASTER_INFO). (Bug #11758581, Bug #50801)

  * Important Change: Replication: Moving the binary log file,
    relay log file, or both files to a new location, then
    restarting the server with a new value for --log-bin,
    --relay-log, or both, caused the server to abort on start.
    This was because the entries in the index file overrode the
    new location. In addition, paths were calculated relative to
    datadir (rather than to the --log-bin or --relay-log values).
    The fix for this problem means that, when the server reads an
    entry from the index file, it now checks whether the entry
    contains a relative path. If it does, the relative part of the
    path is replaced with the absolute path set using the
    --log-bin or --relay-log option. An absolute path remains
    unchanged; in such a case, the index must be edited manually
    to enable the new path or paths to be used. (Bug #11745230,
    Bug #12133)

  * InnoDB Storage Engine: A DDL operation such as ALTER TABLE ...
    ADD COLUMN could stall, eventually timing out with an Error
    1005: Can't create table message referring to
    fil_rename_tablespace. (Bug #13636122, Bug #62100, Bug #63553)

  * InnoDB Storage Engine: If InnoDB was started with
    innodb_force_recovery set to a value of 3 or 4, and there are
    transactions to roll back, normal shutdown would hang waiting
    for those transactions to complete. Now the shutdown happens
    immediately, without rolling back any transactions, because
    non-zero values for innodb_force_recovery are only appropriate
    for troubleshooting and diagnostic purposes. (Bug #13628420)

  * InnoDB Storage Engine: The MySQL server could hang in some
    cases if the configuration option innodb_use_native_aio was
    turned off. (Bug #13619598)

  * InnoDB Storage Engine: The configuration option
    innodb_sort_buf_size was renamed to innodb_sort_buffer_size
    for consistency. This work area is used while creating an
    InnoDB index. (Bug #13610358)

  * InnoDB Storage Engine: The server could crash when creating an
    InnoDB temporary table under Linux, if the $TMPDIR setting
    points to a tmpfs filesystem and innodb_use_native_aio is
    enabled, as it is by default in MySQL 5.5.4 and higher. The
    entry in the error log looked like:
101123  2:10:59  InnoDB: Operating system error number 22 in a file
operation.
InnoDB: Error number 22 means 'Invalid argument'.
    The crash occurred because asynchronous I/O is not supported
    on tmpfs in some Linux kernel versions. The workaround was to
    turn off the innodb_use_native_aio setting or use a different
    temporary directory. The fix causes InnoDB to turn off the
    innodb_use_native_aio setting automatically if it detects that
    the temporary file directory does not support asynchronous
    I/O. (Bug #13593888, Bug #11765450, Bug #58421)

  * InnoDB Storage Engine: During startup, the status variable
    Innodb_buffer_pool_dump_status could be empty for a brief time
    before being initialized to the correct value not started.
    (Bug #13513676)

  * InnoDB Storage Engine: The MySQL error log could contain
    messages like:
InnoDB: Ignoring strange row from mysql.innodb_index_stats WHERE ...
    The fix makes the contents of the innodb_index_stats and
    innodb_table_stats tables case-sensitive, to properly
    distinguish the statistics for tables whose names differ only
    in letter case. Other cases were fixed where the wrong name
    could be selected for an index while retrieving persistent
    statistics. (Bug #13432465)

  * InnoDB Storage Engine: The MySQL server could halt with an
    assertion error:
InnoDB: Failing assertion: page_get_n_recs(page) > 1
    Subsequent restarts could fail with the same error. The error
    occurred during a purge operation involving the InnoDB change
    buffer. The workaround was to set the configuration option
    innodb_change_buffering=inserts. (Bug #13413535, Bug #61104)

  * InnoDB Storage Engine: When doing a live downgrade from MySQL
    5.6.4 or later, with innodb_page_size set to a value other
    than 16384, now the earlier MySQL version reports that the
    page size is incompatible with the older version, rather than
    crashing or displaying a "corruption" error. (Bug #13116225)

  * InnoDB Storage Engine: Certain CREATE TABLE statements could
    fail for InnoDB child tables containing foreign key
    definitions. This problem affected Windows systems only, with
    the setting lower_case_table_names=0. It was a regression from
    MySQL bug #55222. (Bug #13083023, Bug #60229)

  * InnoDB Storage Engine: If the server crashed during a TRUNCATE
    TABLE or CREATE INDEX statement for an InnoDB table, or a DROP
    DATABASE statement for a database containing InnoDB tables, an
    index could be corrupted, causing an error message when
    accessing the table after restart:
InnoDB: Error: trying to load index index_name for table table_name
InnoDB: but the index tree has been freed!
    (Bug #12861864, Bug5.1 #11766019)

  * InnoDB Storage Engine: InnoDB persistent statistics gave less
    accurate estimates for date columns than for columns of other
    data types. The fix changes the way cardinality is estimated
    for non-unique keys, and avoids situations where identical
    values could be counted twice if they occurred on different
    index pages. (Bug #12429443)

   * InnoDB Storage Engine: Improved the accuracy of persistent
    InnoDB statistics for large tables. The estimate of distinct
    records could be inaccurate if the index tree was more than 3
    levels deep. (Bug #12316365)

  * InnoDB Storage Engine: Shutdown could hang with messages like
    this in the log:
Waiting for purge thread  to be suspended
    After 1 hour, the shutdown times out and mysqld quits. This
    problem is most likely to occur with a high value for
    innodb_purge_threads. (Bug #11765863, Bug #58868, Bug #60939)

  * InnoDB Storage Engine: When DROP TABLE failed due to all undo
    slots being in use, the error returned was Unknown table '...'
    rather than the expected Too many active concurrent
    transactions. (Bug #11764724, Bug #57586)
    References: See also Bug #11764668, Bug #57529.

  * InnoDB Storage Engine: Server startup could produce an error
    for temporary tables using the InnoDB storage engine, if the
    path in the $TMPDIR variable ended with a / character. The
    error log would look like:
120202 19:21:26  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './t/#sql7750_1_0.ibd'!
    (Bug #11754376, Bug #45976)

  * Partitioning: When creating a view from a SELECT statement
    that used explicit partition selection, the partition
    selection portion of the query was ignored. (Bug #13559657)

  * Partitioning: Adding a partition to an already existing
    LIST-partitioned table did not work correctly if the number of
    items in the new partition was greater than 16. This could
    happen when trying to add a partition using an ALTER TABLE ...
    ADD PARTITION statement, or an ALTER TABLE ... REORGANIZE
    PARTITION statement. (Bug #13029508, Bug #62505)

  * Partitioning: A function internal to the code for finding
    matching subpartitions represented an unsigned number as
    signed, with the result that matching subpartitions were
    sometimes missed in results of queries. (Bug #12725206, Bug
    #61765)
    References: See also Bug #20257.

  * Partitioning: After updating a row of a partitioned table and
    selecting that row within the same transaction with the query
    cache enabled, then performing a ROLLBACK, the same result was
    returned by an identical SELECT issued in a new transaction.
    (Bug #11761296, Bug #53775)

  * Partitioning: An ALTER TABLE ... ADD PARTITION statement
    subsequent to ALTER TABLE ... REORGANIZE PARTITION failed on a
    table partitioned by HASH or KEY. (Bug #11764110, Bug #56909)

  * Replication: Executing mysqlbinlog with the --start-position=N
    option, where N was equal either to 0 or to a value greater
    than the length of the dump file, caused it to crash.
    This issue was introduced in MySQL 5.5.18 by the fix for Bug
    #32228 and Bug #11747416. (Bug #13593869, Bug #64035)

  * Replication: When starting the server, replication
    repositories were checked even when the --server-id was equal
    to 0 (the default), in spite of the fact that a valid nonzero
    value for --server-id must be supplied for a server that acts
    as either a master or a slave in MySQL replication.
    This could cause problems when trying to perform a live
    upgrade from MySQL 5.5, although it was possible to work
    around the issue by starting the server with
    --skip-slave-start (in addition to any other required
    options).
    To avoid this problem, replication repositories are now
    checked only when the server is started with --server-id using
    a nonzero value. (Bug #13427444, Bug #13504821)

  * Replication: Formerly, the default value shown for the Port
    column in the output of SHOW SLAVE HOSTS was 3306 whether the
    port had been set incorrectly or not set at all. Now, when the
    slave port is not set, 0 is used as the default. This change
    also affects the default used for the --report-port server
    option. (Bug #13333431)

  * Replication: A race condition could occur when running
    multiple instances of mysqld on a single machine, when more
    than slave thread was started at the same time, and each such
    thread tried to use the same temporary file concurrently. (Bug
    #12844302, Bug #62055)

  * Replication: Statements that wrote to tables with
    AUTO_INCREMENT columns based on an unordered SELECT from
    another table could lead to the master and the slave going out
    of sync, as the order in which the rows are retrieved from the
    table may differ between them. Such statements include any
    INSERT ... SELECT, REPLACE ... SELECT, or CREATE TABLE ...
    SELECT statement. Such statements are now marked as unsafe for
    statement-based replication, which causes the execution of one
    to throw a warning, and forces the statement to be logged
    using the row-based format if the logging format is MIXED.
    (Bug #11758263, Bug #50440)

  * Replication: On Windows replication slave hosts, STOP SLAVE
    took an excessive length of time to complete when the master
    was down. (Bug #11752315, Bug #43460)

  * The optimizer did not perform constant propagation for views,
    so a query containing views resulted in a less efficient
    execution plan than the corresponding query using only base
    tables. (Bug #13783777)

  * A memory leak could occur for queries containing a subquery
    that used GROUP BY on an outer column. (Bug #13724099)

  * After using an ALTER TABLE statement to change the
    KEY_BLOCK_SIZE property for an InnoDB table, for example when
    switching from an uncompressed to a compressed table,
    subsequent server restarts could fail with a message like:
InnoDB: Error: data file path/ibdata2 uses page size 1024,
InnoDB: but the only supported page size in this release is=16384
    This issue is a regression introduced in MySQL 5.5.20. (Bug
    #13698765, Bug #64160)

  * _mi_print_key() iterated one time too many when there was a
    NULL bit, resulting in Valgrind warnings. (Bug #13686970)

  * Pushing down to InnoDB an index condition that called a stored
    function resulted in a server crash. This kind of condition is
    no longer pushed down. (Bug #13655397)

  * A SELECT from a subquery that returned an empty result could
    itself fail to return an empty result as expected. (Bug
    #13651009, Bug #13650418)

  * If during server startup a signal such as SIGHUP was caught
    prior to full server initialization, the server could crash.
    This was due to a race condition between the signal handler
    thread and the main thread performing server initialization.
    To prevent this from happening, signal processing is now
    suspended until full initialization of all server components
    has been completed successfully. (Bug #13608371, Bug #62311)

  * The shared version of libmysqlclient did not export these
    functions for linking by client programs: get_tty_password(),
    handle_options(), my_print_help(). (Bug #13604121)

  * An aggregated expression of type MIN() or MAX() should return
    NULL but could instead return the empty set if the query was
    implicitly grouped and there was no HAVING clause that
    evaluates to FALSE. (Bug #13599013)

  * Left join queries could be incorrectly converted to inner
    joins and return erroneous result sets. (Bug #13595212)

  * Date-handling code could raise an assertion attempting to
    calculate the number of seconds since the epoch. (Bug
    #13545236)

  * For queries that used a join type of ref_or_null, the
    optimizer could skip the filesort operation and sort the
    results incorrectly. (Bug #13531865)

  * For some queries, a filesort operation was done even when the
    result contained only a single row and needed no sorting. (Bug
    #13529048)

  * The optimizer could return an incorrect select limit in some
    cases when a query included no explicit LIMIT clause. (Bug
    #13528826)

  * In some cases, the optimizer failed to use a covering index
    when that was possible and read data rows instead. (Bug
    #13514959)

  * The Performance Schema instrumentation for stages did not
    fully honor the ENABLED column in the schema.setup_instruments
    table. (Bug #13509513)

  * SELECT statements failed for the EXAMPLE storage engine. (Bug
    #13511529)
    References: This bug was introduced by Bug #11746275.

  * Converting a string ending with a decimal point (such as '1.')
    to a floating-point number raised a data truncation warning.
    (Bug #13500371)

  * Use of an uninitialized TABLE_SHARE member could cause a
    server crash. (Bug #13489996)

  * Some outer joins that used views as inner tables did not
    evaluate conditions correctly. (Bug #13464334)

  * A query that used an index on a CHAR column referenced in a
    BETWEEN clause could return invalid results. (Bug #13463488,
    Bug #63437)

  * Expressions that compared a BIGINT column with any non-integer
    constant were performed using integers rather than decimal or
    float values, with the result that the constant could be
    truncated. This could lead to any such comparison that used <,
    >, <=, >=, =, !=/<>, IN, or BETWEEN yielding false positive or
    negative results. (Bug #13463415, Bug #11758543, Bug #63502,
    Bug #50756)

  * Instantiating a derived table for a query with an empty result
    caused a server crash. (Bug #13457552)

  * When the optimizer performed conversion of DECIMAL values
    while evaluating range conditions, it could produce incorrect
    results. (Bug #13453382)

  * On Windows, rebuilds in a source distribution failed to create
    the initial database due to insufficient cleanup from the
    previous run or failure to find the proper server executable.
    (Bug #13431251)

  * Enabling index condition pushdown could cause performance
    degradation. (Bug #13430436)

  * Implicitly grouped queries with a const table and no matching
    rows could return incorrect results. (Bug #13430588)

  * When a fixed-width row was inserted into a MyISAM temporary
    table, the entire content of the record buffer was written to
    the table, including any trailing space contained in VARCHAR
    columns, the issue being that this trailing space could be
    uninitialized. This problem has been resolved by insuring that
    only the bytes actually used to store the VARCHAR (and none
    extra) are copied and inserted in such cases. (Bug #13389854)

  * Fractional seconds parts were lost for certain UNION ALL
    queries. (Bug #13375823)

  * Temporary MyISAM tables (unlike normal MyISAM tables) did not
    use the packed record format when they contained VARCHAR
    columns, resulting in larger temporary files (and more file
    I/O) than necessary. (Bug #13350136)

  * When merging ranges that effectively resulted in a full index
    scan, the optimizer did not discard the range predicate as
    unneeded. (Bug #13354910)

  * When executing EXPLAIN, it was assumed that only the default
    multi-range read implementation could produce an ordered
    result; this meant that when a query on a table that used a
    storage engine providing its own sorted MRR, it was ignored,
    so that EXPLAIN failed to report Using MRR even when a
    multi-range read was used. (Bug #13330645)

  * Performance Schema idle event timings were not normalized to
    the same units as wait timings. (Bug #13018537)

  * In MySQL 5.6.3, a number of status variables were changed to
    longlong types so that they would roll over much later.
    However, the format string used by mysqladmin status to print
    Queries per second values did not reflect this, causing such
    values to be misreported. (Bug #12990746)
    References: See also Bug #42698. This bug was introduced by
    Bug #11751727.

  * When the result of a stored function returning a non-integer
    type was evaluated for NULL, an incorrect type warning
    (Warning 1292 Truncated incorrect INTEGER value) is generated,
    although such a test for NULL should work with any type. This
    could cause stored routines not handling the warning correctly
    to fail.
    The issue could be worked around by wrapping the result in an
    expression, using a function such as CONCAT(). (Bug #12872824,
    Bug #62125)

  * When running mysqldump with both the --single-transaction and
    --flush-logs options, the flushing of the log performed an
    implicit COMMIT (see Section 13.3.3, "Statements That Cause an
    Implicit Commit"), causing more than one transaction to be
    used and thus breaking consistency. (Bug #12809202, Bug
    #61854)

  * A query that used an aggregate function such as MAX() or MIN()
    of an index with NOT BETWEEN in the WHERE clause could fail to
    match rows, thus returning an invalid result. (Bug #12773464,
    Bug #61925)

  * With ONLY_FULL_GROUP_BY SQL mode enabled, columns that were
    not aggregated in the the select list or named in a GROUP BY
    were incorrectly permitted in ORDER BY. (Bug #12626418)

  * Mishandling of NO_BACKSLASH_ESCAPES SQL mode within stored
    procedures on slave servers could cause replication failures.
    (Bug #12601974)

  * With ONLY_FULL_GROUP_BY SQL mode enabled, a query that uses
    GROUP BY on a column derived from a subquery in the FROM
    clause failed with a column isn't in GROUP BY error, if the
    query was in a view. (Bug #11923239)

  * Attempting to execute ALTER TABLE on a temporary MERGE table
    having an underlying temporary table rendered the MERGE table
    unusable, unless the ALTER TABLE specified a new list of
    underlying tables. (Bug #11764786, Bug #57657)

  * When used with the --xml option, mysqldump --routines failed
    to dump any stored routines, triggers, or events. (Bug
    #11760384, Bug #52792)

  * A HAVING clause in a query using MIN() or MAX() was sometimes
    ignored. (Bug #11760517, Bug #52935)
    References: See also Bug #11758970, Bug #51242, Bug #11759718,
    Bug #52051.

  * It was possible in the event of successive failures for
    mysqld_safe to restart quickly enough to consume excessive
    amounts of CPU. Now, on systems that support the sleep and
    date system utilities, mysqld_safe checks to see whether it
    has restarted more than 5 times in the current second, and if
    so, waits 1 second before attempting another restart. (Bug
    #11761530, Bug #54035)

  * It was possible on replication slaves where FEDERATED tables
    were in use to get timeouts on long-running operations, such
    as Error 1160 Got an error writing communication packets. The
    FEDERATED tables did not need to be replicated for the issue
    to occur. (Bug #11758931, Bug #51196)
    References: See also Bug #12896628, Bug #61790.

  * Previously, .OLD files were not included among the files
    deleted by DROP DATABASE. Files with this extension are now
    also deleted by the statement. (Bug #11751736, Bug #42708)

  * If an attempt to initiate a statement failed, the issue could
    not be reported to the client because it was not prepared to
    receive any error messages prior to the execution of any
    statement. Since the user could not execute any queries, they
    were simply disconnected without providing a clear error.
    After the fix for this issue, the client is prepared for an
    error as soon as it attempts to initiate a statement, so that
    the error can be reported prior to disconnecting the user.
    (Bug #11755281, Bug #47032)

  * A prepared statement using a view whose definition changed
    between preparation and execution continued to use the old
    definition, which could cause the prepared statement to return
    incorrect results. (Bug #11748352, Bug #36002)

  * Locale information for FORMAT() function instances was lost in
    view definitions. (Bug #63020, Bug #13344643)

  * mysqlhotcopy failed for databases containing views. (Bug
    #62472, Bug #13006947)

  * The VIO description string was initialized even for
    connections where it was unneeded. (Bug #62285, Bug #12951586)

  * The embedded server crashed when argc = 0. (Bug #57931, Bug
    #12561297)

  * The handle_segfault() signal-handler code in mysqld could
    itself crash due to calling unsafe functions. (Bug #54082, Bug
    #11761576)

  * UPDATE IGNORE returned an incorrect count for number of rows
    updated when there were duplicate-key conflicts in a
    multiple-table update. (Bug #59715, Bug #11766576)

  * The optimizer mishandled STRAIGHT_JOIN used with nested joins;
    for example, by not evaluating tables in the specified order.
    (Bug #59487, Bug #11766384, Bug #43368, Bug #11752239, Bug
    #60080, Bug #11766858)

  * A subquery involved in a comparison requiring a character set
    conversion caused an error that resulted in a server crash.
    (Bug #59185, Bug #11766143)

  * Assigning the result of a subquery to a user variable raised
    an assertion when the outer query included DISTINCT and GROUP
    BY. (Bug #57196, Bug #11764371)

  * On Windows, pasting multiple-line input including a CRLF
    terminator on the last line into the mysql client resulted in
    the first character of the last line being changed, resulting
    in erroneous statements. (Bug #60901, Bug #12589167)

  * If tables were locked by LOCK TABLES ... READ in another
    session, SET GLOBAL read_only = 1 failed to complete. (Bug
    #57612, Bug #11764747)

  * The contents of the shared and shared-compat RPM packages had
    been changed in versions 5.5.6 and 5.6.1 to avoid the overlap
    which they traditionally had (and still have in MySQL 5.0 and
    5.1). However, the RPM meta information had not been changed
    in accordance, and so RPM still assumed a conflict between
    shared and shared-compat RPM packages. This has been fixed.
    (Bug #60855, Bug #12368215)
    References: See also Bug #56150.

  * The result of SUBSTRING_INDEX() could be missing characters
    when used as an argument to conversion functions such as
    LOWER(). (Bug #60166, Bug #11829861)

  * A confusing CREATE TABLE error message was improved. (Bug
    #54963, Bug #11762377)

  * For comparisons containing out-of-range constants, the
    optimizer permitted warnings to leak through to the client,
    even though it accounted for the range issue internally. (Bug
    #56962, Bug #11764155)

  * Enabling myisam_use_mmap could cause the server to crash. (Bug
    #48726, Bug #11756764)

  * On Windows, the server incorrectly constructed the full path
    name of the plugin binary for INSTALL PLUGIN and CREATE
    FUNCTION ... SONAME. (Bug #45549, Bug #11754014)

  * Using myisamchk with the sort recover method to repair a table
    having fixed-width row format could cause the row pointer size
    to be reduced, effectively resulting in a smaller maximum data
    file size. (Bug #48848, Bug #11756869)

  * myisam_sort_buffer_size could not be set larger than 4GB on
    64-bit systems. (Bug #45702, Bug #11754145)

  * For MEMORY tables, a scan of a HASH index on a VARCHAR column
    could fail to find some rows if the index was on a prefix of
    the column. (Bug #47704, Bug #11755870)

  * The stored routine cache was subject to a small memory leak
    that over time or with many routines being used could result
    in out-of-memory errors. (Bug #44585, Bug #11753187)

  * Due to improper locking, concurrent inserts into an ARCHIVE
    table at the same time as repair and check operations on the
    table resulted in table corruption. (Bug #37280, Bug
    #11748748)

  * Under some circumstances, the result of SUBSTRING_INDEX()
    incorrectly depended on the contents of the previous row. (Bug
    #42404, Bug #11751514)

  * Setting an event to DISABLED status and with the ON COMPLETION
    NOT PRESERVE attribute caused it to be dropped at the next
    server restart. (Bug #37666, Bug #11748899)

  * Stored functions could produce an error message that referred
    to ORDER BY even though the offending statement within the
    function had no such clause. (Bug #35410, Bug #11748187)

  * The decision about how to sort a result set could be reported
    incorrectly by EXPLAIN for some statements, causing Using
    filesort or Using temporary to be reported when they should
    not have been or vice versa. This could occur for statements
    that included index hints, that had the form SELECT
    SQL_BIG_RESULT ... GROUP BY, that used SQL_CALC_FOUND_ROWS
    with LIMIT, or that used GROUP BY, ORDER BY, and LIMIT.

MySQL Community Server 5.1.62 has been released

Karen Langford — 2012-03-22T23:45:20

Dear MySQL users,

MySQL Server 5.1.62, a new version of the popular Open Source
Database Management System, has been released. MySQL 5.1.62 is
recommended for use on production systems.

For an overview of what's new in MySQL 5.1, please see

http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html

For information on installing MySQL 5.1.62 on new servers or upgrading
to MySQL 5.1.62 from previous MySQL releases, please see

http://dev.mysql.com/doc/refman/5.1/en/installing.html

MySQL Server is available in source and binary form for a number of
platforms from our download pages at

http://dev.mysql.com/downloads/

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

For information on open issues in MySQL 5.1, please see the errata
list at

http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html

The following section lists the changes in the MySQL source code since
the previous released version of MySQL 5.1. It may also be viewed
online at

http://dev.mysql.com/doc/refman/5.1/en/news-5-1-62.html

Enjoy!

=======================================================================
D.1.1. Changes in MySQL 5.1.62 (21 March, 2012)

    Functionality Added or Changed

      * yaSSL was upgraded from version 1.7.2 to 2.2.0.

    Bugs Fixed

      * Security Fix: Bug #13510739 and Bug #63775 were fixed.

      * Incompatible Change: An earlier change (in MySQL 5.1.59 and
        5.5.16) was found to modify date-handling behavior in General
        Availability-status series (MySQL 5.1 and 5.5). This change
        has been reverted.
        The change was that several functions became more strict when
        passed a DATE() function value as their argument, thus they
        rejected incomplete dates with a day part of zero. These
        functions were affected: CONVERT_TZ(), DATE_ADD(), DATE_SUB(),
        DAYOFYEAR(), LAST_DAY(), TIMESTAMPDIFF(), TO_DAYS(),
        TO_SECONDS()
        (http://dev.mysql.com/doc/refman/5.5/en/date-and-time-function
        s.html#function_to-seconds), WEEK(), WEEKDAY(), WEEKOFYEAR(),
        YEARWEEK(). The previous behavior has been restored. (Bug
        #13458237)

      * Important Change: InnoDB Storage Engine: When a row grew in
        size due to an UPDATE operation, other (non-updated) columns
        could be moved to off-page storage so that information about
        the row still fit within the constraints of the InnoDB page
        size. The pointer to the new allocated off-page data was not
        set up until the pages were allocated and written, potentially
        leading to lost data if the system crashed while the column
        was being moved out of the page. The problem was more common
        with tables using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED
        along with the Barracuda file format, particularly with the
        innodb_file_per_table setting enabled, because page allocation
        operations are more common as the .ibd tablespace files are
        extended. Still, the problem could occur with any combination
        of InnoDB version, file format, and row format.
        A related issue was that during such an UPDATE operation, or
        an INSERT operation that reused a delete-marked record, other
        transactions could see invalid data for the affected column,
        regardless of isolation level.
        The fix corrects the order of operations for moving the column
        data off the original page and replacing it with a pointer.
        Now if a crash occurs at the precise moment when the column
        data is being transferred, the transfer will not be re-run
        during crash recovery.
        In MySQL 5.1, this fix applies to the InnoDB Plugin, but not
        the built-in InnoDB storage engine. (Bug #13721257, Bug
        #12612184, Bug #12704861)

      * InnoDB Storage Engine: An erroneous assertion could occur, in
        debug builds only, when creating an index on a column
        containing zero-length values (that is, ''). (Bug #13654923)

      * InnoDB Storage Engine: A DDL operation such as ALTER TABLE ...
        ADD COLUMN could stall, eventually timing out with an Error
        1005: Can't create table message referring to
        fil_rename_tablespace. (Bug #13636122, Bug #62100, Bug #63553)

      * InnoDB Storage Engine: References to C preprocessor symbols
        and macros HAVE_purify, UNIV_INIT_MEM_TO_ZERO, and
        UNIV_SET_MEM_TO_ZERO were removed from the InnoDB source code.
        They were only used in debug builds instrumented for Valgrind.
        They are replaced by calls to the UNIV_MEM_INVALID() macro.
        (Bug #13418934)

      * InnoDB Storage Engine: A DDL operation for an InnoDB table
        could cause a busy MySQL server to halt with an assertion
        error:
InnoDB: Failing assertion: trx->error_state == DB_SUCCESS
        The error occurred if the DDL operation was run while all 1023
        undo slots were in use by concurrent transactions. This error
        was less likely to occur in MySQL 5.5 and 5.6, because raising
        the number of InnoDB undo slots increased the number of
        simultaneous transactions (corresponding to the number of undo
        slots) from 1K to 128K. (Bug #12739098, Bug #62401)

      * InnoDB Storage Engine: With 1024 concurrent InnoDB
        transactions running concurrently and the
        innodb_file_per_table setting enabled, a CREATE TABLE
        operation for an InnoDB table could fail. The .ibd file from
        the failed CREATE TABLE was left behind, preventing the table
        from being created later, after the load had dropped.
        The fix adds error handling to delete the erroneous .ibd file.
        This error was less likely to occur in MySQL 5.5 and 5.6,
        because raising the number of InnoDB undo slots increased the
        number of simultaneous transactions needed to trigger the bug,
        from 1K to 128K. (Bug #12400341)

      * InnoDB Storage Engine: When copying a partitioned InnoDB table
        from a Linux system to a Windows system, you could encounter
        this error:
101115 14:19:53 [ERROR] Table .\test\d has no primary key in InnoDB d
ata
dictionary, but has one in MySQL!
        Normally, the solution to copy InnoDB tables from Linux to
        Windows is to create the tables on Linux with the
        lower_case_table_names option enabled. Partitioned tables,
        with #P# appended to the filename, were not covered by that
        solution. (Bug #11765438, Bug #58406)

      * InnoDB Storage Engine: Server startup could produce an error
        for temporary tables using the InnoDB storage engine, if the
        path in the $TMPDIR variable ended with a / character. The
        error log would look like:
120202 19:21:26  InnoDB: Operating system error number 2 in a file op
eration.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
120202 19:21:26  InnoDB: Error: trying to open a table, but could not

InnoDB: open the tablespace file './t/#sql7750_1_0.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
        The workaround for the problem was to create a similar
        temporary table again, copy its .frm file to tmpdir under the
        name mentioned in the error message (for example, #sql123.frm)
        and restart mysqld with tmpdir set to its normal value without
        a trailing slash, for example /var/tmp. On startup, MySQL
        would see the .frm file and issue DROP TABLE for the orphaned
        temporary table. (Bug #11754376, Bug #45976)

      * A query that used an index on a CHAR column referenced in a
        BETWEEN clause could return invalid results. (Bug #13463488,
        Bug #63437)

      * When the optimizer performed conversion of DECIMAL values
        while evaluating range conditions, it could produce incorrect
        results. (Bug #13453382)

      * When used with the --xml option, mysqldump --routines failed
        to dump any stored routines, triggers, or events. (Bug
        #11760384, Bug #52792)

      * It was possible on replication slaves where FEDERATED tables
        were in use to get timeouts on long-running operations, such
        as Error 1160 Got an error writing communication packets. The
        FEDERATED tables did not need to be replicated for the issue
        to occur. (Bug #11758931, Bug #51196)
        References: See also Bug #12896628, Bug #61790.

      * If an attempt to initiate a statement failed, the issue could
        not be reported to the client because it was not prepared to
        receive any error messages prior to the execution of any
        statement. Since the user could not execute any queries, they
        were simply disconnected without providing a clear error.
        After the fix for this issue, the client is prepared for an
        error as soon as it attempts to initiate a statement, so that
        the error can be reported prior to disconnecting the user.
        (Bug #11755281, Bug #47032)

      * Using myisamchk with the sort recover method to repair a table
        having fixed-width row format could cause the row pointer size
        to be reduced, effectively resulting in a smaller maximum data
        file size. (Bug #48848, Bug #11756869)

      * Due to improper locking, concurrent inserts into an ARCHIVE
        table at the same time as repair and check operations on the
        table resulted in table corruption. (Bug #37280, Bug
        #11748748)

Thanks,
MySQL RE Team
Database Group, Oracle.

MySQL Community Server 5.5.22 has been released

Hery Ramilison — 2012-03-22T23:40:25

Dear MySQL users,

MySQL 5.5.22 is a new version of the 5.5 production release of the
world's most popular open source database. MySQL 5.5.22 is recommended
for use on production systems.

MySQL 5.5 includes several high-impact enhancements to improve the
performance and scalability of the MySQL Database, taking advantage of
the latest multi-CPU and multi-core hardware and operating systems. In
addition, with release 5.5, InnoDB is now the default storage engine for
the MySQL Database, delivering ACID transactions, referential integrity
and crash recovery by default.

MySQL 5.5 also provides a number of additional enhancements including:

     - Significantly improved performance on Windows, with various
       Windows specific features and improvements
     - Higher availability, with new semi-synchronous replication and
       Replication Heart Beat
     - Improved usability, with Improved index and table partitioning,
       SIGNAL/RESIGNAL support and enhanced diagnostics, including a new
       Performance Schema monitoring capability.

For a more complete look at what's new in MySQL 5.5, please see the
following resources:

MySQL 5.5 is GA, Interview with Tomas Ulin:
http://dev.mysql.com/tech-resources/interviews/thomas-ulin-mysql-55.html

Documentation:
     http://dev.mysql.com/doc/refman/5.5/en/mysql-nutshell.html

Whitepaper: What's New in MySQL 5.5:
http://dev.mysql.com/why-mysql/white-papers/mysql-wp-whatsnew-mysql-55.php

If you are running a MySQL production level system, we would like to
direct your attention to MySQL Enterprise Edition, which includes the
most comprehensive set of MySQL production, backup, monitoring,
modeling, development, and administration tools so businesses can
achieve the highest levels of MySQL performance, security and uptime.
     http://mysql.com/products/enterprise/

For information on installing MySQL 5.5.22 on new servers, please see
the MySQL installation documentation at
     http://dev.mysql.com/doc/refman/5.5/en/installing.html

For upgrading from previous MySQL releases, please see the important
upgrade considerations at:
     http://dev.mysql.com/doc/refman/5.5/en/upgrading.html

MySQL Database 5.5.22 is available in source and binary form for a
number of platforms from our download pages at:
     http://dev.mysql.com/downloads/mysql/

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 in the MySQL source code since
the previous released version of MySQL 5.5. It may also be viewed
online at:
     http://dev.mysql.com/doc/refman/5.5/en/news-5-5-22.html

Enjoy!


Changes in MySQL 5.5.22 (21 March 2012)

  Functionality Added or Changed

    * InnoDB Storage Engine: A deprecation warning is now issued
      when --ignore-builtin-innodb is used. (Bug #13586262)

    * yaSSL was upgraded from version 1.7.2 to 2.2.0.

  Bugs Fixed

    * Important Change: InnoDB Storage Engine: When a row grew in
      size due to an UPDATE operation, other (non-updated) columns
      could be moved to off-page storage so that information about
      the row still fit within the constraints of the InnoDB page
      size. The pointer to the new allocated off-page data was not
      set up until the pages were allocated and written, potentially
      leading to lost data if the system crashed while the column
      was being moved out of the page. The problem was more common
      with tables using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED
      along with the Barracuda file format, particularly with the
      innodb_file_per_table setting enabled, because page allocation
      operations are more common as the .ibd tablespace files are
      extended. Still, the problem could occur with any combination
      of InnoDB version, file format, and row format.
      A related issue was that during such an UPDATE operation, or
      an INSERT operation that reused a delete-marked record, other
      transactions could see invalid data for the affected column,
      regardless of isolation level.
      The fix corrects the order of operations for moving the column
      data off the original page and replacing it with a pointer.
      Now if a crash occurs at the precise moment when the column
      data is being transferred, the transfer will not be re-run
      during crash recovery.
      In MySQL 5.1, this fix applies to the InnoDB Plugin, but not
      the built-in InnoDB storage engine. (Bug #13721257, Bug
      #12612184, Bug #12704861)

    * InnoDB Storage Engine: An erroneous assertion could occur, in
      debug builds only, when creating an index on a column
      containing zero-length values (that is, ''). (Bug #13654923)

    * InnoDB Storage Engine: A DDL operation such as ALTER TABLE ...
      ADD COLUMN could stall, eventually timing out with an Error
      1005: Can't create table message referring to
      fil_rename_tablespace. (Bug #13636122, Bug #62100, Bug #63553)

    * InnoDB Storage Engine: A DDL operation for an InnoDB table
      could cause a busy MySQL server to halt with an assertion
      error:
       InnoDB: Failing assertion: trx->error_state == DB_SUCCESS
      The error occurred if the DDL operation was run while all 1023
      undo slots were in use by concurrent transactions. This error
      was less likely to occur in MySQL 5.5 and 5.6, because raising
      the number of InnoDB undo slots increased the number of
      simultaneous transactions (corresponding to the number of undo
      slots) from 1K to 128K. (Bug #12739098, Bug #62401)

    * InnoDB Storage Engine: Server startup could produce an error
      for temporary tables using the InnoDB storage engine, if the
      path in the $TMPDIR variable ended with a / character. The
      error log would look like:
       120202 19:21:26  InnoDB: Operating system error number 2 in
        InnoDB: a file operation.
        InnoDB: The error means the system cannot find the path
        InnoDB: specified.
        InnoDB: If you are installing InnoDB, remember that you
        InnoDB: must create directories yourself, InnoDB does not
        InnoDB: create them.
        120202 19:21:26  InnoDB: Error: trying to open a table, but
        InnoDB: could not open the tablespace file
        InnoDB: './t/#sql7750_1_0.ibd'!
        InnoDB: Have you moved InnoDB .ibd files around without
        InnoDB: using the commands DISCARD TABLESPACE and IMPORT
        InnoDB: TABLESPACE?
        InnoDB: It is also possible that this is a temporary
        InnoDB: table #sql...,
        InnoDB: and MySQL removed the .ibd file for this.
      The workaround for the problem was to create a similar
      temporary table again, copy its .frm file to tmpdir under the
      name mentioned in the error message (for example, #sql123.frm)
      and restart mysqld with tmpdir set to its normal value without
      a trailing slash, for example /var/tmp. On startup, MySQL
      would see the .frm file and issue DROP TABLE for the orphaned
      temporary table. (Bug #11754376, Bug #45976)

    * Replication: Statements that wrote to tables with
      AUTO_INCREMENT columns based on an unordered SELECT from
      another table could lead to the master and the slave going out
      of sync, as the order in which the rows are retrieved from the
      table may differ between them. Such statements include any
      INSERT ... SELECT, REPLACE ... SELECT, or CREATE TABLE ...
      SELECT statement. Such statements are now marked as unsafe for
      statement-based replication, which causes the execution of one
      to throw a warning, and forces the statement to be logged
      using the row-based format if the logging format is MIXED.
      (Bug #11758263, Bug #50440)

    * myisam_sort_buffer_size could not be set larger than 4GB on
      64-bit systems. (Bug #45702, Bug #11754145)

    * Due to improper locking, concurrent inserts into an ARCHIVE
      table at the same time as repair and check operations on the
      table resulted in table corruption. (Bug #37280, Bug
      #11748748)

On behalf of the MySQL Build Team,

Hery Ramilison
MySQL/ORACLE Release Engineering Team

MySQL Connector/Net 6.5.4 GA has been released

Reggie Burnett — 2012-03-08T14:11:14

MySQL Connector/Net 6.5.4 has gone GA!  This is the first 
production-ready version of our new 6.5 connector and we are very 
excited about it.  Connector/Net is an all-managed .NET driver for MySQL 
and is the best solution for your MySQL and .NET data access needs.

Version 6.5.4 includes full support for MySQL server versions 5.0-5.6 
and includes some exciting new features such as:

  * Much improved partial trust support.  Hosting providers can now
    configure their trust policies exactly the way they are configured
    for SQL Server and your application can run without trouble in
    partial/medium trust.
  * Auto-completion support in the Visual Studio editor.  We have
    integrated a brand new parser into our Visual Studio work and we are
    jut getting started showing it's benefits. Open up a VS editor start
    typing your SQL and you'll see what i mean.
  * Command injection support!  Need to override some command that is
    being run from deep within your application but don't want to
    recompile?  Need to force a certain value to be returned in a
    situation for testing?  Command injection is here to help.
  * Exception interception support!  This can help when your app is
    throwing some exception and you want to trap it. You can trap these
    errors and recover from them or log them in some other way.  The
    choice is yours!

We are very excited about this release and look forward to your feedback!

It is now available in source and binary form from 
http://dev.mysql.com/downloads/connector/net/6.5.html#downloads and 
mirror sites (note that not all mirror sites may be up to date at this 
point-if you can't find this version on some mirror, please try again 
later or choose another download site.)

The release is also available for download on My Oracle Support (MOS).  
http://support.oracle.com

Enjoy and thanks for the support!

MySQL Connector/Net 6.5.3 has been released

Reggie Burnett — 2012-02-27T20:52:07

MySQL Connector/Net 6.5.3, a new version of the all-managed .NET driver 
for MySQL has been released.  This is the second of our two Release 
Candidate (RC) releases.  As is the case with all non-GA releases, it 
should not be used in any production environment.  It is appropriate for 
use with MySQL server versions 5.0-5.6

It is now available in source and binary form from 
http://dev.mysql.com/downloads/connector/net/#downloads and mirror sites 
(note that not all mirror sites may be up to date at this point-if you 
can't find this version on some mirror, please try again later or choose 
another download site.)

The 6.5 release of MySQL Connector/Net brings new features such as

  * Exception and command injector support
  * Millseconds support
  * Better partial-trust support
  * Better intellisense including auto-completion when editing stored
    procedures or .mysql files

We have posted a series of posts to our blog outlining these new 
features.  If you are testing 6.5 we are planning on building our final 
GA package in a few days so please file any outstanding bug reports you 
have so we can consider them.

You can find our team blog at http://blogs.oracle.com/MySQLOnWindows.  
You can also post questions on our forums at http://forums.mysql.com/.

Enjoy and thanks for the support!

MySQL Community Server 5.5.21 has been released

Hery Ramilison — 2012-02-21T05:35:32

Dear MySQL users,

MySQL 5.5.21 is a new version of the 5.5 production release of the
world's most popular open source database. MySQL 5.5.21 is recommended
for use on production systems.

MySQL 5.5 includes several high-impact enhancements to improve the
performance and scalability of the MySQL Database, taking advantage of
the latest multi-CPU and multi-core hardware and operating systems. In
addition, with release 5.5, InnoDB is now the default storage engine for
the MySQL Database, delivering ACID transactions, referential integrity
and crash recovery by default.

MySQL 5.5 also provides a number of additional enhancements including:

     - Significantly improved performance on Windows, with various
       Windows specific features and improvements
     - Higher availability, with new semi-synchronous replication and
       Replication Heart Beat
     - Improved usability, with Improved index and table partitioning,
       SIGNAL/RESIGNAL support and enhanced diagnostics, including a new
       Performance Schema monitoring capability.

For a more complete look at what's new in MySQL 5.5, please see the
following resources:

MySQL 5.5 is GA, Interview with Tomas Ulin:
http://dev.mysql.com/tech-resources/interviews/thomas-ulin-mysql-55.html

Documentation:
     http://dev.mysql.com/doc/refman/5.5/en/mysql-nutshell.html

Whitepaper: What's New in MySQL 5.5:
http://dev.mysql.com/why-mysql/white-papers/mysql-wp-whatsnew-mysql-55.php

If you are running a MySQL production level system, we would like to
direct your attention to MySQL Enterprise Edition, which includes the
most comprehensive set of MySQL production, backup, monitoring,
modeling, development, and administration tools so businesses can
achieve the highest levels of MySQL performance, security and uptime.
     http://mysql.com/products/enterprise/

For information on installing MySQL 5.5.21 on new servers, please see
the MySQL installation documentation at
     http://dev.mysql.com/doc/refman/5.5/en/installing.html

For upgrading from previous MySQL releases, please see the important
upgrade considerations at:
     http://dev.mysql.com/doc/refman/5.5/en/upgrading.html

MySQL Database 5.5.21 is available in source and binary form for a
number of platforms from our download pages at:
     http://dev.mysql.com/downloads/mysql/

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 in the MySQL source code since
the previous released version of MySQL 5.5.  It may also be viewed
online at:
     http://dev.mysql.com/doc/refman/5.5/en/news-5-5-21.html

Enjoy!

Changes in MySQL 5.5.21 (17 February 2012)

Functionality Added or Changed

   * A new CMake option, MYSQL_PROJECT_NAME, can be set on Windows
     or Mac OS X to be used in the project name. (Bug #13551687)

Bugs Fixed

   * Performance: InnoDB Storage Engine: Memory allocation for
     InnoDB tables was reorganized to reduce the memory overhead
     for large numbers of tables or partitions, avoiding situations
     where the "resident set size" could grow regardless of FLUSH
     TABLES statements. The problem was most evident for tables
     with large row size. Some of the memory that was formerly
     allocated for every open table is now allocated only when the
     table is modified for the first time. (Bug #11764622, Bug
     #57480)

   * Incompatible Change: An earlier change (in MySQL 5.1.59 and
     5.5.16) was found to modify date-handling behavior in General
     Availability-status series (MySQL 5.1 and 5.5). This change
     has been reverted.
     The change was that several functions became more strict when
     passed a DATE() function value as their argument, thus they
     rejected incomplete dates with a day part of zero. These
     functions were affected: CONVERT_TZ(), DATE_ADD(), DATE_SUB(),
     DAYOFYEAR(), LAST_DAY(), TIMESTAMPDIFF(), TO_DAYS(),
     TO_SECONDS(), WEEK(), WEEKDAY(), WEEKOFYEAR(), YEARWEEK(). The
     previous behavior has been restored. (Bug #13458237)

   * InnoDB Storage Engine: A Valgrind error was fixed in the
     function os_aio_init(). (Bug #13612811)

   * InnoDB Storage Engine: The server could crash when creating an
     InnoDB temporary table under Linux, if the $TMPDIR setting
     points to a tmpfs filesystem and innodb_use_native_aio is
     enabled, as it is by default in MySQL 5.5.4 and higher. The
     entry in the error log looked like:
       101123  2:10:59  InnoDB: Operating system error number
                                22 in a file operation.
       InnoDB: Error number 22 means 'Invalid argument'.
     The crash occurred because asynchronous I/O is not supported
     on tmpfs in some Linux kernel versions. The workaround was to
     turn off the innodb_use_native_aio setting or use a different
     temporary directory. The fix causes InnoDB to turn off the
     innodb_use_native_aio setting automatically if it detects that
     the temporary file directory does not support asynchronous
     I/O. (Bug #13593888, Bug #11765450, Bug #58421)

   * InnoDB Storage Engine: References to C preprocessor symbols
     and macros HAVE_purify, UNIV_INIT_MEM_TO_ZERO, and
     UNIV_SET_MEM_TO_ZERO were removed from the InnoDB source code.
     They were only used in debug builds instrumented for Valgrind.
     They are replaced by calls to the UNIV_MEM_INVALID() macro.
     (Bug #13418934)

   * InnoDB Storage Engine: The MySQL server could halt with an
     assertion error:
       InnoDB: Failing assertion: page_get_n_recs(page) > 1
     Subsequent restarts could fail with the same error. The error
     occurred during a purge
     (http://dev.mysql.com/doc/refman/5.5/en/glossary.html#glos_pur
     ge) operation involving the InnoDB change buffer
     (http://dev.mysql.com/doc/refman/5.5/en/glossary.html#glos_cha
     nge_buffer). The workaround was to set the configuration
     option innodb_change_buffering=inserts. (Bug #13413535, Bug
     #61104)

   * InnoDB Storage Engine: With 1024 InnoDB transactions running
     concurrently and the innodb_file_per_table setting enabled,
     a CREATE TABLE operation for an InnoDB table could fail. The
     .ibd file from the failed CREATE TABLE was left behind,
     preventing the table from being created later, after the load
     had dropped.
     The fix adds error handling to delete the erroneous .ibd file.
     This error was less likely to occur in MySQL 5.5 and 5.6,
     because raising the number of InnoDB undo slots increased the
     number of simultaneous transactions needed to trigger the bug,
     from 1K to 128K. (Bug #12400341)

   * Replication: Executing mysqlbinlog with the --start-position=N
     option, where N was equal either to 0 or to a value greater
     than the length of the dump file, caused it to crash.
     This issue was introduced in MySQL 5.5.18 by the fix for Bug
     #32228 and Bug #11747416. (Bug #13593869, Bug #64035)

   * Replication: On Windows replication slave hosts, STOP SLAVE
     took an excessive length of time to complete when the master
     was down. (Bug #11752315, Bug #43460)

   * A query that used an index on a CHAR column referenced in a
     BETWEEN clause could return invalid results. (Bug #13463488,
     Bug #63437)

   * Expressions that compared a BIGINT column with any non-integer
     constant were performed using integers rather than decimal or
     float values, with the result that the constant could be
     truncated. This could lead to any such comparison that used <,
     >, <=, >=, =, !=/<>, IN, or BETWEEN yielding false positive or
     negative results. (Bug #13463415, Bug #11758543, Bug #63502,
     Bug #50756)

   * When the optimizer performed conversion of DECIMAL values
     while evaluating range conditions, it could produce incorrect
     results. (Bug #13453382)

   * When running mysqldump with both the --single-transaction and
     --flush-logs options, the flushing of the log performed an
     implicit COMMIT (see Section 12.3.3, "Statements That Cause an
     Implicit Commit"), causing more than one transaction to be
     used and thus breaking consistency. (Bug #12809202, Bug
     #61854)

   * It was possible in the event of successive failures for
     mysqld_safe to restart quickly enough to consume excessive
     amounts of CPU. Now, on systems that support the sleep and
     date system utilities, mysqld_safe checks to see whether it
     has restarted more than 5 times in the current second, and if
     so, waits 1 second before attempting another restart. (Bug
     #11761530, Bug #54035)

   * When used with the --xml option, mysqldump --routines failed
     to dump any stored routines, triggers, or events. (Bug
     #11760384, Bug #52792)

   * It was possible on replication slaves where FEDERATED tables
     were in use to get timeouts on long-running operations, such
     as Error 1160 Got an error writing communication packets. The
     FEDERATED tables did not need to be replicated for the issue
     to occur. (Bug #11758931, Bug #51196)
     References: See also Bug #12896628, Bug #61790.

   * If an attempt to initiate a statement failed, the issue could
     not be reported to the client because it was not prepared to
     receive any error messages prior to the execution of any
     statement. Since the user could not execute any queries, they
     were simply disconnected without providing a clear error.
     After the fix for this issue, the client is prepared for an
     error as soon as it attempts to initiate a statement, so that
     the error can be reported prior to disconnecting the user.
     (Bug #11755281, Bug #47032)

   * Using myisamchk with the sort recover method to repair a table
     having fixed-width row format could cause the row pointer size
     to be reduced, effectively resulting in a smaller maximum data
     file size. (Bug #48848, Bug #11756869)

   * On Windows, the server incorrectly constructed the full path
     name of the plugin binary for INSTALL PLUGIN and CREATE
     FUNCTION ... SONAME. (Bug #45549, Bug #11754014)

   * The stored routine cache was subject to a small memory leak
     that over time or with many routines being used could result
     in out-of-memory errors. (Bug #44585, Bug #11753187)


On behalf of the MySQL Build Team,

Hery Ramilison
MySQL/ORACLE Release Engineering Team

MySQL Connector/Net 6.5.2 RC1 has been released

Reggie Burnett — 2012-02-15T15:57:00

MySQL Connector/Net 6.5.2, a new version of the all-managed .NET driver 
for MySQL has been released.  This is the first of our two Release 
Candidate (RC) releases.  As is the case with all non-GA releases, it 
should not be used in any production environment.  It is appropriate for 
use with MySQL server versions 5.0-5.6

It is now available in source and binary form from 
http://dev.mysql.com/downloads/connector/net/#downloads and mirror sites 
(note that not all mirror sites may be up to date at this point-if you 
can't find this version on some mirror, please try again later or choose 
another download site.)

The 6.5 release of MySQL Connector/Net brings new features such as

  * Exception and command injector support
  * Millseconds support
  * Better partial-trust support
  * Better intellisense including auto-completion when editing stored
    procedures or .mysql files

These features are not yet documented in the shipping documentation.  We 
have posted a series of posts to our blog outlining these new features.

You can find our team blog at http://blogs.oracle.com/MySQLOnWindows.  
You can also post questions on our forums at http://forums.mysql.com/.

Enjoy and thanks for the support!

MySQL Cluster 7.2 GA has been released

Bernhard Ocklin — 2012-02-15T14:20:08

Dear MySQL Cluster users,

We are proud to announce to you the MySQL Cluster 7.2.4 GA release, the
first 7.2 production version of the write-scalable, fully transactional cluster 
database.  MySQL Cluster 7.2.4 is recommended for use on production systems.

MySQL Cluster 7.2 includes several high-impact changes to improve scalability
and performance. These changes allow next generation web services to run
complex queries with up to 70 times higher join performance compared to previous 
versions of Cluster.

Cluster 7.2 is now based on the latest MySQL Server 5.5 GA and is certified to run in 
virtualized environments.

MySQL Cluster 7.2 also provides a number of other new enhancements,
including:

- Native Memcached API 
- Multi-Site Clustering
- Simplified Active-Active Replication
- Consolidated Privileges

Together with MySQL Cluster 7.2 we are also presenting to you a new version
of MySQL Cluster Manager 1.1.4 GA. The new version of MySQL Cluster Manager  
improves scalability and simplifies Cluster provisioning and administration further.

For a more complete look at what's new in MySQL 7.2, please see

http://dev.mysql.com/tech-resources/articles/mysql-cluster-7.2-ga.html

For information on installing MySQL Cluster 7.2 on new servers, please see the
MySQL installation documentation at

http://dev.mysql.com/doc/refman/5.5/en/mysql-cluster-installation.html

MySQL Cluster 7.2 can be upgraded online and without downtime from previous 
MySQL Cluster releases. MySQL Cluster 7.2 is available in source and binary form 
for a number of platforms from our download pages at:

http://dev.mysql.com/downloads/cluster/

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.

If you have questions, need help with the community version of MySQL Cluster
you are invited to make use of the MySQL Cluster forum:

http://forums.mysql.com/list.php?25

We welcome and appreciate your feedback, bug reports, bug fixes,
patches, etc.:

http://forge.mysql.com/wiki/Contributing

The following link lists the changes in the MySQL source code since
the previous released version of MySQL Cluster 7.2. It may be viewed
online at:

http://dev.mysql.com/doc/refman/5.5/en/mysql-cluster-news-7-2.html

Let me take the chance to thank the entire MySQL Cluster team for all the great and 
hard work to make the best MySQL Cluster release ever. 

Enjoy!

Bernd Ocklin

MySQL Connector/ODBC 3.51.30 is available!

Lawrenty Novitsky — 2012-02-03T14:41:40

Dear MySQL users,

MySQL Connector/ODBC 3.51.30, a new version of the ODBC driver for the
MySQL database management system, has been released. This release is
the latest release of the 3.51 series and is suitable for use with any
MySQL version since 4.1 (It will not work with 4.0 or earlier
releases.)

The release is now available in source and binary form for a number of
platforms from our download pages at

   http://dev.mysql.com/downloads/connector/odbc/3.51.html

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

Enjoy!

On behalf of MySQL Connectors and Build teams at Oracle

Lawrin Novitsky & Kent Boortz

==============================================================================

   Functionality added or changed:
   * MyODBC queries log is written to %TEMP%\myodbc.sql, or to 
C:\myodbc.sql if
     TEMP is not defined.


   Bugs fixed:
   * SQLPrepare causes Prefetch of table. (Bug #46411)
   * SQL_ATTR_MAX_ROWS make some SELECT statement invalid. (Bug #49726)
   * In some cases TIMESTAMP field could be described as SQL_NO_NULLS.
   (Bug #13532987)
   * SQLFetch has to return an error if indicator pointer is NULL for 
NULL value.
   (Bug #13542600)
   * A failure on one stmt causes another stmt to fail. (Bug 
#13097201/#62657)
   * A DSN created by the setup dialog could contain notation that was not
     recognized by the driver. (Bug #13647492)

     Built using MySQL 5.5.18.

MySQL Connector/ODBC 5.1.10 is available!

Lawrenty Novitsky — 2012-02-02T20:59:10

Dear MySQL users,

MySQL Connector/ODBC 5.1.10, a new version of the ODBC driver for the
MySQL database management system, has been released. This release is
the latest release of the 5.1 series and is suitable for use with any
MySQL version since 4.1 (It will not work with 4.0 or earlier
releases.)

The release is now available in source and binary form for a number of
platforms from our download pages at

   http://dev.mysql.com/downloads/connector/odbc/5.1.html

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

Enjoy!

The MySQL Connectors team at Oracle

==============================================================================

   Functionality added or changed:

   Bugs fixed:
   * In some cases TIMESTAMP field could be described as SQL_NO_NULLS.
     (Bug #13532987)
   * SQLFetch has to return an error if StrLen_Indicator pointer is NULL 
for NULL value.
     (Bug #13542600)
   * A failure on one statement causes another statement to fail. (Bug 
#13097201/#62657)

MySQL Enterprise Monitor 2.3.9 Is Now GA!

Andy Bang — 2012-02-01T01:05:11

We are pleased to announce that MySQL Enterprise Monitor 2.3.9 is now
available for download on the My Oracle Support (MOS) web site as our
latest GA release.  It will also be available via the Oracle Software
Delivery Cloud in approximately 1-2 weeks.  This is a maintenance
release that fixes a number of bugs.  You can find more information on
the contents of this release in the changelog:

     http://dev.mysql.com/doc/mysql-monitor/2.3/en/mem-news-2-3-9.html

You will find binaries for the new release on My Oracle Support:

     https://support.oracle.com

Choose the "Patches & Updates" tab, and then use the "Product or
Family (Advanced Search)" feature.

You will also find the binaries on the Oracle Software Delivery Cloud
in approximately 1-2 weeks:

     http://edelivery.oracle.com/

Choose "MySQL Database" as the Product Pack and you will find the
Enterprise Monitor along with other MySQL products.

More information on MySQL Enterprise and the Enterprise Monitor can be
found here:

     http://www.mysql.com/products/enterprise/
     http://www.mysql.com/products/enterprise/advisors.html
     http://www.mysql.com/products/enterprise/query.html
     http://forums.mysql.com/index.php?137

If you are not a MySQL Enterprise customer and want try the Monitor
and Query Analyzer using our 30-day free customer trial, go to
http://www.mysql.com/trials, or contact Sales at
http://www.mysql.com/about/contact/sales.html?s=corporate.

If you haven't looked at 2.3 recently, please do so now and let us
know what you think.

Thanks and Happy Monitoring!

   - The MySQL Enterprise Tools Development Team

MySQL Connector/Net 6.5.1 Beta has been released

Reggie Burnett — 2012-01-26T03:54:08

MySQL Connector/Net 6.5.1, a new version of the all-managed .NET driver 
for MySQL has been released.  This is a beta release of our newest 
connector and comes with several new features.  It is of beta quality 
and should not be used in any production environment.  It is appropriate 
for use with MySQL server versions 5.0-5.6

It is now available in source and binary form from 
http://dev.mysql.com/downloads/connector/net/#downloads and mirror sites 
(note that not all mirror sites may be up to date at this point-if you 
can't find this version on some mirror, please try again later or choose 
another download site.)

This new versions brings new features such as

  * Exception and command injector support
  * Millseconds support
  * Better partial-trust support
  * Better intellisense including auto-completion when editing stored
    procedures or .mysql files

These features are not yet documented in the shipping documentation.  We 
have posted a series of posts to our blog outlining these new features.

You can find our team blog at http://blogs.oracle.com/MySQLOnWindows.  
You can also post questions on our forums at http://forums.mysql.com/.

Enjoy and thanks for the support!

MySQL Community Server 5.1.61 has been released

Karen Langford — 2012-01-11T17:13:25

Dear MySQL users,

MySQL Server 5.1.61, a new version of the popular Open Source
Database Management System, has been released. MySQL 5.1.61 is
recommended for use on production systems.

For an overview of what's new in MySQL 5.1, please see

http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html

For information on installing MySQL 5.1.61 on new servers or upgrading
to MySQL 5.1.61 from previous MySQL releases, please see

http://dev.mysql.com/doc/refman/5.1/en/installing.html

MySQL Server is available in source and binary form for a number of
platforms from our download pages at

http://dev.mysql.com/downloads/

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

For information on open issues in MySQL 5.1, please see the errata
list at

http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html

The following section lists the changes in the MySQL source code since
the previous released version of MySQL 5.1. It may also be viewed
online at

http://dev.mysql.com/doc/refman/5.1/en/news-5-1-61.html

Enjoy!

=======================================================================
D.1.1. Changes in MySQL 5.1.61 (10 January, 2012)


    Bugs Fixed

      * InnoDB Storage Engine: Issuing INSERT...ON DUPLICATE KEY
        statements for InnoDB tables from concurrent threads could
        cause a deadlock
        (http://dev.mysql.com/doc/refman/5.5/en/glossary.html#glos_dea
        dlock), particularly with the INSERT...ON DUPLICATE KEY UPDATE
        form. The fix avoids deadlocks caused by the same row being
        accessed by more than one transaction. Deadlocks could still
        occur when multiple rows are inserted and updated
        simultaneously by different transactions in inconsistent
        order; those types of deadlocks require the standard error
        handling on the application side, of re-trying the
        transaction. (Bug #11759688, Bug #52020)

      * An incorrect InnoDB assertion could cause the server to halt.
        This issue only affected debug builds. The assertion
        referenced the source file btr0pcur.ic and the variable
        cursor->pos_state. (Bug #13358468)

      * The handle_segfault() signal-handler code in mysqld could
        itself crash due to calling unsafe functions. (Bug #54082, Bug
        #11761576)

      * ARCHIVE tables with NULL columns could cause server crashes or
        become corrupt under concurrent load. (Bug #51252, Bug
        #11758979)

      * Enabling myisam_use_mmap could cause the server to crash. (Bug
        #48726, Bug #11756764)

      * Concurrent access to ARCHIVE tables could cause corruption.
        (Bug #42784, Bug #11751793)


Thanks,
MySQL RE Team
Database Group, Oracle.