Dear MySQL users,

MySQL Shell 1.0.4 M2 is the second development release of the
MySQL for MySQL Shell 1.0 series.

The MySQL Shell is an interactive JavaScript and Python command-line
interface, supporting development and administration for the MySQL
Server. The MySQL Shell enables developers to use a new Create Read
Update Delete (CRUD) API. MySQL Shell is a component of the MySQL
Server.

This is a Developer Release, so we are looking forward to getting your
feedback on the MySQL Shell as well as the new API and all the other new
features.

The MySQL Shell provides

     * Both Interactive and Batch operations

     * JavaScript, Python, and SQL language modes

     * Document and Relational Models

     * CRUD Document and Relational API via scripting

     * Output results in Traditional Table, JSON, and Tab Separated formats

     * Global and Stored Sessions

     * And much more


To download the MySQL Shell
http://dev.mysql.com/downloads/shell

To learn more about MySQL Shell, a component of the MySQL Server, see
http://dev.mysql.com/doc/refman/5.7/en/mysql-shell.html

To learn more about using MySQL as a document store, see
http://dev.mysql.com/doc/refman/5.7/en/document-store.html

For MySQL Shell Tutorials
JavaScript - http://dev.mysql.com/doc/refman/5.7/en/mysqlx-shell-tutorial-javascript.html
Python - http://dev.mysql.com/doc/refman/5.7/en/mysqlx-shell-tutorial-python.html

User documentation for the new X DevAPI
http://dev.mysql.com/doc/x-devapi-userguide/en/index.html

For more information about how the X DevAPI is implemented in MySQL Shell,
and its usage, see http://dev.mysql.com/doc/dev/mysqlsh-devapi/

Changes in MySQL Shell 1.0.4 (2016-06-23, Milestone 2)

   Bugs Fixed

     * A space was missing after the Python prompt. (Bug
       #23304556)

     * Functions depending on an internal cache, such as
       Schema.collections, Schema.tables, and Schema.views were
       not being updated correctly, which made statements such
       as DROP appear to not function correctly. (Bug #23095017,
       Bug #81040)

     * Using SSL to create a connection was failing with MySQL
       Error (2026): SSL bad version. (Bug #81094, Bug
       #23112964)

     * The help text has been improved to be more accurate and
       use correct language. (Bug #81085, Bug #23106440)

On behalf of the MySQL Release Team,
Balasubramanian Kandasamy 

Dear MySQL users,

MySQL Connector/J 6.0.3 m2 Development Release is a developer milestone
release for the 6.0.x series.

It is the second public release of the current Connector/J 6.0 development
branch, providing an insight to upcoming features. Although some of
these are still under development, this release includes the following
new features and changes, also described in more detail on
http://dev.mysql.com/doc/relnotes/connector-j/en/news-6-0-3.html.

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.

Enjoy!

Changes in MySQL Connector/J 6.0.3 m2 (2016-06-24)

     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)

       * SSL is now supported for connections to a MySQL server
         using the X Protocol. (Bug #21532788)

       * The following objects are no longer extensions of the
         Extension interface, but get their own implementations
         now, which reduces their dependencies on other objects:

            + BalanceStrategy

            + ProfilerEventHandler

            + AuthenticationPlugin

     Bugs Fixed

       * An excessive amount of memory was used when the
         connection properties enablePacketDebug and traceProtocol
         were both set to "true." (Bug #23535571)

       * 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)

       * The download package for Connector/J 6.0.2 Milestone 1
         contained the Developer Guide for the wrong version of
         Connector/J. (Bug #23111273, Bug #81089)

       * A NullPointerException occurred in
         com.mysql.cj.mysqlx.io.AsyncMessageReader due to a race
         condition when there were more than 2000 concurrent
         connections taking place. (Bug #23044312)

       * getTimestamp() returned wrong value for the fractional
         part of a TIME or DATETIME field. (Bug #22932078)

       * 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 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/6.0/en/connector-j-
         reference-configuration-properties.html) for details.
         (Bug #22678872)
         References: See also: Bug #22848249.

       * 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)

       * After a failed call of a stored procedure, any subsequent
         X DevAPI call resulted in a hang. (Bug #22038729)

       * 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)

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

       * 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)

       * When working with MySQL server 5.5 and 5.6, because
         Connector/J did not check the version number of the
         server it was connected to, errors and failures occurred
         when there was an attempt to use certain
         version-dependent features (for example, using fractional
         seconds for servers earlier than 5.6.4). With this fix,
         the proper exceptions are thrown in those cases.

Documentation
--------------
Online: http://dev.mysql.com/doc/connector-j/6.0/en/index.html

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 Connector/Net 6.9.9 is a maintenance release for the 6.9.x
series of the .NET driver for MySQL. It can be used for production
environments.

It is appropriate for use with MySQL server versions 5.5-5.7.

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

Changes in MySQL Connector/Net 6.9.9 (2016-07-01)


   Functionality Added or Changed

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

   Bugs Fixed

     * Improvements were made to how the connector handles
       aborted connections. (Bug #23346197, Bug #80997)

     * With Entity Framework 6, building a table with a primary
       key would not enclose the key name in quotes, which
       caused a syntax error. (Bug #22696180, Bug #22696207, Bug
       #76292)

     * The connector was not disposing the transaction returned
       by DBContext.Database.BeginTransaction() when exiting a
       using code block. (Bug #22514355, Bug #22514363)

     * The connector did not attempt to enumerate stored
       procedures via mysql.proc(). Instead it looked up stored
       procedures in INFORMATION_SCHEMA.ROUTINES. This could
       have led to performance degradation in certain scenarios.
       (Bug #20960373, Bug #23528155, Bug #74116)


The documentation is available at:
http://dev.mysql.com/doc/connector-net/en/

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


Enjoy and thanks for the support!

On behalf of the MySQL Connector/NET and the MySQL/ORACLE RE Team.

Dear MySQL users,

MySQL for Visual Studio 2.0.3 M2 is the second 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/doc/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.

You can download MySQL Installer from our official Downloads page at
http://dev.mysql.com/downloads/installer/.

MySQL for Visual Studio can also be downloaded by using the product
standalone installer found at
http://dev.mysql.com/downloads/windows/visualstudio/.

Changes in MySQL for Visual Studio 2.0.3 (2016-07-01, Milestone 2)

   Known limitation of this release: Some features such as Entity
   Framework and some Server Explorer functionality like drag & drop
   elements into a Dataset Designer or Design Tables do not work in this
   version.

     * Functionality Added or Changed

     * Bugs Fixed

   Functionality Added or Changed

     * Improved the handling of errors to manage exceptions from
       MySQL Shell, and to display relevant information about the
       exceptions in the selected output. This includes the full error
       message from MySQL Shell.

     * Added SSL support for MySQL connections that use the X
       Protocol. SSL support works with PEM files, so SSL connections
       need to be created through the "MySQL Connections Manager" in
       MySQL for Visual Studio, or from MySQL Workbench.

     * Added support for the following X DevAPI functions:
       parseUri() and isOpen().

     * A new MySQL Output pane was added that contains a results
       grid view similar to the view found in MySQL Workbench.  It
       contains the following data for executed statements: Success,
       Execution index, Execution Time, Query Text, Message (output from
       the server), and Duration / Fetch.  This functionality is
       available for JavaScript and Python queries.

     * Added "Console Mode" support for JavaScript and Python
       script editors, where query execution mimics the way the MySQL
       Shell works, meaning X DevAPI statements are executed after
       hitting "ENTER" and results are displayed inline.

     * Added the ability to switch between "Batch" (execute
       multiple statements) and "Console" (execute each statement after
       pressing Enter) modes, from the Query Editor toolbar as a
       dropdown list.

     * A MySQL connection manager dialog was added to help fully
       manage MySQL connections. It supports connection sharing with
       MySQL Workbench, and supports create, edit, configure, and delete
       actions.  MySQL connections created with the connection manager
       where the password is securely stored in the system's password
       vault functions with the Server Explorer in Visual Studio. The
       password is extracted from the password vault, and persists in
       the Server Explorer connections.

   Bugs Fixed

     * The "mysqlx" module was not imported properly to execute
       JavaScript queries. (Bug #23091964, Bug #81052)

     * After opening a valid MySQL connection and creating a new
       JavaScript MySQL script, disconnecting then reconnecting to the
       MySQL Server while changing the port to 33060 would fail.

     * MySQL for Visual Studio now shows a message stating that
       a SSL connection is required by the MySQL server if the
       require_secure_transport variable is set.

     * All script editors now display detailed information about
       the connection used. Before, the information was displayed in the
       toolbar as labels, but now all information is consolidated in a
       menu opened where the connection name is displayed. Additional
       information includes the connection method, host identifier,
       server version, user, and schema.

     * Output from executing JavaScript and Python commands were
       not visible unless the Output window was already opened.  The
       Output window now automatically opens when executing commands.


On behalf of the Oracle MySQL Release Engineering Team,
Nawaz

Dear MySQL users,

MySQL Connector/Net 6.8.8 is a maintenance release for the 6.8.x
series of the .NET driver for MySQL. It can be used for production
environments.

It is appropriate for use with MySQL server versions 5.5-5.7.

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

Changes in MySQL Connector/Net 6.8.8 (2016-07-01)

Functionality Added or Changed

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

Bugs Fixed

    * Improvements were made to how the connector handles
      aborted connections. (Bug #23346197, Bug #80997)

    * With Entity Framework 6, building a table with a primary
      key would not enclose the key name in quotes, which
      caused a syntax error. (Bug #22696180, Bug #22696207, Bug
      #76292)

    * The connector was not disposing the transaction returned
      by DBContext.Database.BeginTransaction() when exiting a
      using code block. (Bug #22514355, Bug #22514363)

    * The connector did not attempt to enumerate stored
      procedures via mysql.proc(). Instead it looked up stored
      procedures in INFORMATION_SCHEMA.ROUTINES. This could
      have led to performance degradation in certain scenarios.
      (Bug #20960373, Bug #23528155, Bug #74116)

The documentation is available at:
http://dev.mysql.com/doc/connector-net/en/

Nuget packages are available at:

https://www.nuget.org/packages/MySql.Data/6.8.8
https://www.nuget.org/packages/MySql.Data.Entity/6.8.8
https://www.nuget.org/packages/MySql.Web/6.8.8

Enjoy and thanks for the support!

On behalf of the MySQL Connector/NET and the MySQL/ORACLE RE Team.
Hery Ramilison

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.3(Release Candidate), 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.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.3 (5.7.13-ndb-7.5.3) (2016-07-08,
Release Candidate)

   MySQL Cluster NDB 7.5.3 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.13 (see Changes in MySQL 5.7.13
   (2016-06-02)
   (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-13.h
   tml)).


   Functionality Added or Changed

     * Important Change: It is now possible to set READ_BACKUP
       for an existing table online using an SQL statement such
       as ALTER TABLE ... ALGORITHM=INPLACE,
       COMMENT="NDB_TABLE=READ_BACKUP=1"
       (http://dev.mysql.com/doc/refman/5.7/en/alter-table-onlin
       e-operations.html). See Setting NDB_TABLE options in
       table comments
       (http://dev.mysql.com/doc/refman/5.7/en/create-table-ndb-
       table-comment-options.html), for further information
       about the READ_BACKUP option. (Bug #80858, Bug #23001617)
       References: See also: Bug #18435416.

     * Added three new tables to the ndbinfo
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
       info.html) information database to provide running
       information about locks and lock attempts in an active
       MySQL Cluster. These tables, with brief descriptions, are
       listed here:

          + cluster_locks
            (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluste
            r-ndbinfo-cluster-locks.html): Current lock requests
            which are waiting for or holding locks; this
            information can be useful when investigating stalls
            and deadlocks. Analogous to cluster_operations.

          + locks_per_fragment
            (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluste
            r-ndbinfo-locks-per-fragment.html): Counts of lock
            claim requests, and their outcomes per fragment, as
            well as total time spent waiting for locks
            successfully and unsuccessfully. Analogous to
            operations_per_fragment
            (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluste
            r-ndbinfo-operations-per-fragment.html) and
            memory_per_fragment
            (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluste
            r-ndbinfo-memory-per-fragment.html).

          + server_locks
            (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluste
            r-ndbinfo-server-locks.html): Subset of cluster
            transactions---those running on the local mysqld,
            showing a connection ID per transaction. Analogous
            to server_operations
            (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluste
            r-ndbinfo-server-operations.html).
       For more information, see The ndbinfo MySQL Cluster
       Information Database
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
       info.html).

   Bugs Fixed

     * The ndbinfo
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
       info.html) cpustat_1sec
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
       info-cpustat-1sec.html) and cpustat_20sec
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
       info-cpustat-20sec.html) tables did not provide any
       history information. (Bug #23520271)

     * During shutdown, the mysqld process could sometimes hang
       after logging NDB Util: Stop ... NDB Util: Wakeup. (Bug
       #23343739)
       References: See also: Bug #21098142.

     * During expansion or reduction of a hash table, allocating
       a new overflow page in the DBACC kernel block caused the
       data node to fail when it was out of index memory. This
       could sometimes occur after a large table had increased
       or decreased very rapidly in size. (Bug #23304519)
       References: This issue is a regression of: Bug #13436216.

     * Following a restart of the cluster, the first attempt to
       read from any of the ndbinfo
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
       info.html) cpustat
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
       info-cpustat.html), cpustat_50ms
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
       info-cpustat-50ms.html), cpustat_1sec
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
       info-cpustat-1sec.html), or cpustat_20sec
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
       info-cpustat-20sec.html) tables generated a warning to
       the effect that columns were missing from the table.
       Subsequently, the thread_sleeping and spin_time columns
       were found to be missing from each of these tables. (Bug
       #81681, Bug #23514557)
       References: See also: Bug #23305078.

     * Using a ThreadConfig
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
       d-definition.html#ndbparam-ndbmtd-threadconfig) parameter
       value with a trailing comma led to an assertion. (Bug
       #81588, Bug #23344374)

     * Cluster API: The scan lock takeover issued by
       NdbScanOperation::lockCurrentTuple()
       (http://dev.mysql.com/doc/ndbapi/en/ndb-ndbscanoperation-
       methods.html#ndb-ndbscanoperation-lockcurrenttuple) did
       not set the operation type for the takeover operation.
       (Bug #23314028)      * Table indexes were listed in the output of ndb_desc in a
       nondeterministic order that could vary between platforms.
       Now these indexes are ordered by ID in the output. (Bug
       #81763, Bug #23547742)

Regards
-Sree

Dear MySQL users,

MySQL Connector Python 2.2.0 M1 is the first development release of the
MySQL Connector Python 2.2 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 Connector/Python, and its
usage, see http://dev.mysql.com/doc/dev/connector-python.

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.

Enjoy and thanks for the support!

On behalf of the MySQL Release Team
Balasubramanian Kandasamy

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.3.14, 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.3/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.3.14 (5.6.31-ndb-7.3.14) (2016-07-18)

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

   Obtaining MySQL Cluster NDB 7.3.  MySQL Cluster NDB 7.3
   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.3, see
   What is New in MySQL Cluster NDB 7.3
   (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is
   -new-7-3.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.31 (see Changes in MySQL 5.6.31
   (2016-06-02)
   (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-31.h
   tml)).

     * Functionality Added or Changed

     * Bugs Fixed

   Functionality Added or Changed

     * ClusterJ: To make it easier for ClusterJ to handle fatal
       errors that require the SessionFactory to be closed, a
       new public method in the SessionFactory interface,
       getConnectionPoolSessionCounts()
       (http://dev.mysql.com/doc/ndbapi/en/mccj-clusterj-session
       factory.html#mccj-clusterj-sessionfactory-getconnectionpo
       olsessioncounts), has been created. When it returns zeros
       for all pooled connections, it means all sessions have
       been closed, at which point the SessionFactory can be
       closed and reopened. See Reconnecting to a MySQL Cluster
       (http://dev.mysql.com/doc/ndbapi/en/mccj-using-clusterj-s
       tart.html#mccj-using-clusterj-reconnect) for more detail.
       (Bug #22353594)

   Bugs Fixed

     * 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)

     * 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, the other data node
       shut down as well, due to arbitration failure. (Bug
       #23006431)

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


On behalf of the MySQL Release Team,
Balasubramanian Kandasamy

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.12, 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.12 (5.6.31-ndb-7.4.12) (2016-07-18)

   MySQL Cluster NDB 7.4.12 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.31 (see Changes in MySQL 5.6.31
   (2016-06-02)
   (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-31.h
   tml)).

   Functionality Added or Changed

     * ClusterJ: To make it easier for ClusterJ to handle fatal
       errors that require the SessionFactory to be closed, a
       new public method in the SessionFactory interface,
       getConnectionPoolSessionCounts()
       (http://dev.mysql.com/doc/ndbapi/en/mccj-clusterj-session
       factory.html#mccj-clusterj-sessionfactory-getconnectionpo
       olsessioncounts), has been created. When it returns zeros
       for all pooled connections, it means all sessions have
       been closed, at which point the SessionFactory can be
       closed and reopened. See Reconnecting to a MySQL Cluster
       (http://dev.mysql.com/doc/ndbapi/en/mccj-using-clusterj-s
       tart.html#mccj-using-clusterj-reconnect) for more detail.
       (Bug #22353594)

   Bugs Fixed

     * 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)

     * Although arguments to the DUMP command are 32-bit
       integers, ndb_mgmd used a buffer of only 10 bytes when
       processing them. (Bug #23708039)

     * During shutdown, the mysqld process could sometimes hang
       after logging NDB Util: Stop ... NDB Util: Wakeup. (Bug
       #23343739)
       References: See also: Bug #21098142.

     * During an online upgrade from a MySQL Cluster NDB 7.3
       release to an NDB 7.4 (or later) release, the failures of
       several data nodes running the lower version during local
       checkpoints (LCPs), and just prior to upgrading these
       nodes, led to additional node failures following the
       upgrade. This was due to lingering elements of the
       EMPTY_LCP protocol initiated by the older nodes as part
       of an LCP-plus-restart sequence, and which is no longer
       used in NDB 7.4 and later due to LCP optimizations
       implemented in those versions. (Bug #23129433)

     * 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, the other data node
       shut down as well, due to arbitration failure. (Bug
       #23006431)

     * The ndbinfo.tc_time_track_stats table uses histogram
       buckets to give a sense of the distribution of latencies.
       The sizes of these buckets were also reported as
       HISTOGRAM BOUNDARY INFO messages during data node
       startup; this printout was redundant and so has been
       removed. (Bug #22819868)

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

     * mysqld did not shut down cleanly when executing
       ndb_index_stat. (Bug #21098142)
       References: See also: Bug #23343739.

     * 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 >= 2.

          + Added the 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.

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

On behalf of the MySQL Release Team
-Sree

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.25, 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.25 (5.5.50-ndb-7.2.25) (2016-07-18)

   MySQL Cluster NDB 7.2.25 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.50 (see Changes in MySQL 5.5.50
   (2016-06-02)
   (http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-50.html)).

   Bugs Fixed

     * 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)

On behalf of Oracle MySQL RE team
Gipson Pulla

Dear MySQL users,

MySQL Enterprise Backup v4.0.2, 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.2 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.2 is given below.

Changes in MySQL Enterprise Backup 4.0.2 (2016-07-26)

Functionality Added or Changed

     * When there were no tables matching the regular expression
       specified with the --include-table option during a backup
       operation, mysqlbackup still created a backup, which
       contained an empty folder for each database on the
       server. mysqlbackup now throws an error when
       --include-tables selects no tables to be backed up. (Bug
       #18114353)

     * MySQL Enterprise Backup can now backup and restore
       encrypted InnoDB tables. See Working with Encrypted
       InnoDB Tables and Options for Working with Encrypted
       InnoDB Tablespaces for details.

   Bugs Fixed

     * When trying to restore a compressed image backup of a
       server that had separate undo tablespaces residing in the
       data directory with the copy-back-and-apply-log command,
       the operation failed at the apply-log phase, as
       mysqlbackup could not load the undo tablepaces. (Bug
       #23583961)

     * Attempts to restore an image backup from the cloud using
       the --skip-binlog option failed with a "global tail magic
       mismatch" error. This was because mysqlbackup failed to
       perform a non-sequential read from the cloud with gaps
       caused by the skipping of the binary logs. This fix makes
       sure mysqlbackup can perform such reads. (Bug #23534700)

     * When a compressed backup was being restored, if the undo
       logs had been put into separate tablespaces outside of
       the data directory on the backed up server, they got
       restored twice, once mistakenly as general tablespaces
       with the .ibd extension, and once as undo tablespaces
       without a file extension. This fix makes sure they are
       restored normally as undo tablespaces only. (Bug
       #23179194)

     * An extract operation for an image backup failed with a
       checksum mismatch error in cases when, during the backup,
       an InnoDB tablespace file kept growing in size, and
       mysqlbackup failed to put the correct file size in its
       file header. (Bug #22905984)
       References: This issue is a regression of: Bug #22613568.

     * During a mysqlbackup operation on a compressed backup
       (that is, the --uncompress option was used), mysqlbackup,
       in some situations, wrote to the log file multiple
       instances of the message "ERROR: InnoDB: file write at
       offset > 4 GB," even though the operation was actually
       successful. (Bug #22733760)

     * Occasionally, some files were missing from an image
       backup created by the --backup-to-image command. It was
       due to an internal race condition, which this fix
       eliminates. (Bug #19600687)

The complete manual for MEB 4.0.2 is at
http://dev.mysql.com/doc/mysql-enterprise-backup/4.0/en/index.html

The tool is available for download from Oracle Software Delivery
Cloud (http://edelivery.oracle.com/).

You can also download the binaries from MOS, https://support.oracle.com
Choose the "Patches & Updates" tab, and then use the "Product or Family
(Advanced Search)" feature. If you haven't looked at MEB recently,
please do so now and let us know how MEB works for you.

Your feedback is greatly appreciated!

Please report any problems you have at https://bug.oraclecorp.com/
for the product "MySQL Enterprise Backup"

Thanks,

On behalf MySQL RE team at Oracle

Sreedhar S

Dear MySQL users,

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

Enjoy!


Changes in MySQL 5.5.51 (2016-07-29)

   Bugs Fixed

     * Replication: When using statement-based or mixed binary
       logging format with --read-only=ON, it was not possible to modify
       temporary tables. (Bug #62008, Bug #12818255) References: See
       also: Bug #14294223, Bug #16561483.

     * MySQL Server upgrades performed using RPM packages failed
       when upgrading from MySQL 5.1 Community to MySQL 5.5 Community or
       MySQL 5.1 Commercial to MySQL 5.5 Commercial. (Bug #23736787)

     * A buffer overflow in the regex library was fixed. (Bug
       #23498283)

     * Certain arguments to NAME_CONST() could cause a server
       exit. (Bug #23279858)

     * 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)

     * If a stored function updated a view for which the view
       table had a trigger defined that updated another table, it could
       fail and report an error that an existing table did not exist.
       (Bug #21142859, Bug #76808)

     * If an INSTALL PLUGIN statement contained invalid UTF-8
       characters in the shared library name, it caused the server to
       hang (or to raise an assertion in debug builds). (Bug #14653594,
       Bug #23080148)

     * For multibyte character sets, LOAD DATA could fail to
       allocate space correctly and ignore input rows as a result. (Bug
       #76237, Bug #20683959, Bug #23080148) References: This issue is a
       regression of: Bug #14653594.

On behalf of Oracle MySQL Release Engineering Team,
Nawaz Nazeer Ahamed

Dear MySQL users,

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

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

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

     Starting with 5.6.11, Microsoft Windows packages for MySQL 5.6
     are available both as a "full" installer and as a "web" installer.
     The full installer is significantly larger and comes bundled with
     the latest software releases available. This bundle makes it easy
     to download and configure a full server and development suite.

     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.

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

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

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

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

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

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

  https://wikis.oracle.com/display/mysql/Contributing

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

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

Enjoy!

==============================================================================
Changes in MySQL 5.6.32 (2016-07-29)

   Bugs Fixed

     * InnoDB: Full-text search auxiliary tables could be
       dropped by one session while being access by another.
       (Bug #23742339)

     * InnoDB: Selecting full-text index information schema
       tables for a deleted table caused a segmentation fault.
       (Bug #23479595)

     * InnoDB: Rollback of a full-text index synchronization
       operation raised an assertion. The rollback operation
       attempted to acquire a mutex still held by the background
       synchronization thread. (Bug #23320569)

     * InnoDB: Setting innodb_monitor_enable to all did not
       enable all counters. (Bug #22576241, Bug #80083)

     * Replication: When using row-based replication and InnoDB,
       replication slaves reverted to using an older locking
       scheme when a transaction had already acquired an AUTOINC
       lock related to a LOAD FILE or INSERT ... SELECT type of
       statement, reducing replication slave performance. The
       fix ensures that sql_command is set correctly for any of
       the DML events such as WRITE_ROWS_EVENT, UPDATE_EVENT,
       and DELETE_EVENT. (Bug #79324, Bug #22247668)

     * Replication: When using statement-based or mixed binary
       logging format with --read-only=ON, it was not possible
       to modify temporary tables. (Bug #62008, Bug #12818255)
       References: See also: Bug #14294223, Bug #16561483.

     * MySQL Server upgrades performed using RPM packages failed
       when upgrading from MySQL 5.5 Community to MySQL 5.6
       Community or MySQL 5.5 Commercial to MySQL 5.6
       Commercial. (Bug #23736787)

     * The code for reading character set information from
       Performance Schema statement events tables (for example,
       events_statements_current) did not prevent simultaneous
       writing to that information. As a result, the SQL query
       text character set could be invalid, which could result
       in a server exit. Now an invalid character set causes
       SQL_TEXT column truncation. (Bug #23540008)

     * A buffer overflow in the regex library was fixed. (Bug
       #23498283)

     * Certain arguments to NAME_CONST() could cause a server
       exit. (Bug #23279858)

     * For unit-testing with the MySQL test suite, the make
       unit-test command is no longer available. The ctest
       program should be used instead. See Unit Tests Added to
       Main Test Runs
       (http://dev.mysql.com/doc/mysqltest/2.0/en/unit-tests-fro
       m-mtr.html). (Bug #23273434)

     * ST_Distance() could raise an assertion for NULL return
       values. (Bug #22760390)

     * With the query cache enabled, executing a prepared
       statement with CURSOR_TYPE_READ_ONLY and then again with
       CURSOR_TYPE_NO_CURSOR caused the server to return an
       error. (Bug #22559575, Bug #80026)

     * mysql_real_connect() was not thread-safe when invoked
       with the MYSQL_READ_DEFAULT_FILE or
       MYSQL_READ_DEFAULT_GROUP option enabled. (Bug #22322504,
       Bug #79510)

     * 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)

     * If a stored function updated a view for which the view
       table had a trigger defined that updated another table,
       it could fail and report an error that an existing table
       did not exist. (Bug #21142859, Bug #76808)

     * If an INSTALL PLUGIN statement contained invalid UTF-8
       characters in the shared library name, it caused the
       server to hang (or to raise an assertion in debug
       builds). (Bug #14653594, Bug #23080148)

     * For multibyte character sets, LOAD DATA could fail to
       allocate space correctly and ignore input rows as a
       result. (Bug #76237, Bug #20683959, Bug #23080148)
       References: This issue is a regression of: Bug #14653594.

On Behalf of MySQL RE Team
Prashant Tekriwal

Dear MySQL users,

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

Since MySQL Server 5.7.13, we have introduced the concept of
Rapid Plugins. Out of the box, 5.7.14 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.14 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.14 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.14 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.14 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.14 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.13. It may also be viewed
online at

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

Enjoy!

Changes in MySQL 5.7.14 (2016-07-29)

    sys Schema Notes

      * The sys schema now has a quote_identifier() function
        that, given a string argument, produces a quoted
        identifier suitable for inclusion in SQL statements. (Bug
        #22011361, Bug #78823)

      * Output from the sys schema diagnostics() procedure now
        includes the Tls_version column from the
        mysql.slave_master_info system table.

    Functionality Added or Changed

      * The %global compatver value for RPM packages for RHEL/OEL
        and Fedora releases was updated from 5.6.25 to 5.6.31.
        (Bug #23038018)
        References: See also: Bug #22980983.

      * Specifying an empty value for the --port option (for
        example, --port=, --port="") is now deprecated and
        results in a warning. An empty value will be an error in
        MySQL 8.0. (Bug #23023457, Bug #80903)

      * CMake support for compiling with Solaris Studio 12.5 was
        added. (Bug #81274, Bug #23212938)

      * The INFORMATION_SCHEMA INNODB_LOCKS and INNODB_LOCK_WAITS
        tables are now deprecated and will be removed in a future
        MySQL release.

    Bugs Fixed

      * Performance: A flaw in the allocation of memory for
        appending string values caused some operations to be
        performed slowly, including creation of tables having
        generated columns and inserts of large values into JSON
        columns. (Bug #80556, Bug #22843444)
        References: See also: Bug #22157531, Bug #22239803.

      * InnoDB: Full-text search auxiliary tables could be
        dropped by one session while being access by another.
        (Bug #23742339)

      * InnoDB: Selecting full-text index information schema
        tables for a deleted table caused a segmentation fault.
        (Bug #23479595)

      * InnoDB: A tablespace operation did not properly update
        the SYS_VIRTUAL system table. (Bug #23325659)

      * InnoDB: Rollback of a full-text index synchronization
        operation raised an assertion. The rollback operation
        attempted to acquire a mutex still held by the background
        synchronization thread. (Bug #23320569)

      * InnoDB: After compressing a table, an incorrect data
        length was passed to an internal tablespace encryption
        function, causing an assertion. (Bug #23279788)
        References: This issue is a regression of: Bug #22956469.

      * InnoDB: An r-tree page lock placed during a search
        operation prevented an undo operation within the same
        transaction from merging pages. (Bug #23241575)

      * InnoDB: A bulk load insert of a record with a compressed
        size greater than half of the compressed page size
        resulted in infinite B-tree page splitting when
        compressing the uncompressed page. (Bug #23120933)

      * InnoDB: A lock order violation related to InnoDB
        full-text search caused errors and raised an assertion.
        (Bug #23120005)
        References: This issue is a regression of: Bug #22996488.

      * InnoDB: In read-only mode, InnoDB attempted to set a
        corrupt bit in the SYS_INDEXES system table. In read-only
        mode, the corruption should only be marked in memory.
        (Bug #23077748)

      * InnoDB: InnoDB attempted to materialize non-key generated
        virtual columns that were not required for partitioning.
        (Bug #23037025)
        References: This issue is a regression of: Bug #21864838.

      * InnoDB: An insert operation on a table containing virtual
        and spatial indexes raised an assertion due to an invalid
        parent path encountered during page splitting. (Bug
        #23008863)

      * InnoDB: An ALTER TABLE operation on a table with an
        indexed virtual column raised an assertion. (Bug
        #22965271)

      * InnoDB: Adding or dropping a generated virtual column
        could raise an assertion due to a table handle held by an
        active memcached connection. (Bug #22922527)

      * InnoDB: A full-text query that involved a large number of
        records exceeded the result cache limit and caused a
        server exit. (Bug #22709692, Bug #80296)

      * InnoDB: InnoDB did not block the creation of a foreign
        key constraint with referential actions on the base
        column of a generated stored column. (Bug #22687023, Bug
        #80304)

      * InnoDB: The optimizer failed to mark the columns required
        for MATCH function evaluation when the secondary index
        used for the full-text query was not chosen by the
        optimizer. (Bug #22679209, Bug #80298)

      * InnoDB: In READ COMMITTED isolation level, InnoDB
        unnecessarily acquired the lock_sys mutex at COMMIT for a
        transaction block consisting of read-only SELECT
        statements.
        Thanks to Zhai Weixiang for the patch. (Bug #22617328,
        Bug #76728)

      * InnoDB: Setting innodb_monitor_enable to all did not
        enable all counters. (Bug #22576241, Bug #80083)

      * InnoDB: InnoDB now permits defining a foreign key
        constraint with a cascading referential action on the
        base column of an indexed virtual column, and defining
        cascading referential actions on non-virtual foreign key
        columns that are explicitly included in a virtual index.
        (Bug #22469130, Bug #79772)

      * InnoDB: An assertion was raised during rollback of an
        ALTER TABLE operation that dropped and added a secondary
        index. (Bug #22005726)

      * Partitioning: In some cases, an issue with partition
        pruning being attempted a second time during optimization
        after all partitions had already been pruned at parsing
        time led to an assert. (Bug #23194259)

      * Replication: Replication slaves could exit trying to
        apply an UPDATE row event containing virtual generated
        columns received from a master that was set to
        binlog_row_image=minimal. (Bug #23604483)

      * Replication: When using row-based replication and InnoDB,
        replication slaves reverted to using an older locking
        scheme when a transaction had already acquired an AUTOINC
        lock related to a LOAD FILE or INSERT ... SELECT type of
        statement, reducing replication slave performance. The
        fix ensures that sql_command is set correctly for any of
        the DML events such as WRITE_ROWS_EVENT, UPDATE_EVENT,
        and DELETE_EVENT. (Bug #79324, Bug #22247668)

      * Replication: When using statement-based or mixed binary
        logging format with --read-only=ON, it was not possible
        to modify temporary tables. (Bug #62008, Bug #12818255)
        References: See also: Bug #14294223, Bug #16561483.

      * MySQL Server upgrades performed using RPM packages failed
        when upgrading from MySQL 5.6 Community to MySQL 5.7
        Community or MySQL 5.6 Commercial to MySQL 5.7
        Commercial. (Bug #23736787)

      * On CentOS, mysqld installed from a MySQL Community
        distribution failed to start if a my.cnf file with no
        datadir value specified was used. (Bug #23721277, Bug
        #82049)

      * The -DWITH_EDITLINE=system CMake option failed with
        recent versions of the editline library. (Bug #23708332)

      * Executing prepared statements with the audit_log plugin
        installed could cause a server exit. (Bug #23699991)

      * The sys schema ps_trace_statement_digest() procedure
        failed for statements not supported by EXPLAIN, for
        statements for which EXPLAIN could not find tables, and
        for statements with no digest found during the monitored
        period. (Bug #23621189)

      * A SELECT Performance Schema tables when an internal
        buffer was full could cause a server exit. (Bug
        #23550835, Bug #23298025, Bug #81464)

      * The code for reading character set information from
        Performance Schema statement events tables (for example,
        events_statements_current) did not prevent simultaneous
        writing to that information. As a result, the SQL query
        text character set could be invalid, which could result
        in a server exit. Now an invalid character set causes
        SQL_TEXT column truncation. (Bug #23540008)

      * An error message spelling error was corrected. Thanks to
        Derek Jones for the patch. (Bug #23525874, Bug #81713)

      * In the Performance Schema, allocating a record when a
        buffer was full could lead to a server exit. (Bug
        #23515302)

      * Several issues for Debian/Ubuntu packages were fixed:

           + The mysql-systemd-start script in the
             mysql-community-server package depended on
             mysqladmin for the ping command. Packages including
             this script now are made dependent on the
             mysql-community-client package.

           + The systemd service still used mysqld_safe. It now
             uses mysqld --daemonize.

           + Entering a blank root password during the
             installation process caused installation to hang.

           + MySQL upgrades failed to create a missing data
             directory.

           + In addition, CMake-generated packaging for
             Debian/Ubuntu packages was refactored for improved
             maintainability.
        (Bug #23501369, Bug #81647, Bug #22972977, Bug #21236550,
        Bug #21228746, Bug #22833016, Bug #23582336)

      * A buffer overflow in the regex library was fixed. (Bug
        #23498283)

      * Upgrading from native MySQL 5.6 Debian/Ubuntu packages to
        Oracle-supplied MySQL 5.7 packages caused server restart
        failures. (Bug #23498230)

      * The CMake configuration was too aggressive in making
        symbols invisible, resulting in link problems with GCC
        5.3 on Solaris. (Bug #23344916, Bug #81593)

      * Audit log filtering against the user was performing
        comparisons against USER(), not CURRENT_USER(). (Bug
        #23344762)

      * After upgrading only the server using RPM packages, the
        server could fail to start, complaining about a bad
        errmsg.sys file. (Bug #23338603)
        References: This issue is a regression of: Bug #18518216.

      * Several issues were addressed in the sys schema stored
        procedures that show enabled or disabled Performance
        Schema setup:

           + Enabled and disabled accounts were shown as
             host@user, not user@host.

           + Disabled users in ps_setup_show_disabled were called
             enabled_users.

           + ps_setup_show_enabled() showed disabled objects.

           + setup_actors content was not filtered (all rows were
             returned whether the actor was enabled or disabled).

           + Output order is more deterministic.
        (Bug #23335880, Bug #22066096, Bug #78874)

      * Upgrading from native Ubuntu 5.7.12 packages to MySQL
        5.7.13 packages failed with conflict messages. (Bug
        #23327563)

      * For debug builds, the server exited abnormally if a
        shutdown command was issued while the audit_log plugin
        was loaded and an active connection existed. (Bug
        #23310864)

      * The server could fail to interpret expired passwords as
        expired. (Bug #23291841)

      * Certain arguments to NAME_CONST() could cause a server
        exit. (Bug #23279858)

      * For unit-testing with the MySQL test suite, the make
        unit-test command is no longer available. The ctest
        program should be used instead. See Unit Tests Added to
        Main Test Runs (http://dev.mysql.com/doc/mysqltest/2.0/en/unit-tests-from-mtr.html).
        (Bug #23273434)

      * Audit log plugins (including query rewrite plugins, which
        use the audit API) were being acquired and released per
        statement, negatively affecting scalability. To improve
        performance, these plugins now are acquired once and
        released only when the connection ends. (Bug #23236404,
        Bug #81298)

      * mysql-test-run.pl now has a --manual-boot-gdb option that
        is similar to --boot-gdb but attaches the debugger to the
        server during the bootstrapping process, permitting the
        use of a remote debugger. (Bug #23090633)

      * The -fexpensive-optimizations option to GCC caused ARM64
        and PowerPC builds to compute floating-point operations
        slightly differently from other platforms. CMake now
        checks for this problem and disables the option as
        necessary. (Bug #23046775)

      * The test_service_sql_api.test_session_general_log test
        case now cleans up the general_log table by truncating it
        at the end of the test. Thanks to Daniel Black for the
        patch. (Bug #23021111, Bug #80895)

      * Lines written to the error log had no space separating
        the timestamp and thread ID columns if the thread ID took
        five or more characters. (Bug #23005009, Bug #80854)

      * For the innodb_buffer_stats_by_schema and
        innodb_buffer_stats_by_table sys schema views, the
        pages_hashed and pages_old columns were incorrect. Thanks
        to Tsubasa Tanaka for the patch. (Bug #22988461, Bug
        #80833)

      * An incorrect result could be returned for a query using a
        merged derived table or a view when compared to a similar
        query using a base table directly, if the query included
        a WHERE condition in a scalar subquery inside a HAVING
        condition of the main query block. (Bug #22967439)

      * ST_GeomFromGeoJSON() treated JSON NULL as invalid input.
        Now it treats JSON NULL as SQL NULL and thus returns SQL
        NULL for JSON NULL input. (Bug #22930020, Bug #80712)

      * For the host_summary_by_statement_latency and
        x$host_summary_by_statement_latency sys schema views, the
        max_latency column was incorrect. (Bug #22848110, Bug
        #80569)

      * ST_Distance() could raise an assertion for NULL return
        values. (Bug #22760390)

      * In the absence of SQL_CALC_FOUND_ROWS, FOUND_ROWS() for a
        UNION statement always returned the actual number of rows
        found even when LIMIT was present. (Bug #22602381, Bug
        #80148)

      * A statement containing a format specifier resulted in a
        server exit when the query rewrite plugin tried to log
        the statement. (Bug #22601485)

      * With the query cache enabled, executing a prepared
        statement with CURSOR_TYPE_READ_ONLY and then again with
        CURSOR_TYPE_NO_CURSOR caused the server to return an
        error. (Bug #22559575, Bug #80026)

      * mysql_real_connect() was not thread-safe when invoked
        with the MYSQL_READ_DEFAULT_FILE or
        MYSQL_READ_DEFAULT_GROUP option enabled. (Bug #22322504,
        Bug #79510)

      * With GTIDs enabled, XA COMMIT on a disconnected XA
        transaction within a multiple-statement transaction
        raised an assertion. (Bug #22173903)

      * The sys schema create_synonym_db() function failed if the
        synonym name was a reserved word or contained backtick
        (`) characters. (Bug #22011361, Bug #78823)

      * The sys schema host_summary view could fail with a
        division-by-zero error. (Bug #21970078)

      * The GCC workaround for compiling on ARM64 added by Bug
        #21552524 is needed only for GCC before 5.2.1. (Bug
        #21845828)
        References: See also: Bug #21552524.

      * The sys schema format_path() function replaced substrings
        of the path name argument without verifying that the
        substrings were delimited by path name separators.
        Replacement now works correctly, including on Windows. A
        consequence is that backslashes in Windows path names are
        no longer converted to forward slashes in the result.
        (Bug #21512106)

      * MySQL now supports compiling using the GCC __atomic
        builtins introduced in GCC 4.7 that permit a more
        efficient implementation of the MySQL atomics API. These
        __atomic builtins are only used for platforms where the
        old GCC __sync builtins are not available, such as
        PowerPC where the server otherwise would not build. (Bug
        #21221500)

      * If a stored function updated a view for which the view
        table had a trigger defined that updated another table,
        it could fail and report an error that an existing table
        did not exist. (Bug #21142859, Bug #76808)

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

      * The bundled Protobuf sources (under the extra directory)
        were upgraded from version 2.6.0 to 2.6.1. (Bug #81280,
        Bug #23213376)

      * Protobuf is currently used only by the X plugin, but
        MySQL builds built the protobuf libraries and executables
        even if X plugin building was disabled with
        -DWITH_RAPID=0. (Bug #81066, Bug #23097750)

      * On Solaris, a misaligned memory buffer could cause a
        server exit when selecting from the global_status
        Performance Schema table. (Bug #81065, Bug #23097305)

      * A compilation error was corrected for a make_link() call
        when compiling in C++11 mode. Thanks for Daniel Black for
        the contribution. (Bug #80996, Bug #23080289)

      * Two mysql-test-run.pl tests (ctype_gb18030_binlog and
        ctype_ldml) failed to produce repeatable output due to
        improper cleanup. Thanks to Daniel Black for the patch.
        (Bug #80896, Bug #23021095)

      * MySQL failed to build with GCC 6 using the default mode
        for C++ of -std=gnu++14. The CMake configuration has been
        adjusted to explicitly set the mode to -std=gnu++03 for
        GCC 6. (Bug #80371, Bug #22732697)

      * Ubuntu packages create the root user account using the
        auth_socket authentication plugin to achieve
        secure-by-default installation if installation was done
        with a blank root password. However, auth_socket was
        being used even if the password was not blank. (Bug
        #80137, Bug #22594846, Bug #23321113, Bug #81518)

      * Compiling the InnoDB memcached plugin did not work on
        some platforms where MySQL was configured using
        -DWITH_LIBEVENT=system. (Bug #80073, Bug #22573379, Bug
        #23567441)

      * The client-side plugin deinitialization function
        signature was changed from int (*deinit)() to int
        (*deinit)(void) to avoid warnings when compiling with
        -Wstrict-prototypes. (Bug #78177, Bug #21680094, Bug
        #81419, Bug #23282498)

On Behalf of the MySQL/ORACLE RE Team
Hery Ramilison 

Dear MySQL users,

The MySQL Windows Experience Team is proud to announce the release of
MySQL Notifier version 1.1.7, the latest addition to the MySQL
Installer for Windows.

MySQL Notifier enables developers and DBAs to easily monitor, start and
stop all their MySQL database instances. It provides a familiar
Microsoft SQL Server look and feel and integrates with MySQL Workbench.

MySQL Notifier is installed using the MySQL Installer for Windows.

The MySQL installer comes in 2 versions

- Full (150 MB) which includes a complete set of mysql products with
  their binaries included in the download

or

- Web (1.5 MB - a network install) which will just pull the MySQL
  Notifier over the web and install it when run.

You can download MySQL Installer from our official Downloads page at
http://dev.mysql.com/downloads/installer/.


Changes in MySQL Notifier 1.1.7 (2016-08-01)

   Functionality Added or Changed

     * The automatic migration of connections from MySQL
       Notifier to MySQL Workbench can now be delayed for a
       period of time or suspended indefinitely.

     * An option for setting the interval to ping monitored
       MySQL server instances for status changes was added to
       the Actions, Options menu.

   Bugs Fixed

     * The Configure Instance option was renamed to Manage
       Instance. (Bug #24339668)

     * An error was displayed when valid domain user credentials
       were used to add a remote Windows service. (Bug
       #24305736)

     * Testing new connections for remote MySQL instances would
       display a "High Severity Error" message. (Bug #24010582)

     * When MySQL Notifier was installed using MySQL Installer,
       an exception was thrown and MySQL Notifier failed to
       start. (Bug #23762891)

     * The SQL Editor link to MySQL Workbench was disabled for
       each monitored MySQL instance or service when MySQL
       Workbench was installed. (Bug #23748734)

     * Validation checking identified domain\username as an
       invalid format to use when adding a remote Windows
       service to be monitored. Now, domain users with
       sufficient permissions to access the remote computer can
       connect using the domain\username format. (Bug #23746334)

     * The main XML element in %APPDATA%\Oracle\MySQL
       Notifier\settings.config was renamed to MySQLNotifier
       from MySQLForExcel. Indentations were added to improve
       the overall readability of configuration settings. (Bug
       #23740262)

     * Windows services on a remote computer were not retrieved
       and could not be added to the list services to be
       monitored. (Bug #23667056)

     * A corrupted connections.xml file caused MySQL Notifier to
       display a "Root element is missing" error message when
       started. (Bug #22160640, Bug #73540)

     * Attempts to subscribe to a remote Windows service for the
       first time failed and returned a "High Severity Error"
       message when the remote service was an instance of MySQL.
       (Bug #20389122, Bug #75319)

     * Case-sensitive naming prevented status changes to MySQL
       instances running as services for Windows. Now, service
       names for MySQL instances are added with compatible
       casing. (Bug #19881188, Bug #74516)

     * A "High Severity Error" raised by MySQL Notifier appeared
       intermittently during installations performed using MySQL
       Installer. (Bug #17825477)


You can access the MySQL Notifier documentation at
http://dev.mysql.com/doc/refman/5.6/en/windows-notifier.html.

You can find our team's blog at http://blogs.oracle.com/MySQLOnWindows.

You can also post questions on our MySQL Notifier forum found at
http://forums.mysql.com/.

Enjoy and thanks for the support!


MySQL Notifier Team.

Dear MySQL users,

MySQL Enterprise Backup v4.0.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.

MySQL Enterprise Backup v4.0.3 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.3 is given below.

Changes in MySQL Enterprise Backup 4.0.3            (2016-08-05)

   Version 4.0.3 is the latest release in the MySQL Enterprise
   Backup 4.0 series, including such features like support for
   MySQL 5.7 and ability to backup and restore encrypted InnoDB
   tables. See What's New in MySQL Enterprise Backup 4.0?
   (http://dev.mysql.com/doc/mysql-enterprise-backup/4.0/en/what
   -is-new.html) for details.

   Bugs Fixed

     * MySQL Enterprise Backup 4.0.2 did not work with MySQL
       5.7.10 or earlier, quitting unexpectedly during its
       operations. (Bug #24373967)


The complete manual for MEB 4.0.3 is at
http://dev.mysql.com/doc/mysql-enterprise-backup/4.0/en/index.html

The tool is available for download from Oracle Software Delivery
Cloud (http://edelivery.oracle.com/).

You can also download the binaries from MOS, https://support.oracle.com
Choose the "Patches & Updates" tab, and then use the "Product or Family
(Advanced Search)" feature. If you haven't looked at MEB recently,
please do so now and let us know how MEB works for you.

Your feedback is greatly appreciated!

Please report any problems you have at https://bug.oraclecorp.com/
for the product "MySQL Enterprise Backup"

Thanks,

On behalf MySQL RE team at Oracle
Sreedhar S

Dear MySQL users,

MySQL MySQL Utilities 1.6.4 GA is the first GA version of 1.6
release series. It can be used for production environments.

MySQL Utilities version 1.6.4 GA is compatible with MySQL Server
versions 5.5 and greater. Python v2.6 and v2.7 are supported.
It is available for download from:

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

A brief summary of changes is listed below. Please check the CHANGES.txt
file inside the distribution for a more complete list of changes.

MySQL Utilities provides a collection of command-line utilities that are
used for maintaining and administering MySQL servers, including:
• Admin Utilities (Clone, Copy, Compare, Diff, Export, Import,
User Management)
• Replication Utilities (Setup, Configuration, Verification)
• General Utilities (Disk Usage, Redundant Indexes, Manage Meta &
Audit Data)
• And more

Changes in MySQL Utilities 1.6.4 (2016-08-05)

Functionality Added or Changed

    * Added a new --master-fail-retry option to the
      mysqlfailover utility that allows the user to specify an
      additional delay for detecting when the master has
      failed. The new option allows scenarios where the network
      may have severe latency issues, the server is busy, or
      the server is being rebooted, thereby reducing the
      possibility of false positive failover events.
      (Bug #22878052)

Bugs Fixed

    * Starting with MySQL 5.7.13, some platform distributions
      display a different version string for the command,
      "mysqld --version". For example,
      "5.7.13-0ubuntu0.16.04.2" versus "5.7.13". The utilities
      now correctly identify the version for these server
      versions, or any server with a version string containing
      more than two periods. Without this fix, some utilities
      would incorrectly identify the server version and produce
      warnings, errors, or fail. (Bug #24348569)

    * Corrects an exception thrown for hostname aliases that
      had more than (2) segments. For example, local.mydomain
      contains 2, localhost.mydomain.local contains (3), which
      would result in a catastrophic error "too many values"
      causing the utility to crash. (Bug #23300260)

    * Corrects a problem found when copying tables that
      contained NOT NULL blob fields. When blob fields are
      marked NOT NULL, the copy process would fail with an SQL
      error when inserting data into the target table.
      Copying NOT NULL blob fields is not supported. The
      utility now checks all tables in the list of databases
      for NOT NULL blob fields. If any are found, the database
      and table names are printed along with an error message.
      A workaround is to drop the NOT NULL definition on blob
      fields before the copy and add it after the copy
      completes. (Bug #23111808, Bug #78084)

    * Specifying the --testdir option resulted in unexpected
      behavior when verifying results because the path of the
      directory expected to contain the test results was not
      modified accordingly. (Bug #22934469, Bug #80754)

    * Adds the ability to specify a connection timeout value
      passed to Connector/Python (the connection to MySQL) for
      the mysqlfailover utility. More specifically, it allows a
      user to override Connector/Python's connection_timeout
      default value of 10. (Bug #22932375, Bug #80747)

    * Adds checks for the --exclude option to the
      mysqldbcompare, mysqldbcopy, and mysqldbexport utilities
      to determine if the pattern supplied has any special
      characters (such as an asterisk) which may indicate that
      the pattern could be a regex pattern. If there are
      special non-SQL LIKE pattern characters, and the user has
      not specified the --regexp option, a warning is presented
      to suggest the user may want to check the pattern using
      the --regexp option. (Bug #22905132)

    * Corrects an issue with the --rpl-user and
      --discover-slaves-login options where special symbols or
      improperly quoted strings could cause a crash instead of
      an error message. Tests were also added to ensure the
      utilities report an error should the user:password values
      fail to parse correctly. (Bug #22780854)

    * Corrects a problem using special characters with the
      --rpl-user option. More specifically, if the user
      attempted to use a ":" (colon) in the password, the
      utility failed with an error stating that there are too
      many values to unpack. The utility will now attempt to
      use the first colon encountered for the parse (split).
      Thus, user names should not contain colons, but passwords
      may use any valid symbol (if properly quoted) including
      the colon. (Bug #22619159)

    * Corrects a problem when running mysqlbinlogpurge on a
      5.7.6 or later replication topology setup for
      multi-source replication, which could fail to detect that
      the slave is connected to the master specified if that
      master was not on the primary (first) replication
      channel. The utility now iterates through the slave
      status to check for the requested master in the list. If
      not found, the original error(s) are generated, otherwise
      the master is matched to one of the replication channels,
      and progress continues. (Bug #22543517)

    * Corrects an issue when exporting tables with bit fields
      in SQL format, where bit fields were being exported as
      strings instead of being encoded, like b'???'. Export now
      correctly formats the SQL statements in the output to
      properly handle bit fields. (Bug #22495193, Bug #79837)

    * Installation packaging code was modified to function with
      Mac OS X 10.11 (El Capitan). Installation no longer
      fails, and users can now install MySQL Utilities on El
      Capitan. (Bug #22393353, Bug #79700)

    * Corrects a problem with mysqluc where pressing the delete
      key failed to position the cursor in the correct
      location. The cursor location is now fixed, and the
      delete and arrow keys work properly. (Bug #22076859, Bug
      #78893)

    * Removed the "CREATE database" statement from the diff
      output for mysqldiff and mysqldbcompare for cases where
      the database name is the only difference. That is, the
      different output should not show a difference when
      comparing db1 to db2 when the only difference is the name
      of the database. However, the difference is shown for
      differences in quote usage and if decorators differ, such
      as the character set. (Bug #21222808, Bug #77058)

    * Corrected an issue when copying users that were created
      with the "IDENTIFIED WITH" authentication plugin option.
      The utility would copy the user, but not copy the
      authentication plugin setting, making it impossible to
      copy users with the plugin. The utility now captures the
      plugin name and assigns it to the new user. An error is
      thrown if the plugin is not on the destination machine or
      is inactive. A warning is also issued if the user
      attempts to assign a password to a new user when the
      source user has an authentication plugin. In this case,
      the utility will use the password and not the
      authentication plugin for the new user. (Bug #17666275,
      Bug #70745)


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

Enjoy! 

On Behalf of the MySQL/ORACLE RE Team
Hery Ramilison 

Dear MySQL users,
MySQL Connector/Net 7.0.4 is the first development release that expands
cross-platform support to Linux and OS X when using Microsoft's .NET Core
framework. Now, .NET developers can use the X DevAPI with .NET Core and
Entity Framework Core (EF Core) 1.0 to create server applications that run
on Windows, Linux and OS X. We are very excited about this change and 
really look forward to your feedback on it!
 
MySQL Connector/Net 7.0.4 is also the third 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.

To download MySQL Connector/Net 7.0.4 M3, see the "Development
Releases" tab at http://dev.mysql.com/downloads/connector/net/


Changes in MySQL Connector/Net 7.0.4           (2016-08-22)

   Functionality Added or Changed

     * Added X DevAPI support for flexible parameter lists that do not  require string parsing.

     * Added X DevAPI support for URI connection strings in the following formats:
        mysqlx://[<user>[:<password>]@]<host>[:<port>]
        mysqlx://[<user>[:<password>]@]<host>[:<port>]/<database>
        mysqlx://[<user>[:<password>]@]<host>[:<port>]/[<database>]?<option>=<value>[&<option>=<value>]
        mysqlx+ssh://[<user>[:<password>]@]<host>[:<port>]

     * Views are no longer implemented using a separate View
        class in the X DevAPI. Instead, the IsView property has
        been added to the Table class and views are implemented
        as tables.

     * Added in MySql.Data support for .NET Core 1.0, which runs
        on Windows, OS X, and Linux.

     * Added in MySQL.Data.EntityFrameworkCore support for
        Entity Framework (EF) Core (includes support for .NET
        Framework 4.5.1).

   Bugs Fixed

     * Passing no document or a DbDoc object that contained an
       empty array to the Add() method of a collection would
       throw an exception. Now, passing in either an empty
       document or array of documents returns a Results object
       in which RecordsAffected is zero. (Bug #23542066)

     * Passing a DbDoc object that contained an array to the
       Add() method of a collection would throw an exception.
       (Bug #23542031)


Nuget packages are available at:
https://www.nuget.org/packages/MySql.Data/7.0.4-IR19
https://www.nuget.org/packages/MySql.Data.Entity/7.0.4-IR19
https://www.nuget.org/packages/MySql.Fabric/7.0.4-IR19
https://www.nuget.org/packages/MySql.Web/7.0.4-IR19
https://www.nuget.org/packages/MySql.Data.EntityFrameworkCore/7.0.4-IR-19
https://www.nuget.org/packages/MySql.Data.Core/7.0.4-IR-19


Enjoy and thanks for the support!

On behalf of the MySQL Release Team
-Sreedhar S