Dear MySQL users,

MySQL for Visual Studio 2.0.2 M1 is the first development release of the
MySQL for Visual Studio 2.0 series.  This series adds support for the
new X DevAPI. The X DevAPI enables application developers to write code
that combines the strengths of the relational and document models using
a modern, NoSQL-like syntax that does not assume previous experience
writing traditional SQL.

To learn more about how to write applications using the X DevAPI, see
http://dev.mysql.com/doc/x-devapi-userguide/en/. For more information about
how the X DevAPI is implemented in MySQL for Visual Studio, and its usage,
see http://dev.mysql.com/docs/refman-5.7/en/mysql-shell-visual-studio.html.

Please note that the X DevAPI requires at least MySQL Server version
5.7.12 or higher with the X Plugin enabled. For general documentation
about how to get started using MySQL as a document store, see
http://dev.mysql.com/doc/refman/5.7/en/document-store.html.

Changes in MySQL for Visual Studio 2.0.2 (2016-04-11, Milestone 1)

   Known limitation of this release: SSL connections are not yet
   supported.

   Functionality Added

     * Added support for Visual Studio 2015 with .NET Framework
       4.6.

     * Added support for Python scripts. Python code can now be
       executed and can interact with the X DevAPI introduced in
       MySQL 5.7.12, where relational and document data can be
       queried. Extended views (Field Types, Query Statistics and
       Execution Plan) are not available for Python in this version.

     * Added new result views for document-based (JSON) data
       returned by MySQL X, where data can be viewed in a grid,
       tree, or text representation.

     * Added a new Javascript query type, in addition to SQL
       type that was already present. JavaScript code can be
       executed and interact with the X DevAPI introduced in
       MySQL 5.7.12, where relational and document data can be
       queried. Extended views (Field Types, Query Statistics
       and Execution Plan) are not available for JavaScript in
       this version.

     * Enhanced the user interface for query scripts where
       different views for result sets returned by the MySQL
       Server are now available, similar to the ones in MySQL
       Workbench. For SQL scripts the available views are:

          + Results: shows returned data

          + Field Types: shows information about columns of a
            result set, such as names, data types, character
            sets, and more.

          + Query Statistics: shows information about the
            executed query, such as execution times, processed
            rows, index and temporary tables usage, and more.

          + Execution Plan: shows a text-view explanation of the
            query execution performed internally by the MySQL
            Server.

     * After MySQL scripts are executed, each result set
       returned by the MySQL Server is now displayed in a
       separate Results tab. In previous versions, only the last
       result set returned by MySQL Server was displayed in the
       Output tab.

     * Added an option to create MySQL scripts directly from a
       MySQL Server instance in the Server Explorer. This
       simplifies the process of creating scripts, as there is
       no longer a requirement to open a connection for each
       script like in previous versions of MySQL for Visual
       Studio.

   Bugs Fixed

     * Fixed the coloring of SQL code so it is readable on any
       VS color theme, like the "Dark" one.


On behalf of the MySQL Release Team 

Dear MySQL users,

MySQL Connector/Net 7.0.2 M1 is the first development release of MySQL
Connector/Net to add support for the new X DevAPI. The X DevAPI enables
application developers to write code that combines the strengths of the
relational and document models using a modern, NoSQL-like syntax that
does not assume previous experience writing traditional SQL.

To learn more about how to write applications using the X DevAPI, see
http://dev.mysql.com/doc/x-devapi-userguide/en/index.html. For more
information about how the X DevAPI is implemented in Connector/Net, see
http://dev.mysql.com/doc/dev/connector-net.

Please note that the X DevAPI requires at least MySQL Server version
5.7.12 or higher with the X Plugin enabled. For general documentation
about how to get started using MySQL as a document store, see
http://dev.mysql.com/doc/refman/5.7/en/document-store.html.


Changes in MySQL Connector/Net 7.0.2 (2016-04-11, Milestone 1)

Functionality Added

* Added support for the new X DevAPI


Nuget packages are available at:
https://www.nuget.org/packages/MySql.Data/7.0.2-DMR
https://www.nuget.org/packages/MySql.Data.Entity/7.0.2-DMR
https://www.nuget.org/packages/MySql.Fabric/7.0.2-DMR
https://www.nuget.org/packages/MySql.Web/7.0.2-DMR

Enjoy and thanks for the support!

On behalf of the MySQL Release Team

Dear MySQL Users,

MySQL Cluster is the distributed, shared-nothing variant of MySQL.
This storage engine provides:

  - In-Memory storage - Real-time performance (with optional
    checkpointing to disk)
  - Transparent Auto-Sharding - Read & write scalability
  - Active-Active/Multi-Master geographic replication
  - 99.999% High Availability with no single point of failure
    and on-line maintenance
  - NoSQL and SQL APIs (including C++, Java, http and Memcached)

MySQL Cluster 7.2.24, has been released and can be downloaded from

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

where you will also find Quick Start guides to help you get your
first MySQL Cluster database up and running.

The release notes are available from

http://dev.mysql.com/doc/relnotes/mysql-cluster/7.2/en/index.html

MySQL Cluster enables users to meet the database challenges of next
generation web, cloud, and communications services with uncompromising
scalability, uptime and agility.

More details can be found at

  http://www.mysql.com/products/cluster/

Enjoy !


==============================================================================
Changes in MySQL Cluster NDB 7.2.24 (5.5.48-ndb-7.2.24) (2016-04-19)

   MySQL Cluster NDB 7.2.24 is a new release of MySQL Cluster,
   incorporating new features in the NDB storage engine, and
   fixing recently discovered bugs in previous MySQL Cluster NDB
   7.2 development releases.

   Obtaining MySQL Cluster NDB 7.2.  MySQL Cluster NDB 7.2
   source code and binaries can be obtained from
   http://dev.mysql.com/downloads/cluster/.

   This release also incorporates all bugfixes and changes made
   in previous MySQL Cluster releases, as well as all bugfixes
   and feature changes which were added in mainline MySQL 5.5
   through MySQL 5.5.48 (see Changes in MySQL 5.5.48 (2016-02-05)(
   http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-48.html)).

   Bugs Fixed

     * Restoration of metadata with ndb_restore -m occasionally
       failed with the error message Failed to create index...
       when creating a unique index. While diagnosing this
       problem, it was found that the internal error
       PREPARE_SEIZE_ERROR (a temporary error) was reported as
       an unknown error. Now in such cases, ndb_restore retries
       the creation of the unique index, and PREPARE_SEIZE_ERROR
       is reported as NDB Error 748 Busy during read of event
       table. (Bug #21178339)
       References: See also Bug #22989944.

Dear MySQL Users,

MySQL Cluster is the distributed, shared-nothing variant of MySQL.
This storage engine provides:

  - In-Memory storage - Real-time performance
  - Transparent Auto-Sharding - Read & write scalability
  - Active-Active/Multi-Master geographic replication
  - 99.999% High Availability with no single point of failure
    and on-line maintenance
  - NoSQL and SQL APIs (including C++, Java, http, Memcached
    and JavaScript/Node.js)

MySQL Cluster 7.4 makes significant advances in performance;
operational efficiency (such as enhanced reporting and faster restarts
and upgrades) and conflict detection and resolution for active-active
replication between MySQL Clusters.

MySQL Cluster 7.4.11, has been released and can be downloaded from

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

where you will also find Quick Start guides to help you get your
first MySQL Cluster database up and running.

The release notes are available from

http://dev.mysql.com/doc/relnotes/mysql-cluster/7.4/en/index.html

MySQL Cluster enables users to meet the database challenges of next
generation web, cloud, and communications services with uncompromising
scalability, uptime and agility.

More details can be found at

http://www.mysql.com/products/cluster/

Enjoy !


Changes in MySQL Cluster NDB 7.4.11 (5.6.29-ndb-7.4.11) (2016-04-20)

   MySQL Cluster NDB 7.4.11 is a new release of MySQL Cluster
   7.4, based on MySQL Server 5.6 and including features in
   version 7.4 of the NDB storage engine, as well as fixing
   recently discovered bugs in previous MySQL Cluster releases.

   Obtaining MySQL Cluster NDB 7.4.  MySQL Cluster NDB 7.4
   source code and binaries can be obtained from
http://dev.mysql.com/downloads/cluster/.

   For an overview of changes made in MySQL Cluster NDB 7.4, see
   What is New in MySQL Cluster NDB 7.4
   (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is-new-7-4.html).

   This release also incorporates all bugfixes and changes made
   in previous MySQL Cluster releases, as well as all bugfixes
   and feature changes which were added in mainline MySQL 5.6
   through MySQL 5.6.29 (see Changes in MySQL 5.6.29
   (2016-02-05)
   (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-29.html)).


   Functionality Added or Changed

     * Cluster API: Added the
       Ndb::setEventBufferQueueEmptyEpoch() method, which makes
       it possible to enable queuing of empty events (event type
       TE_EMPTY). (Bug #22157845)

   Bugs Fixed

     * Important Change: The minimum value for the
       BackupDataBufferSize data node configuration parameter
       has been lowered from 2 MB to 512 KB. The default and
       maximum values for this parameter remain unchanged. (Bug
       #22749509)

     * Microsoft Windows: Performing ANALYZE TABLE on a table
       having one or more indexes caused ndbmtd to fail with an
       InvalidAttrInfo error due to signal corruption. This
       issue occurred consistently on Windows, but could also be
       encountered on other platforms. (Bug #77716, Bug
       #21441297)

     * During node failure handling, the request structure used
       to drive the cleanup operation was not maintained
       correctly when the request was executed. This led to
       inconsistencies that were harmless during normal
       operation, but these could lead to assertion failures
       during node failure handling, with subsequent failure of
       additional nodes. (Bug #22643129)

     * The previous fix for a lack of mutex protection for the
       internal TransporterFacade::deliver_signal() function was
       found to be incomplete in some cases. (Bug #22615274)
       References: This bug was introduced by Bug #77225, Bug
       #21185585.

     * When setup of the binary log as an atomic operation on
       one SQL node failed, this could trigger a state in other
       SQL nodes in which they appeared to detect the SQL node
       participating in schema change distribution, whereas it
       had not yet completed binary log setup. This could in
       turn cause a deadlock on the global metadata lock when
       the SQL node still retrying binary log setup needed this
       lock, while another mysqld had taken the lock for itself
       as part of a schema change operation. In such cases, the
       second SQL node waited for the first one to act on its
       schema distribution changes, which it was not yet able to
       do. (Bug #22494024)

     * Duplicate key errors could occur when ndb_restore was run
       on a backup containing a unique index. This was due to
       the fact that, during restoration of data, the database
       can pass through one or more inconsistent states prior to
       completion, such an inconsistent state possibly having
       duplicate values for a column which has a unique index.
       (If the restoration of data is preceded by a run with
       --disable-indexes and followed by one with
       --rebuild-indexes, these errors are avoided.)
       Added a check for unique indexes in the backup which is
       performed only when restoring data, and which does not
       process tables that have explicitly been excluded. For
       each unique index found, a warning is now printed. (Bug
       #22329365)

     * Restoration of metadata with ndb_restore -m occasionally
       failed with the error message Failed to create index...
       when creating a unique index. While disgnosing this
       problem, it was found that the internal error
       PREPARE_SEIZE_ERROR (a temporary error) was reported as
       an unknown error. Now in such cases, ndb_restore retries
       the creation of the unique index, and PREPARE_SEIZE_ERROR
       is reported as NDB Error 748 Busy during read of event
       table. (Bug #21178339)
       References: See also Bug #22989944.

     * When setting up event logging for ndb_mgmd on Windows,
       MySQL Cluster tries to add a registry key to
       HKEY_LOCAL_MACHINE, which fails if the user does not have
       access to the registry. In such cases ndb_mgmd logged the
       error Could neither create or open key, which is not
       accurate and which can cause confusion for users who may
       not realize that file logging is available and being
       used. Now in such cases, ndb_mgmd logs a warning Could
       not create or access the registry key needed for the
       application to log to the Windows EventLog. Run the
       application with sufficient privileges once to create the
       key, or add the key manually, or turn off logging for
       that application. An error (as opposed to a warning) is
       now reported in such cases only if there is no available
       output at all for ndb_mgmd event logging. (Bug #20960839)

     * NdbDictionary metadata operations had a hard-coded 7-day
       timeout, which proved to be excessive for short-lived
       operations such as retrieval of table definitions. This
       could lead to unnecessary hangs in user applications
       which were difficult to detect and handle correctly. To
       help address this issue, timeout behaviour is modified so
       that read-only or short-duration dictionary interactions
       have a 2-minute timeout, while schema transactions of
       potentially long duration retain the existing 7-day
       timeout.
       Such timeouts are intended as a safety net: In the event
       of problems, these return control to users, who can then
       take corrective action. Any reproducible issue with
       NdbDictionary timeouts should be reported as a bug. (Bug
       #20368354)

     * Optimization of signal sending by buffering and sending
       them periodically, or when the buffer became full, could
       cause SUB_GCP_COMPLETE_ACK signals to be excessively
       delayed. Such signals are sent for each node and epoch,
       with a minimum interval of TimeBetweenEpochs; if they are
       not received in time, the SUMA buffers can overflow as a
       result. The overflow caused API nodes to be disconnected,
       leading to current transactions being aborted due to node
       failure. This condition made it difficult for long
       transactions (such as altering a very large table), to be
       completed. Now in such cases, the ACK signal is sent
       without being delayed. (Bug #18753341)

     * An internal function used to validate connections failed
       to update the connection count when creating a new Ndb
       object. This had the potential to create a new Ndb
       object for every operation validating the connection,
       which could have an impact on performance, particularly
       when performing schema operations. (Bug #80750, Bug
       #22932982)

     * When an SQL node was started, and joined the schema
       distribution protocol, another SQL node, already waiting
       for a schema change to be distributed, timed out during
       that wait. This was because the code incorrectly assumed
       that the new SQL node would also acknowledge the schema
       distribution even though the new node joined too late to
       be a participant in it.
       As part of this fix, printouts of schema distribution
       progress now always print the more significant part of a
       bitmask before the less significant; formatting of
       bitmasks in such printouts has also been improved. (Bug
       #80554, Bug #22842538)

     * MySQL Cluster did not compile correctly with Microsoft
       Visual Studio 2015, due to a change from previous
       versions in the VS implementation of the _vsnprintf()
       function. (Bug #80276, Bug #22670525)

     * When setting CPU spin time, the value was needlessly cast
       to a boolean internally, so that setting it to any
       nonzero value yielded an effective value of 1. This
       issue, as well as the fix for it, apply both to setting
       the SchedulerSpinTimer parameter and to setting spintime
       as part of a ThreadConfig parameter value. (Bug #80237,
       Bug #22647476)

     * Processing of local checkpoints was not handled correctly
       on Mac OS X, due to an uninitialized variable. (Bug
       #80236, Bug #22647462)

     * A logic error in an if statement in
       storage/ndb/src/kernel/blocks/dbacc/DbaccMain.cpp
       rendered useless a check for determining whether
       ZREAD_ERROR should be returned when comparing operations.
       This was detected when compiling with gcc using
       -Werror=logical-op. (Bug #80155, Bug #22601798)
       References: This bug was introduced by Bug #21285604.

     * The ndb_print_file utility failed consistently on Solaris
       9 for SPARC. (Bug #80096, Bug #22579581)

     * Builds with the -Werror and -Wextra flags (as for release
       builds) failed on SLES 11. (Bug #79950, Bug #22539531)

     * When using CREATE INDEX to add an index on either of two
       NDB tables sharing circular foreign keys, the query
       succeeded but a temporary table was left on disk,
       breaking the foreign key constraints. This issue was also
       observed when attempting to create an index on a table in
       the middle of a chain of foreign keys---that is, a table
       having both parent and child keys, but on different
       tables. The problem did not occur when using ALTER TABLE
       to perform the same index creation operation; and
       subsequent analysis revealed unintended differences in
       the way such operations were performed by CREATE INDEX.
       To fix this problem, we now make sure that operations
       performed by a CREATE INDEX statement are always handled
       internally in the same way and at the same time that the
       same operations are handled when performed by ALTER TABLE
       or DROP INDEX. (Bug #79156, Bug #22173891)

     * NDB failed to ignore index prefixes on primary and unique
       keys, causing CREATE TABLE and ALTER TABLE statements
       using them to be rejected. (Bug #78441, Bug #21839248)

     * Compilation of MySQL with Visual Studio 2015 failed in
       ConfigInfo.cpp, due to a change in Visual Studio's
       handling of spaces and concatenation.

     * Cluster API: Executing a transaction with an
       NdbIndexOperation based on an obsolete unique index
       caused the data node process to fail. Now the index is
       checked in such cases, and if it cannot be used the
       transaction fails with an appropriate error. (Bug #79494,
       Bug #22299443)

     * Integer overflow could occur during client handshake
       processing, leading to a server exit. (Bug #22722946)

     * For busy servers, client connection or communication
       failure could occur if an I/O-related system call was
       interrupted. The mysql_options() C API function now has a
       MYSQL_OPT_RETRY_COUNT option to control the number of
       retries for interrupted system calls. (Bug #22336527)
       References: See also Bug #22389653.

Regards
-Sree 

We're very happy to announce the release of MySQL Enterprise Transparent
Data Encryption (TDE), included with MySQL Enterprise Edition.

MySQL Enterprise Transparent Data Encryption (TDE) protects your
critical data by enabling data-at-rest encryption in the database. It
protects the privacy of your information, prevents data breaches and
helps meet regulatory requirements including the Payment Card Industry
Data Security Standard (PCI DSS), Health Insurance Portability and
Accountability Act (HIPAA) and numerous others.  MySQL Enterprise TDE
highlights:

* Data at Rest Encryption- Strong AES 256 encryption for your MySQL
  InnoDB Tables

* Transparent to applications and users - No application code, schema or
  data type changes

* Transparent to DBAs - Keys are hidden from DBAs, no configuration
  changes

* Key Management - Keys are securely stored away from the data.  Key
  rotation is simple and secure

Use MySQL Enterprise TDE to meet regulatory requirements to protect data:

* PCI . DSS: Payment Card Data (esp. 3.5 and 3.6)

* HIPAA: Privacy of Health Data

* Sarbanes Oxley

* EU Data Protection Directive: Protection of Personal Data

* Data Protection Act (UK): Protection of Personal Data

For additional details, please join us for the upcoming webinar:
* MySQL Security . Discover the New Transparent Data Encryption:
  http://www.mysql.com/news-and-events/web-seminars/mysql-security-transparent-data-encryption/

MySQL Enterprise TDE is included in MySQL 5.7.12. Download MySQL Enterprise TDE from:
* My Oracle Support: https://support.oracle.com 
* Oracle Software Delivery Cloud: https://edelivery.oracle.com/

Documentation
* MySQL Transparent Data Encryption documentation:
  http://dev.mysql.com/doc/refman/5.7/en/innodb-tablespace-encryption.html

If you have any questions or encounter any problems:
* Open a support ticket: https://support.oracle.com
* File a bug report: http://bugs.mysql.com/

If you're not already a MySQL Enterprise Edition customer, start your
free 30-day trial today: https://www.mysql.com/trials/

Thank you for using MySQL!

Dear MySQL users,

MySQL Enterprise Backup v3.12.3, a new version of the online MySQL backup
tool, is now available for download from the My Oracle Support (MOS) website
as our latest GA release. This release will be available on eDelivery (OSDC)
after the next upload cycle. MySQL Enterprise Backup is a commercial
extension to the MySQL family of products.

A brief summary of the changes in MySQL Enterprise Backup (MEB)
version 3.12.3 is given below.

Changes in MySQL Enterprise Backup 3.12.3      (2016-05-09)

Functionality Added or Changed

     * There are two enhancements on how you can configure SSL
       host authenticate for cloud operations of MySQL
       Enterprise Backup:

          + A CA certificate directory, in addition to the
            default folder of the system, can now be specified
            with the new --cloud-ca-path option.

          + mysqlbackup now supports authentication using a CA
            bundle file, whose path is specified by the new
            --cloud-ca-info option.
       See descriptions for the two new options in Cloud Storage
       Options
       (http://dev.mysql.com/doc/mysql-enterprise-backup/3.12/en
       /backup-cloud-options.html) for more information. (Bug
       #22761313)

     * mysqlbackup used to sync all data from the buffer cache
       to the hard disk before closing all tables at the end of
       a backup operation. However, for systems with slow
       storage devices and databases with a huge number of
       tables, the sync would increase the backup time
       significantly. To shorten the backup time for those and
       other cases, starting with this release, the sync is no
       longer performed automatically. Users who want the sync
       to be performed at the end of a backup have to use the
       new --free-os-buffer option.
       (Bug #22561345)

     * To avoid completing a backup of a slave server when
       temporary tables are still open on the slave, which will
       cause the restored slave server to be in an inconsistent
       replication state, mysqlbackup now has a new mechanism
       for ensuring that all temporary tables have already been
       closed before finishing a slave backup. See "Temporary
       tables on statement-based replication (SBR) slave" for
       details. A new option, --safe-slave-backup-timeout, has
       been created for specifying the time mysqlbackup will
       wait for all temporary tables to be closed before it
       times out. (Bug #19158516)

     * The compression options
       (http://dev.mysql.com/doc/mysql-enterprise-backup/3.12/en
       /backup-compression-options.html) can now be used with
       the backup-and-apply-log operation to create a directory
       backup that is prepared and compressed; the backup can
       then be restored using the copy-back operation and the
       --uncompress option. (Bug #18913565)

     * During a copy-back-and-apply-log or a copy-back
       operation, mysqlbackup now checks that the specified
       values for the innodb_log_files_in_group and
       innodb_log_file_size options match those recorded in the
       backup's backup-my.cnf file, and throws an error if the
       values do not match. This prevents mysqlbackup from
       restoring the backup with the wrong parameters, which
       would result in a restored server that cannot be started.
       (Bug #14751027)

   Bugs Fixed

     * An incremental or compressed backup might fail with an
       end-of-file error if there are large data files that kept
       growing during the backup. It was because, as the data
       files expanded, the write process altered the file sizes,
       which confused the read process for the same files. With
       this fix, file sizes and information on them is now
       properly handled. (Bug #23048004)
       References: This issue is a regression of: Bug #19149210.

     * Restoring a cloud backup sometimes failed with Error 18:
       Transferred a partial file. It was because mysqlbackup
       created wrong range headers for its REST requests for
       partial downloads. (Bug #23035334)

     * mysqlbackup crashed when a validate operation was
       performed on an incremental backup that contained an undo
       tablespace but not a system tablespace. It was because
       mysqlbackup did not handle data files for undo
       tablespaces properly, and this fix corrects that. (Bug
       #22960185)

     * Offline backups using MySQL Enterprise Backup
       sometimes failed, with occasional crashes of
       mysqlbackup. (Bug #22595461)

     * For a backup of a slave server, the file name of the
       master server's binary log and the binary log position
       for starting replication, which were stored in the file
       backup_varaibles.txt in the backup as masterlog_file and
       masterlog_pos, got corrupted when an apply-log or
       copy-back-and-apply-log operation was applied to the
       backup. (Bug #22329306)

     * validate operations for backup images and backup-to-image
       operations left over a temporary folder (/tmp) after the
       operations were over. (Bug #20912357)

     * Backups failed for a server that had once been started
       with the --log-bin option and then restarted without it.
       It was because mysqlbackup, seeing the old binary log
       index file on the server, looked in vain for the current
       binary log files, reported that they could not be found,
       and then quitted. With this fix, mysqlbackup checks if
       binary logging is enabled for the server; if it is not,
       mysqlbackup then skips the copying of the binary log into
       the backup. (Bug #20873010)

 Regards
 -Sreedhar S 

Hello all,

MySQL Connector Java 5.1.39, a maintenance release of the production 5.1
branch, has been released. Connector/J is a Type-IV pure-Java JDBC driver
for MySQL, supporting the JDBC 4.2 API. It is suitable for use with MySQL
server versions 5.5, 5.6, and 5.7.

MySQL Connector Java is available in source and binary form from the
Connector/J download page at
http://dev.mysql.com/downloads/connector/j/5.1.html

MySQL Connector Java (Commercial) is available for download on the My
Oracle Support (MOS) website. This release will be available on
eDelivery (OSDC) in next month's upload cycle.

As always, we recommend that you check the "CHANGES" file in the
download archive to be aware of changes in behavior that might affect
your application.

MySQL Connector/J 5.1.39 includes the following general bug fixes and
improvements, also available in more detail on
http://dev.mysql.com/doc/relnotes/connector-j/en/news-5-1-39.html :

Changes in MySQL Connector/J 5.1.39 (2016-05-09)

Functionality Added or Changed

* For MySQL server 5.7.5 and later, the EOF packet in the
MySQL server/client protocol has been deprecated and
replaced by the OK packet. The change is now supported by
Connector/J. (Bug #23212347)

Bugs Fixed

* Connector/J hung, returned a NullPointerException, or
returned an incorrect exception when using result sets
with the properties TYPE_FORWARD_ONLY and
CONCUR_UPDATABLE. It was due to an inaccurate check for
the cursor for the result set. This fix makes sure
Connector/J checks accurately on whether a cursor has
been requested, both when executing a statement and
fetching its results. (Bug #23201930)

* When using server-side prepared statements with
profileSQL=true and useInformationSchema=true, an
SQLException (" ResultSet is from UPDATE. No Data")
occurred when the client tried to advance to the next row
in the result set. This was due to a failure of an
internal query for metadata, which is now prevented by
this fix. (Bug #23188498)

* LoadBalanceConnectionGroupManager.removeHost() was not
removing hosts as expected. This fix tries to ensure that
host removals will be successful under different
situations. (Bug #22848249)
References: See also: Bug #22678872.

* For connections with useCursorFetch=true and fetch size
set with defaultFetchSize or setFetchSize, if data from a
TIME and a BLOB data column was selected together,
corrupted value for the TIME data was returned. (Bug
#22833410, Bug #80522)

* For a load-balanced connection, an
ArrayIndexOutOfBoundsException was thrown when
ConnectionGroupManager.removeHost() was called. It was
due to an error in
LoadBalancedConnectionProxy.removeHost(), which has now
been fixed. (Bug #22730682)

* A Fabric connection threw a NullPointerException when all
hosts have been removed from its host list, or when the
internal load-balanced connection became null due to
inconsistency of the replication connection. This fix
adds to Connector/J the abilities to handle those
situations. Also, a new connection property,
loadBalanceHostRemovalGracePeriod, has been introduced,
which sets the grace period for waiting to remove the
currently active host from a load-balanced connection.
See the entry for the new property in Driver/Datasource
Class Names, URL Syntax and Configuration Properties for
Connector/J
(http://dev.mysql.com/doc/connector-j/5.1/en/connector-j-
reference-configuration-properties.html) for details.
(Bug #22678872)
References: See also: Bug #22848249.

* FabricMySQLDataSource.getConnection() threw a null
pointer exception when a master failover took place. (Bug
#22598938)

* The OSGi manifest file in the Connector/J JAR file did
not expose the MySQL Fabric packages, so the
Fabric-related classes could not be resolved even though
they were present in the JAR file. (Bug #22385172)

* With some Tomcat web applications, when Connector/J
connects to the server with useLegacyDatetimeCode=false
without setting serverTimeZone, a NullPointerException
was returned. This was because the timezone property file
for Connector/J was loaded by the bootstrap class loader,
which did not know the location of the property file and
thus failed to load it. This fix avoids the problem by
making Connector/J use the same class loader for both the
property file and the Connector/J classes. (Bug
#22353759, Bug #79343)

* When using JDBC 4.2 and with the connection property
cachePrepStmts set to "true," after a prepared statement
had been cached, rerunning the SQL statement resulted in
a pre-JDBC 4.2 PreparedStatement object being
instantiated. This fix prevents the problem by having the
PreparedStatement instantiated by a factory instead of a
constructor method. (Bug #22352812, Bug #79598)

* At every connection, Connector/J got the sql_mode
variable from the server and tried to parse it as a
number; because sql_mode is not a number (except for very
old versions of MySQL), an NumberFormatException was
always thrown and then caught by the code. This fix
refactored the code to avoid the unnecessary throwing and
catching of the error. (Bug #21181466, Bug #77171)

* When inserting multiple timestamp values into a table
with useLegacyDatetimeCode=false and useCursorFetch=true,
after a null value had been inserted, further inserts
could not change a timestamp's value. This fix makes sure
the binding of the value is reset before a new insert
takes place. (Bug #20685487, Bug #75956)

* The exception message in CallableStatement() for
incorrect output parameter registration gave little
detail and the wrong error code. (Bug #18068303, Bug
#71131)

* Calling getTimestamp() on a timestamp column resulted in
a java.sql.SQLException (Cannot convert value ... to
TIMESTAMP). That was due to the missing metadata for each
row in the ResultSet. This fix ensures that the metadata
is no longer missing. (Bug #16738378, Bug #56479)

* On very fast servers with other third-party components
accessing the data, a ConcurrentModificationException was
sometimes thrown. This fix prevents the exception by
adding a synchronization to
ConnectionImpl.closeAllOpenStatements(), and by
refactoring part of the code inside the method. (Bug
#16736619, Bug #59462)

Documentation
--------------
Online: http://dev.mysql.com/doc/connector-j/5.1/en/

Reporting Bugs
---------------
We welcome and appreciate your feedback and bug reports:
http://bugs.mysql.com/

On Behalf of the MySQL/ORACLE RE Team
Hery Ramilison

Dear MySQL users,

MySQL Enterprise Backup v4.0.1, a new version of the online MySQL backup
tool, is now available for download from the My Oracle Support (MOS) website
as our latest GA release. This release will be available on eDelivery (OSDC)
after the next upload cycle. MySQL Enterprise Backup is a commercial
extension to the MySQL family of products.

MySQL Enterprise Backup v4.0.1 supports only the MySQL server 5.7.9 and above.
For any earlier versions of the MySQL server, please use
MySQL Enterprise Backup 3.12 instead.

A brief summary of the changes in MySQL Enterprise Backup (MEB)
version 4.0.1 is given below.

Changes in MySQL Enterprise Backup 4.0.1    (2016-05-26)


   Functionality Added or Changed

     * There are two enhancements on how you can configure SSL
       host authenticate for cloud operations of MySQL
       Enterprise Backup:

          + A CA certificate directory, in addition to the
            default folder of the system, can now be specified
            with the new --cloud-ca-path option.

          + mysqlbackup now supports authentication using a CA
            bundle file, whose path is specified by the new
            --cloud-ca-info option.
       See descriptions for the two new options in Cloud Storage
       Options
       (http://dev.mysql.com/doc/mysql-enterprise-backup/4.0/en/
       backup-cloud-options.html) for more information. (Bug
       #22761313)

     * mysqlbackup used to sync all data from the buffer cache
       to the hard disk before closing all tables at the end of
       a backup operation. However, for systems with slow
       storage devices and databases with a huge number of
       tables, the sync would increase the backup time
       significantly. To shorten the backup time for those and
       other cases, starting with this release, the sync is no
       longer performed automatically. Users who want the sync
       to be performed at the end of a backup have to use the
       new --free-os-buffer option. (Bug #22561345)

     * MySQL Enterprise Backup now supports backup of slave
       servers in a multi-source replication setup. (Bug
       #21830316, Bug #22283631)

     * To avoid completing a backup of a slave server when
       temporary tables are still open on the slave, which will
       cause the restored slave server to be in an inconsistent
       replication state, mysqlbackup now has a new mechanism
       for ensuring that all temporary tables have already been
       closed before finishing a slave backup. See Temporary
       tables on statement-based replication (SBR) slave
       (http://dev.mysql.com/doc/mysql-enterprise-backup/3.12/en
       /advanced.slave-backup-restore.html#meb-temp-tables-sbr)
       for details. A new option, --safe-slave-backup-timeout,
       has been created for specifying the time mysqlbackup will
       wait for all temporary tables to be closed before it
       times out. (Bug #19158516)

     * The compression options
       (http://dev.mysql.com/doc/mysql-enterprise-backup/4.0/en/
       backup-compression-options.html) can now be used with the
       backup-and-apply-log operation to create a directory
       backup that is prepared and compressed; the backup can
       then be restored using the copy-back operation and the
       --uncompress option. (Bug #18913565)

     * During a copy-back-and-apply-log or a copy-back
       operation, mysqlbackup now checks that the specified
       values for the innodb_log_files_in_group and
       innodb_log_file_size options match those recorded in the
       backup's backup-my.cnf file, and throws an error if the
       values do not match. This prevents mysqlbackup from
       restoring the backup with the wrong parameters, which
       would result in a restored server that cannot be started.
       (Bug #14751027)

     * Values for MASTER_USER and MASTER_PORT are now included
       in the CHANGE MASTER TO statement in the slave
       information file (meta/ibbackup_slave_info) when the
       --slave-info option is used for backing up a slave
       server. (Bug #14213115)

   Bugs Fixed

     * An apply-log operation failed when a RENAME TABLE
       (http://dev.mysql.com/doc/refman/5.7/en/rename-table.html
       ) statement within the redo log was applied to the backup
       even when the renamed table was already included into the
       backup. This fix prevents the problem by making
       mysqlbackup ignore "dirty" (intermediate) log records
       when (a) the new table name is already in used, or (b) if
       the tablespace has not been loaded into memory with the
       old table name. (Bug #23068440)

     * An incremental or compressed backup might fail with an
       end-of-file error if there are large data files that kept
       growing during the backup. It was because, as the data
       files expanded, the write process altered the file sizes,
       which confused the read process for the same files. With
       this fix, file sizes and information on them is now
       properly handled. (Bug #23048004)
       References: This issue is a regression of: Bug #19149210.

     * Restoring a cloud backup sometimes failed with Error 18:
       Transferred a partial file. It was because mysqlbackup
       created wrong range headers for its REST requests for
       partial downloads. (Bug #23035334)

     * mysqlbackup crashed when a validate operation was
       performed on an incremental backup that contained an undo
       tablespace but not a system tablespace. It was because
       mysqlbackup did not handle data files for undo
       tablespaces properly, and this fix corrects that. (Bug
       #22960185)

     * Attempts to restore a compressed image backup using the
       copy-back-and-apply-log command failed with "ERROR:
       InnoDB: Missing MLOG_FILE_NAME or MLOG_FILE_DELETE for
       redo log record ...." It was because the undo tablespaces
       were not loaded, so that the log operations on them
       failed. This fix ensures that the undo tablespaces are
       loaded. (Bug #22914556)

     * If a table had been renamed during a backup operation, it
       sometimes got copied twice into the backup, once under
       its old table name and another time under its new name.
       It was because mysqlbackup, when checking for tables that
       have been changed during the backup process, only checked
       tables by their .ibd file names. With this fix, the
       tablespace ID is also checked, so that a renamed table
       will be recognized as such and will not be copied twice.
       (Bug #22859445)

     * Sometimes, when sizes of the data files kept growing
       during a single-file backup, a broken image backup might
       be produced, causing subsequent commands on it (for
       example, validate or copy-back-and apply-log) to fail. It
       was due to a mismatch of the file size given in the image
       file's header and the actual file size on disk, which is
       now prevented by this fix. (Bug #22613568)

     * Offline backups sometimes failed, with occasional crashes
       of mysqlbackup. (Bug #22595461)

     * For a backup of a slave server, the file name of the
       master server's binary log and the binary log position
       for starting replication, which were stored in the file
       backup_varaibles.txt in the backup as masterlog_file and
       masterlog_pos, got corrupted when an apply-log or
       copy-back-and-apply-log operation was applied to the
       backup. (Bug #22329306)

     * When mysqlbackup came across a file of an unknown file
       type and its path name contained characters that
       mysqlbackup could not convert to the file system
       character set, it threw an error. With this fix,
       mysqlbackup continues with its operation in the situation
       after giving a warning. (Bug #22098742)

     * On Windows platforms, mysqlbackup crashed instead of
       quitting gracefully when the --datadir option was not
       specified for a copy-back or copy-back-and-apply-log
       operation. (Bug #22069093)

     * A backup failed if, towards the end of the backup
       process, mysqlbackup found the binary log file that was
       current at the beginning of the backup had been purged.
       With this fix, mysqlbackup now ignores the fact that the
       file has been purged, resets the log position to the now
       current binary log file, and continues with the backup
       without raising any issues. (Bug #21655145)

     * During a backup, mysqlbackup performed, by default, an
       SQL query to get storage engine information that was to
       be put into the backup_history table. Because the query
       caused all table files on the server to be scanned, it
       consumed a great amount of IO resources when there were
       many tables on the server, resulting sometimes in serious
       performance issues. With this fix, only tables included
       in the backup are scanned, thus reducing the IO stress on
       the server. (Bug #21098174)

     * When creating a compressed backup, mysqlbackup threw an
       error if a table on the server was dropped in the middle
       of the process. With this fix, the dropped table is
       ignored (as it does not need to be restored) and
       mysqlbackup finishes without throwing an error. (Bug
       #21087079)
       References: See also: Bug #18358912.

     * validate operations for backup images and backup-to-image
       operations left over a temporary folder (/tmp) after the
       operations were over. (Bug #20912357)

     * Backups failed for a server that had once been started
       with the --log-bin option and then restarted without it.
       It was because mysqlbackup, seeing the old binary log
       index file on the server, looked in vain for the current
       binary log files, reported that they could not be found,
       and then quitted. With this fix, mysqlbackup checks if
       binary logging is enabled for the server; if it is not,
       mysqlbackup then skips the copying of the binary log into
       the backup. (Bug #20873010)

     * A backup of a slave server failed if, during the backup,
       a relay log file got purged from the slave server (for
       example, due to a log file rotation). With this fix,
       backup continues even if mysqlbackup finds a relay log
       file missing. (Bug #20769891, Bug #76312, Bug #21655314,
       Bug #19255925)

     * When the trace level of mysqlbackup messages was greater
       than "0," if the operation command for mysqlbackup was
       invalid or missing, a stack trace and some error messages
       were printed, which made it look like mysqlbackup had
       crashed. With this fix, a new message is now shown before
       the stack trace, to better explain the situation. (Bug
       #20281022)

     * If an incremental backup had already been applied to a
       directory backup with the apply-incremental-backup
       command and the up-to-date backup was then restored to a
       data directory, it was possible to restore the same
       incremental backup again to the data directory using the
       copy-back-and-apply-log command, potentially causing data
       inconsistencies. With this fix, the incremental data can
       be reapplied only when the --force option is used.
       Without the --force option, the copy-back-and-apply-log
       command skips the apply log operation if the incremental
       backup is a directory backup and throws an error if it is
       an image backup. (Bug #18004179)

Regards
- Sreedhar S 

Dear MySQL Users,

MySQL Cluster is the distributed, shared-nothing variant of MySQL.
This storage engine provides:

  - In-Memory storage - Real-time performance (with optional
    checkpointing to disk)
  - Transparent Auto-Sharding - Read & write scalability
  - Active-Active/Multi-Master geographic replication

  - 99.999% High Availability with no single point of failure
    and on-line maintenance
  - NoSQL and SQL APIs (including C++, Java, http, Memcached
    and JavaScript/Node.js)

MySQL Cluster 7.5.2 DMR can be downloaded from the "Development
Releases" tab at

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

where you will also find Quick Start guides to help you get your
first MySQL Cluster database up and running.

The release notes are available from

  http://dev.mysql.com/doc/relnotes/mysql-cluster/7.5/en/index.html

MySQL Cluster enables users to meet the database challenges of next
generation web, cloud, and communications services with uncompromising
scalability, uptime and agility.

More details can be found at

  http://www.mysql.com/products/cluster/

Enjoy !

Changes in MySQL Cluster NDB 7.5.2 (5.7.12-ndb-7.5.2) (2016-06-01,
Developer Milestone 3)

   MySQL Cluster NDB 7.5.2 is a new release of MySQL Cluster
   7.5, based on MySQL Server 5.7 and including features in
   version 7.5 of the NDB
   (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.html)
   storage engine, as well as fixing recently discovered bugs in
   previous MySQL Cluster releases.

   Obtaining MySQL Cluster NDB 7.5.  MySQL Cluster NDB 7.5
   source code and binaries can be obtained from
   http://dev.mysql.com/downloads/cluster/.

   For an overview of changes made in MySQL Cluster NDB 7.5, see
   What is New in MySQL Cluster NDB 7.5
   (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-what-is
   -new.html).

   This release also incorporates all bugfixes and changes made
   in previous MySQL Cluster releases, as well as all bugfixes
   and feature changes which were added in mainline MySQL 5.7
   through MySQL 5.7.12 (see Changes in MySQL 5.7.12
   (2016-04-11)
   (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-12.h
   tml)).

   Functionality Added or Changed

     * Performance: A deficiency in event buffer memory
       allocation was identified as inefficient and possibly
       leading to undesirable results. This could happen when
       additional memory was allocated from the operating system
       to buffer received event data even when memory had
       already been allocated but remained unused. This is fixed
       by allocating the event buffer memory directly from the
       page allocation memory manager (mmap()), where such
       functionality is offered by the operating system,
       allowing for direct control over the memory such that it
       is in fact returned to the system when released.
       This remimplementation avoids the tendencies of the
       existing one to approach worst-case memory usage,
       maintainence of data structures for a worst-case event
       buffer event count, and useless caching of free memory in
       unusable positions. This work should also help minimize
       the runtime costs of buffering events, minimize heap
       fragmentation, and avoid OS-specific problems due to
       excessive numbers of distinct memory mappings.
       In addition, the relationship between epochs and internal
       EventData objects is now preserved throughout the event
       lifecycle, reception to consumption, thus removing the
       need for iterating, and keeping in synch, two different
       lists representing the epochs and their EventData
       objects.
       As part of this work, better reporting on the relevant
       event buffer metrics is now provided in the cluster logs.
       References: See also: Bug #21651536, Bug #21660947, Bug
       #21661297, Bug #21673318, Bug #21689380, Bug #21809959.

     * ndb_restore now performs output logging for specific
       stages of its operation. (Bug #21097957)

     * An improvement in the hash index implementation used by
       MySQL Cluster data nodes means that partitions may now
       contain more than 16 GB of data for fixed columns, and
       the maximum partition size for fixed column data is now
       increased to 128 TB. The previous limitation originated
       with the DBACC block in the NDB
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.htm
       l) kernel using only 32-bit references to the fixed-size
       part of a row handled in the DBTUP block, even though
       45-bit references were already in use elsewhere in the
       kernel outside the DBACC block; all such references in
       DBACC now use 45-bit pointers instead.
       As part of this work, error messages returned by the
       DBACC kernel block that were overly generic have now been
       improved by making them more specific. (Bug #17465232)

     * The NDB
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.htm
       l) storage engine supports the MySQL JSON
       (http://dev.mysql.com/doc/refman/5.7/en/json.html) data
       type and MySQL JSON functions implemented in MySQL 5.7.8
       and later. This support is subject to the limitation that
       a single NDB table can have at most 3 JSON columns.

     * A number of changes and improvements were made to the
       handling of send threads by NDB
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.htm
       l). The changes are summarized with brief descriptions in
       the following list:

          + Decreased resource requirements for send threads,
            making sure that a given configuration using send
            threads outperforms the same configuration without
            send threads.

          + Made use of otherwise idle threads (other than
            receiver threads) as send threads without incurring
            extra CPU resources in low-load situations.

          + Improved response time for write transactions.

          + Provided for handling of bad configuration data in a
            more graceful manner.

          + Made it possible to measure CPU usage with improved
            real-time reporting from data nodes on their
            resource usage.
       As part of implementing the last item of those just
       listed, a number of new tables providing information
       about CPU and thread activity by node, thread ID, and
       thread type have been added to the ndbinfo
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
       info.html) information database. These tables are listed
       here:

          + cpustat
            (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluste
            r-ndbinfo-cpustat.html): Provides per-second,
            per-thread CPU statistics

          + cpustat_50ms
            (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluste
            r-ndbinfo-cpustat-50ms.html): Shows raw per-thread
            CPU statistics data, gathered every 50ms

          + cpustat_1sec
            (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluste
            r-ndbinfo-cpustat-1sec.html): Provides raw
            per-thread CPU statistics data, gathered each second

          + cpustat_20sec
            (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluste
            r-ndbinfo-cpustat-20sec.html): Displays raw
            per-thread CPU statistics data, gathered every 20
            seconds

          + threads
            (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluste
            r-ndbinfo-threads.html): Shows names and
            descriptions of thread types
       For more information, see The ndbinfo MySQL Cluster
       Information Database
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
       info.html).

     * Rewrote the implementation of the NDB
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.htm
       l) storage engine's global schema lock functionality to
       make use of the metadata lock hooks implemented in the
       MySQL Server in MySQL 5.7.11.

     * A number of improvements provide additional read
       scalability for NDB by making it possible to read tables
       locally. It is now possible to enable reads from any
       replica, rather than from the primary replica only. This
       is disabled by default to remain compatible with previous
       behavior, but can be enabled for a given SQL node using
       the ndb_read_backup
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-opt
       ions-variables.html#sysvar_ndb_read_backup) system
       variable added in this release.
       It also becomes possible to be more flexible about the
       assignment of partitions by setting a fragment count
       type. Possible count types are one per node, one per node
       group, one per Local Data Manager (LDM) per node (this is
       the previous assignment scheme and still the default),
       and one per LDM per node group. This setting can be
       controlled for individual tables by means of a
       FRAGMENT_COUNT_TYPE option embedded in an NDB_TABLE
       comment in CREATE TABLE
       (http://dev.mysql.com/doc/refman/5.7/en/create-table.html
       ) or ALTER TABLE
       (http://dev.mysql.com/doc/refman/5.7/en/alter-table.html)
       .
       Tables using one of the two per-node-group settings for
       the fragment count type can also be fully replicated.
       This requires that the table's fragment count type is
       ONE_PER_NODE_GROUP or ONE_PER_LDM_PER_NODE_GROUP, and can
       be enabled using the option FULLY_REPLICATED=1 within in
       an NDB_TABLE comment. The option can be enabled by
       default for all new NDB tables using the
       ndb_fully_replicated
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-opt
       ions-variables.html#sysvar_ndb_fully_replicated) system
       variable added in this release.
       Settings for table-level READ_BACKUP are also supported
       using the COMMENT="NDB_TABLE=..." syntax. It is also
       possible (and often preferable) to set multiple options
       in one comment within a single CREATE TABLE or ALTER
       TABLE statement. For more information and examples, see
       Setting NDB_TABLE options in table comments
       (http://dev.mysql.com/doc/refman/5.7/en/create-table-ndb-
       table-comment-options.html).
       This release also introduces the ndb_data_node_neighbour
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-opt
       ions-variables.html#sysvar_ndb_data_node_neighbour)
       system variable, which is intended to be employed with
       transaction hinting (and fully-replicated tables), and to
       provide the current SQL node with the ID of a "nearby"
       data node to use. See the description of this variable in
       the documentation for more information.
       References: See also: Bug #18435416.

     * Made the following enhancements and additions to the
       ThreadConfig multithreaded data node (ndbmtd)
       configuration parameter:

          + Added support for non-exclusive CPU locking on
            FreeBSD and Windows using cpubind and cpuset.

          + Added support for exclusive CPU locking on Solaris,
            using cpubind_exclusive and cpuset_exclusive, which
            are added in this release.

          + Added thread prioritzation using thread_prio, which
            is added in this release. thread_prio is supported
            on Linux, FreeBSD, Windows, and Solaris, but the
            exact effects of this setting are platform-specific;
            see the documentation for details.

          + Added support for setting realtime on Windows
            platforms.
       For more information, see the description of the
       ThreadConfig
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
       d-definition.html#ndbparam-ndbmtd-threadconfig) parameter
       in the online documentation.

     * Cluster API: Added the
       Ndb::setEventBufferQueueEmptyEpoch()
       (http://dev.mysql.com/doc/ndbapi/en/ndb-ndb-methods.html#
       ndb-ndb-seteventbufferqueueemptyepoch) method, which
       makes it possible to enable queuing of empty events
       (event type TE_EMPTY). (Bug #22157845)

     * Cluster API: Ndb_free_list_t is a template used in the
       implementation of the NDB API to create a list keeping
       released API objects such as NdbTransaction
       (http://dev.mysql.com/doc/ndbapi/en/ndb-ndbtransaction.ht
       ml), NdbOperation
       (http://dev.mysql.com/doc/ndbapi/en/ndb-ndboperation.html
       ), and NdbRecAttr
       (http://dev.mysql.com/doc/ndbapi/en/ndb-ndbrecattr.html).
       One drawback to this template is that released API
       objects are kept in the list for the lifetime of the
       owning Ndb
       (http://dev.mysql.com/doc/ndbapi/en/ndb-ndb.html) object,
       such that a transient peak in the demand for any object
       causes an effective leak in memory that persists until
       this Ndb object itself has been released.
       This work adds statistics to each Ndb_free_list instance
       which samples the usage of objects maintained by the
       list; now, when objects are released, they can be
       released into the free list, or deallocated, based on the
       collected usage statistics.

   Bugs Fixed

     * Performance: A performance problem was found in an
       internal polling method do_poll() where the polling
       client did not check whether it had itself been woken up
       before completing the poll. Subsequent analysis showed
       that it is sufficient that only some clients in the
       polling queue receive data. do_poll() can then signal
       these clients and give up its polling rights, even if the
       maximum specified wait time (10 ms) has not expired.
       This change allows do_poll() to continue polling until
       either the maximum specified wait time has expired, or
       the polling client itself has been woken up (by receiving
       what it was waiting for). This avoids unnecessary thread
       switches between client threads and thus reduces the
       associated overhead by as much as 10% in the API client,
       resulting in a significant performance improvement when
       client threads perform their own polling. (Bug #81229,
       Bug #23202735)

     * Incompatible Change: When the data nodes are only
       partially connected to the API nodes, a node used for a
       pushdown join may get its request from a transaction
       coordinator on a different node, without (yet) being
       connected to the API node itself. In such cases, the
       NodeInfo object for the requesting API node contained no
       valid info about the software version of the API node,
       which caused the DBSPJ block to assume (incorrectly) when
       aborting to assume that the API node used NDB version
       7.2.4 or earlier, requiring the use of a backward
       compatability mode to be used during query abort which
       sent a node failure error instead of the real error
       causing the abort.
       Now, whenever this situation occurs, it is assumed that,
       if the NDB software version is not yet available, the API
       node version is greater than 7.2.4. (Bug #23049170)

     * Important Change: When started with the --initialize
       (http://dev.mysql.com/doc/refman/5.7/en/server-options.ht
       ml#option_mysqld_initialize) option, mysqld no longer
       enables the NDBCLUSTER
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.htm
       l) storage engine plugin. This change was needed to
       prevent attempted initialization of system databases as
       distributed (rather than as specific to individual SQL
       nodes), which could result in a metadata lock deadlock.
       This fix also brings the behavior of --initialize in this
       regard into line with that of the discontinued
       --bootstrap
       (http://dev.mysql.com/doc/refman/5.7/en/server-options.ht
       ml#option_mysqld_bootstrap) option, which started a
       minimal mysqld instance without enabling NDB. (Bug
       #22758238)

     * Microsoft Windows: ndb_mgmd failed to start on 32-bit
       Windows platforms, due to an issue with calling
       dynamically loaded functions; such issues were also
       likely to occur with other NDB programs using ndb_init().
       It was found that all of the functions used are already
       supported in targeted versions of Windows, so this
       problem is fixed by removing the dynamic loading of these
       functions and using the versions provided by the Windows
       header files instead. (Bug #80876, Bug #23014820)

     * Microsoft Windows: When building MySQL Cluster on Windows
       using more than one parallel build job it was sometimes
       possible for the build to fail because host_info.exe
       could not be be installed. To fix this problem, the
       install_mcc target is now always built prior to the
       host_info target. (Bug #80051, Bug #22566368)

     * Microsoft Windows: Performing ANALYZE TABLE
       (http://dev.mysql.com/doc/refman/5.7/en/analyze-table.htm
       l) on a table having one or more indexes caused ndbmtd to
       fail with an InvalidAttrInfo error due to signal
       corruption. This issue occurred consistently on Windows,
       but could also be encountered on other platforms. (Bug
       #77716, Bug #21441297)

     * Reserved send buffer for the loopback transporter,
       introduced in MySQL Cluster NDB 7.4.8 and used by API and
       management nodes for administrative signals, was
       calculated incorrectly. (Bug #23093656)
       References: This issue is a regression of: Bug #21664515.

     * During a node restart, re-creation of internal triggers
       used for verifying the referential integrity of foreign
       keys was not reliable, because it was possible that not
       all distributed TC and LDM instances agreed on all
       trigger identities. To fix this problem, an extra step is
       added to the node restart sequence, during which the
       trigger identities are determined by querying the current
       master node. (Bug #23068914)
       References: See also: Bug #23221573.

     * Following the forced shutdown of one of the 2 data nodes
       in a cluster where NoOfReplicas=2
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
       d-definition.html#ndbparam-ndbd-noofreplicas), the other
       data node shut down as well, due to arbitration failure.
       (Bug #23006431)

     * Aborting a CREATE LOGFILE GROUP
       (http://dev.mysql.com/doc/refman/5.7/en/create-logfile-gr
       oup.html) statement which had failed due to lack of
       shared global memory was not performed correctly, causing
       node failure. In addition, the transaction in which this
       occurred was not rolled back correctly, also causing any
       subsequent CREATE LOGFILE GROUP to fail. (Bug #22982618)

     * The ndbinfo.tc_time_track_stats
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
       info-tc-time-track-stats.html) table uses histogram
       buckets to give a sense of the distribution of latencies.
       The sizes of these bucket were also reported as HISTOGRAM
       BOUNDARY INFO messages during data node startup; this
       printout was redundant and so has been removed. (Bug
       #22819868)

     * Online upgrades from previous versions of MySQL Cluster
       to MySQL Cluster NDB 7.5 were not possible due to missing
       entries in the matrix used to test upgrade compatibility
       between versions. (Bug #22024947)

     * A failure occurred in DBTUP in debug builds when
       variable-sized pages for a fragment totalled more than 4
       GB. (Bug #21313546)

     * Restoration of metadata with ndb_restore -m
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-pro
       grams-ndb-restore.html#option_ndb_restore_restore_meta)
       occasionally failed with the error message Failed to
       create index... when creating a unique index. While
       disgnosing this problem, it was found that the internal
       error PREPARE_SEIZE_ERROR (a temporary error) was
       reported as an unknown error. Now in such cases,
       ndb_restore retries the creation of the unique index, and
       PREPARE_SEIZE_ERROR is reported as NDB Error 748 Busy
       during read of event table. (Bug #21178339)
       References: See also: Bug #22989944.

     * mysqld did not shut down cleanly when executing
       ndb_index_stat. (Bug #21098142)

     * The following improvements were made to the data node
       error logging mechanism:

          + Increased the message slot size 499 bytes to 999
            bytes to prevent log messages from overwriting one
            another or from being truncated.

          + Added a Trace file name field to the output. This
            field contains the trace file name (without any
            path) and trace file number for the thread causing
            the trace.

          + ndbmtd trace files are also now shown in the error
            log.
       (Bug #21082710)

     * DBDICT and GETTABINFOREQ queue debugging were enhanced as
       follows:

          + Monitoring by a data node of the progress of
            GETTABINFOREQ signals can be enabled by setting
            DictTrace
            (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluste
            r-ndbd-definition.html#ndbparam-ndbd-dicttrace) >=
            2.

          + Added the ApiVerbose
            (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluste
            r-api-definition.html#ndbparam-api-apiverbose)
            configuration parameter, which enables NDB API debug
            logging for an API node where it is set greater than
            or equal to 2.

          + Added DUMP code 1229 which shows the current state
            of the GETTABINFOREQ queue. (See DUMP 1229
            (http://dev.mysql.com/doc/ndbapi/en/ndb-internals-du
            mp-command-1229.html).)
       See also The DBDICT Block
       (http://dev.mysql.com/doc/ndbapi/en/ndb-internals-kernel-
       blocks-dbdict.html). (Bug #20368450)
       References: See also: Bug #20368354.

     * When a write to the ndb_binlog_index table failed during
       a MySQL Server shutdown, mysqld killed the NDB binary
       logging thread. (Bug #81166, Bug #23142945)

     * Memory associated with table descriptions was not freed
       by the internal table information method
       NdbDictInterface::parseTableInfo(). (Bug #81141, Bug
       #23130084)

     * Fixed a memory leak that occurred when an error was
       raised in ha_ndbcluster::get_metadata() or one of the
       functions which this method calls. (Bug #81045, Bug
       #23089566)

     * An internal function used to validate connections failed
       to update the connection count when creating a new Ndb
       (http://dev.mysql.com/doc/ndbapi/en/ndb-ndb.html) object.
       This had the potential to create a new Ndb object for
       every operation validating the connection, which could
       have an impact on performance, particularly when
       performing schema operations. (Bug #80750, Bug #22932982)

     * A table scan on an NDB
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.htm
       l) table using neither an ordered index nor any Disk Data
       columns normally uses an ACC scan. If this happened while
       scanning an unique but unordered index which shrank (due
       to rows being deleted) after the scan started and then
       grew again (rows inserted), a single row that had been
       neither deleted nor inserted could be scanned twice. (Bug
       #80733, Bug #22926938)

     * Starting a backup in the ndb_mgm client after creating a
       large number of tables caused a forced shutdown of the
       cluster. (Bug #80640, Bug #228849958)

     * When an SQL node was started, and joined the schema
       distribution protocol, another SQL node, already waiting
       for a schema change to be distributed, timed out during
       that wait. This was because the code incorrectly assumed
       that the new SQL node would also acknowledge the schema
       distribution even though the new node joined too late to
       be a participant in it.
       As part of this fix, printouts of schema distribution
       progress now always print the more significant part of a
       bitmask before the less significant; formatting of
       bitmasks in such printouts has also been improved. (Bug
       #80554, Bug #22842538)

     * The ndb_print_file utility failed consistently on Solaris
       9 for SPARC. (Bug #80096, Bug #22579581)

     * The MySQL Cluster Auto-Installer failed to work in
       various ways on different platforms. (Bug #79853, Bug
       #22502247)

     * The internal function ndbrequire(), which, like assert(),
       evaluates a given expression and terminates the process
       if the expression does not evaluate as true, now includes
       the failed expression in its output to the error logs.
       (Bug #77021, Bug #21128318)

     * Trying to drop a table during an ongoing backup failed
       with the error message Unknown table; now, it fails with
       Unable to alter table as backup is in progress. (Bug
       #47301, Bug #11755512)
       References: See also: Bug #44695, Bug #11753280.

     * Disk Data: The following improvements were made to
       logging during restarts by data nodes using MySQL Cluster
       Disk Data:

          + The total amount of undo log to be applied by the
            data node is now provided as the total number of
            pages present in the log. This is a worst case
            estimate.

          + Progress information is now provided at regular
            intervals (once for each 30000 records) as the undo
            log is applied. This information is supplied as the
            number of records and number of undo log pages
            applied so far during the current restart.
       (Bug #22513381)

     * Cluster API: Deletion of Ndb objects used a
       dispoportionately high amount of CPU. (Bug #22986823)

     * Cluster API: Executing a transaction with an
       NdbIndexOperation
       (http://dev.mysql.com/doc/ndbapi/en/ndb-ndbindexoperation
       .html) based on an obsolete unique index caused the data
       node process to fail. Now the index is checked in such
       cases, and if it cannot be used the transaction fails
       with an appropriate error. (Bug #79494, Bug #22299443)

     * mysql_upgrade failed to upgrade the sys schema if a sys
       database directory existed but was empty. (Bug #81352,
       Bug #23249846, Bug #22875519)

On behalf of the MySQL RE Team,
Lars Tangvald

Dear MySQL users,

MySQL Server 5.5.50 is a new version of the 5.5 production release
of the world's most popular open source database. MySQL 5.5.50 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 Heartbeat
  - 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

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.50 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.50 is available in source and binary form for a
number of platforms from our download pages at:

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

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/relnotes/mysql/5.5/en/news-5-5-50.html

Enjoy!


==============================================================================
Changes in MySQL 5.5.50 (2016-06-02)


     * Functionality Added or Changed

     * Bugs Fixed

   Functionality Added or Changed

     * The version of the tcmalloc library included in MySQL
       distributions was very old. It has been removed and is no
       longer included with MySQL. (Bug #80994, Bug #23068660)

   Bugs Fixed

     * INSERT with ON DUPLICATE KEY UPDATE and REPLACE on a
       table with a foreign key constraint defined failed with
       an incorrect "duplicate entry" error rather than a
       foreign key constraint violation error. (Bug #23135731)
       References: This issue is a regression of: Bug #78853,
       Bug #22037930.

     * Setting sort_buffer_size to a very large value could
       cause some operations to fail with an out-of-memory
       error. (Bug #22594514)

     * Several potential buffer overflow issues were corrected.
       (Bug #21977380, Bug #23187436, Bug #23202778, Bug
       #23195370, Bug #23202699)

     * If the CA certificate as given to the --ssl-ca option had
       an invalid path, yaSSL returned an error message
       different from OpenSSL. Now both return SSL connection
       error: SSL_CTX_set_default_verify_paths failed. (Bug
       #21920657)

     * Some string functions returned one or a combination of
       their parameters as their result. If one of the
       parameters had a non-ASCII character set, the result
       string had the same character set, resulting in incorrect
       behavior when an ASCII string was expected. (Bug
       #18740222)

     * A null pointer dereference of a parser structure could
       occur during stored procedure name validation. (Bug
       #79396, Bug #22286421)

     * mysqld_multi displayed misleading error messages when it
       was unable to execute my_print_defaults. (Bug #74636, Bug
       #19920049)

Thanks,
Prashant Tekriwal
MySQL Release Engineering Team

Changes in MySQL 5.6.31 (2016-06-02)


     * Security Notes

     * Functionality Added or Changed

     * Bugs Fixed

   Security Notes

     * The linked OpenSSL library for the MySQL Commercial
       Server has been updated to version 1.0.1t. Issues fixed
       in the new version are described at
       http://www.openssl.org/news/vulnerabilities.html.
       This change does not affect the Oracle-produced MySQL
       Community build of MySQL Server, which uses the yaSSL
       library instead. (Bug #23229564)

   Functionality Added or Changed

     * A new CMake option, WITH_SYMVER16, if enabled, causes the
       libmysqlclient client library to contain extra symbols to
       be compatible with libmysqlclient on RHEL/OEL 5, 6, 7,
       and Fedora releases. All symbols present in
       libmysqlclient.so.16 are tagged with symver 16 in
       libmsqlclient.so.18, making those symbols have both
       symver 16 and 18. (Bug #22980983)

     * support-files/MacOSX/ReadMe.txt is no longer included in
       MySQL distributions. (Bug #81038, Bug #23088916)

     * The version of the tcmalloc library included in MySQL
       distributions was very old. It has been removed and is no
       longer included with MySQL. (Bug #80994, Bug #23068660)

   Bugs Fixed

     * InnoDB: MySQL failed to build on Fedora 24 using GCC 6.
       (Bug #23227804)

     * InnoDB: Potential buffer overflow issues were corrected
       for the InnoDB memcached plugin. (Bug #23187607)

     * InnoDB: The full-text index cache was freed during a
       background index cache synchronization. (Bug #22996488)

     * InnoDB: A full-text index operation raised an assertion.
       (Bug #22963169)

     * InnoDB: An INSERT operation on a table with a FULLTEXT
       index and FTS_DOC_ID column failed because the inserted
       FTS_DOC_ID value exceeded the permitted gap between
       consecutive FTS_DOC_ID values. To avoid this problem, the
       permitted gap between the largest used FTS_DOC_ID value
       and new FTS_DOC_ID value was raised from 10000 to 65535.
       (Bug #22679185)

     * InnoDB: With innodb_autoinc_lock_mode=0, multiple threads
       waiting for a table-level lock caused an unexpected
       deadlock. (Bug #21983865, Bug #78761)

     * InnoDB: A FLUSH TABLES ... FOR EXPORT operation appeared
       to stall. A loop in the ibuf_contract_in_background
       function failed to exit. (Bug #21133329, Bug #77011)

     * InnoDB: A full-text query raised an assertion. Under
       certain circumstances, DDL operations such as ALTER TABLE
       ... RENAME caused full-text auxiliary tables to be
       removed on server restart. (Bug #13651665)

     * Replication: In the next_event() function, which is
       called by a slave's SQL thread to read the next even from
       the relay log, the SQL thread did not release the
       relaylog.log_lock it acquired when it ran into an error
       (for example, due to a closed relay log), causing all
       other threads waiting to acquire a lock on the relay log
       to hang. With this fix, the lock is released before the
       SQL thread leaves the function under the situation. (Bug
       #21697821)
       References: See also: Bug #20492319.

     * Replication: If a multi-threaded replication slave
       running with relay_log_recovery=1 stopped unexpectedly,
       during restart the relay log recovery process could fail.
       This was due to transaction inconsistencies not being
       filled, see Handling an Unexpected Halt of a Replication
       Slave
(http://dev.mysql.com/doc/refman/5.6/en/replication-solutions-unexpected-slave-halt.html).
       Prior to this fix, to
       recover from this situation required manually setting
       relay_log_recovery=0, starting the slave with START SLAVE
       UNTIL SQL_AFTER_MTS_GAPS to fix any transaction
       inconsistencies and then restarting the slave with
       relay_log_recovery=1. This process has now been
       automated, enabling relay log recovery of a
       multi-threaded slave upon restart automatically. (Bug
       #77496, Bug #21507981)

     * INSERT with ON DUPLICATE KEY UPDATE and REPLACE on a
       table with a foreign key constraint defined failed with
       an incorrect "duplicate entry" error rather than a
       foreign key constraint violation error. (Bug #23135731)
       References: This issue is a regression of: Bug #78853,
       Bug #22037930.

     * For debug builds, CONCAT_WS() could raise an assertion if
       there was nothing to append. (Bug #22888420)

     * Invoking Enterprise Encryption functions in multiple
       threads simultaneously could cause a server exit. (Bug
       #22839278)

     * Attempting to use Enterprise Encryption functions after
       creating and dropping them could cause a server exit.
       (Bug #22669012)

     * Setting sort_buffer_size to a very large value could
       cause some operations to fail with an out-of-memory
       error. (Bug #22594514)

     * An assertion could be raised when a deadlock occurred due
       to a SELECT ... GROUP BY ... FOR UPDATE query executed
       using a Loose Index Scan. (Bug #22187476)

     * Several potential buffer overflow issues were corrected.
       (Bug #21977380, Bug #23187436, Bug #23202778, Bug
       #23195370, Bug #23202699)

     * If the CA certificate as given to the --ssl-ca option had
       an invalid path, yaSSL returned an error message
       different from OpenSSL. Now both return SSL connection
       error: SSL_CTX_set_default_verify_paths failed. (Bug
       #21920657)

     * Some string functions returned one or a combination of
       their parameters as their result. If one of the
       parameters had a non-ASCII character set, the result
       string had the same character set, resulting in incorrect
       behavior when an ASCII string was expected. (Bug
       #18740222)

     * On Windows, MySQL installation could result in MySQL
       being placed under C:\Program Files\Canon\Easy-WebPrint
       EX. (Bug #14583183)
       References: See also: Bug #70918, Bug #68821, Bug #68227.

     * On Fedora 24, upgrades using a Community MySQL Server RPM
       failed to replace an installed MariaDB Galera server due
       to a change in the MariaDB package. (Bug #81390, Bug
       #23273818)

     * MySQL did not compile under Solaris 12 using Sun Studio.
       To correct this, instances of __attribute__ were changed
       to MY_ATTRIBUTE. (Bug #80748, Bug #22932576)

     * The INSTALL-SOURCE file had partly outdated information
       and has been removed from source packages. (Binary
       packages are unaffected). (Bug #80680, Bug #23081064)

     * For a server compiled with
       -DWITH_PERFSCHEMA_STORAGE_ENGINE=0, a memory leak could
       occur for buffered log messages used during server
       startup. (Bug #80089, Bug #22578574)

     * For debug builds, merging a derived table into an outer
       query block could raise an assertion. (Bug #79502, Bug
       #22305361, Bug #21139722)

     * A null pointer dereference of a parser structure could
       occur during stored procedure name validation. (Bug
       #79396, Bug #22286421)

     * Using CREATE USER to create an account with the
       mysql_native_password or mysql_old_password
       authentication plugin and using a clause of the form
       IDENTIFIED WITH plugin AS 'hash_string' caused the
       account to be created without a password. (Bug #78033,
       Bug #21616496)

     * Failure of UNINSTALL PLUGIN could lead to inaccurate or
       confusing errors for subsequent INSTALL PLUGIN
       operations. (Bug #74977, Bug #20085672)

     * mysqld_multi displayed misleading error messages when it
       was unable to execute my_print_defaults. (Bug #74636, Bug
       #19920049)

     * On Windows, MySQL installation failed if the
       HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVers
       ion\Uninstall\ registry key was present with a key/value
       pair of "InstallLocation" and "\Hewlett-Packard\\". (Bug
       #74631, Bug #19949163)

     * mysqldump failed silently with no error message when it
       encountered an error while executing FLUSH LOGS. (Bug
       #71783, Bug #18284273)

Dear MySQL users,

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

Since MySQL Server 5.7.12, we have introduced the concept of
Rapid Plugins. Out of the box, 5.7.13 follows the same stability promise
as our current release process, but it also allows for plugins with
additional functionality to be installed very easily. The first plugin
to be released with MySQL Server 5.7.13 following this concept is the
new X Plugin, which exposes a new communications protocol called the X
Protocol. The expanded capabilities of the X Protocol enable us to
provide the new X DevAPI in our MySQL Connectors and Client
applications, like the new MySQL Shell. The goal of the X DevAPI is to
support a new schema object type called document collections as well as
relational and combined document store/relational capabilities. Now
developers, designers and DBAs can deploy MySQL databases that implement
document store, relational, or hybrid document/relation models. For
documentation about how to get started using MySQL as a document store,
see http://dev.mysql.com/doc/refman/5.7/en/document-store.html.

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

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

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

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

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

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

MySQL Server 5.7.13 is also available from our repository for Linux
platforms, go here for details:

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

Windows packages are available via the Installer for Windows or .ZIP
(no-install) packages for more advanced needs. The point and click
configuration wizards and all MySQL products are available in the
unified Installer for Windows:

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

5.7.13 also comes with a web installer as an alternative to the full
installer.

The web installer doesn't come bundled with any actual products
and instead relies on download-on-demand to fetch only the
products you choose to install. This makes the initial download
much smaller but increases install time as the individual products
will need to be downloaded.

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

http://bugs.mysql.com/report.php

The following section lists the changes in MySQL 5.7 since
the release of MySQL 5.7.12. It may also be viewed
online at

http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-13.html

Enjoy!

Changes in MySQL 5.7.13 (2016-06-02)

     Account Management Notes

       * In MySQL 5.7.8, the maximum length of MySQL user names
         was increased from 16 to 32 characters, but some
         applicable contexts for this increase were overlooked.
         Additional changes in maximum user name length now have
         been applied:

            + The size of these mysql system table columns is
              increased:
                 o The definer column of the event and proc tables
                 o The grantor column of the procs_priv and
                   tables_priv tables
              In each case, the column previously was defined as
              CHAR(77), where 77 was chosen to permit a
              user_name@host_name string containing a user name up
              to 16 characters, a @ character, and a host name up
              to 60 characters. Each column now is defined as
              CHAR(93), reflecting an increase in permitted user
              name length from 16 to 32 characters.

            + A similar change from CHAR(77) to CHAR(93)applies to
              the DEFINER column of these INFORMATION_SCHEMA
              tables: EVENTS, ROUTINES, TRIGGERS, VIEWS. Along
              with the changes to INFORMATION_SCHEMA tables,
              output from any corresponding SHOW statements now
              displays DEFINER values up to 93 characters.
              Examples of affected statements: SHOW EVENTS, SHOW
              TRIGGERS, SHOW PROCEDURE STATUS.
         If you upgrade to this MySQL release from an earlier
         version, you must run mysql_upgrade (and restart the
         server) to incorporate the changes to the mysql system
         database. A server from MySQL 5.7.13 or higher for which
         mysql_upgrade has not been run continues to permit a
         maximum of 77 characters in the system tables mentioned
         previously, and an ER_USER_COLUMN_OLD_LENGTH error will
         occur in those system table contexts where a
         user_name@host_name value from 78 to 93 characters long
         is given.

     Audit Log Notes

       * The audit_log plugin that forms the basis for MySQL
         Enterprise Audit now supports fine-grained filtering of
         events. This enables a reduction in the number of log
         entries written to the audit log file, which increases
         overall performance due to fewer write operations during
         log recording. It also simplifies subsequent audit log
         processing in terms of readability and processing time.
         Fine-grained audit log filtering is rule based,
         implemented using tables that store rule definitions and
         a set of user-defined functions (UDFs) that enable rule
         manipulation. To simplify installing the tables and UDFs
         along with the audit_log plugin, an installation script
         is now provided. For more information, see Installing or
         Uninstalling MySQL Enterprise Audit
         (http://dev.mysql.com/doc/refman/5.7/en/audit-log-install
         ation.html), and Audit Log Filtering
         (http://dev.mysql.com/doc/refman/5.7/en/audit-log-filteri
         ng.html).
         By default, rule-based audit log filtering logs no
         auditable events for any users. This differs from
         pre-MySQL 5.7.13 legacy audit log filtering, which logs
         all auditable events for all users. To produce
         log-everything behavior with rule-based filtering, see
         the installation instructions.

     Configuration Notes

       * On platforms for which systemd support is installed,
         systemd has the capability of managing multiple MySQL
         instances. For details, see Configuring Multiple MySQL
         Instances Using systemd
         (http://dev.mysql.com/doc/refman/5.7/en/server-management
         -using-systemd.html#systemd-multiple-mysql-instances).
         Consequently, mysqld_multi and mysqld_multi.server are
         not installed because they are unnecessary. (Bug #81093,
         Bug #23134620)

     Security Notes

       * The linked OpenSSL library for the MySQL Commercial
         Server has been updated to version 1.0.1t. Issues fixed
         in the new version are described at
         http://www.openssl.org/news/vulnerabilities.html.
         This change does not affect the Oracle-produced MySQL
         Community build of MySQL Server, which uses the yaSSL
         library instead. (Bug #23229564)

       * MySQL Server now includes an SQL interface for keyring
         key management, implemented as a set of user-defined
         functions (UDFs) that access the functions provided by
         the internal keyring service. For more information, see
         Keyring Key Management Functions
         (http://dev.mysql.com/doc/refman/5.7/en/keyring-udfs.html
         ). For information about the keyring service functions
         invoked by the UDFs, see The Keyring Service
         (http://dev.mysql.com/doc/refman/5.7/en/keyring-service.h
         tml). For general keyring information, see The MySQL
         Keyring
         (http://dev.mysql.com/doc/refman/5.7/en/keyring.html).

     Functionality Added or Changed

       * For better separation of output from multiple statements,
         mysqltest now flushes output sent to stdout when the
         output destination is not a file. Previously, flushing
         occurred only for file output. (Bug #21435906)

       * support-files/MacOSX/ReadMe.txt is no longer included in
         MySQL distributions. (Bug #81038, Bug #23088916)

       * The version of the tcmalloc library included in MySQL
         distributions was very old. It has been removed and is no
         longer included with MySQL. (Bug #80994, Bug #23068660)

       * The my_make_scrambled_password() function in the C client
         library was restricted earlier in MySQL 5.7 (not exported
         to client programs). The function has once again been
         made visible to client programs. (Bug #80974, Bug
         #23061746)

       * It is possible to use ALTER TABLE to change the default
         value of a column col_name, which may change the value of
         a generated column expression that refers to the column
         using DEFAULT(col_name). For this reason, ALTER TABLE
         operations that change the definition of a column now
         cause a table rebuild if any generated column expression
         uses DEFAULT(). (Bug #80299, Bug #22680839)

       * This release adds an unquoting extraction operator ->>,
         sometimes also referred to as an inline path operator,
         for use with JSON documents stored in MySQL. The new
         operator is similar to the -> operator, but performs JSON
         unquoting of the value as well. For a JSON column mycol
         and JSON path expression mypath, the following three
         expressions are equivalent:

            + JSON_UNQUOTE( JSON_EXTRACT(mycol, "$.mypath") )

            + JSON_UNQUOTE(mycol->"$.mypath")

            + mycol->>"$.mypath"
         The ->> operator can be used in SQL statements wherever
         JSON_UNQUOTE(JSON_EXTRACT()) would be allowed. This
         includes (but is not limited to) SELECT lists, WHERE and
         HAVING clauses, and ORDER BY and GROUP BY clauses.
         For more information, see Functions That Search JSON
         Values
         (http://dev.mysql.com/doc/refman/5.7/en/json-search-funct
         ions.html), and JSON Path Syntax
         (http://dev.mysql.com/doc/refman/5.7/en/json-path-syntax.
         html). (Bug #78736, Bug #21980346)

     Bugs Fixed

       * InnoDB: A rollback operation run concurrently with an
         operation involving a generated virtual column caused a
         server exit. (Bug #23313102)
         References: This issue is a regression of: Bug #21869656.

       * InnoDB: Potential buffer overflow issues were corrected
         for the InnoDB memcached plugin. (Bug #23187607)

       * InnoDB: An ALTER TABLE operation that added an
         AUTO_INCREMENT column on a table with virtual columns
         raised an assertion. (Bug #23052231)

       * InnoDB: Statements executed in a transaction that was
         rolled back asynchronously by a higher priority
         transaction caused a deadlock error and subsequent
         replication failure. (Bug #23021168, Bug #80898)

       * InnoDB: An ALTER TABLE operation that attempted to add a
         generated virtual column and a full-text index raised an
         assertion. (Bug #23014521)

       * InnoDB: The full-text index cache was freed during a
         background index cache synchronization. (Bug #22996488)

       * InnoDB: A full-text index operation raised an assertion.
         (Bug #22963169)

       * InnoDB: Memory was allocated to I/O slots unnecessarily,
         causing an apparent memory leak. (Bug #22956469, Bug
         #80772)

       * InnoDB: An ALTER TABLE operation raised an assertion when
         attempting to create a key containing a generated column.
         (Bug #22951879)

       * InnoDB: A startup failure due to an invalid option
         resulted in a server exit after a subsequent restart. An
         error returned by the innobase_start_or_create_for_mysql
         function was not checked. (Bug #22939581, Bug #80761)

       * InnoDB: An ALTER TABLE ... IMPORT TABLESPACE operation on
         file-per-table tablespace containing an encrypted table
         failed when run in a different session than the preceding
         ALTER TABLE ... DISCARD TABLESPACE operation. (Bug
         #22918999, Bug #80708)

       * InnoDB: A FLUSH TABLES operation on a table with a
         discarded tablespace raised an assertion. (Bug #22899690,
         Bug #80669)

       * InnoDB: A DML operation involving a table with a virtual
         column raised an assertion. (Bug #22899305)

       * InnoDB: An invalid read at innobase_get_computed_value()
         raised a Valgrind error. (Bug #22898168, Bug #80667)

       * InnoDB: Online DDL operations like ALTER TABLE ... ADD
         INDEX were not permitted for tables created with the
         ENCRYPTION attribute. (Bug #22897921)

       * InnoDB: InnoDB memcached code assumed the nonexistence of
         the htonll() function on OS X, resulting in a build
         failure on OS X 10.10 and later. (Bug #22865112)

       * InnoDB: Starting the server in read-only mode failed when
         encrypted tables were present. The call to
         fil_encryption_rotate() was not skipped when the server
         was started in read-only mode. (Bug #22723797)

       * InnoDB: An R-tree purge operation raised an assertion.
         (Bug #22698076, Bug #80327)

       * InnoDB: An INSERT operation on a table with a FULLTEXT
         index and FTS_DOC_ID column failed because the inserted
         FTS_DOC_ID value exceeded the permitted gap between
         consecutive FTS_DOC_ID values. To avoid this problem, the
         permitted gap between the largest used FTS_DOC_ID value
         and new FTS_DOC_ID value was raised from 10000 to 65535.
         (Bug #22679185)

       * InnoDB: Validation code for transparent page compression
         incorrectly permitted innodb_strict_mode=OFF, which
         allowed the COMPRESSION attribute to be applied to a
         general tablespace. Page compression is only supported
         with file-per-table tablespaces. (Bug #22615096, Bug
         #80182)

       * InnoDB: An memory order issue related to atomic
         operations caused assertion failures on ARM64 and POWER
         platforms. (Bug #22608616)

       * InnoDB: DROP TABLESPACE returned an error if the remote
         general tablespace data file was missing. (Bug #22232892,
         Bug #79330)

       * InnoDB: An ALTER TABLE operation that changed table row
         format from COMPACT to COMPRESSED raised an assertion. A
         function involved in the operation passed incorrect page
         size information. (Bug #22046353)

       * InnoDB: With innodb_autoinc_lock_mode=0, multiple threads
         waiting for a table-level lock caused an unexpected
         deadlock. (Bug #21983865, Bug #78761)

       * InnoDB: A race condition in trx_kill_blocking() raised an
         assertion. (Bug #21508537)

       * InnoDB: An OPTIMIZE TABLE operation on a table with a
         full-text index raised an assertion. (Bug #21378944)

       * InnoDB: A buffer pool load operation resulted in a
         "Cannot allocate 0 bytes" error. (Bug #21371070)

       * InnoDB: A FLUSH TABLES ... FOR EXPORT operation appeared
         to stall. A loop in the ibuf_contract_in_background
         function failed to exit. (Bug #21133329, Bug #77011)

       * InnoDB: A full-text query raised an assertion. Under
         certain circumstances, DDL operations such as ALTER TABLE
         ... RENAME caused full-text auxiliary tables to be
         removed on server restart. (Bug #13651665)

       * Replication: With gtid_mode=ON, executing an empty query
         before setting gtid_next made the latter action fail. It
         was because only statements that do not change the data
         can be executed before one can successfully change
         gtid_next, and an empty query was not considered one of
         those "safe" statements. This fix allows the setting of
         gtid_next after an empty query. (Bug #22811150)

       * Replication: Slaves running MySQL 5.7 could not connect
         to a MySQL 5.5 master due to an error retrieving the
         server_uuid, which is not part of MySQL 5.5. This was
         caused by changes in the method of retrieving the
         server_uuid. (Bug #22748612)
         References: This issue is a regression of: Bug #21455603.

       * Replication: Setting certain semisynchronous-replication
         configurations on the master server when semisynchronous
         replication was not enabled on it might cause the server
         to exit. This fix prevents the unexpected exits to occur
         in the situation. (Bug #22602324)

       * Replication: The variable explicit_defaults_ts was not
         initialized during the construction of a Query_event
         object. That caused Valgrind warnings for dependency on
         an uninitialized variable. This fix makes sure the
         variable is initialized. (Bug #22110916, Bug #78999)
         References: This issue is a regression of: Bug #18885916,
         Bug #72794.

       * Replication: In the next_event() function, which is
         called by a slave's SQL thread to read the next even from
         the relay log, the SQL thread did not release the
         relaylog.log_lock it acquired when it ran into an error
         (for example, due to a closed relay log), causing all
         other threads waiting to acquire a lock on the relay log
         to hang. With this fix, the lock is released before the
         SQL thread leaves the function under the situation. (Bug
         #21697821)
         References: See also: Bug #20492319.

       * Replication: A partially failed statement was not
         correctly consuming an auto-generated or specified GTID
         when binary logging was disabled. The fix ensures that a
         partially failed DROP TABLE, a partially failed DROP USER
         or a partially failed DROP VIEW consume respectively the
         relevant GTID and save it into @@GLOBAL.GTID_EXECUTED and
         mysql.gtid_executed table when binary logging is
         disabled. (Bug #21686749)

       * Replication: An intermittent ASan error was being
         reported on the rpl.rpl_checksum_cache test. The error
         reported was related to the binary log sender doing a
         heap-use-after-free on a given memory address. (Bug
         #78995, Bug #22109863)

       * Replication: mysqldump has been updated to make it
         compatible with multi-source replication. Now when
         replication channels other than the default channel are
         found, mysqldump --dump-slave outputs a CHANGE MASTER TO
         statement for each replication channel. (Bug #78467, Bug
         #21855705)

       * Replication: If a multi-threaded replication slave
         running with relay_log_recovery=1 stopped unexpectedly,
         during restart the relay log recovery process could fail.
         This was due to transaction inconsistencies not being
         filled, see Handling an Unexpected Halt of a Replication
         Slave
         (http://dev.mysql.com/doc/refman/5.7/en/replication-solut
         ions-unexpected-slave-halt.html). Prior to this fix, to
         recover from this situation required manually setting
         relay_log_recovery=0, starting the slave with START SLAVE
         UNTIL SQL_AFTER_MTS_GAPS to fix any transaction
         inconsistencies and then restarting the slave with
         relay_log_recovery=1. This process has now been
         automated, enabling relay log recovery of a
         multi-threaded slave upon restart automatically. (Bug
         #77496, Bug #21507981)

       * Fedora builds now are configured using
         -DMYSQL_MAINTAINER_MODE=0 to silence GCC 6 warnings. (Bug
         #23274249)

       * Allocation of a large number (2^20) of Performance Schema
         index statistic objects could cause a server exit. (Bug
         #23188107)

       * If the keyring_okv plugin configuration directory was
         missing, attempts to rotate the InnoDB master key could
         cause a server exit. (Bug #23149683)

       * INSERT with ON DUPLICATE KEY UPDATE and REPLACE on a
         table with a foreign key constraint defined failed with
         an incorrect "duplicate entry" error rather than a
         foreign key constraint violation error. (Bug #23135731)
         References: This issue is a regression of: Bug #78853,
         Bug #22037930.

       * Contention in Performance Schema mutex instrumentation
         creation and destruction has been reduced, such that
         mutexes for which instruments are frequently created and
         destroyed are maintained in separate pages from those for
         which instruments are rarely created and destroyed. (Bug
         #22965826)

       * With certain build options, an uninitialized variable in
         get_key_scans_params() could produce a compilation error.
         (Bug #22916059)

       * Adding new tokens to the parser caused query digest
         values to change. (Bug #22906606)

       * For debug builds, CONCAT_WS() could raise an assertion if
         there was nothing to append. (Bug #22888420)

       * Fixed Valgrind warnings for failed LEAST() evaluations.
         (Bug #22883278)

       * INET_NTOA() could cause a server exit when producing an
         error message. (Bug #22881810)
         References: This issue is a regression of: Bug #22042027.

       * The my_write() call could cause a server exit if it
         attempted to check the current connection and the
         connection had been killed. (Bug #22867809)
         References: This issue is a regression of: Bug #21688407.

       * Invoking Enterprise Encryption functions in multiple
         threads simultaneously could cause a server exit. (Bug
         #22839278)

       * Setting log_syslog_tag to NULL could cause a server exit.
         (Bug #22834781)
         References: This issue is a regression of: Bug #22180046.

       * If the expression for an indexed generated column
         contained an AND or OR operator, the optimizer could
         choose that index too often and create execution plans
         that produced incorrect results. (Bug #22810883)

       * CREATE TABLE statements in mysqlpump output could be
         missing KEY clauses and would not load. (Bug #22726732)

       * Attempting to use Enterprise Encryption functions after
         creating and dropping them could cause a server exit.
         (Bug #22669012)

       * Setting sort_buffer_size to a very large value could
         cause some operations to fail and result in a server
         exit. (Bug #22594514)

       * For an InnoDB table containing generated columns, using
         the table in a join could result in a server exit due to
         improper error checking. (Bug #22561845)

       * REPLACE on a table with an indexed generated column could
         cause a server exit if the index prefix length was
         calculated incorrectly. (Bug #22445211)

       * An UPDATE operation affecting a generated virtual BLOB
         column could cause a server exit. (Bug #22444212)

       * SHOW CREATE TABLE for a table containing a generated
         column could cause a server exit or produce an Illegal
         mix of collations error. (Bug #22392268)

       * On a slave server, replication of an UPDATE statement
         that updated an indexed BLOB virtual generated column of
         an InnoDB table could cause a server exit. (Bug
         #22241015)

       * An assertion could be raised when a deadlock occurred due
         to a SELECT ... GROUP BY ... FOR UPDATE query executed
         using a Loose Index Scan. (Bug #22187476)

       * mysqlpump could exit due to improper handling of error
         conditions in a dump thread. (Bug #22017120)

       * Several potential buffer overflow issues were corrected.
         (Bug #21977380, Bug #23187436, Bug #23202778, Bug
         #23195370, Bug #23202699)

       * If the CA certificate as given to the --ssl-ca option had
         an invalid path, yaSSL returned an error message
         different from OpenSSL. Now both return SSL connection
         error: SSL_CTX_set_default_verify_paths failed. (Bug
         #21920657)

       * Installing MySQL from a yum or zypper repository resulted
         in /var/log/mysqld.log being created with incorrect user
         and group permissions. (Bug #21879694, Bug #78512)

       * With show_compatibility_56=OFF, SHOW VARIABLES and SHOW
         STATUS statements having a WHERE clause did not work.
         (Bug #21783883)

       * The audit_log plugin failed to abort the current
         operation when told to do so by a plugin handler for a
         MYSQL_AUDIT_PARSE_PREPARSE event. (Bug #21457956)

       * Memory leaks reported by Valgrind for mysqlpump were
         fixed. (Bug #21237667)

       * Some string functions returned one or a combination of
         their parameters as their result. If one of the
         parameters had a non-ASCII character set, the result
         string had the same character set, resulting in incorrect
         behavior when an ASCII string was expected. (Bug
         #18740222)

       * On Fedora 24, upgrades using a Community MySQL Server RPM
         failed to replace an installed MariaDB Galera server due
         to a change in the MariaDB package. (Bug #81390, Bug
         #23273818)

       * The mysql_read_defaults_options() function was missing a
         break statement, causing any option value for the
         --ssl-cipher option also to be applied to the
         --tls-version option, with unpredictable results. (Bug
         #81139, Bug #23129821)

       * A DELETE from joined tables using a derived table in the
         WHERE clause failed if one of the joined tables was used
         in the derived table. (Bug #81014, Bug #23074801)

       * Compiling of clients that used the MySQL C API could fail
         if they used an obsolete path to mysql.h or
         <mysql/mysql.> and did not set the include path. This was
         due to use of #include <file_name> notation rather than
         #include "file_name" in internal MySQL header files,
         which have been adjusted. (Bug #80935, Bug #23047194)

       * MySQL did not compile under Solaris 12 using Sun Studio.
         To correct this, instances of __attribute__ were changed
         to MY_ATTRIBUTE. (Bug #80748, Bug #22932576)

       * The service_mysql_keyring.h and services.h header files
         misspelled mysql_keyring_service_st as
         mysql_keyring_file_service_st. (Bug #80688, Bug
         #22908232)

       * The fix for Bug #79194 did not cover the eq_ref access
         method, with the result that left joins could return
         incorrect results.
         Note
         This bug fix has a very small negative performance effect
         such that it fails to cache an eq_ref-accessed row that
         is on the inner side of an outer join. Regular inner
         joins are not affected.
         (Bug #80526, Bug #22833364)
         References: This issue is a regression of: Bug #79194,
         Bug #22176604.

       * The sanity() macro in strings/decimal.c produced Valgrind
         warnings due to reading uninitialized buffer contents.
         (Bug #80461, Bug #22782203, Bug #22839915)

       * Starting the server with --initialize failed if the
         keyring_file_data system variable was also set at
         startup. To handle this, with --initialize the server no
         longer skips registration of plugins loaded with the
         --early-plugin-load option. (Bug #80451, Bug #22777039)

       * Loading the Rewriter query rewrite plugin when there was
         no query_rewrite database resulted in Valgrind warnings.
         (Bug #80333, Bug #22710312)

       * The optimizer transformed EXISTS (SELECT * ...)
         constructs to EXISTS (SELECT 1 ...) before all columns in
         the inner subquery had been resolved, which could result
         in rejection of valid queries that included a HAVING
         clause without GROUP BY in the subquery. (Bug #80231, Bug
         #22655856)

       * For a server compiled with
         -DWITH_PERFSCHEMA_STORAGE_ENGINE=0, a memory leak could
         occur for buffered log messages used during server
         startup. (Bug #80089, Bug #22578574)

       * A query could return incorrect results under these
         conditions: A column with a default value contained NULL;
         SELECT DISTINCT or a GROUP BY clause was used and the
         column containing the NULL value was part of the select
         list; an InnoDB temporary table was used during query
         processing. (Bug #79591, Bug #22343910)

       * A null pointer dereference of a parser structure could
         occur during stored procedure name validation. (Bug
         #79396, Bug #22286421)

       * Database initialization failed during installation using
         Ubuntu 15.10 packages. (Bug #79377, Bug #22252900)

       * mysql_upgrade failed to widen the User and Proxied_user
         columns in the mysql.proxies_priv system table from 16 to
         32 characters. (Bug #78254, Bug #21762656)

       * Failure of UNINSTALL PLUGIN could lead to inaccurate or
         confusing errors for subsequent INSTALL PLUGIN
         operations. (Bug #74977, Bug #20085672)

       * mysqld_multi displayed misleading error messages when it
         was unable to execute my_print_defaults. (Bug #74636, Bug
         #19920049)

       * Previously, upgrading the server using an RPM package
         (including installation using yum) required upgrading the
         client package to the same MySQL version, which may be
         undesirable for some installations. This rule has been
         relaxed so that upgrading to a General Availability (GA)
         server version requires only that some GA client version
         be installed, which is less likely to require a client
         upgrade. (Bug #72230, Bug #18518216)

       * mysqldump failed silently with no error message when it
         encountered an error while executing FLUSH LOGS. (Bug
         #71783, Bug #18284273)

On Behalf of the MySQL/ORACLE RE Team
Hery Ramilison

 
Dear MySQL users,

The MySQL developer tools team announces 6.3.7 as our GA release for
MySQL Workbench 6.3.

For the full list of changes in this revision, visit
http://dev.mysql.com/doc/relnotes/workbench/en/changes-6-3.html

For discussion, join the MySQL Workbench Forums:
http://forums.mysql.com/index.php?152

Download MySQL Workbench 6.3.7 GA now, for Windows, Mac OS X 10.9+,
Oracle Linux 6 and 7, Fedora 23 and Fedora 24, Ubuntu 16.04
or sources, from:

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

Enjoy!

 Changes in MySQL Workbench 6.3.7 (2016-06-13)


     * Functionality Added or Changed

     * Bugs Fixed

   Functionality Added or Changed

     * The Default target MySQL version model preference is now
       an open text field instead of a dropdown select box. For
       example, rather than choosing a version such as "5.7",
       you can now enter a specific version such as 5.7.12. (Bug
       #23080421, Bug #81023)

   Bugs Fixed

     * Executing Data Import/Restore would emit an unhandled
       exception with Import from Self-Contained File enabled.
       (Bug #23505226)

     * On Linux, the Table Data Export wizard failed to complete
       the export process. (Bug #23477814)

     * The MySQL Enterprise Backup Restore functionality could
       emit an unhandled exception under some circumstances.
       (Bug #23472573)

     * Editing a remote MySQL options file via the Options File
       management tool would emit an unhandled exception after
       clicking Apply. (Bug #23307191)

     * Exporting data to JSON was exporting NULL values as NULL
       instead of null, thus breaking the JSON output. (Bug
       #23241155, Bug #81331)

     * Under Users and Privileges, Workbench did not allow
       hyphens for host names in the "limit to hosts matching"
       field. (Bug #23224606, Bug #81301)

     * When viewing the code for an existing view (SQL to create
       the view), hexadecimal values were truncated. (Bug
       #23187761, Bug #81208)

     * Selecting "5.7" from Default target MySQL version did not
       take into account changes to newer versions, as 5.7
       behaved like 5.7.0 instead of a newer version. For
       example, it was not possible to use the JSON data type
       for variables inside the stored procedure editor as JSON
       was added in MySQL 5.7.7. (Bug #23080421, Bug #81023)

     * The Schema filter was slow (poor performance) when a lot
       (1000+) of schemas were present. (Bug #23047787, Bug
       #80946)

     * The database migration wizard database field was
       described as "Leave blank to select it later" but this
       text was updated to read as "Cannot be blank" because it
       is a required field. (Bug #22896342)

     * The generated SQL generated by the forward engineering
       wizard would incorrectly output "VIRTUALCOMMENT" instead
       of "VIRTUAL COMMENT". (Bug #22880159, Bug #80618)

     * An new option is available to specify a path to the SSH
       configuration and/or known hosts file. This option
       overwrites the defaults. (Bug #22866791, Bug #80605)

     * Workbench's Alter Table functionality did not behave
       correctly when a column was defined using a TIMESTAMP
       with fractional seconds, such as TIMESTAMP(1). In this
       case, some columns would be hidden from the editor. (Bug
       #22839982, Bug #80547)

     * Under Reverse Engineering, the information provided in
       the wild card description to select objects contained a
       typo. (Bug #22828056, Bug #80516)

     * After successfully executing the database migration
       wizard, executing it a second time required Workbench to
       be restarted. (Bug #22811588, Bug #80479)

     * When executing Data Export using a remote MySQL
       connection, the error resulting from a missing mysqldump
       binary was unclear. (Bug #22753693, Bug #80240)

     * The PostgreSQL migration wizard could fail to migrate
       PostgreSQL databases that were generated with tryton.
       (Bug #22747525, Bug #79217)

     * The Dashboard and Server Status reported different Select
       per second values. The Server Status page reported
       incorrect (inflated by about 3x) values. (Bug #22739583,
       Bug #74822)

     * The PostgreSQL migration wizard could fail with an
       "pg_catalog.pg_enum does not exist" error. (Bug
       #22738451, Bug #71121)

     * The Workbench interface would incorrectly orient itself
       to display as Right-To-Left (RTL) when a system's
       language is set to a RTL language, despite Workbench not
       being translated to that language. (Bug #22722701, Bug
       #72126)

     * Attempting to test custom connection details (a
       connection not yet created by Workbench) caused Workbench
       to fail and exit. The Test Connection functionality only
       functioned for existing or new connections. (Bug
       #22698924, Bug #80325)

     * The "Limit to Hosts Matching" field in the user manager
       would incorrectly report a "Host name contains incorrect
       characters" error if the host named contained numeric
       characters. (Bug #22670269)

     * Import and export to JSON format failed if the table had
       column names that were keywords such as key or value.
       (Bug #22668918, Bug #80272)

     * The Alter Table functionality did not detect a default
       value change from no default value to an empty string. In
       other words, adding a default value of "" resulted in
       Workbench reporting "No changes detected". (Bug
       #22664805, Bug #80267)

     * The DBMS connection keep-alive interval option did not
       function properly. As a result, Workbench could lose the
       connection and result in errors similar to "Error Code:
       2013. Lost connection to MySQL server during query". (Bug
       #22642241, Bug #80225)

     * All generated paths now will use "/" as the directory
       separator in order to avoid the "\s" being interpreted as
       a space, such as "C:\path\to\certs\server-cert.pem" for
       generated SSL certificates. (Bug #22636645, Bug #80087)

     * Importing CSV data with from a properly UTF-8 encoded
       source would sometimes fail, and instead could result
       with errors such as "'ascii' codec can't encode character
       u'\xcf' at position 29: ordinal not in range(128)". (Bug
       #22635390, Bug #80205)

     * With Fabric, Workbench cached the topology information
       and did not update it when the topology changed, like
       when switching to a new master. (Bug #22601466)

     * Code completion has been further improved to only show
       relevant details, such as if a table is referenced in the
       FROM clause then only show columns from that table and
       not all from the default schema, and entries have been
       reordered to show columns first (only preceded by
       keywords). (Bug #22579426, Bug #80092)

     * Some stored procedure definitions were incorrectly
       reported as having invalid syntax. (Bug #22552958, Bug
       #80007)

     * Executing Alter Stored Procedure with a user lacking
       SELECT privileges would crash MySQL Workbench. (Bug
       #22509047, Bug #79871)

     * With the MySQL Firewall plugin enabled, having a user
       name containing a single quote character (rare, but not
       illegal) the queries would fail and produce an error in
       the Users and Privileges area of Workbench. These checks
       are now properly escaped. (Bug #22468850)

     * With the validate_password plugin enabled, when Workbench
       attempted to check the strength of a new password by
       sending a query to the server, the password was not
       properly escaped in this query. In such cases, the
       password was incorrectly reported as a strong or weak
       password. The associated "SELECT
       VALIDATE_PASSWORD_STRENGTH" query is now properly
       escaped. (Bug #22468332)

     * Some internal Workbench queries failed to execute with
       sql_mode set to ANSI_QUOTES. (Bug #22464406)

     * The Total Time field within the Recent Activity grid of
       the Online Backup / MySQL Enterprise Backup section of
       Workbench showed an incorrect duration value. (Bug
       #22462974, Bug #73499)

     * With MySQL Server 5.5 and lower, executing Alter Table on
       tables with partitions would fail with an error similar
       to "Syntax error: 'PARTITION' (identifier) is not valid
       input at this position". (Bug #22453898, Bug #79734)

     * MySQL Workbench lacked a CentOS profile, so could fail to
       make remote connections to a CentOS machine. (Bug
       #22453095, Bug #72205)

     * After opening the stored procedure editor from the object
       browser, clicking Execute would execute a query that did
       not take into account the IN parameters. (Bug #22378620)

     * On Windows, the "DEFAULT NULL" value could
       unintentionally be removed from the "Alter Table" window
       when clicking on it. (Bug #22375946, Bug #79661)

     * The Database Migration migration link on the home page
       was not functioning immediately after a successful
       migration. (Bug #22271448)

     * Several grammar and spelling corrections were implemented
       into the GUI. (Bug #22251496, Bug #79373)

     * Under certain circumstances, sub-queries were reported as
       syntax errors. (Bug #22251347, Bug #79371)

     * Several SQL Server 2014 database migration improvements.
       (Bug #22243141, Bug #79299)

     * While modeling, pressing the Enter key while editing a
       document's properties would close the document properties
       window instead of adding a new line. (Bug #22204168)

     * When copying tables, Workbench makes one connection at
       the start to disable triggers, makes a separate
       connection to do the data copy, then returns to the first
       connection to re-enable triggers. If the copy takes
       longer than the server's wait_timeout, the first
       connection timed out. (Bug #22190703, Bug #79242)

     * The Driver sends Unicode data as UTF-8 advanced database
       migration option that is available when using an ODBC
       driver is now disabled by default. Also, connections
       could hang when this option was enabled. (Bug #22149342,
       Bug #76382)

     * Executing Delete Row(s) after selecting more than six
       rows from the results grid would not delete all of the
       selected rows. (Bug #21909625, Bug #78560)

     * Adding a DATETIME with precision (such as DATETIME(3))
       from the Table Editor would eventually get reverted to
       DATETIME (without precision). (Bug #21666012, Bug #78153)

     * The search (magnifying glass) icon in the schema search
       field was misplaced after the left sidebar was resized.
       (Bug #21329109, Bug #77507)

     * Workbench will now prompt to continue the execution of
       operations containing loops in stored procedures, instead
       of just canceling it after ~200 executions. (Bug
       #21310357, Bug #77470)

     * The Performance Schema installation procedure in
       Workbench failed to check user privileges before
       attempting the installation. For example, if the user had
       all privileges except "ALTER ROUTINE", it would update
       sys.version but fail to complete the installation, and
       also fail to back out thereby leaving the sys.version as
       current but none of the functions were updated. (Bug
       #21261239, Bug #77360)

     * On Linux and OS X, the Options File viewer shortened
       (cut) long option names in the GUI, although editing
       their values changed the correct options. (Bug #21167521,
       Bug #77179)

     * MySQL connections were leaked when connecting and
       disconnecting to MySQL databases. It leaked one
       connection per re-connect to a database. (Bug #20996606)

     * A large database caused the size reported under the
       Schema Inspector to wrap around and display a negative
       number. (Bug #20990435)

     * From the Options File management feature, clicking
       Discard with the Advanced tab open would always revert
       the thread_handling option value to
       "one-thread-per-connection" even if it was set to "no
       threads". (Bug #20956570)

     * The print preview icon dialog was missing the Workbench
       icon. (Bug #20309812, Bug #75422)

     * Changes to the modeling Appearance font preference did
       not save properly, or have an effect. (Bug #20196073, Bug
       #75173)

     * On Windows, the Query Stats graph would not render with
       MySQL Server 5.7. (Bug #20141414, Bug #75100)

     * The Query Stats information tab was populated even when
       the Performance Schema was disabled. (Bug #20141262, Bug
       #75101)

     * The Toggle whether execution of SQL script should
       continue after failed statements button was updated to
       better indicate when the option is enabled or disabled.
       (Bug #20093801, Bug #74982)

     * On Windows, after closing and reopening Workbench with
       several SQL Editor tabs open, the tabs names were hash
       values (instead of MySQL connection names) if the
       connection names contained non-standard text. (Bug
       #20086117, Bug #74966)

     * In the Table Editor, if a column has NN checked, and NN
       is then unchecked, then a default NULL value is
       automatically added to the CREATE TABLE statement when
       Apply is clicked. The column then shows a default value
       of NULL in the Table Editor. (Bug #19890571, Bug #74558)

     * If a setting is (incorrectly) defined twice in my.ini,
       Workbench separates its values with a newline ("\n"). For
       example, if sort_buffer_size is defined twice, Workbench
       displays it as "sort_buffer_size=256K\n256K". Workbench
       now follows MySQL Server behavior, and uses the last
       defined option. (Bug #19769849)

     * The cursor could seemingly disappear after executing a
       query, as it could remain at its last position when the
       query started to execute. (Bug #19703074, Bug #74128)

     * The model Page setup... functionality was not always
       preserved when choosing a size for printing. (Bug
       #11766583, Bug #59724)

 On behalf of the MySQL Workbench and the MySQL/ORACLE RE Team
 Gipson Pulla

Dear MySQL users,

MySQL Connector/Net 7.0.3 is the second development release of MySQL
Connector/Net to add support for the new X DevAPI.  The X DevAPI enables
application developers to write code that combines the strengths of the
relational and document models using a modern, NoSQL-like syntax that
does not assume previous experience writing traditional SQL.

To learn more about how to write applications using the X DevAPI, see
http://dev.mysql.com/doc/x-devapi-userguide/en/index.html. For more
information about how the X DevAPI is implemented in Connector/Net, see
http://dev.mysql.com/doc/dev/connector-net.

Please note that the X DevAPI requires at least MySQL Server version
5.7.12 or higher with the X Plugin enabled. For general documentation
about how to get started using MySQL as a document store, see
http://dev.mysql.com/doc/refman/5.7/en/document-store.html.

Changes in MySQL Connector/Net 7.0.3 (2016-06-20, Milestone 2)


     * Functionality Added or Changed

     * Bugs Fixed

   Functionality Added or Changed

     * Fixed binary collations as strings instead of bytes.

     * Added TLS support for TLSv1.1 and TLSv1.2 when connecting
       to MySQL Server 5.7.

   Bugs Fixed

     * Added results to the Commit() and Rollback() Session X
       DevAPI methods, in order to read Warnings. This feature
       has limitations that will be addressed in a future
       release.

     * Replaced the use of "@" for "$" in JSON path expressions
       for X DevAPI usage. This feature has limitations that
       will be addressed in a future release.

     * Added X DevAPI support for TLSv1.0. This feature has
       limitations that will be addressed in a future release.


Nuget packages are available at:

https://www.nuget.org/packages/MySql.Data/7.0.3-DMR
https://www.nuget.org/packages/MySql.Data.Entity/7.0.3-DMR
https://www.nuget.org/packages/MySql.Fabric/7.0.3-DMR
https://www.nuget.org/packages/MySql.Web/7.0.3-DMR


Enjoy and thanks for the support!

On behalf of the MySQL Release Team
Prashant Tekriwal

Dear MySQL users,

MySQL Connector/Node.js is a new Node.js driver for use with the X
DevAPI. This release, v1.0.3 M2, is the second development release of the
MySQL Connector/Node.js 1.0 series.

The X DevAPI enables application developers to write code that combines
the strengths of the relational and document models using a modern,
NoSQL-like syntax that does not assume previous experience writing
traditional SQL.

To learn more about how to write applications using the X DevAPI, see
http://dev.mysql.com/doc/x-devapi-userguide/en/. For more information
about how the X DevAPI is implemented in MySQL Connector/Node.js, and
its usage, see http://dev.mysql.com/doc/dev/connector-nodejs/.

Please note that the X DevAPI requires at least MySQL Server version
5.7.12 or higher with the X Plugin enabled. For general documentation
about how to get started using MySQL as a document store, see
http://dev.mysql.com/doc/refman/5.7/en/document-store.html.

Changes in MySQL Connector/Node.js 1.0.3 (2016-06-21 Milestone 2)

      Bugs Fixed

        * Connector/Node.JS was unable to create a session when SSL
          was enabled. (Bug #23118665)


Enjoy and thanks for the support!

On Behalf of the MySQL/ORACLE RE Team
Hery Ramilison