Dear MySQL users,

The MySQL Windows Experience Team is proud to announce the release of
MySQL for Excel version 1.3.5. This is a maintenance release for 1.3.x.
It can be used for production environments.

MySQL for Excel is an application plug-in enabling data analysts to very
easily access and manipulate MySQL data within Microsoft Excel. It
enables you to directly work with a MySQL database from within Microsoft
Excel so you can easily do tasks such as:

  * Importing MySQL Data into Excel

  * Exporting Excel data directly into MySQL to a new or existing table

  * Editing MySQL data directly within Excel


MySQL for Excel 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.

- Web (1.5 MB - a network install) which will just pull the MySQL for
  Excel 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/

The MySQL for Excel product can also be downloaded by using the product
standalone installer found at this link
http://dev.mysql.com/downloads/windows/excel/


Changes in MySQL for Excel 1.3.5 (2015-10-23)

   Functionality Added or Changed

     * Added support for the JSON data type that was added in
       MySQL Server 5.7.

       The JSON data type is now selectable from the Export Data
       column dialog, if the advanced option to show all data
       types is enabled. All data operations (Import, Export,
       Append and Edit) now function with the JSON data type.

     * Added a new advanced option to Show column data types
       above column names. When checked, the Append Data dialog
       grid will show data type information for columns on
       source and target grids. This is especially helpful when
       manually mapping columns.

     * A new Append Data advanced option was added, titled
       Confirm column mapping overwriting. When enabled, dragging and
       dropping source columns over target columns that were already
       mapped (in other words, they already contained a mapped source
       column) now triggers a confirmation dialog asking if the
       overwrite should be executed. This option is disabled by default
       as data overwrite is a common operation. (Bug #16239058)

   Bugs Fixed

     * Attempting to save data to a column where the data can
       not be written (incompatible data type) now generates an
       error. (Bug #21898699, Bug #78550)

     * Changed the way data type related warnings are linked to
       grid columns in the Append Data dialog. Now the warnings
       are linked to the target (lower) grid view columns,
       because a single source column can be mapped to multiple
       target columns, and the warnings are about source data
       not being suitable for the target column's data type.
       (Bug #21898678, Bug #78549)

     * When scrolling the target MySQL table grid horizontally,
       the upper column headers that contained names of the
       mapped source columns were not rendering text properly.
       The text moved while scrolling, and the column separators
       disappeared when scrolling to the right. (Bug #21898210,
       Bug #78548)

     * Change the data type detection logic for a column's data
       that was failing when only the first row of data
       contained data, when the rest of the rows were empty.
       (Bug #21799680, Bug #78358)

     * Connection information created after the last save was
       cleared from memory when an Excel Workbook was closed,
       thus causing the connection information to not write to
       disk. Now the connection cleanup happens after a
       Workbench is saved, thereby saving the new connection
       information. (Bug #21172751, Bug #21089790, Bug #76475,
       Bug #73467)

     * Stopped using hidden defined names to store formulas that
       transform date values into a date format used by MySQL.
       These defined names were being detected by Excel as
       macros or user functions that could not be saved in
       macro-free workbooks, thus generating bogus warnings
       every time a Workbook was saved when the Excel plugin was
       active. (Bug #19358961, Bug #73467)

     * Updated the data connection library to Connector/NET
       v6.9.8, which fixes the problem of accessing a schema
       that contained Unicode (non-ASCII) characters in its
       name. These databases now successfully open. (Bug
       #17409832)

     * Deleted stored mappings would remain in the stored
       mapping method list. (Bug #16493255)

     * Enhanced the custom grid view control used in the Append
       Data dialog to automatically adjust the width of the grid
       columns. This adjustment considers the grid's cell
       contents, the base column header text, and also the
       contents of the additional header rows. Before, the
       target column width was too short. (Bug #16237502)


Quick links:
You can access the MySQL for Excel documentation at http://dev.mysql.com/doc/en/mysql-for-excel.html.
You can find our team's blog at http://blogs.oracle.com/MySQLOnWindows.
You can also post questions on our MySQL for Excel forum found at http://forums.mysql.com/list.php?172.
You can follow our videos on our YouTube channel found at http://www.youtube.com/user/MySQLChannel.


Enjoy and thanks for the support!

The MySQL on Windows team at Oracle.

Dear MySQL users,

The MySQL development team is pleased to announce the generally
available (GA) release of MySQL Router 2.0.2 GA.

The MySQL Router is a new building block for high availability
solutions. MySQL Router simplifies development of high availability
applications by intelligently routing queries to MySQL Servers
for increased performance, robustness, and uptime.

MySQL Router also connects seamlessly with MySQL Fabric permitting
Fabric to manage the high availability groups for the router,
supporting monitoring and automatic management of MySQL servers
for redundancy and continued operation.

You can download MySQL Router from http://dev.mysql.com/downloads/router.
Package binaries are available for several platforms and also as a
source code download.

If you are a commercial customer, MySQL Router is available via the
MySQL Oracle Support (MOS) website. Packages will be available on
eDelivery at the next monthly refresh.

Documentation for MySQL Router can be found at
http://dev.mysql.com/doc/mysql-router/en/ (link will be active soon)

Enjoy!

On behalf of Oracle MySQL Release Team 

Dear Users,

The MySQL Windows Experience Team is proud to announce the release of
MySQL for Visual Studio 1.2.5.

This is a maintenance release for the 1.2 release series. It can be
used for production environments.

MySQL for Visual Studio is a product that includes all of the Visual
Studio integration functionality to create and manage MySQL databases
when developing .NET applications.

MySQL for Visual Studio is installed using the MySQL Installer for
Windows which comes in 2 versions:

   . Full (150 MB) which includes a complete set of MySQL products with
   their binaries included in the downloaded bundle.

   . Web (1.5 MB - a network install) which will just pull MySQL for
   Visual Studio 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/.


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 1.2.5 (2015-10-29)

This section documents all changes and bug fixes applied to MySQL for
Visual Studio since the release of 1.2.5. Several new features were
added to the 1.2.x branch, for more information see the section below
called: What Is New In MySQL for Visual Studio 1.2.


   Known Limitations:

      . Item templates do not work correctly with MySQL Server 5.7.x,
        as it prevents the creation of an Entity Framework model.


   Functionality Added or Changed

      . Added the Entity Framework option to the MySQL Website
        Configuration dialog for web projects, so Entity Framework
        version 5 or 6 can be used with a MySQL database provider.
        These automatically add the configuration/references needed
        to the web.config file and the project itself. Also, all available
        configuration options are now listed in the dialog.

      . Project Templates were replaced with Project Items.
        The Project Templates option was removed from the plugin
        toolbar, and from the Project menu, in order to add the Project
        Items feature with two options: MySQL New MVC Item and

        MySQL New Windows Form, which are available on the Add New
        Item dialog when adding a new Project Item. They add new
        windows forms or MVC controllers/views connected to MySQL.


   Bugs Fixed

      . The Installer could not uninstall MySQL for Visual Studio if Visual
        Studio was uninstalled first. (Bug #21953055, Bug #71226)

      . In v1.2.4, the Launch Workbench and Open MySQL Utilities
        Console toolbar buttons were disabled. (Bug #21495692)

      . The Templates installer feature could not be uninstalled via
        Add/Remove Programs. Because Project Templates were
        replaced by Project Items, this is no longer a concern.
        (Bug #21488922, Bug #77802)

      . The dataset designer wizard was not showing the stored
        procedure parameters when creating a "TableAdapter" using
        existing stored procedures for the "Select" command. Also,
        the stored procedure command had an "error" thus causing the
        dataset to not be created. (Bug #20233133, Bug #74195)


What Is New In MySQL for Visual Studio 1.2
------------------------------------------

. New MySQL Project Items for creating data views in Windows Forms and
  ASP.NET MVC web applications.

. A new option in web configuration tool for the ASP.NET Personalization
  Provider (this feature requires MySQL Connector/NET 6.9 or newer).

. A new option in web configuration tool for the ASP.NET Site Map
  Provider (this feature requires MySQL Connector/NET 6.9 or newer).

. A new option for the MySQLSimpleMembership provider in the web
  configuration tool. (This feature requires MySQL Connector/NET or
  newer).


MySQL Windows Forms Project Item
--------------------------------

This Project Item is available on the Add New Item dialog in Visual
Studio when adding a new item to an existing project.

The dialog presented to create the MySQL Windows Forms Project Item
automates the generation of a Windows Form, representing a view for
MySQL data available through an existing Entity Framework's model entity
containing a MySQL table or view. Different view types are available to
present the data:

   . Single-column: A form that contains one control by each existing
     column in the table with navigation controls and that allows CRUD
     operations.All controls can include validations for numeric and
     DateTime data types.

   . Grid: A form with a data grid view that contains navigation
     controls.

   . Master-detail: A form with a single control layout for the Parent
     table and a data grid view to navigate through child table's data.

Supported with C# or Visual Basic language. This feature requires
Connector/NET 6.7.5, 6.8.3 or 6.9.x.

For more details on the features included check the documentation at:
https://dev.mysql.com/doc/connector-net/en/visual-studio-project-items-forms.html



MySQL ASP.NET MVC Project Item
------------------------------

This Project Item is available on the Add New Item dialog in Visual
Studio when adding a new item to an existing project.

The dialog presented to create the MySQL ASP.NET MVC Item automates the
generation of a controller and its corresponding view, representing a
view for MySQL data available through an existing Entity Framework's
model entity containing a MySQL table or view. The MVC versions
supported by this wizard are 3 when using Visual Studio 2010 or 2012,
and 4 when using Visual Studio 2013 or greater.

The generation of the MVC items is done by creating an Entity Framework
data model either with Entity Framework version 5 or 6 depending on the
user's selection.

Supported with C# or Visual Basic language. This feature requires
Connector/NET 6.7.5, 6.8.3 or 6.9.x.

For more details on the features included check the documentation at:
https://dev.mysql.com/doc/connector-net/en/idm139719963401984.html



New option in web configuration tool for the ASP.NET Personalization Provider
-----------------------------------------------------------------------------

Personalization provider allows to store personalization state-state
data regarding the content and layout of Web Parts pages-generated by
the Web Parts personalization service using MySQL as a data source. This
feature requires Connector/NET 6.9.x or greater.

http://dev.mysql.com/doc/connector-net/en/connector-net-website-config.html


New option in web configuration tool for the ASP.NET Site Map Provider
----------------------------------------------------------------------

Site Map provider allows to show a hierarchical list of links that
describe the structure of a site. This feature requires Connector/NET
6.9.x or greater.

http://dev.mysql.com/doc/connector-net/en/connector-net-website-config.html



New option in web configuration tool for the ASP.NET Simple Membership provider
-------------------------------------------------------------------------------

The latest provider added to handle web site membership tasks with
ASP.NET. This feature requires Connector/Net 6.9.x or greater.

http://dev.mysql.com/doc/connector-net/en/connector-net-simple-membership-tutorial.html


Quick links:
. MySQL for Visual Studio documentation: http://dev.mysql.com/doc/connector-net/en/connector-net-visual-studio.html
. Inside MySQL blog (NEW blog home): http://insidemysql.com/
. MySQL on Windows blog (OLD blog home): http://blogs.oracle.com/MySQLOnWindows
. MySQL for Visual Studio forum: http://forums.mysql.com/list.php?174
. MySQL YouTube channel: http://www.youtube.com/user/MySQLChannel
. MySQL Bugs database: http://bugs.mysql.com


Enjoy and thanks for the support!

Hello all,

MySQL Cluster Manager 1.4.0, has been released and can be downloaded
from the My Oracle Support (MOS) website. It will also be available
on Oracle Software Delivery Cloud at http://edelivery.oracle.com with
the next monthly update

MySQL Cluster Manager is an optional component of the MySQL Cluster Carrier
Grade Edition, providing a command-line interface that automates common
management tasks, including the following online operations:
 - Configuring and starting MySQL Cluster
 - Upgrades
 - Adding and removing cluster nodes
 - Adding and removing site hosts
 - Configuration changes
 - Backup and restore

MySQL Cluster Manager is a commercial extension to the MySQL family of products.
More details can be found at http://www.mysql.com/products/cluster/mcm/

A brief summary of changes in MySQL Cluster Manager version 1.4.0 is listed below:

Changes in MySQL Cluster Manager 1.4.0 (2015-12-07)

   This section documents all changes and bug fixes that have
   been applied in MySQL Cluster Manager 1.4.0 since the release
   of MySQL Cluster Manager version 1.3.6.

   Functionality Added or Changed

     * Packaging: MySQL Cluster Manager is now built and shipped
       with GLib-2.44.0, OpenSSL 1.0.1p, and the MySQL 5.6
       client library. (Bug #22202878)

     * Agent: When using the import cluster command, before, if
       an SQL node was started at the command line with options
       outside of a special, pre-defined set, the import would
       fail with the complaint that those options were
       unsupported. Now, import will continue in the situation,
       as long as those options and their values also appear in
       the node's configuration created by MySQL Cluster Manager
       for import. (Bug #21943518)

     * Agent: A warning is now logged (if log-level=warning)
       when a failed process is not restarted because the
       parameter StopOnError has the value "true." (Bug
       #21575241)

     * Agent: Two new options have been introduced for the
       upgrade cluster command: --retry and --nodeid. They,
       together with the --force option, allow a retry after an
       initial attempt to upgrade a cluster has failed. See
       description for upgrade cluster for detail. (Bug
       #20469067, Bug #16932006, Bug #21200698)

     * Client: The get command now returns attributes in the
       same order as the MySQL Cluster ndb_mgmd command does
       when the --print-full-config option is used, with the
       non-data nodes going first, and in increasing order of
       the node ID. (Bug #22202973)

     * Client: A new autotune command has been introduced, which
       tunes a number of parameters of the cluster to optimize
       its performance. (Bug #22202855)

     * Client: The show settings command has a new --hostinfo
       option, with which the command prints out information on
       the host the mcm client is connected to. (Bug #21923561)

     * Client: You can now use the wildcard * (asterisk
       character) to match attribute names in a get command. See
       The get Command
       (http://dev.mysql.com/doc/mysql-cluster-manager/1.4/en/mc
       m-get.html) for examples. (Bug #18069656)

   Bugs Fixed

     * Agent: On Windows platform, after a cluster import, the
       subsequent cluster restart would time out if a
       non-default value of the option pid_file has been
       imported for a mysqld node. (Bug #21943518)
       References: This bug is a regression of Bug #21111944.

     * Agent: When a data node could not be restarted after a
       set command because some attributes were set wrongly,
       another set command could not be used to correct the
       attributes, because the set command required the data
       node to be running. With this fix, the second set command
       can now be executed even when the data node is not
       running, as long as the --force option is used. The
       failed node is then restarted, followed by a rolling
       restart of the cluster. (Bug #21943518)

     * Agent: A timeout occurred for a restore cluster command
       when the number of tables in the cluster was huge
       (>1000). It was because a timeout extension was blocked.
       This fix unblocks the extension. (Bug #21393857)

     * Agent: At the initial startup of a large cluster (with
       memory size in the order of 10GB), the process might time
       out while waiting for a data node to start. This fix
       makes the transaction timeout longer for data node
       initiation. (Bug #21355383)

     * Agent: Under some conditions, a check status command
       might report negative node group ID values for processes
       after an add process command was completed. That was
       because the agent was reporting the node group IDs before
       their proper values had arrived, after the creation of
       new node groups. This fix makes the agent wait for the
       correct node group IDs before reporting them. (Bug
       #21346804)

     * Agent: After successful the execution of an add process
       and a subsequent start cluster --added command, a third
       command that was issued very shortly afterward might
       fail. This was due to the way the updates for the
       processes' statuses were handled after the new nodes were
       added, which has now been corrected. (Bug #21138604)
       References: See also Bug #21346804.

     * Agent: Setting a value for a "key-only" option for a
       MySQL node (that is, an option that does not take a
       value---for example, skip_show_database) with the set
       command and restarting the cluster afterward caused mcmd
       to attempt a cluster upgrade and back up the cluster.
       (Bug #21098403)

     * Agent: The create site command sometimes failed with the
       error message "Lost connection to MySQL server during
       query." It was due to an error in the code that handled
       the socket, which has now been fixed. (Bug #21027818)

     * Agent: Parameters listed under the [mysqld default] or
       [tcp default] section of the config.ini file were not
       imported as configuration parameters for unmanaged API
       nodes. (Bug #20889471)

     * Client: Output of the get command used with the
       --include-defaults (-d) option did not include matching
       TCP attributes that had default values. (Bug #21895322)

You can also find more information on the contents of this release in
the change log:
http://dev.mysql.com/doc/relnotes/mysql-cluster-manager/1.4/en/mcm-news-1-4-0.html

The user manual can be found at:
http://dev.mysql.com/doc/index-cluster.html

Your feedback is greatly appreciated!

Please report any problems you have at https://bug.oraclecorp.com/

Enjoy!

On Behalf of the MySQL/ORACLE RE Team,

Lars Tangvald

Changes in MySQL 5.7.10 (2015-12-07)


     * Functionality Added or Changed

     * Security Notes

     * Bugs Fixed

   Functionality Added or Changed

     * InnoDB: Enabling the new
       innodb_background_drop_list_empty debug configuration
       option helps avoid test case failures by delaying table
       creation until the background drop list is empty. (Bug
       #21891560)

     * InnoDB: The innodb_support_xa system variable, which
       enables support for two-phase commit in XA transactions,
       is deprecated. InnoDB support for two-phase commit in XA
       transactions is always enabled as of MySQL 5.7.10.
       Disabling innodb_support_xa is no longer permitted as it
       makes replication unsafe and prevents performance gains
       associated with binary log group commit.

     * MySQL distributions now include lz4_decompress and
       zlib_decompress utilities that can be used to decompress
       mysqlpump output that was compressed using the
       --compress-output=LZ4 and --compress-output=ZLIB options.
       For more information, see lz4_decompress --- Decompress
       mysqlpump LZ4-Compressed Output
       (http://dev.mysql.com/doc/refman/5.7/en/lz4-decompress.html),
       and zlib_decompress --- Decompress mysqlpump
       ZLIB-Compressed Output
       (http://dev.mysql.com/doc/refman/5.7/en/zlib-decompress.html).
       (Bug #21644479)

     * mysql_upgrade now attempts to print more informative
       errors than FATAL ERROR: Upgrade failed. (Bug #21489398)

     * These client programs now support the
       --enable-cleartext-plugin option: mysqlcheck, mysqldump,
       mysqlimport, mysqlshow. This option enables the
       mysql_clear_password cleartext authentication plugin.
       (See The Cleartext Client-Side Authentication Plugin
(http://dev.mysql.com/doc/refman/5.7/en/cleartext-authentication-plugin.html).)
       (Bug #21235226)

     * These functions now produce warnings for invalid input:
       UNHEX(), INET_NTOA(), INET_ATON(), INET6_NTOA(),
       INET6_ATON(). Also, INET_ATON() now returns NULL and
       produces a warning for arguments that contain more than
       four groups of digits. (Bug #78856, Bug #22042027, Bug
       #78884, Bug #22071558)

   Security Notes

     * Previously, MySQL supported TLSv1.0 and TLSv1.1 SSL
       protocols. When compiled with OpenSSL 1.0.1 or higher,
       MySQL now also supports TLSv1.2 protocol to enable a
       higher level of security for SSL connections.

       Because TLSv1.2 requires OpenSSL, this feature is
       available in binary distributions only for MySQL
       Commercial Server, and not for MySQL Community Server
       (which is compiled using yaSSL). To enable TLSv1.2
       support if you build from source, you must set the
       WITH_SSL CMake option to use OpenSSL when configuring
       MySQL.

   Bugs Fixed

     * InnoDB: When attempting to create a cascading foreign key
       constraint on a primary key column used in a virtual
       index, the error message that was returned did not
       include information from
       dict_foreign_has_col_in_v_index(). (Bug #22050059)

     * InnoDB: An in-place operation that rebuilt a table with
       multiple indexed virtual columns raised an assertion.
       (Bug #22018532)

     * InnoDB: A SELECT ... FOR UPDATE operation on a table that
       only contained virtual columns and a virtual column index
       raised an invalid assertion. (Bug #21981164, Bug
       #21880930)

     * InnoDB: The calculation in dict_index_node_ptr_max_size()
       that determines the maximum index record size treated
       fixed fields that exceeded the maximum column length as
       fixed-size fields instead of variable length fields. (Bug
       #21968191)

     * InnoDB: A server exit during a TRUNCATE TABLE operation
       on a table with a full-text index caused startup to fail.
       (Bug #21959479)

     * InnoDB: An ALTER TABLE ... DISCARD TABLESPACE operation
       raised an invalid assertion. (Bug #21957001, Bug #78728)

     * InnoDB: Compared to previous releases, small tablespaces
       containing tables with BLOB values had larger data files
       due to regression introduced in MySQL 5.7.5. (Bug
       #21950389, Bug #78623)
       References: This bug is a regression of Bug #18756233.

     * InnoDB: The ord_part flag was not reset after a failed
       operation to create an index on a virtual column, causing
       InnoDB to assert on a subsequent insert operation. (Bug
       #21941320, Bug #21979969)

     * InnoDB: Successive open table operations on tables with
       virtual columns caused a memory access violation. (Bug
       #21939731)

     * InnoDB: An invalid search tuple was created for a table
       with virtual columns. (Bug #21922176)

     * InnoDB: InnoDB attempted to purge a virtual column index
       record that was not marked for deletion. (Bug #21901389)

     * InnoDB: Update vector generation for a full-text search
       DOC_ID did not initialize a new ufield, resulting in an
       assertion. (Bug #21891185)

     * InnoDB: InnoDB failed to prevent foreign key SET NULL or
       CASCADE constraints on virtual column base columns and
       virtual index columns. (Bug #21890816)

     * InnoDB: An invalid comparison raised an assertion under a
       64k innodb_page_size setting. (Bug #21882024)

     * InnoDB: When estimating the maximum record size of a
       b-tree index page, InnoDB incorrectly treated long-length
       fixed fields (greater than 767 bytes) as fixed-size
       fields instead of variable length fields. (Bug #21880445)

     * InnoDB: In debug builds, dtuple_get_n_fields attempted to
       read freed memory that was previously allocated for a
       virtual column tuple, resulting in a server exit. (Bug
       #21875974)

     * InnoDB: Selecting from INNODB_CMPMEM with option
       big-tables=1 raised a buffer pool mutex assertion. (Bug
       #21871451, Bug #78494)

     * InnoDB: InnoDB returned an invalid corruption-related
       error message during an IMPORT TABLESPACE operation. (Bug
       #21838158, Bug #77321)

     * InnoDB: After a crash on Windows, copying the data
       directory to a non-Windows platform to perform the
       restore caused a crash recovery failure on startup. The
       code did not convert file path separators from "\" to "/"
       in the redo log. (Bug #21825127, Bug #78410)

     * InnoDB: A FLUSH TABLE ... FOR EXPORT operation asserted
       in row_quiesce_table_start() when run on a partitioned
       table with partitions residing in a system or general
       tablespace. (Bug #21796845)

     * InnoDB: A DROP TABLE operation resulted in a server exit.
       The return value of a function call was not checked,
       which lead to dereferencing of a null pointer. The patch
       for this bug also addresses a potential race condition.
       (Bug #21794102, Bug #78336)

     * InnoDB: In debug builds, an ordered scan across multiple
       partitions did not use a priority queue, resulting in an
       assertion. (Bug #21753477)

     * InnoDB: After restarting the server, the COMPRESSION
       column of the INNODB_SYS_TABLESPACES table displayed
       incorrect data. The COMPRESSION column was removed from
       INNODB_SYS_TABLESPACES. To view the current setting for
       page compression, use SHOW CREATE TABLE. (Bug #21687636,
       Bug #78197)

     * InnoDB: An invalid table flags value raised an assertion.
       The SYS_TABLES.MIX_LEN(flags2) value was not read for
       tables that use ROW_FORMAT=REDUNDANT. (Bug #21644827)

     * InnoDB: An online ALTER TABLE operation caused a server
       exit. (Bug #21640679)

     * InnoDB: An assertion was raised when crash recovery
       handling of an MLOG_TRUNCATE redo log record treated a
       shared tablespace as a file-per-table tablespace. Redo
       was skipped for the shared tablespace. (Bug #21606676)

     * InnoDB: Transaction rollback after recovery failed due to
       an invalid assertion. (Bug #21575121)

     * InnoDB: Insufficient information in the undo log about
       spatial columns raised an assertion and could result in a
       upgrade failure. Consequently, a slow shutdown is
       required prior to performing an in-place upgrade from
       MySQL 5.7.8 or 5.7.9 to 5.7.10 or higher. For more
       information, refer to Changes Affecting Upgrades to MySQL
       5.7
(http://dev.mysql.com/doc/refman/5.7/en/upgrading-from-previous-series.html).
       (Bug #21508582)
       References: This bug is a regression of Bug #21340268.

     * InnoDB: A secondary index is not permitted on a virtual
       column that is based on a foreign key-referenced column
       that uses ON DELETE CASCADE, ON DELETE SET NULL, ON
       UPDATE CASCADE, or ON UPDATE SET NULL. The restriction
       was not enforced. (Bug #21508402)

     * InnoDB: A duplicate key error that occurred during an
       online DDL operation reported an incorrect key name. (Bug
       #21364096, Bug #77572)

     * InnoDB: An ALTER TABLE operation caused the server to
       exit on disk full. (Bug #21326304, Bug #77497)

     * InnoDB: The system tablespace data file did not extend
       automatically when reaching the file size limit, causing
       startup to fail with a size mismatch error and preventing
       the addition of another system tablespace data file. (Bug
       #21287796, Bug #77128)

     * InnoDB: Altering the letter case of a column introduced
       an inconsistency between the frm file and data dictionary
       resulting in a failed CREATE INDEX operation on the
       altered column. (Bug #20755615)

     * InnoDB: An ALTER TABLE operation that converted a table
       to an InnoDB file-per-table tablespace did not check for
       unknown files with the same name as the destination .idb
       file, permitting an unknown file of the same name to be
       overwritten. (Bug #19218794, Bug #73225)

     * InnoDB: row_merge_read_clustered_index() did not handle a
       bulk load error correctly. (Bug #19163625)

     * Partitioning: Partition scans did not evaluate virtual
       generated columns properly. This could cause issues with
       partitioned tables having an index on a virtual BLOB
       column. (Bug #21864838, Bug #21881155)

     * Partitioning: While executing CHECK TABLE, when checking
       whether rows were in the correct partition, the partition
       engine missed updates for virtual generated columns. (Bug
       #21779554)

     * Partitioning: Performing an in-place ALTER TABLE on a
       partitioned InnoDB table having one or more partitions
       which used a separate tablespace could cause the server
       to fail. (Bug #21755994)

     * Partitioning: When all partitions were pruned, they were
       not initialized for scanning during initialization of
       indexes. This involved two related issues, one being that
       the active index was not set back to the maxmimum key
       value when the index was closed. In addition, when this
       occurred as part of a multi-range read, there were
       attempts to access unset variables. (Bug #78260, Bug
       #21754608, Bug #21620577)

     * Replication: Fatal errors encountered during flushing or
       synchronizing the binary log were being ignored. Such
       errors are now caught and handled depending on the
       setting of binlog_error_action. (Bug #76795, Bug #68953,
       Bug #20938915, Bug #16666407)

     * INSERT ... ON DUPLICATE KEY UPDATE could result in a
       memory leak when executed as a prepared statement. (Bug
       #22151233)
       References: This bug was introduced by Bug #21908206.

     * If the server was started with
       --performance_schema_accounts_size=0, querying the
       Performance Schema status variable tables caused a server
       exit. (Bug #22131713)

     * For debug builds, using ALTER TABLE to add a generated
       column to a table could cause a deadlock. (Bug #22083048)

     * Some of the source files for spatial functions in the sql
       directory took excessive compile time and required too
       much compiler memory allocation. (Bug #22078874)

     * Internal buffer sizes in resolve_stack_dump were
       increased to accommodate larger symbol space requirements
       for C++ code. (Bug #22071592)

     * The systemd unit file did not specify any --pid-file
       option for mysqld, with the result that server startup
       could fail. The unit file now includes a default
       --pid-file option in the ExecStart value. This default
       can be overridden in the override.conf file by changing
       both PIDFile and ExecStart to specify the PID file path
       name. (Bug #22066787)

     * A query with nested derived tables and scalar subqueries
       in the select list of the derived tables might in some
       cases cause a server exit. (Bug #22062023)

     * When mysqld was run with --initialize, it used chown() to
       set the data directory owner, even if ownership was
       already correct. This caused problems for AppArmor and
       SELinux. The server now checks whether the data directory
       owner is correct and skips the chown() call if so. (Bug
       #22041387)

     * Failed evaluation of a generated column expression for
       CREATE TABLE or ALTER TABLE could cause a server exit.
       Now if expression evaluation causes truncation or
       provides incorrect input to a function, the statement
       terminates with an error and the DDL operation is
       rejected. (Bug #22018999)

     * Creating a unique index on a virtual POINT column could
       result in an error or assertion for later table accesses.
       (Bug #22017616)

     * Problems leading to Valgrind warnings for libmysqld were
       corrected. (Bug #22007587)

     * Sending a load spike to a newly started server could
       cause the Performance Schema to allocate a large amount
       of memory, possibly leading to out-of-memory failure.
       (Bug #22006088)

     * MySQL development RPM packages could fail to install if
       MySQL Connector/C development RPM packages were
       installed. (Bug #22005375)

     * A missing error check could result in a server exit for
       DELETE statements that referred to user-defined
       variables. (Bug #21982313)

     * Possible buffer overflow from incorrect use of strcpy()
       and sprintf() was corrected. (Bug #21973610)

     * MySQL RPM packages for RHEL5 failed to create the mysql
       system user. (Bug #21950975)

     * MySQL does not support columns of ROW type, but the
       server did not prevent generated columns from being
       created that used ROW expressions. These are now
       prohibited. (Bug #21940542)

     * The version_tokens plugin called the locking service
       using a timeout value of only one second. The timeout is
       now taken from the default value of the lock_wait_timeout
       system variable (that is, one year). (Bug #21928198)

     * Spatial functions could return invalid results if given a
       polygon or multipolygon argument containing holes such
       that a hole vertex touched the exterior ring at a point
       lying in the interior of an exterior ring segment. This
       could manifest itself as: ST_UNION() producing an invalid
       polygon; ST_SymDifference() producing an invalid
       multipolygon; ST_Intersection() producing an invalid
       self-intersecting polygon; ST_Difference() producing an
       invalid geometry. (Bug #21927733, Bug #21927639, Bug
       #21927558, Bug #21977775)

     * With the STRICT_TRANS_TABLES SQL mode enabled, it was not
       possible to insert data into a VIRTUAL generated column
       defined with the NOT NULL attribute. (Bug #21927469)

     * Problems leading to Valgrind warnings for OpenSSL random
       number generation were corrected. (Bug #21927436)

     * Querying views on Windows could lead to memory leaks.
       (Bug #21908206)
       References: This bug was introduced by Bug #13901905.

     * Generated column definitions specified with the NULL
       attribute resulted in a syntax error. (Bug #21900170)

     * A stored procedure that used ST_Area() could return
       different numbers of rows for the first and second
       executions. (Bug #21889842)

     * For polygon values with an interior ring that touches an
       exterior ring, ST_Buffer() could return invalid polygon
       values. (Bug #21871856)

     * Two rows in the Performance Schema threads table could
       have the same THREAD_OS_ID value. (Bug #21865330)

     * For debug builds, using ALTER TABLE to change the
       expression for a generated column could cause a server
       exit. (Bug #21854004)

     * ALTER USER failed if the server was started with
       --skip-grant-tables. (Bug #21847825)

     * Performance Schema reads of a session's THD structure
       while the session was running could create race
       conditions and result in a server exit. (Bug #21841412)

     * A prepared statement that computes ST_IsSimple() or
       ST_Buffer_Strategy() on a nullable column in an outer
       join could return different numbers of rows for the first
       and second statement executions. (Bug #21841051)

     * Queries on the Performance Schema variables_by_thread
       table could cause a server exit when examining the system
       variables of a new connection. (Bug #21840950)

     * Executing HELP statements or statements involving the
       CONVERT_TZ() function could lead to a memory leak and to
       MyISAM reference-count errors at server shutdown. (Bug
       #21840241)

     * Spatial functions could read already freed memory. (Bug
       #21823135)

     * For Debian package control files, libnuma-dev was added
       to Build-Depends to enable NUMA support. (Bug #21822631)

     * Selecting DECIMAL values into user-defined variables
       could cause a server exit. (Bug #21819304)

     * Re-evaluation of a generated column expression could
       cause access to previously freed memory and a server
       exit. (Bug #21810529)

     * MySQL did not recognize functional dependencies from base
       columns in a generated column expression to the generated
       column. (Bug #21807579)

     * ST_SymDifference() could raise an assertion for polygons
       with self-intersection points. (Bug #21767301, Bug
       #79031, Bug #22124757)

     * USER field output from the audit log plugin was
       malformed. (Bug #21766380)

     * A server exit could occur for queries for which a) a
       GROUP BY included primary key and secondary key columns;
       and b) the WHERE clause included an equality predicate on
       the first primary key column where that column was
       constant. (Bug #21761044)

     * Building MySQL using parallel compilation sometimes
       failed with an attempt to compile sql_yacc.yy before
       lex_token.h had been created. (Bug #21680733)

     * With binary logging enabled, issuing DROP TEMPORARY TABLE
       when in XA_IDLE state caused an assertion to be raised.
       Now an ER_XAER_RMFAIL error is returned.
       In consquence of the fix for this issue, statements that
       previously succeeded in XA_IDLE state now fail with an
       ER_XAER_RMFAIL error. When running with --gtid-mode=ON,
       an explicit DROP continues to fail with
       ER_GTID_UNSAFE_CREATE_DROP_TEMPORARY_TABLE_IN_TRANSACTION
       . (Bug #21638823)

     * A query with a subquery in the left-hand part of an IN
       subquery that was transformed into a semi-join might
       cause a server exit. (Bug #21606400)

     * Concurrent FLUSH PRIVILEGES and REVOKE or GRANT
       statements could produce a small time window during which
       invalid memory access to proxy user information could
       occur, leading to a server exit. (Bug #21602056)

     * Using WITH ROLLUP within a subquery could cause a server
       exit. (Bug #21575790)

     * For debug builds, a call to MAKE_SET() with a subquery as
       argument might be evaluated before tables were locked,
       causing an assertion to be raised. (Bug #21547779)

     * Starting the server with the query_alloc_block_size
       system variable set to certain negative values on a
       machine without enough memory could result in
       out-of-memory errors. (Bug #21503595)

     * Using UNINSTALL PLUGIN to uninstall the daemon_example
       plugin could cause a server exit. (Bug #21467458)

     * FLUSH DES_KEY_FILE failed to reload the DES key file.
       (Bug #21370329)

     * If an error occurred during the setup phase of subquery
       materialization used to compute an IN predicate, cleanup
       of the temporary table did not happen, leading to
       Valgrind errors. (Bug #21346081)

     * On Windows, the sysbench benchmark tool's "run" command
       would hang when attempting to create multiple tables for
       the OLTP test when using shared memory connections. (Bug
       #21319192, Bug #77481)

     * Queries rejected by MySQL Enterprise Firewall were
       truncated to 512 characters when written to the error
       log. (Bug #20948270)

     * A server exit could occur for the second execution of a
       prepared statement for which an ORDER BY clause referred
       to a column position. (Bug #20755389)

     * Repeated execution of a prepared statement could cause a
       server exit if the default database was changed. (Bug
       #20447262)

     * mysql_plugin could exit due to improper checking of
       string operation operands. (Bug #20376670)

     * After failure to create a temporary table during join
       processing and releasing the table descriptor, an attempt
       to access the now-invalid descriptor could cause a server
       exit. (Bug #19918299)

     * Type conversion failure for DECIMAL values could cause a
       server exit. (Bug #19912326, Bug #20013538)

     * INSERT DELAYED could cause a server exit for tables
       partitioned with a character column as the key and for
       which the expression required a character set conversion.
       (Bug #19894161)

     * A server exit could occur when updating a view using an
       ALL comparison operator on a subquery that selects from
       an indexed column in the main table. (Bug #19434916)

     * With AddressSanitizer (ASAN) enabled, triggers that
       contained null or invalid characters could cause an ASAN
       server exit. (Bug #18831513)

     * Incorrect error checking for the NAME_CONST() function
       could lead to a server exit. (Bug #17733850)

     * Queries that needed to store the result of ST_AsWKB() in
       a temporary table could fail with an error message. (Bug
       #79060, Bug #22131961)
       References: This bug was introduced by Bug #21614368.

     * If mysqld was started with the --help option, it created
       a binary log index file. If that file was located in the
       data directory and the command preceded data directory
       initialization, initialization then failed due to a
       nonempty data directory. (Bug #78986, Bug #22107047)

     * mysqladmin --help displayed the old-password command,
       even though the command itself was removed in MySQL
       5.7.5. (Bug #78774, Bug #21972941)

     * The filename character set is intended for internal use,
       but references to it in SQL statements did not produce an
       error. Now they do. (Bug #78732, Bug #21958734)

     * If a generated column used an expression that is affected
       by the SQL mode, the expression could produce different
       results for the same input values, depending on the
       current SQL mode. (For example, interpretation of the ||
       operator depends on the PIPES_AS_CONCAT SQL mode.) Now
       expression evaluation uses the SQL mode in effect at the
       time the column is defined. (Bug #78665, Bug #21929967)

     * Casting large hexadecimal values could produce an
       incorrect result and no truncation warning. (Bug #78641,
       Bug #21922414)

     * mysqlpump generated incorrect ALTER TABLE statements for
       adding foreign keys. (Bug #78593, Bug #21907297)

     * The error message returned when trying to define a BLOB,
       TEXT, JSON, or GEOMETRY column with a default value
       (Error 1101, ER_BLOB_CANT_HAVE_DEFAULT) referred to BLOB
       and TEXT columns only. The same error applies to any of
       these four types when trying to use the DEFAULT option
       with it in a column definition; the corresponding error
       message now makes this clear by referring to JSON and
       GEOMETRY columns as well. (Bug #78527, Bug #21887035)

     * A query using JSON_EXTRACT() returned the wrong result
       after a virtual index was added to the table. (Bug
       #78464, Bug #21854241)

     * It was possible to store non-ASCII data in columns
       intended to store data of character set ascii. (Bug
       #78276, Bug #21774967)

     * Adding a SPATIAL index to a MyISAM table could cause the
       cardinality of other indexes to become incorrect. (Bug
       #78213, Bug #21789000)

     * MySQL could fail to compile on Solaris 11.3 when
       /usr/gnu/bin/as was used as the linker. (Bug #77797, Bug
       #21484716)

     * Some punctuation characters in the armscii8 character set
       are represented by two encodings, with the result that a
       character stored using one encoding would not be found
       using a search with the other encoding. For such
       characters, MySQL now selects the encoding with the
       lowest value to consistently map instances onto the same
       encoding. (Bug #77713, Bug #21441405)

     * Item_copy_decimal::copy() did not take the
       div_precision_increment system variable value into
       account, resulting in DECIMAL values being returned with
       incorrect precision from some queries. (Bug #77634, Bug
       #21462523)

     * For queries with implicit grouping; an index with a
       string column as its first part; and a WHERE clause with
       an equality comparison comparing the column to a string
       with trailing characters in addition to the column value,
       an aggregate function that should return NULL returned
       non-NULL. (Bug #77480, Bug #21318711)

     * LOAD_FILE() could cause a server exit for some pathnames
       if the character set was cp932. (Bug #76555, Bug
       #20819220)

     * For constructs such as ORDER BY numeric_expr COLLATE
       collation_name, the character set of the expression was
       treated as latin1, which resulted in an error if the
       collation specified after COLLATE is incompatible with
       latin1. Now when a numeric expression is implicitly cast
       to a character expression in the presence of COLLATE, the
       character set used is the one associated with the named
       collation. (Bug #73858, Bug #20425399)

 
Dear MySQL users,

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

Enjoy!

Changes in MySQL 5.5.47 (2015-12-07)


     * Functionality Added or Changed

     * Bugs Fixed

   Functionality Added or Changed

     * MySQL Server RPM packages now contain a conflict
       indicator for MySQL Connector C, such that an error
       occurs when installing MySQL Server if MySQL Connector C
       is also installed. To install MySQL Server, remove any
       MySQL Connector C packages first. (Bug #21900800)

     * mysql_upgrade now attempts to print more informative
       errors than FATAL ERROR: Upgrade failed. (Bug #21489398)

     * These client programs now support the
       --enable-cleartext-plugin option: mysqlcheck, mysqldump,
       mysqlimport, mysqlshow. This option enables the
       mysql_clear_password cleartext authentication plugin.
       (See The Cleartext Client-Side Authentication Plugin
       (http://dev.mysql.com/doc/refman/5.5/en/cleartext-authentication-plugin.html).)
        (Bug #21235226)

   Bugs Fixed

     * InnoDB: Altering the letter case of a column introduced
       an inconsistency between the frm file and data dictionary
       resulting in a failed CREATE INDEX operation on the
       altered column. (Bug #20755615)

     * MySQL development RPM packages could fail to install if
       MySQL Connector/C development RPM packages were
       installed. (Bug #22005375)

     * Possible buffer overflow from incorrect use of strcpy()
       and sprintf() was corrected. (Bug #21973610)

     * MySQL RPM packages for RHEL5 failed to create the mysql
       system user. (Bug #21950975)

     * Concurrent FLUSH PRIVILEGES and REVOKE or GRANT
       statements could produce a small time window during which
       invalid memory access to proxy user information could
       occur, leading to a server exit. (Bug #21602056)

     * Starting the server with the query_alloc_block_size
       system variable set to certain negative values on a
       machine without enough memory could result in
       out-of-memory errors. (Bug #21503595)

     * Using UNINSTALL PLUGIN to uninstall the daemon_example
       plugin could cause a server exit. (Bug #21467458)

     * FLUSH DES_KEY_FILE failed to reload the DES key file.
       (Bug #21370329)

     * A server exit could occur for the second execution of a
       prepared statement for which an ORDER BY clause referred
       to a column position. (Bug #20755389)

     * Repeated execution of a prepared statement could cause a
       server exit if the default database was changed. (Bug
       #20447262)

     * Outer references do not work as arguments to MATCH(), but
       the server did not properly detect them. Now it does and
       raises an error. (Bug #20007383)
       References: See also Bug #21140088.

     * Valgrind errors were produced during row comparator
       setup. (Bug #19929406)

     * INSERT DELAYED could cause a server exit for tables
       partitioned with a character column as the key and for
       which the expression required a character set conversion.
       (Bug #19894161)

     * A server exit could occur when updating a view using an
       ALL comparison operator on a subquery that selects from
       an indexed column in the main table. (Bug #19434916)

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

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

On behalf of Oracle MySQL Release Engineering Team,
Gipson Pulla

Hello all,

MySQL Connector Java 5.1.38, a maintenance release of the production 5.1
branch, has been released. Connector/J is a Type-IV pure-Java JDBC
driver for MySQL. It is suitable for use with MySQL server versions 5.5,
5.6, and 5.7. It is also the first release of MySQL Connector/J to support
the Java Database Connectivity (JDBC) 4.2 API.

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

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

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

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

Changes in MySQL Connector/J 5.1.38 (2015-12-07)

   Functionality Added or Changed

     * When connecting to a MySQL server 5.7 instance that
       supports TLS, Connector/J now prefers a TLS over a plain
       TCP connection. (Bug #21947042)

     * Two new connection properties, allowSlaveDownConnections
       and readFromMasterWhenNoSlaves, have been introduced for
       configuring replication-aware connections. See
       Configuring Master/Slave Replication with Connector/J
       (http://dev.mysql.com/doc/connector-j/en/connector-j-master-slave-replication-connection.html)
       and the entries for the new properties in Driver/Datasource
       Class Names, URL Syntax and Configuration Properties for
       Connector/J (http://dev.mysql.com/doc/connector-j/en/connector-j-reference-configuration-properties.html)
       for details. (Bug #21286268)

   Bugs Fixed

     * In a Fabric environment, a ClassCastException resulted
       when a stored procedure was called with an INOUT
       parameter. This was because in this situation, what was
       being cast was a proxied version of the object. This fix
       extracts the underlying object from its proxy, allowing
       it to be cast to the implementing class. (Bug #22096981)

     * getTypeInfo() erroneously returned a PRECISION value of
       "255" instead of "65535" for the data type VARBINARY.
       (Bug #21978216)

     * A deadlock was observed when in the same server group,
       two concurrent threads were using different Fabric
       connections, and one executed a failover procedure while
       the other simultaneously called a method that acquired a
       lock on the underlying replication connection instance
       monitor. This fix revised the locking mechanism of
       replication connections, in order to prevent the observed
       deadlocks. (Bug #21966391, Bug #21934573, Bug #78710)

     * State information of a Fabric group was not updated by
       Connector/J after a local cache's Time to Live (TTL)
       expired, which resulted in the client not recognizing any
       topology changes happening to the group like a master
       failover, a server rejoining, and so on. (Bug #21296840,
       Bug #17910835)

     * Connector/J threw an AbstractMethodError when a JDBC 4
       functionality (for example, createBlob()) was used on a
       replication-aware connection. This has been fixed by
       putting replication connections under the multi-host
       connection proxy structure that Connector/J has been
       using for load-balanced and fail-over connections. (Bug
       #11763419)
       References: See also Bug #11763401.

     * After the initial call of Connection.setReadOnly()
       following the creation of a replication-aware connection,
       subsequent calls of Connection.setReadOnly() could not
       change the nature of the connection. This has been fixed
       by putting replication connections under the multi-host
       connection proxy structure that Connector/J has been
       using for load-balanced and fail-over connections. (Bug
       #11763401)
       References: See also Bug #11763419.

Documentation
--------------
Online: http://dev.mysql.com/doc/connector-j/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 Server 5.6.28, a new version of the popular Open Source
Database Management System, has been released. MySQL 5.6.28 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

For information on installing MySQL 5.6.28 on new servers or upgrading
to MySQL 5.6.28 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.27. It may also be viewed
online at

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

Enjoy!

Changes in MySQL 5.6.28 (2015-12-07):

   Functionality Added or Changed

     * MySQL Server RPM packages now contain a conflict
       indicator for MySQL Connector C, such that an error
       occurs when installing MySQL Server if MySQL Connector C
       is also installed. To install MySQL Server, remove any
       MySQL Connector C packages first. (Bug #21900800)

     * mysql_upgrade now attempts to print more informative
       errors than FATAL ERROR: Upgrade failed. (Bug #21489398)

     * These client programs now support the
       --enable-cleartext-plugin option: mysqlcheck, mysqldump,
       mysqlimport, mysqlshow. This option enables the
       mysql_clear_password cleartext authentication plugin.
       (See The Cleartext Client-Side Authentication Plugin
       (http://dev.mysql.com/doc/refman/5.6/en/cleartext-authentication-plugin.html).)
       (Bug #21235226)

     * Support for building with Solaris Studio 5.13 was added.
       (Bug #21185883)

     * Performance Schema digests in DIGEST_TEXT columns have
       ... appended to the end to indicate when statements
       exceed the maximum statement size and were truncated.
       This is also now done for statement text values in
       SQL_TEXT columns. (Bug #75861, Bug #20519832)

   Bugs Fixed

     * InnoDB: InnoDB returned an invalid corruption-related
       error message during an IMPORT TABLESPACE operation. (Bug
       #21838158, Bug #77321)

     * InnoDB: An old version of numactl headers on the build
       host caused a compilation error when building a MySQL
       version that includes NUMA memory policy support. (Bug
       #21785074)

     * InnoDB: An online ALTER TABLE operation caused a server
       exit. (Bug #21640679)

     * InnoDB: A schema mismatch error occurred when importing a
       tablespace that was altered by DROP INDEX operation on
       the source server. (Bug #21514135, Bug #77659)

     * InnoDB: A duplicate key error that occurred during an
       online DDL operation reported an incorrect key name. (Bug
       #21364096, Bug #77572)

     * InnoDB: An ALTER TABLE operation caused the server to
       exit on disk full. (Bug #21326304, Bug #77497)

     * InnoDB: The system tablespace data file did not extend
       automatically when reaching the file size limit, causing
       startup to fail with a size mismatch error and preventing
       the addition of another system tablespace data file. (Bug
       #21287796, Bug #77128)

     * InnoDB: Altering the letter case of a column introduced
       an inconsistency between the frm file and data dictionary
       resulting in a failed CREATE INDEX operation on the
       altered column. (Bug #20755615)

     * InnoDB: An ALTER TABLE operation that converted a table
       to an InnoDB file-per-table tablespace did not check for
       unknown files with the same name as the destination .idb
       file, permitting an unknown file of the same name to be
       overwritten. (Bug #19218794, Bug #73225)

     * Replication: As binlog_error_action=ABORT_SERVER is the
       default in MySQL 5.7.7 and later it is being used for
       more error situations. The behavior has been adjusted to
       generate a core dump to improve troubleshooting
       possibilities. (Bug #21486161, Bug #77738)

     * Replication: Fatal errors encountered during flushing or
       synchronizing the binary log were being ignored. Such
       errors are now caught and handled depending on the
       setting of binlog_error_action. (Bug #76795, Bug #68953,
       Bug #20938915, Bug #16666407)

     * Internal buffer sizes in resolve_stack_dump were
       increased to accommodate larger symbol space requirements
       for C++ code. (Bug #22071592)

     * MySQL development RPM packages could fail to install if
       MySQL Connector/C development RPM packages were
       installed. (Bug #22005375)

     * Possible buffer overflow from incorrect use of strcpy()
       and sprintf() was corrected. (Bug #21973610)

     * MySQL RPM packages for RHEL5 failed to create the mysql
       system user. (Bug #21950975)

     * For Debian package control files, libnuma-dev was added
       to Build-Depends to enable NUMA support. (Bug #21822631)

     * Selecting DECIMAL values into user-defined variables
       could cause a server exit. (Bug #21819304)

     * Concurrent FLUSH PRIVILEGES and REVOKE or GRANT
       statements could produce a small time window during which
       invalid memory access to proxy user information could
       occur, leading to a server exit. (Bug #21602056)

     * Starting the server with the query_alloc_block_size
       system variable set to certain negative values on a
       machine without enough memory could result in
       out-of-memory errors. (Bug #21503595)

     * Using UNINSTALL PLUGIN to uninstall the daemon_example
       plugin could cause a server exit. (Bug #21467458)

     * FLUSH DES_KEY_FILE failed to reload the DES key file.
       (Bug #21370329)

     * If an error occurred during the setup phase of subquery
       materialization used to compute an IN predicate, cleanup
       of the temporary table did not happen, leading to
       Valgrind errors. (Bug #21346081)

     * Queries rejected by MySQL Enterprise Firewall were
       truncated to 512 characters when written to the error
       log. (Bug #20948270)

     * A server exit could occur for the second execution of a
       prepared statement for which an ORDER BY clause referred
       to a column position. (Bug #20755389)

     * Repeated execution of a prepared statement could cause a
       server exit if the default database was changed. (Bug
       #20447262)

     * Outer references do not work as arguments to MATCH(), but
       the server did not properly detect them. Now it does and
       raises an error. (Bug #20007383)
       References: See also Bug #21140088.

     * Valgrind errors were produced during row comparator
       setup. (Bug #19929406)

     * After failure to create a temporary table during join
       processing and releasing the table descriptor, an attempt
       to access the now-invalid descriptor could cause a server
       exit. (Bug #19918299)

     * Type conversion failure for DECIMAL values could cause a
       server exit. (Bug #19912326, Bug #20013538)

     * INSERT DELAYED could cause a server exit for tables
       partitioned with a character column as the key and for
       which the expression required a character set conversion.
       (Bug #19894161)

     * During a filesort for an UPDATE statement, the optimizer
       could access a stale pointer, resulting in a server exit.
       (Bug #19893908)

     * A server exit could occur when updating a view using an
       ALL comparison operator on a subquery that selects from
       an indexed column in the main table. (Bug #19434916)

     * Some stress test files in the
       mysql-test/suite/innodb_stress directory had the
       executable file mode set although they were not script
       files. (Bug #78403, Bug #21822413)

     * The server initialization script used for the service
       mysql status command on Linux sometimes incorrectly
       reported that the server was stopped. (Bug #77696, Bug
       #21768876) 

On Behalf of the MySQL/ORACLE RE Team
Hery Ramilison

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

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

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

Download MySQL Workbench 6.3.6 GA now, for Windows, Mac OS X 10.9+,
Oracle Linux 6 and 7, Fedora 22 and Fedora 23, Ubuntu 14.04 and
Ubuntu 15.10 or sources, from:

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

Enjoy!

Changes in MySQL Workbench 6.3.6 (2015-12-15)

   Functionality Added or Changed

     * On OS X, the multiple object selector was disabled in the
       model overview. (Bug #22265928)

     * On Linux, Fedora 23 is now supported. (Bug #22146526, Bug
       #79101)

     * The "mysql_old_password
       (http://dev.mysql.com/doc/refman/5.7/en/old-client.html)"
       protocol is no longer supported by Workbench, as its
       support was removed in MySQL Server 5.7. This affects the
       former "Use old authentication protocol" option from the 
       "Advanced" configuration tab. This option has now been 
       removed. (Bug #22093548, Bug #78947)

     * Management operations when using an SSH MySQL Server
       connection that authenticated using a password (and not
       SSH keys) would not function. (Bug #22047602)

     * The File, New Query option no longer requires an open
       MySQL connection. (Bug #21879064)

     * The MySQL Firewall tab is now disabled when the Firewall
       user is being created. (Bug #21150265)

   Bugs Fixed

     * Setting the MySQL Firewall mode to "PROTECTING" for a
       user without defined rules would emit an unhandled
       exception. (Bug #22294174)

     * Improvements were made to the Microsoft SQL Server 2008
       migration wizard. (Bug #22271597)

     * On OS X, the MySQL Firewall management option was missing
       from the commercial edition builds. (Bug #22270244)

     * After editing the code of a routine and closing the
       routine editor, the changed routine was duplicated
       instead of applying the changes to the original routine
       object. (Bug #22269199)

     * The JSON Data Field Value Editor functionality was
       improved, and bugs were fixed. Workbench 6.3.5 had known
       limitations. (Bug #22265214, Bug #22337871)

     * On Linux, the MySQL Firewall installation checked the
       path /usr/share/ instead of /usr/share/mysql/. (Bug
       #22263249)

     * For Online Backup, the Fix Grants for MEB function would
       not create the MySQL Enterprise Backup user account. (Bug
       #22258080)

     * The SSL results page listed the "-" character as "_" for
       the SSL certificate file names. (Bug #22243210)

     * Exporting a database from the Data Export wizard did not
       function with remote connections. (Bug #22233795)

     * The libzip library was updated; Workbench can now be
       installed on Ubuntu 15.10. (Bug #22230416, Bug #79320)

     * After initially altering a table using the Alter Table,
       subsequent alterations to the same table in the same
       screen, without having closed the screen, would not
       always complete, as the previous alterations were applied
       again. For example, it might attempt to add a column that
       was already added, or remove a column that was already
       deleted. (Bug #22202325, Bug #79265)

     * Workbench did not recognize identifiers with a leading
       digit if it was preceded by a dot. (Bug #22193758, Bug
       #79247)

     * After creating a table, editing the table in the same tab
       would yield an error after clicking Apply. (Bug
       #22178996, Bug #79199)

     * Clicking Apply a second time while performing an Alter
       Table operation would emit a "No Changes Detected"
       message, despite changes being present. (Bug #22169405,
       Bug #79164)

     * The MySQL connection search field's background and text
       were both white, making it difficult to decipher. (Bug
       #22168697, Bug #79159)

     * On Windows 10, and with resolutions of 1366x768 and
       below, the default table editor window did not show the
       table columns.
       As a workaround, the output pane could be resized or
       hidden. (Bug #22168049, Bug #79160)

     * The "BY" keyword is now supported. (Bug #22151204, Bug
       #79121)

     * The MySQL Enterprise Backup binary can now be configured
       per MySQL connection, to match the correct version needed
       by the connected MySQL server. Before, only one MySQL
       Enterprise Backup binary could be used for all
       connections. (Bug #22143844, Bug #79108)

     * Compiling Workbench now requires Connector/C++ 1.1.7 or
       higher, as this is the first Connector/C++ release that
       supports JSON. (Bug #22141269, Bug #79054)

     * On the Server Logs management tab, the Copy and Copy
       Details options were switched. (Bug #22139172, Bug
       #79082)

     * The Error Logs management tab showed a MySQL Firewall
       button within the community edition. (Bug #22139172, Bug
       #79082)

     * Attempting to install MySQL Enterprise Firewall would
       fail with the following error: "Unhandled exception: type
       object 'FileUtils' has no attribute
       'check_file_readable'".
       As a workaround, execute a xyz_install_firewall.sql
       script that is bundled with MySQL Server. (Bug #22138989,
       Bug #79083)

     * The Alter Table tool did not function with partitioned
       tables. (Bug #22135172, Bug #79070)

     * The preference windows could not be resized. (Bug
       #22121297, Bug #79022)

     * The USE statement result was not preserved in the SQL
       editor, which sometimes led to unknown errors when
       executing multiple statements. (Bug #22106190, Bug
       #78985)

     * After placing a new table on an EER diagram, and
       double-clicking on the new table, the column fields were
       hidden. (Bug #22090203, Bug #78931)

     * "ALTER PROCEDURE" changes were not detected by Workbench
       6.3.5.
       As a workaround, the SQL Editor could be used to decorate
       the "CREATE PROCEDURE" code with delimiters. (Bug
       #22084956, Bug #78924)

     * Workbench 6.3.5 would fail to export MySQL Server 5.6 and
       below, due to changes present in MySQL Server 5.7.
       As a workaround, a MySQL 5.6 version of mysqldump could
       be used. (Bug #22060729)

     * The modeling table editor did not list the JSON data type
       in the dropdown select list, nor did it accept it
       manually. Importing a JSON column from a live database
       worked, but creating/assigning the JSON type in the
       editor was not possible. (Bug #22060699, Bug #22116098,
       Bug #79012)

     * Reverse Engineering a database that contained JSON data
       (columns) failed, and crashed Workbench. (Bug #22053512)

     * The Validate option was missing from the JSON field
       value's editor. (Bug #22052957)

     * The Grid and Tree tabs would interfere with each other in
       the JSON Data Field Value Editor. (Bug #22052934)

     * When using a remote connection, clicking the wrench icon
       next to a table name in the object browser would cause a
       crash. (Bug #22052557)

     * From Models, Create EER Model From Script, importing a
       script would close the diagram instead of creating the
       model. (Bug #22048218)

     * The MySQL Firewall installation wizard did not function.
       (Bug #22047561)

     * The data migration wizard did not always function with
       BLOB data. (Bug #22046141)

     * On Linux, with the commercial edition, the Online Backup
       log window's status log would not always update. (Bug
       #22027353)

     * Attempting to add comments to stored procedures would
       fail with invalid syntax errors. (Bug #21941439, Bug
       #78683)

     * The Action Output auto-scrolling failed to function after
       clicking inside the action log. (Bug #21930774, Bug
       #78648)

     * The Table Data Import wizard failed to import large
       integers. They are now properly detected and assigned as
       BIGINT. (Bug #21896324)

     * Whitespace is now trimmed from the MySQL Connection
       fields. (Bug #21865018, Bug #78471)

     * The MySQL Server start and stop management operations
       would generate unhandled exceptions. (Bug #21861171)

     * With MySQL Server 5.7.8+ connections, the login name
       (username) can now be 32 characters in length. (Bug
       #21848065)

     * The Copy All Field Names action would insert extra
       (repeated) column names. (Bug #21760124, Bug #78280)

     * The SYS Schema could not be installed using a remote
       MySQL Server connection. (Bug #21661235)

     * The SHOW GRANTS statement would be seen as invalid
       syntax. (Bug #21520434, Bug #77868)

     * Generated columns(a feature added in MySQL 5.7) were not
       fully supported in the SQL editor, Table Editor, nor
       Modeling interface. (Bug #21505058, Bug #77837)

     * The bundled OpenSSL library was upgraded to version
       1.0.1p. (Bug #21438134)

     * When adding stored procedures to a Routine Group,
       Workbench would sometimes append "_SYNTAX_ERROR" to the
       procedures. (Bug #21174637, Bug #77197)

     * Several behavioral improvements were made to Workbench
       for when the MySQL Server connection is down. (Bug
       #21131790)

     * SQL auto-completion would sometimes show unavailable
       columns. (Bug #21046868, Bug #76954)

     * Including a model (via File, Include Model) generated a
       window that was too small. (Bug #20956593)

     * When editing a MySQL Server connection, pressing Enter
       under Server Connection, Advanced, Others, could shutdown
       Workbench. (Bug #20930014)

     * On Windows, the Vertical Output tab failed to close. (Bug
       #20834266, Bug #76590)

     * The performance_schema_max_sql_text_length and
       max_digest_length options were not displayed under the
       Options File tab. These variables dictate how queries
       under Statement Analysis are truncated. (Bug #20671061,
       Bug #76223)

     * Resizing the New Job window in the Online Backup
       management tool would show a floating text box. (Bug
       #20631601, Bug #76110)

     * On Fedora 21, Locate Log Files and Show Log File did not
       function due to an underlining Fedora 21 glib issue. (Bug
       #20609499, Bug #76066)

     * On OS X with multiple displays present, the SQL
       auto-complete box would always show on the main display,
       even if Workbench was on the secondary display. The
       underlining Scintilla library was updated to solve this
       problem. (Bug #20341650, Bug #75460)

     * Workbench would report SQL syntax errors for subqueries
       using multiple parentheses. (Bug #20330840, Bug #75462)

     * Saving a model file with non-ASCII characters in the name
       would crash Workbench, and renaming a file using
       non-ASCII characters would rename the file using the .bak
       file extension. (Bug #20328493, Bug #75455)

     * On Windows, the MySQL Workbench application is now
       associated to files with the .sql extension. (Bug
       #20326058, Bug #75453)

     * Scheduled incremental backups would not function if the
       file path contained spaces. (Bug #20254772, Bug #75092)

     * The Check for Update functionality did not detect newer
       Workbench versions for the commercial edition. (Bug
       #20167571, Bug #75132)

     * With incremental backups, TTS usage was attempted with
       the Use Transportable Tablespaces option disabled. This
       resulted in an error. (Bug #20098272)

     * Workbench's Alter Table functionality did not detect
       changes to fractional seconds. (Bug #19774377, Bug
       #74254)

 
Dear MySQL users,

The MySQL Windows Experience Team is proud to announce the
release of MySQL for Excel version 1.3.6. This is a maintenance
release for 1.3.x. It can be used for production environments.

MySQL for Excel is an application plug-in enabling data analysts
to very easily access and manipulate MySQL data within Microsoft
Excel. It enables you to directly work with a MySQL database from
within Microsoft Excel so you can easily do tasks such as:

  * Importing MySQL Data into Excel

  * Exporting Excel data directly into MySQL to a new or existing table

  * Editing MySQL data directly within Excel


MySQL for Excel 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.

- Web (1.5 MB - a network install) which will just pull the MySQL for
  Excel 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/

The MySQL for Excel product can also be downloaded by using the product
standalone installer found at this link
http://dev.mysql.com/downloads/windows/excel/

Changes in MySQL for Excel 1.3.6 (2016-01-07)

     * Functionality Added or Changed

     * Bugs Fixed

   Functionality Added or Changed

     * A new Generate an INSERT statement for each data row
       option was added to the Advanced Options dialog for
       Append and Export Data operations. This is disabled by
       default. A single INSERT statement is generated that
       inserts all affected rows, unless this option is enabled.
       When checked, an INSERT statement for each data row being
       appended or exported is generated in the resulting SQL
       query sent to the MySQL server. When unchecked, a single
       INSERT statement is generated as a bulk data operation,
       which performs better than multiple INSERT statements.
       While row-by-row inserts are slower, for debugging errors
       it could help determine which row causes an error, since
       the MySQL Server will process them row by row.

     * Added column properties to the Export Data dialog to
       support the definition of Auto Increment and Default
       Value for new MySQL tables where the data will be
       exported.
       Added a context menu to declare a numeric field to be
       Unsigned or to have Zero-Fill, accessible by
       right-clicking the Data Type combo box.
       Added the TIMESTAMP data type to the full list of valid
       data types, as it was not being shown before. Added help
       tool tips to fields in the Export Data dialog that
       explain in detail how the column properties work in a
       MySQL database.

   Bugs Fixed

     * The Pivot Table feature was updated to work with Excel
       2016. (Bug #22387425)

     * Closing the plugin via the Close button in the panel
       would not toggle the MySQL for Excel checkbox in the Data
       ribbon. (Bug #22374026, Bug #79655)

     * Fixed the content detector for the active Excel cell
       after importing data and after loading database objects
       when a database is opened. Now, the data options are not
       enabled until a table is selected. (Bug #22372915)

     * Append and Export operations would not append/export
       boolean data. (Bug #22138966)

     * The MySQL for Excel Refresh All function would throw an
       unhandled exception. (Bug #22110627, Bug #78941)

     * With Office 2007, data would not auto-save after closing
       Excel. (Bug #22081313, Bug #78910)

     * Numeric data stored in text columns is now correctly
       formatted by Excel as text, and not as the "General"
       format that automatically formats cells as numbers when
       the data is stored in a text object. This fixes the issue
       where text columns were formatted as numbers, which
       stripped leading zeros. (Bug #20905284, Bug #76738)

     * Changed settings for containers and forms to let all UI
       components automatically scale on different DPI settings.
       Also removed the restriction to resize the MySQL for
       Excel's pane, so in case a different DPI setting is used
       and the fonts look too big, the pane can be resized to
       see contents as best as possible. (Bug #18099454, Bug
       #71389)

Quick links:
MySQL for Excel documentation: http://dev.mysql.com/doc/en/mysql-for-excel.html.
Inside MySQL blog (NEW blog home): http://insidemysql.com/
MySQL on Windows blog (OLD blog home): http://blogs.oracle.com/MySQLOnWindows.
MySQL for Excel forum: http://forums.mysql.com/list.php?172.
MySQL YouTube channel: http://www.youtube.com/user/MySQLChannel.

Enjoy and thanks for the support!
The MySQL on Windows team at Oracle. 

Dear MySQL users,

The MySQL Windows Experience Team is proud to announce the release
of MySQL for Visual Studio 1.2.6.

This is a maintenance release for 1.2.x. It can be used for
production environments.
 
MySQL for Visual Studio is a product that includes all of the
Visual Studio integration functionality to create and manage
MySQL databases when developing .NET applications.

MySQL for Visual Studio is installed using the MySQL Installer
for Windows which comes in 2 versions:
   * Full (150 MB) which includes a complete set of MySQL products
     with their binaries included in the downloaded bundle.
   * Web (1.5 MB - a network install) which will just pull MySQL
     for Visual Studio 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/.
 
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 1.2.6 (2016-01-07)

   Bugs Fixed

     * With MySQL for Visual Studio installed, attempting to
       create MSSQL connections would fail and throw an
       exception. (Bug #22122881, Bug #77441)

     * The Tools, Extensions and Updates, Installed, Tools
       window always reported "1.0.0" as the current MySQL for
       Visual Studio version number. (Bug #22114385)

     * Executing Generate Database from Model from an existing
       Entity Framework model would throw an exception related
       to an error with the T4 template file, when then aborted
       the creation of the database. The Connector/Net Entity
       Framework assembly (MySql.Data.Entity.EF6.dll) path was
       fixed in the MySQL T4 template file (SSDLToMySQL.tt).
       (Bug #20234532, Bug #74388)

     * With Visual Studio 2012, generating a database from a
       model would fail and throw an exception. However,
       clicking OK after the error would cause the action to
       succeed. (Bug #18181649)
 
 
What Is New In MySQL for Visual Studio 1.2
-------------------------------------------------------------------
- New MySQL Project Items for creating data views in Windows Forms and
  ASP.NET MVC web applications.

- A new option in web configuration tool for the ASP.NET Personalization
  Provider (this feature requires MySQL Connector/NET 6.9 or newer).

- A new option in web configuration tool for the ASP.NET Site Map
  Provider   (this feature requires MySQL Connector/NET 6.9 or newer).

- A new option for the MySQLSimpleMembership provider in the web
  configuration tool. (This feature requires MySQL Connector/NET or newer).
 
 
MySQL Windows Forms Project Item
---------------------------------------------------
This Project Item is available on the Add New Item dialog in Visual Studio
when adding a new item to an existing project.

The dialog presented to create the MySQL Windows Forms Project Item
automates the generation of a Windows Form, representing a view for
MySQL data available through an existing Entity Framework's model
entity containing a MySQL table or view.

Different view types are available to present the data:
   * Single-column: A form that contains one control by each existing
     column in the table with navigation controls and that allows CRUD
     operations.All controls can include validations for numeric and
     DateTime data types.

   * Grid: A form with a data grid view that contains navigation controls.

   * Master-detail: A form with a single control layout for the Parent table
     and a data grid view to navigate through child table's data.

Supported with C# or Visual Basic language. This feature requires
Connector/NET 6.7.5, 6.8.3 or 6.9.x.

For more details on the features included check the documentation at:
https://dev.mysql.com/doc/connector-net/en/visual-studio-project-items-forms.html
 
 
MySQL ASP.NET MVC Project Item
------------------------------------------------
This Project Item is available on the Add New Item dialog in Visual Studio
when adding a new item to an existing project.

The dialog presented to create the MySQL ASP.NET MVC Item automates the
generation of a controller and its corresponding view, representing a view
for MySQL data available through an existing Entity Framework's model entity
containing a MySQL table or view. The MVC versions supported by this wizard
are 3 when using Visual Studio 2010 or 2012, and 4 when using Visual Studio
2013 or greater.

The generation of the MVC items is done by creating an Entity Framework data
model either with Entity Framework version 5 or 6 depending on the user's
selection.

Supported with C# or Visual Basic language. This feature requires
Connector/NET 6.7.5, 6.8.3 or 6.9.x.

For more details on the features included check the documentation at:
https://dev.mysql.com/doc/connector-net/en/visual-studio-project-items-mvc.html
 
 
New option in web configuration tool for the ASP.NET Personalization Provider
---------------------------------------------------------------------------------------------------------------------------
Personalization provider allows to store personalization state-state data regarding
the content and layout of Web Parts pages-generated by the Web Parts personalization
service using MySQL as a data source. This feature requires Connector/NET 6.9.x
or greater.

http://dev.mysql.com/doc/connector-net/en/connector-net-website-config.html
 
 
New option in web configuration tool for the ASP.NET Site Map Provider
----------------------------------------------------------------------------------------------------------------
Site Map provider allows to show a hierarchical list of links that describe the
structure of a site. This feature requires Connector/NET 6.9.x or greater.

http://dev.mysql.com/doc/connector-net/en/connector-net-website-config.html
 
 
New option in web configuration tool for the ASP.NET Simple Membership provider
------------------------------------------------------------------------------------------------------------------------------
The latest provider added to handle web site membership tasks with ASP.NET.
This feature requires Connector/Net 6.9.x or greater.

http://dev.mysql.com/doc/connector-net/en/connector-net-simple-membership-tutorial.html
 
 
 
Quick links:
- MySQL for Visual Studio documentation:
  http://dev.mysql.com/doc/connector-net/en/connector-net-visual-studio.html
- Inside MySQL blog (NEW blog home): http://insidemysql.com/
- MySQL on Windows blog (OLD blog home): http://blogs.oracle.com/MySQLOnWindows
- MySQL for Visual Studio forum: http://forums.mysql.com/list.php?174
- MySQL YouTube channel: http://www.youtube.com/user/MySQLChannel
- MySQL Bugs database: http://bugs.mysql.com
 
Enjoy and thanks for the support!

Dear MySQL Users,

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

  - In-memory persistent 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.9, 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.9 (5.6.28-ndb-7.4.9) (2016-01-18)

   MySQL Cluster NDB 7.4.9 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
   MySQL Cluster Development in MySQL Cluster NDB 7.4
   (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-development-
   5-6-ndb-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.28 (see Changes in MySQL 5.6.28
   (2015-12-07)
   (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-28.html)).

   Functionality Added or Changed

     * Important Change: Previously, the NDB scheduler always
       optimized for speed against throughput in a predetermined
       manner (this was hard coded); this balance can now be set
       using the SchedulerResponsiveness data node configuration
       parameter. This parameter accepts an integer in the range
       of 0-10 inclusive, with 5 as the default. Higher values
       provide better response times relative to throughput.
       Lower values provide increased throughput, but impose
       longer response times. (Bug #78531, Bug #21889312)

     * Added the tc_time_track_stats table to the ndbinfo
       information database. This table provides time-tracking
       information relating to transactions, key operations, and
       scan operations performed by NDB. (Bug #78533, Bug
       #21889652)

     * Cluster Replication: Normally, RESET SLAVE causes all
       entries to be deleted from the mysql.ndb_apply_status
       table. This release adds the ndb_clear_apply_status
       system variable, which makes it possible to override this
       behavior. This variable is ON by default; setting it to
       OFF keeps RESET SLAVE from purging the ndb_apply_status
       table. (Bug #12630403)

   Bugs Fixed

     * Important Change: Users can now set the number and length
       of connection timeouts allowed by most NDB programs with
       the --connect-retries and --connect-retry-delay command
       line options introduced for the programs in this release.
       For ndb_mgm, --connect-retries supersedes the existing
       --try-reconnect option. (Bug #57576, Bug #11764714)

     * When executing a schema operation such as CREATE TABLE on
       a MySQL Cluster with multiple SQL nodes, it was possible
       for the SQL node on which the operation was performed to
       time out while waiting for an acknowledgement from the
       others. This could occur when different SQL nodes had
       different settings for --ndb-log-updated-only,
       --ndb-log-update-as-write, or other mysqld options
       effecting binary logging by NDB.
       This happened due to the fact that, in order to
       distribute schema changes between them, all SQL nodes
       subscribe to changes in the ndb_schema system table, and
       that all SQL nodes are made aware of each others
       subscriptions by subscribing to TE_SUBSCRIBE and
       TE_UNSUBSCRIBE events. The names of events to subscribe
       to are constructed from the table names, adding REPL$ or
       REPLF$ as a prefix. REPLF$ is used when full binary
       logging is specified for the table. The issue described
       previously arose because different values for the options
       mentioned could lead to different events being subscribed
       to by different SQL nodes, meaning that all SQL nodes
       were not necessarily aware of each other, so that the
       code that handled waiting for schema distribution to
       complete did not work as designed.
       To fix this issue, MySQL Cluster now treats the
       ndb_schema table as a special case and enforces full
       binary logging at all times for this table, independent
       of any settings for mysqld binary logging options. (Bug
       #22174287, Bug #79188)

     * Attempting to create an NDB table having greater than the
       maximum supported combined width for all BIT columns
       (4096) caused data node failure when these columns were
       defined with COLUMN_FORMAT DYNAMIC. (Bug #21889267)

     * Creating a table with the maxmimum supported number of
       columns (512) all using COLUMN_FORMAT DYNAMIC led to data
       node failures. (Bug #21863798)

     * In certain cases, a cluster failure (error 4009) was
       reported as Unknown error code. (Bug #21837074)

     * For a timeout in GET_TABINFOREQ while executing a CREATE
       INDEX statement, mysqld returned Error 4243 (Index not
       found) instead of the expected Error 4008 (Receive from
       NDB failed).
       The fix for this bug also fixes similar timeout issues
       for a number of other signals that are sent the DBDICT
       kernel block as part of DDL operations, including
       ALTER_TAB_REQ, CREATE_INDX_REQ, DROP_FK_REQ,
       DROP_INDX_REQ, INDEX_STAT_REQ, DROP_FILE_REQ,
       CREATE_FILEGROUP_REQ, DROP_FILEGROUP_REQ, CREATE_EVENT,
       WAIT_GCP_REQ, DROP_TAB_REQ, and LIST_TABLES_REQ, as well
       as several internal functions used in handling NDB schema
       operations. (Bug #21277472)
       References: See also Bug #20617891, Bug #20368354, Bug
       #19821115.

     * Using ndb_mgm STOP -f to force a node shutdown even when
       it triggered a complete shutdown of the cluster, it was
       possible to lose data when a sufficient number of nodes
       were shut down, triggering a cluster shutodwn, and the
       timing was such that SUMA handovers had been made to
       nodes already in the process of shutting down. (Bug
       #17772138)

     * The internal NdbEventBuffer::set_total_buckets() method
       calculated the number of remaining buckets incorrectly.
       This caused any incomplete epoch to be prematurely
       completed when the SUB_START_CONF signal arrived out of
       order. Any events belonging to this epoch arriving later
       were then ignored, and so effectively lost, which
       resulted in schema changes not being distributed
       correctly among SQL nodes. (Bug #79635, Bug #22363510)

     * Compilation of MySQL Cluster failed on SUSE Linux
       Enterprise Server 12. (Bug #79429, Bug #22292329)

     * Schema events were appended to the binary log out of
       order relative to non-schema events. This was caused by
       the fact that the binlog injector did not properly handle
       the case where schema events and non-schema events were
       from different epochs.
       This fix modifies the handling of events from the two
       schema and non-schema event streams such that events are
       now always handled one epoch at a time, starting with
       events from the oldest available epoch, without regard to
       the event stream in which they occur. (Bug #79077, Bug
       #22135584, Bug #20456664)

     * When executed on an NDB table, ALTER TABLE ... DROP INDEX
       made changes to an internal array referencing the indexes
       before the index was actually dropped, and did not revert
       these changes in the event that the drop was not
       completed. One effect of this was that, after attempting
       to drop an index on which there was a foreign key
       dependency, the expected error referred to the wrong
       index, and subsequent attempts using SQL to modify
       indexes of this table failed. (Bug #78980, Bug #22104597)

     * NDB failed during a node restart due to the status of the
       current local checkpoint being set but not as active,
       even though it could have other states under such
       conditions. (Bug #78780, Bug #21973758)

     * ndbmtd checked for signals being sent only after a full
       cycle in run_job_buffers, which is performed for all job
       buffer inputs. Now this is done as part of
       run_job_buffers itself, avoiding executing for extended 
       periods without sending to other nodes or flushing signals 
       to other threads. (Bug #78530, Bug #21889088)

     * In MySQL Cluster 7.4 scan executions was optimised by 
       handling multiple rows at a time. This has two effects, 
       1) it gives scans higher prio compared to key lookup 
       operations, 2) it changes the behaviour of the scheduler. 
       2) was fixed, restoring the former scheduling behaviour.
       1) is kept since it has a significant performance benefit 
       but means were provided for change of this in exceptional 
       circumstances. (Bug #78526, Bug #21886644)

     * Disk Data: A unique index on a column of an NDB table is
       implemented with an associated internal ordered index,
       used for scanning. While dropping an index, this ordered
       index was dropped first, followed by the drop of the
       unique index itself. This meant that, when the drop was
       rejected due to (for example) a constraint violation, the
       statement was rejected but the associated ordered index
       remained deleted, so that any subsequent operation using
       a scan on this table failed. We fix this problem by
       causing the unique index to be removed first, before
       removing the ordered index; removal of the related
       ordered index is no longer performed when removal of a
       unique index fails. (Bug #78306, Bug #21777589)

     * Cluster Replication: While the binary log injector thread
       was handling failure events, it was possible for all NDB
       tables to be left indefinitely in read-only mode. This
       was due to a race condition between the binlog injector
       thread and the utility thread handling events on the
       ndb_schema table, and to the fact that, when handling
       failure events, the binlog injector thread places all NDB
       tables in read-only mode until all such events are
       handled and the thread restarts itself.
       When the binlog inject thread receives a group of one or
       more failure events, it drops all other existing event
       operations and expects no more events from the utility
       thread until it has handled all of the failure events and
       then restarted itself. However, it was possible for the
       utility thread to continue attempting binary log setup
       while the injector thread was handling failures and thus
       attempting to create the schema distribution tables as
       well as event subscriptions on these tables. If the
       creation of these tables and event subscriptions occurred
       during this time, the binlog injector thread's
       expectation that there were no further event operations
       was never met; thus, the injector thread never restarted,
       and NDB tables remained in read-only as described
       previously.
       To fix this problem, the Ndb object that handles schema
       events is now definitely dropped once the ndb_schema
       table drop event is handled, so that the utility thread
       cannot create any new events until after the injector
       thread has restarted, at which time, a new Ndb object for
       handling schema events is created. (Bug #17674771, Bug
       #19537961, Bug #22204186, Bug #22361695)

     * Cluster API: The binlog injector did not work correctly
       with TE_INCONSISTENT event type handling by
       Ndb::nextEvent(). (Bug #22135541)
       References: See also Bug #20646496.

     * Cluster API: Ndb::pollEvents() and pollEvents2() were
       slow to receive events, being dependent on other client
       threads or blocks to perform polling of transporters on
       their behalf. This fix allows a client thread to perform
       its own transporter polling when it has to wait in either
       of these methods.
       Introduction of transporter polling also revealed a
       problem with missing mutex protection in the
       ndbcluster_binlog handler, which has been added as part
       of this fix. (Bug #20957068, Bug #22224571, Bug #79311)

     * Cluster API: Garbage collection is performed on several
       objects in the implementation of NdbEventOperation, based
       on which GCIs have been consumed by clients, including
       those that have been dropped by
       Ndb::dropEventOperation(). In this implementation, the
       assumption was made that the global checkpoint index
       (GCI) is always monotonically increasing, although this
       is not the case during an initial restart, when the GCI
       is reset. This could lead to event objects in the NDB API
       being released prematurely or not at all, in the latter
       case causing a resource leak.
       To prevent this from happening, the NDB event object's
       implementation now tracks, internally, both the GCI and
       the generation of the GCI; the generation is incremented
       whenever the node process is restarted, and this value is
       now used to provide a monotonically increasing sequence.
       (Bug #73781, Bug #21809959)

On behalf of the MySQL Release Team,
Lars Tangvald

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.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.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.12 (5.6.28-ndb-7.3.12) (2016-01-19)

   MySQL Cluster NDB 7.3.12 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
   MySQL Cluster Development in MySQL Cluster NDB 7.3
   (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-develop
   ment-5-6-ndb-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.28 (see Changes in MySQL 5.6.28
   (2015-12-07)
   (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-28.h
   tml)).

   Bugs Fixed

     * Important Note: If an NDB table having a foreign key was
       dropped while one of the data nodes was stopped, the data
       node later failed when trying to restart. (Bug #18554390)

     * In debug builds, a WAIT_EVENT while polling caused
       excessive logging to stdout. (Bug #22203672)

     * When executing a schema operation such as CREATE TABLE on
       a MySQL Cluster with multiple SQL nodes, it was possible
       for the SQL node on which the operation was performed to
       time out while waiting for an acknowledgement from the
       others. This could occur when different SQL nodes had
       different settings for --ndb-log-updated-only,
       --ndb-log-update-as-write, or other mysqld options
       effecting binary logging by NDB.
       This happened due to the fact that, in order to
       distribute schema changes between them, all SQL nodes
       subscribe to changes in the ndb_schema system table, and
       that all SQL nodes are made aware of each others
       subscriptions by subscribing to TE_SUBSCRIBE and
       TE_UNSUBSCRIBE events. The names of events to subscribe
       to are constructed from the table names, adding REPL$ or
       REPLF$ as a prefix. REPLF$ is used when full binary
       logging is specified for the table. The issue described
       previously arose because different values for the options
       mentioned could lead to different events being subscribed
       to by different SQL nodes, meaning that all SQL nodes
       were not necessarily aware of each other, so that the
       code that handled waiting for schema distribution to
       complete did not work as designed.
       To fix this issue, MySQL Cluster now treats the
       ndb_schema table as a special case and enforces full
       binary logging at all times for this table, independent
       of any settings for mysqld binary logging options. (Bug
       #22174287, Bug #79188)

     * Attempting to create an NDB table having greater than the
       maximum supported combined width for all BIT columns
       (4096) caused data node failure when these columns were
       defined with COLUMN_FORMAT DYNAMIC. (Bug #21889267)

     * Creating a table with the maxmimum supported number of
       columns (512) all using COLUMN_FORMAT DYNAMIC led to data
       node failures. (Bug #21863798)

     * Using ndb_mgm STOP -f to force a node shutdown even when
       it triggered a complete shutdown of the cluster, it was
       possible to lose data when a sufficient number of nodes
       were shut down, triggering a cluster shutodwn, and the
       timing was such that SUMA handovers had been made to
       nodes already in the process of shutting down. (Bug
       #17772138)

     * The internal NdbEventBuffer::set_total_buckets() method
       calculated the number of remaining buckets incorrectly.
       This caused any incomplete epoch to be prematurely
       completed when the SUB_START_CONF signal arrived out of
       order. Any events belonging to this epoch arriving later
       were then ignored, and so effectively lost, which
       resulted in schema changes not being distributed
       correctly among SQL nodes. (Bug #79635, Bug #22363510)

     * Compilation of MySQL Cluster failed on SUSE Linux
       Enterprise Server 12. (Bug #79429, Bug #22292329)

     * Schema events were appended to the binary log out of
       order relative to non-schema events. This was caused by
       the fact that the binlog injector did not properly handle
       the case where schema events and non-schema events were
       from different epochs.
       This fix modifies the handling of events from the two
       schema and non-schema event streams such that events are
       now always handled one epoch at a time, starting with
       events from the oldest available epoch, without regard to
       the event stream in which they occur. (Bug #79077, Bug
       #22135584, Bug #20456664)

     * NDB failed during a node restart due to the status of the
       current local checkpoint being set but not as active,
       even though it could have other states under such
       conditions. (Bug #78780, Bug #21973758)

     * Cluster Replication: While the binary log injector thread
       was handling failure events, it was possible for all NDB
       tables to be left indefinitely in read-only mode. This
       was due to a race condition between the binlog injector
       thread and the utility thread handling events on the
       ndb_schema table, and to the fact that, when handling
       failure events, the binlog injector thread places all NDB
       tables in read-only mode until all such events are
       handled and the thread restarts itself.
       When the binlog inject thread receives a group of one or
       more failure events, it drops all other existing event
       operations and expects no more events from the utility
       thread until it has handled all of the failure events and
       then restarted itself. However, it was possible for the
       utility thread to continue attempting binary log setup
       while the injector thread was handling failures and thus
       attempting to create the schema distribution tables as
       well as event subscriptions on these tables. If the
       creation of these tables and event subscriptions occurred
       during this time, the binlog injector thread's
       expectation that there were no further event operations
       was never met; thus, the injector thread never restarted,
       and NDB tables remained in read-only as described
       previously.
       To fix this problem, the Ndb object that handles schema
       events is now definitely dropped once the ndb_schema
       table drop event is handled, so that the utility thread
       cannot create any new events until after the injector
       thread has restarted, at which time, a new Ndb object for
       handling schema events is created. (Bug #17674771, Bug
       #19537961, Bug #22204186, Bug #22361695)

     * Cluster API: The binlog injector did not work correctly
       with TE_INCONSISTENT event type handling by
       Ndb::nextEvent(). (Bug #22135541)
       References: See also Bug #20646496.

     * Cluster API: Ndb::pollEvents() and pollEvents2() were
       slow to receive events, being dependent on other client
       threads or blocks to perform polling of transporters on
       their behalf. This fix allows a client thread to perform
       its own transporter polling when it has to wait in either
       of these methods.
       Introduction of transporter polling also revealed a
       problem with missing mutex protection in the
       ndbcluster_binlog handler, which has been added as part
       of this fix. (Bug #20957068, Bug #22224571, Bug #79311)

On behalf of Oracle MySQL RE team
Sreedhar S

Dear MySQL Users,

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

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

MySQL Cluster 7.2.23, 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.23 (5.5.47-ndb-7.2.23) (2016-01-19)

   MySQL Cluster NDB 7.2.23 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.47 (see Changes in MySQL 5.5.47
   (2015-12-07)
   (http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-47.html)).

   Bugs Fixed

     * In debug builds, a WAIT_EVENT while polling caused
       excessive logging to stdout. (Bug #22203672)

     * When executing a schema operation such as CREATE TABLE on
       a MySQL Cluster with multiple SQL nodes, it was possible
       for the SQL node on which the operation was performed to
       time out while waiting for an acknowledgement from the
       others. This could occur when different SQL nodes had
       different settings for --ndb-log-updated-only,
       --ndb-log-update-as-write, or other mysqld options
       effecting binary logging by NDB.
       This happened due to the fact that, in order to
       distribute schema changes between them, all SQL nodes
       subscribe to changes in the ndb_schema system table, and
       that all SQL nodes are made aware of each others
       subscriptions by subscribing to TE_SUBSCRIBE and
       TE_UNSUBSCRIBE events. The names of events to subscribe
       to are constructed from the table names, adding REPL$ or
       REPLF$ as a prefix. REPLF$ is used when full binary
       logging is specified for the table. The issue described
       previously arose because different values for the options
       mentioned could lead to different events being subscribed
       to by different SQL nodes, meaning that all SQL nodes
       were not necessarily aware of each other, so that the
       code that handled waiting for schema distribution to
       complete did not work as designed.
       To fix this issue, MySQL Cluster now treats the
       ndb_schema table as a special case and enforces full
       binary logging at all times for this table, independent
       of any settings for mysqld binary logging options. (Bug
       #22174287, Bug #79188)

     * Using ndb_mgm STOP -f to force a node shutdown even when
       it triggered a complete shutdown of the cluster, it was
       possible to lose data when a sufficient number of nodes
       were shut down, triggering a cluster shutodwn, and the
       timing was such that SUMA handovers had been made to
       nodes already in the process of shutting down. (Bug
       #17772138)

     * The internal NdbEventBuffer::set_total_buckets() method
       calculated the number of remaining buckets incorrectly.
       This caused any incomplete epoch to be prematurely
       completed when the SUB_START_CONF signal arrived out of
       order. Any events belonging to this epoch arriving later
       were then ignored, and so effectively lost, which
       resulted in schema changes not being distributed
       correctly among SQL nodes. (Bug #79635, Bug #22363510)

     * Schema events were appended to the binary log out of
       order relative to non-schema events. This was caused by
       the fact that the binlog injector did not properly handle
       the case where schema events and non-schema events were
       from different epochs.
       This fix modifies the handling of events from the two
       schema and non-schema event streams such that events are
       now always handled one epoch at a time, starting with
       events from the oldest available epoch, without regard to
       the event stream in which they occur. (Bug #79077, Bug
       #22135584, Bug #20456664)

     * NDB failed during a node restart due to the status of the
       current local checkpoint being set but not as active,
       even though it could have other states under such
       conditions. (Bug #78780, Bug #21973758)

     * Cluster Replication: While the binary log injector thread
       was handling failure events, it was possible for all NDB
       tables to be left indefinitely in read-only mode. This
       was due to a race condition between the binlog injector
       thread and the utility thread handling events on the
       ndb_schema table, and to the fact that, when handling
       failure events, the binlog injector thread places all NDB
       tables in read-only mode until all such events are
       handled and the thread restarts itself.
       When the binlog inject thread receives a group of one or
       more failure events, it drops all other existing event
       operations and expects no more events from the utility
       thread until it has handled all of the failure events and
       then restarted itself. However, it was possible for the
       utility thread to continue attempting binary log setup
       while the injector thread was handling failures and thus
       attempting to create the schema distribution tables as
       well as event subscriptions on these tables. If the
       creation of these tables and event subscriptions occurred
       during this time, the binlog injector thread's
       expectation that there were no further event operations
       was never met; thus, the injector thread never restarted,
       and NDB tables remained in read-only as described
       previously.
       To fix this problem, the Ndb object that handles schema
       events is now definitely dropped once the ndb_schema
       table drop event is handled, so that the utility thread
       cannot create any new events until after the injector
       thread has restarted, at which time, a new Ndb object for
       handling schema events is created. (Bug #17674771, Bug
       #19537961, Bug #22204186, Bug #22361695)

     * Cluster API: The binlog injector did not work correctly
       with TE_INCONSISTENT event type handling by
       Ndb::nextEvent(). (Bug #22135541)
       References: See also Bug #20646496.

     * Cluster API: Ndb::pollEvents() and pollEvents2() were
       slow to receive events, being dependent on other client
       threads or blocks to perform polling of transporters on
       their behalf. This fix allows a client thread to perform
       its own transporter polling when it has to wait in either
       of these methods.
       Introduction of transporter polling also revealed a
       problem with missing mutex protection in the
       ndbcluster_binlog handler, which has been added as part
       of this fix. (Bug #20957068, Bug #22224571, Bug #79311)

Dear MySQL Users,

A new GA (general availability) version of MySQL Connector/C++ has
been made available: MySQL Connector/C++ 1.1.7 GA. The MySQL
Connector/C++ provides a C++ API for connecting client applications to
the MySQL Server 5.5 or newer.

You can download the production release at:

http://dev.mysql.com/downloads/connector/cpp/1.1.html

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

The MySQL driver for C++ offers an easy to use API derived from JDBC
4.0. MySQL Workbench has used it successfully for years.

We have improved the driver since the last GA release. Please see the
documentation and the CHANGES file in the source distribution for a
detailed description of bugs that have been fixed. Bug descriptions are
also listed below.

Enjoy!

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

Changes in MySQL Connector/C++ 1.1.7

Configuration Notes

* Binary distributions for this release of MySQL
Connector/C++ were linked against libmysqlclient from
MySQL 5.7.10, except for OS X 10.8/10.9, for which
distributions were linked against MySQL 5.7.9. This
enables Connector/C++ to take advantage of features
present in recent client library versions. Some examples:

+ Support for the MySQL JSON data type is available.
Current versions of MySQL Workbench require JSON
support, so to build MySQL Workbench 6.3.5 or higher
from source, it is necessary to use a version of
Connector/C++ at least as recent as 1.1.7.

+ Applications will attempt to establish a secure
(encrypted) connection by default whenever the
server is enabled to support secure connections, and
fall back to an unencrypted connection otherwise.
(This is as described at Configuring MySQL to Use
Secure Connections

(http://dev.mysql.com/doc/refman/5.7/en/using-secure-connections.html).)
To enforce a secure connection, such that an error occurs
if secure connections are not available, applications can
enable the sslEnforce connection option.
To build Connector/C++ from source, you must use either a
General Availability version of MySQL 5.7 (5.7.9 or
higher) or Connector/C 6.1.8 or higher. Set the MYSQL_DIR
CMake option appropriately at configuration time as
necessary. (Bug #22351273)

Security Notes

* The linked OpenSSL library for Connector/C++ Commercial
has been updated to version 1.0.1q. Issues fixed in the
new OpenSSL version are described at
http://www.openssl.org/news/vulnerabilities.html.
This change does not affect Oracle-produced MySQL
Community builds of Connector/C++, which use the yaSSL
library instead.

Spatial Data Support

* The required version of the Boost library for
Connector/C++ builds has been raised to 1.56.0.

Bugs Fixed

* MySQL_Prepared_ResultSet::relative() failed to fetch the
record due to a missing proxy->fetch() call. (Bug
#21152054)

* During Connector/C++ builds, the MySQL Server CXXFLAGS
and CFLAGS values were used rather than the system
default values. To specify explicitly to use the server
values, enable the new USE_SERVER_CXXFLAGS CMake option.
(Bug #77655, Bug #21391025)

On Behalf of the MySQL/ORACLE RE Team

Dear MySQL users,

MySQL Enterprise Backup v3.12.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.

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

Changes in MySQL Enterprise Backup 3.12.2      (2016-01-21)

   Functionality Added or Changed

     * If the value for the innodb_checksum_algorithm or
       backup_innodb_checksum_algorithm option provided on the
       mysqlbackup command line differed from that of the
       server, mysqlbackup gave a single warning that the
       checksum algorithm specified might be incompatible with
       the server. Starting with 3.12.2, to be consistent with
       the way checksums are handled by the MySQL server since
       5.6.25, mysqlbackup gives a separate warning for every
       single page of data in every .ibd file for which the
       checksum algorithm specified does not match the one used
       on the server. (Bug #22509993)

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

   Bugs Fixed

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

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

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

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

     * When a backup took a long time to perform and the binary
       logs were rotated in the middle of the process,
       mysqlbackup lost track of the binary log files it was
       copying, skipping the second last log file and attempting
       to copy the last one twice; that resulted in a file
       creation error, at which point mysqlbackup quit
       without releasing its lock on the tables in the database.
       With this fix, all binary log files are now copied
       properly, and the lock on the tables is released at the
       end of the backup process as usual. (Bug #20971763)

     * When restoring an incremental backup image, if the binary
       log in the backup was larger than 16MB, the restored
       binary log would become corrupted, as mysqlbackup kept
       overwriting the same 16-MB file again and again with
       binary log contents. With this fix, the binary log is now
       correctly restored and has the same size as it did on the
       backed-up server. (Bug #20915642)

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

     * When the --password option was used without an argument
       with the copy-back-and-apply-log command, mysqlbackup did
       not prompt user for a password, but either took the
       password from the defaults files, or took it to be an
       empty string when no value was specified in the defaults
       files. (Bug #20657939)

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

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


You can also find more information on the contents of this release in the change log:
http://dev.mysql.com/doc/mysql-enterprise-backup/3.12/en/meb-news.html

The complete manual for MEB 3.12.2 is at
http://dev.mysql.com/doc/mysql-enterprise-backup/3.12/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