MySQL Connector/ODBC 8.0.16 has been released

[Hery Ramilison]

Dear MySQL users,

MySQL Connector/ODBC 8.0.16 is a new version in the MySQL Connector/ODBC 
8.0 series,

the ODBC driver for the MySQL Server.

The available downloads include both a Unicode driver and an ANSI driver 
based on the
same modern codebase. Please select the driver type you need based on 
the type of your
application - Unicode or ANSI. Server-side prepared statements are 
enabled by default.

It is suitable for use with the latest MySQL server version 8.0.

This release of the MySQL ODBC driver is conforming to the ODBC 3.8 
specification.
It contains implementations of key 3.8 features, including 
self-identification
as a ODBC 3.8 driver, streaming of output parameters (supported for 
binary types
only), and support of the SQL_ATTR_RESET_CONNECTION connection attribute 
(for the

Unicode driver only).

The release is now available in source and binary form for a number of 
platforms

from our download pages at

https://dev.mysql.com/downloads/connector/odbc/

For information on installing, please see the documentation at

https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-installation.html

Enjoy and thanks for the support!

==

Changes in MySQL Connector/ODBC 8.0.16 (2019-04-25, General Availability)

Bugs Fixed


 * Connector/ODBC 8.0 is now built with OpenSSL 1.0.2R.
   Issues fixed in the new OpenSSL version are described at
   http://www.openssl.org/news/vulnerabilities.html. (Bug
   #29538143)

 * An exception was emitted when fetching contents of a
   BLOB/TEXT records after executing a statement as a
   server-side prepared statement with a bound parameter.
   The workaround is not using parameters or specifying
   NO_SSPS=1 in the connection string; this allows the
   driver to fetch the data. (Bug #29282638, Bug #29512548,
   Bug #28790708, Bug #93895, Bug #94545, Bug #92078)

On Behalf of Oracle/MySQL Release Engineering Team,
Hery Ramilison

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL Connector/Node.js 8.0.16 has been released

[Gipson Pulla]

Dear MySQL users,

MySQL Connector/Node.js is a new Node.js driver for use with the X
DevAPI. This release, v8.0.16, is a maintenance release of the
MySQL Connector/Node.js 8.0 series.

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

MySQL Connector/Node.js can be downloaded through npm (see
https://www.npmjs.com/package/@mysql/xdevapi for details) or from
https://dev.mysql.com/downloads/connector/nodejs/.

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

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


Changes in MySQL Connector/Node.js 8.0.16 (2019-04-25, General
Availability)

X DevAPI Notes


 * Connector/Node.js now supports connection attributes as
   key-value pairs that application programs can pass to the
   server. Connector/Node.js defines a default set of
   attributes, which can be disabled or enabled. In addition
   to these default attributes, applications can also
   provide their own set of custom attributes.

  + Specify connection attributes as a
connection-attributes parameter in a connection
string, or by using the connectionAttributes
property using either a plain JavaScript object or
JSON notation to specify the connection
configuration options.
The connection-attributes parameter value must be
either empty (the same as specifying true), a
Boolean value (true or false to enable or disable
the default attribute set), or a list of zero or
more key=value pair specifiers separated by commas
(to be sent in addition to the default attribute
set). Within a list, a missing key value evaluates
as NULL.
The connectionAttributes property allows passing
user-defined attributes to the application using
either a plain JavaScript object or JSON notation to
specify the connection configuration options. Define
each attribute in a nested object under
connectionAttributes where the property names
matches the attribute names, and the property values
match the attribute values. Unlike
connection-attributes, and while using plain
JavaScript objects or JSON notation, if the
connectionAttributes object contains duplicate keys
then no error is thrown and the last value specified
for a duplicate object key is chosen as the
effective attribute value.
Examples:
Not sending the default client-defined attributes:
mysqlx.getSession('{ "user": "root", "connectionAttributes": false }')

mysqlx.getSession('mysqlx://root@localhost?connection-attributes=false
')

mysqlx.getSession({ user: 'root', connectionAttributes: { foo: 'bar',
baz: 'qux', quux: '' } })
mysqlx.getSession('mysqlx://root@localhost?connection-attributes=[foo=
bar,baz=qux,quux]')


   Application-defined attribute names cannot begin with _
   because such names are reserved for internal attributes.
   If connection attributes are not specified in a valid
   way, an error occurs and the connection attempt fails.
   For general information about connection attributes, see
   Performance Schema Connection Attribute Tables
(http://dev.mysql.com/doc/refman/8.0/en/performance-schema-connection-attribute-tables.html).

Functionality Added or Changed


 * Optimized the reuse of existing connections through
   client.getSession() by only re-authenticating if
   required.

 * For X DevAPI, performance for statements that are
   executed repeatedly (two or more times) is improved by
   using server-side prepared statements for the second and
   subsequent executions. This happens internally;
   applications need take no action and API behavior should
   be the same as previously. For statements that change,
   repreparation occurs as needed. Providing different data
   values or different offset() or limit() values does not
   count as a change. Instead, the new values are passed to
   a new invocation of the previously prepared statement.

Bugs Fixed


 * Idle pooled connections to MySQL Server were not reused,
   and instead new connections had to be recreated. (Bug
   #29436892)

 * Executing cli

MySQL Community Server 5.6.44 has been released

[Gipson Pulla]

Dear MySQL users,

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

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

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

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

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

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

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

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

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

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

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

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

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

Enjoy!

Changes in MySQL 5.6.44 (2019-04-25, General Availability)

   Beginning with MySQL 5.6.44, Oracle no longer provides
   binaries for SUSE 11.

Security Notes


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

Bugs Fixed


 * Important Note: The libevent library included with the
   MySQL Server was upgraded to version 2.1.8. (Bug
   #28207237, Bug #29041505, Bug #29055011)

 * InnoDB: The INDEX_LENGTH value in
   INFORMATION_SCHEMA.TABLES was not updated when adding an
   index. (Bug #19811005)

 * Partitioning: An AUTO_INCREMENT key added to a
   partitioned table by an ALTER TABLE statement using
   ALGORITHM=INPLACE restarted on each partition. (Bug
   #92241, Bug #28573894)

 * Replication: If an applier thread was stopped while it
   was in the process of opening a table, no error was set,
   which could result in a segmentation fault or assertion
   depending on the build type. Error handling is now
   correctly activated in this situation. (Bug #28864557)

 * Replication: If a storage engine has the capability to
   log in STATEMENT format but not in ROW format, when
   binlog_format is set to STATEMENT, an unsafe SQL
   statement should be logged and a warning message should
   be written to the error log. However, such statements
   were instead not executed and an error message was
   written to the error log, which is the correct behavior
   when binlog_format is set to MIXED or ROW. The issue has
   now been corrected so that unsafe statements are logged
   with a warning as expected when binlog_format is set to
   STATEMENT. (Bug #28429993, Bug #73936)

 * Microsoft Windows: Validity testing for the
   named_pipe_full_access_group system variable did not
   account for NULL values. (Bug #29256690)

 * MySQL 5.6 did not build with maintainer mode enabled with
   GCC 7. (Bug #29048768)

 * A damaged mysql.user table could cause a server exit.
   (Bug #28986737)

 * mysqladmin shutdown did not wait for mysqld to shut down.
   (Bug #28466137, Bug #91803)
   References: This issue is a regression of: Bug #25364806.

 * Some status variable values could temporarily increase
   before returning to their original value. (Bug #27839644,
   Bug #90351)

 * The binary file for the udf_example user-defined function
   was omitted from binary distributions. (Bug #26115002,
   Bug #29178542)

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


On Behalf of MySQL/ORACLE RE Team
Gipson Pulla

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL Connector/NET 8.0.16 has been released

[Surabhi Bhat]

Dear MySQL users,

MySQL Connector/NET 8.0.16 is the fourth version to support
Entity Framework Core 2.1 and the sixth general availability release
of MySQL Connector/NET to add support for the new X DevAPI, which
enables application developers to write code that combines the
strengths of the relational and document models using a modern,
NoSQL-like syntax that does not assume previous experience writing 
traditional SQL.


To learn more about how to write applications using the X DevAPI, see
http://dev.mysql.com/doc/x-devapi-userguide/en/index.html. For more
information about how the X DevAPI is implemented in Connector/NET, see
http://dev.mysql.com/doc/dev/connector-net.NuGet packages provide 
functionality at a project level. To get the

full set of features available in Connector/NET such as availability
in the GAC, integration with Visual Studio's Entity Framework Designer
and integration with MySQL for Visual Studio, installation through
the MySQL Installer or the stand-alone MSI is required.

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

To download MySQL Connector/NET 8.0.16, see
http://dev.mysql.com/downloads/connector/net/

Installation instructions can be found at
https://dev.mysql.com/doc/connector-net/en/connector-net-installation.html


Changes in MySQL Connector/NET 8.0.16 ( 2019-04-25, General Availability )


 * Functionality Added or Changed

 * Bugs Fixed

Functionality Added or Changed


 * Document Store: Support was added for the -> operator to
   be used with JSON document paths in relational
   statements. For example:
table.Select().Where("additionalinfo->$.hobbies = 'Reading'");

   (Bug #29347028)

 * Document Store: The performance for statements that are
   executed repeatedly (two or more times) is improved by
   using server-side prepared statements for the second and
   subsequent executions. This happens internally;
   applications need take no action and API behavior should
   be the same as previously. For statements that change,
   repreparation occurs as needed. Providing different data
   values or different OFFSET or LIMIT clause values does
   not count as a change. Instead, the new values are passed
   to a new invocation of the previously prepared statement.

 * Document Store: Connector/NET now supports the ability to
   send connection attributes (key-value pairs that
   application programs can pass to the server at connect
   time). Connector/NET defines a default set of attributes,
   which can be disabled or enabled. In addition,
   applications can specify attributes to be passed together
   with the default attributes. The default behavior is to
   send the default attribute set.
   The aggregate size of connection attribute data sent by a
   client is limited by the value of the
   performance_schema_session_connect_attrs_size server
   variable. The total size of the data package should be
   less than the value of the server variable. For X DevAPI
   applications, specify connection attributes as a
   connection-attributes parameter in a connection string.
   For usage information, see Options for X Protocol Only
   
(http://dev.mysql.com/doc/connector-net/en/connector-net-8-0-connection-options.html#connector-net-8-0-connection-options-xprotocol).
   For general information about connection attributes, see
   Performance Schema Connection Attribute Tables
   
(http://dev.mysql.com/doc/refman/8.0/en/performance-schema-connection-attribute-tables.html).

 * Document Store: Connector/NET now has improved support
   for resetting sessions in connection pools. Returning a
   session to the pool drops session-related objects such as
   temporary tables, session variables, and transactions,
   but the connection remains open and authenticated so that
   reauthentication is not required when the session is
   reused.

 * Connector/NET applications now can use certificates in
   PEM format to validate SSL connections in addition to the
   native PFX format (see Tutorial: Using SSL with Connector/NET
   
(http://dev.mysql.com/doc/connector-net/en/connector-net-tutorials-ssl.html)).
   PEM support applies to both classic MySQL protocol
   and X Protocol connections.

Bugs Fixed


 * Document Store: All methods able to execute a statement
   were unable to execute the same statement a second time.
   Now, the values and binding parameters remain available
   after the method is executed and string parameters are no
   longer converted to numbers. Both changes enable a
   follow-on execution to reuse the previous parameters.
   (Bug #2

MySQL Community Server 5.7.26 has been released

[Surabhi Bhat]

Dear MySQL users,

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Enjoy!


==

Changes in MySQL 5.7.26 (2019-04-25, General Availability)

   Beginning with MySQL 5.7.26, Oracle no longer provides binaries for
   SUSE 11.

 * Security Notes

 * Bugs Fixed

Security Notes


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

Bugs Fixed


 * Important Note: The libevent library included with the
   MySQL Server was upgraded to version 2.1.8. (Bug #28207237, Bug
   #29041505, Bug #29055011)

 * InnoDB: Optimized InnoDB internal temporary tables did
   not support in-place UPDATE operations, which caused the number
   of delete-marked records to increase continuously.  The large
   number of delete-marked records could cause longer than expected
   query execution times. (Bug #29207450)

 * InnoDB: The base column information for a generated
   column was not stored. (Bug #29021730)

 * InnoDB: Assertion code related to the innodb_flush_method
   O_DIRECT_NO_FSYNC setting was no longer valid due to a recent
   modification to that setting. Assertion code was revised. (Bug
   #29007731) References: See also: Bug #27309336.

 * InnoDB: Memory leaks discovered in the innochecksum
   utility were removed. (Bug #28917614, Bug #93164)

 * InnoDB: A DDL operation that followed a failed attempt to
   create an index on a virtual column resulted in an assertion
   failure. (Bug #28825718)

 * InnoDB: A Linux AIO handler function failed to check if
   completed I/O events succeeded. Thanks to Wei Zhao for the
   contribution. (Bug #27850600, Bug #90402)

 * InnoDB: A function called by a CREATE TABLE thread
   attempted to access a table object after it was freed by a
   background thread.  Thanks to Yan Huang for the patch. (Bug
   #27373959, Bug #89126)

 * InnoDB: Two sessions concurrently executing an INSERT ...
   ON DUPLICATE KEY UPDATE operation generated a deadlock.  During
   partial rollback of a tuple, another session could update it. The
   fix for this bug reverts fixes for Bug #11758237, Bug #17604730,
   and Bug #20040791. (Bug #25966845)

 * InnoDB: When the method used to access a joined table was
   const, InnoDB attempted to unlock the matching row multiple
   times. (Bug #20939184)

 * InnoDB: The INDEX_LENGTH value in
   INFORMATION_SCHEMA.TABLES was not updated when adding an index.
   (Bug #19811005)

 * Partitioning: An AUTO_INCREMENT key added to a
   partitioned table by an ALTER TABLE statement using
   ALGORITHM=INPLACE restarted on each partition. (Bug #92241, Bug
   #28573894)

 * Replication: If the WAIT_FOR_EXECUTED_GTID_SET() function
   was used with a timeout value including a fractional part (for
   example, 1.5), an err

MySQL Workbench 8.0.16 has been released

[Balasubramanian Kandasamy]

Dear MySQL users,

The MySQL developer tools team announces 8.0.16 as our general available 
(GA) for

MySQL Workbench 8.0.

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



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

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

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

Enjoy!


Changes in MySQL Workbench 8.0.16 (2019-04-25, General
Availability)


 * Functionality Added or Changed

 * Bugs Fixed

Functionality Added or Changed


 * The script editor now highlights matching pairs of
   parentheses when one of the pair is selected. (Bug
   #27473434, Bug #73167)

 * Microsoft Visual Studio support was upgraded from Visual
   Studio 15 to Visual Studio 17.

 * Previously, the output from running schema validation
   plugins on a MySQL model was distributed to different
   areas of MySQL Workbench, making portions of the
   information easy to miss. The same functionality now is
   shown in a single location and reorganized to provide
   informational, warning, and error messages by category. A
   new Validate tab also provides a simple way to reselect
   and rerun validation tests from the output area in the
   right side panel (see Schema Validation Plugins
(http://dev.mysql.com/doc/workbench/en/wb-validation-plugins.html)).

Bugs Fixed


 * MySQL Workbench stopped working when an existing table
   with an expression in a column of type BINARY was
   selected for editing. (Bug #29449200)

 * MySQL Enterprise Firewall could not be installed from the
   Enterprise Edition of MySQL Workbench. (Bug #29359957,
   Bug #94335)

 * An incorrect-integer-value error resulted when the Table
   Data Import Wizard attempted to import CSV data to a
   valid database table. (Bug #29348922)

 * MySQL 5.7 tables exported to MySQL 8.0.14 or 8.0.15
   produced the following error: Unknown table
   'COLUMN_STATISTICS' in information_schema.
   (Bug#29344344, Bug #94294)

 * A successful connection made with SSH tunneling from a
   Linux host produced an ongoing loop of errors if an
   attempt was made to close the connection. (Bug #29342871,
   Bug #94212)

 * The LATERAL keyword now conforms with the SQL editor
   convention to highlight and indent the words considered
   keywords by MySQL. (Bug #29251184, Bug #94012)

 * An exception was raised when a valid path to the MySQL
   Enterprise Backup 8.0.14 or 8.0.15 executable was
   provided in the prerequisite settings. To back up MySQL
   8.0.14 or 8.0.15 data, upgrade to MySQL Workbench 8.0.16
   or use MySQL Enterprise Backup 8.0.14 or 8.0.15 directly
   (see Introduction to MySQL Enterprise Backup
(http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/intro.html)).
   (Bug #29246551)

 * An error in the generated mysql_rdbms_info.xml file
   caused MySQL Workbench to stop working. (Bug #29237703,
   Bug #93987)

 * The size of the Table Data Import Wizard window changed
   unexpectedly between steps, causing the navigation
   buttons to vanish from visible range unless the window
   was expanded to include them. (Bug #29200662, Bug #93869)

 * With the GNOME desktop theme set to Adwaita (default) or
   Adwaita-dark, text selected within the SQL editor was
   invisible. (Bug #29184506, Bug #93847)

 * The Command-V keyboard shortcut on macOS returned an
   error indicating that a paste-row operation was
   attempted, rather than the single-value paste used to
   edit a field within the result grid following a
   successful query. (Bug #29137004, Bug #93710)

 * Executing a function or stored procedure caused an
   unexpected program shutdown on Linux hosts.
   (Bug#29134435)

 * The SQL beautifier feature produced no change when it was
   executed within the Triggers tab of the table editor.
   (Bug #29133592)

 * The table inspector did not start properly and produced
   an error on macOS when it was selected from the context
   menu of a valid table within the Schema tab.
   (Bug#29128333)

 * An exception was generated when the results of a query
   was toggled between visual explain and tubular explain
   formats within the Execution Plan tab. (Bug #29121364)

 * A user account that was deleted properly from Users and
   Privileges remained visible until the Administration tab
   closed and reopened. (Bug #29061678)

 * New tables added to the canvas of an EER diagram
   displayed the table name bar only, without columns, when
   the table tool (Place a New Table) from the vertical
 

MySQL Connector/Python 8.0.16 has been released

[Balasubramanian Kandasamy]

Dear MySQL users,

MySQL Connector/Python 8.0.16 is the latest GA release version of the
MySQL Connector Python 8.0 series. The X DevAPI enables application
developers to write code that combines the strengths of the relational
and document models using a modern, NoSQL-like syntax that does not
assume previous experience writing traditional SQL.

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

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

To download MySQL Connector/Python 8.0.16, see the "General Available
(GA) releases" tab at http://dev.mysql.com/downloads/connector/python/

Enjoy!

Changes in MySQL Connector/Python 8.0.16 (2019-04-25, General
Availability)


 * Functionality Added or Changed

 * Bugs Fixed

Functionality Added or Changed


 * Two informative text files were added: INFO_BIN contains
   information about the build environment used to produce
   the distribution, and INFO_SRC provides information about
   the product version and the source repository from which
   the distribution was produced. (Bug #29454706)

 * Django 1.11 is now the minimum supported Django version.

 * For X DevAPI applications, Connector/Python now supports
   the ability to send connection attributes (key-value
   pairs that application programs can pass to the server at
   connect time). Connector/Python defines a default set of
   attributes, which can be disabled or enabled. In
   addition, applications can specify attributes to be
   passed in addition to the default attributes. The default
   behavior is to send the default attribute set.
   For X DevAPI applications, specify connection attributes
   as a connection-attributes parameter in a connection
   string, or setting connection-attributes as a dictionary
   inside the connection settings parameter under the
   connection-attributes key. Both the mysqlx.get_session()
   and mysqlx.get_client() methods can receive this
   information.
   The connection-attributes parameter value must be empty
   (the same as specifying true), a Boolean value (true or
   false to enable or disable the default attribute set), or
   a list or zero or more key=value specifiers separated by
   commas (to be sent in addition to the default attribute
   set). Within a list, a missing key value evaluates as an
   empty string. An example connection string:
mysqlx://user:password@host:33060/schema?connection-attributes=[foo=bar,baz=qux,quux]

   Application-defined attribute names cannot begin with _
   because such names are reserved for internal attributes.
   If connection attributes are not specified in a valid
   way, an error occurs and the connection attempt fails.
   For general information about connection attributes, see
   Performance Schema Connection Attribute Tables
(http://dev.mysql.com/doc/refman/8.0/en/performance-schema-connection-attribute-tables.html).

 * Connector/Python now has improved support for resetting
   sessions in connection pools. Returning a session to the
   pool drops session-related objects such as temporary
   tables, session variables, and transactions, but the
   connection remains open and authenticated so that
   reauthentication is not required when the session is
   reused.

 * Protobuf was updated to Protobuf 3.6.1.

 * For X DevAPI, performance for statements that are
   executed repeatedly (two or more times) is improved by
   using server-side prepared statements for the second and
   subsequent executions. This happens internally;
   applications need take no action and API behavior should
   be the same as previously. For statements that change,
   repreparation occurs as needed. Providing different data
   values or different offset() or limit() values does not
   count as a change. Instead, the new values are passed to
   a new invocation of the previously prepared statement.

Bugs Fixed


 * Added a "username" alias for the "user" connection
   argument. Thanks to Matthew Woods for the patch. (Bug
   #29324966, Bug #94248)

 * Solaris 11 package files had the expected owner/group set
   as pb2user/common instead of root/bin. (Bug #29278489)

 * CRUD operations would not allow referencing a renamed
   column (AS SomeLabel) from the fetched result. (Bug
   #29001628)

 * Fixed a memory corruption issue that caused an unexpected
   halt when fetching

MySQL Enterprise Backup 8.0.16 has been released

[Bjorn Munch]

MySQL Enterprise Backup 8.0.16, a new version of the online MySQL backup
tool, is now available for download from the My Oracle Support (MOS) website
as our latest GA release. This release will be available on eDelivery (OSDC)
after the next upload cycle. MySQL Enterprise Backup is a commercial
extension to the MySQL family of products.
 
MySQL Enterprise Backup 8.0.16 supports only the MySQL Server 8.0.16.
For earlier versions of MySQL 8.0, use the MySQL Enterprise Backup
version with the same version number as the server. For MySQL server
5.7, please use MySQL Enterprise Backup 4.1, and for MySQL Server 5.6
and 5.5, please use MySQL Enterprise Backup 3.12.
 
A brief summary of the changes in MySQL Enterprise Backup (MEB)
version 8.0.16 is given below.

--

Changes in MySQL Enterprise Backup 8.0.16 (2019-04-25, GA)

 * Functionality Added or Changed

 * Bugs Fixed

Functionality Added or Changed


 * mysqlbackup now supports encrypted InnoDB undo logs
(http://dev.mysql.com/doc/refman/8.0/en/innodb-tablespace-encryption.html#innodb-tablespace-encryption-undo-log).
   The encrypted undo tablespaces are handled the same way
   as the encrypted tablespaces for InnoDB tables. See
   Working with Encrypted InnoDB Tablespaces
(http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/meb-encrypted-innodb.html)
   for details.

 * Near the end of the backup process, instead of locking
   the whole server instance for a brief period of time,
   mysqlbackup now applies these locks consecutively:

 1. A backup lock
(http://dev.mysql.com/doc/refman/8.0/en/lock-instance-for-backup.html)
on the server instance, which
blocks DDLs (except those on user-created temporary
tables), but not DMLs on InnoDB tables.

 2. A FLUSH TABLES tbl_name [, tbl_name] ... WITH READ
LOCK
(http://dev.mysql.com/doc/refman/8.0/en/flush.html#flush-tables-with-read-lock-with-list)
operation on all non-InnoDB tables, for copying the
relevant ones among them into the backup. This step is
skipped if no user-created non-InnoDB tables exist.

 3. A brief blocking of logging activities on the
server, for collecting logging-related information.
   See The Backup Process
(https://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/meb-backup-process)
   for details. The removal of the lock
   on the whole server instance reduces disruption to the
   database service by the backup operation.
   Important
   The change requires that the BACKUP_ADMIN
(http://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_backup-admin)
   and SELECT
(http://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_select)
   privileges on all tables be granted
   to the user by which mysqlbackup connects to the server
   (the BACKUP_ADMIN
(http://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_backup-admin)
   privilege is automatically granted to users with the RELOAD
(http://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_reload)
   privilege when an in-place upgrade to MySQL Server 8.0 from an
   earlier version is performed).

 * mysqlbackup now supports dynamic changes to undo
   tablespaces
   (http://dev.mysql.com/doc/refman/8.0/en/innodb-undo-tablespaces.html)
   on the server being backed up. During a
   restore, the default undo tablespaces, as well as any
   non-default undo tablespaces resided in the backed-up
   server's data directory, are restored to the location
   pointed to by the mysqlbackup option
   --innodb_undo_directory. Non-default, external undo
   tablespaces are restored to the locations they were found
   on the backed-up server. See undo log files
(http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/meb-files-backed-up-summary.html#meb_file_undo-log-files)
   for details.

 * In addition to the requirement that the target data
   directory for a restore specified by the --datadir option
   must be non-existent or empty, mysqlbackup now enforces
   the same rule for the --innodb_data_home_dir,
   --innodb_log_group_home_dir, and --innodb_undo_directory
   options (the --force option cannot be used to override
   the requirement on the three options).

Bugs Fixed


 * Zip packages of mysqlbackup contained duplicate files,
   which have now been removed. (Bug #29497272, Bug #94683)

 * mysqlbackup might quit unexpectedly if it lost its
   connection to the server at the middle of a backup
   operation. With this fix, mysqlbackup exits gracefully in
   the situation after throwing the appropriate errors. (Bug
   #29376006)

 * Restore of an incremental backup failed if, on the
   server, some binary log files had been purged in between
   the times the incremental backup and i

MySQL Router 8.0.16 for MySQL Server 8.0 and 5.7 has been released

[Bjorn Munch]

Dear MySQL users,

MySQL Router 8.0.16 is a new release for MySQL Router 8.0 series.

MySQL Router 8.0 is highly recommended for use with MySQL Server 8.0 and 5.7.
Please upgrade to MySQL Router 8.0.16.

The MySQL Router is a new building block for high availability solutions
based on MySQL InnoDB clusters.

By taking advantage of the new Group Replication technology, and
combined with the MySQL Shell, InnoDB clusters provide an integrated
solution for high availability and scalability for InnoDB based MySQL
databases, that does not require advanced MySQL expertise.

The deployment of applications with high availability requirements is
greatly simplified by MySQL Router. MySQL client connections are
transparently routed to online members of a InnoDB cluster, with MySQL
server outages and cluster reconfigurations being automatically handled
by the Router.

To download MySQL Router 8.0.16, see the "Generally Available (GA)
Releases" tab at http://dev.mysql.com/downloads/router. Package
binaries are available for several platforms and also as a source code
download.

Documentation for MySQL Router can be found at
http://dev.mysql.com/doc/mysql-router/en/

Enjoy!

Changes in MySQL Router 8.0.16 (2019-04-25, General Availability)

 * Functionality Added or Changed

 * Bugs Fixed

Functionality Added or Changed


 * Before, bootstrapping would generate Read-Write (PRIMARY)
   and Read-Only (SECONDARY) configuration routing sections
   for multi-master mode, but only Read-Write sections for
   single-master mode. Now, both Read-Write and Read-Only
   sections are always generated.

 * Bootstrapping now sets new routing_strategy values in the
   generated configuration file. Read-Write (PRIMARY)
   sections set routing_strategy to first-available; and
   Read-Only (SECONDARY) sections set it to
   round-robin-with-fallback. Previously, they were both set
   to round-robin.
   The default behavior (for example, if routing_strategy is
   not defined in mysqlrouter.conf) did not change and is
   still round-robin.

 * Added ability to integrate external log-rotation
   applications by reopening the file-based logfile on
   SIGHUP. On Linux, this allows integrating the system-wide
   logrotate utility.

 * On Windows, added the ability to report events to the
   Windows Application Events log.

 * Added a new sinks configuration file option to define one
   or more logger sinks. For example, all level=debug
   messages can be sent to a file while only level=error are
   sent to an eventlog.
   The supported sinks are: consolelog, filelog, eventlog on
   Windows, and syslog on Unix-based systems.

 * An HTTP interface was added based on libevent's HTTP
   library. It's configured using a new [http_server]
   configuration section that contains the following
   options:

  + port: The TCP port listening for HTTP requests; it
defaults to 8011.

  + bind_address: IPv4 address bound to the port; it
defaults to 0.0.0.0.

  + static_folder: Base directory for static file
requests; it's empty by default. An empty value
means no static files are served.

  + require_realm: Name of the [http_auth_realm]
instance.

  + ssl: The value 1 enables SSL, and 0 disables it. TLS
clients supporting TLSv1.2 or later are required.

  + ssl_cert: File name of the certificate and its chain
certifications in PEM format; required if ssl=1.

  + ssl_key: File name of the key in PEM format;
required if ssl=1.

  + ssl_cipher: The cipher-spec (see openssl's 'ciphers'
list). Defaults to a comma-separated list of all
approved ciphers. Unknown ciphers are silently
ignored. Fails if list of ciphers is empty and
ssl=1.

  + ssl_dh_param: Read the DH parameter from this file
in PEM format. Uses the dh-param from RFC 5114 by
default if ssl=1.

 * A mysqlrouter_passwd tool was added to manage password's
   for the HTTP server component.
   Two new HTTP configuration sections were added;
   [http_auth_backend] and [http_auth_realm]. Both are
   optional, and multiple definitions are allowed. There
   options are:
   [http_auth_backend]

  + backend: Name of the backend implementation; it
defaults to file.

  + filename: Name of the backend storage file, relative
to the data_folder directory.
   [http_auth_realm]

  + backend: Name of the [http_auth_backend] section.

  + method: The HTTP authentication method; defaults to
basic.

  + require: Requires that the user validates with the
authentication backend; defaults to valid-user,
which enables this check.

   

MySQL Community Server 8.0.16 has been released [part 2]

[Bjorn Munch]

[This is part 2 of the announcement]

Bugs Fixed, continued

 * InnoDB: Write-ahead did not work as expected due to an
   incorrectly initialized variable.
   Thanks to Yuhui Wang for the contribution. (Bug
   #29028838, Bug #93442)

 * InnoDB: The base column information for a generated
   column was not stored. (Bug #29021730)

 * InnoDB: An implicit lock check on secondary indexes
   needlessly compared columns using collation rules. (Bug
   #29010725)

 * InnoDB: Assertion code related to the innodb_flush_method
   O_DIRECT_NO_FSYNC setting was no longer valid due to a
   recent modification to that setting. Assertion code was
   revised. (Bug #29007731)
   References: See also: Bug #27309336.

 * InnoDB: When starting the server with undo log encryption
   enabled, the master key for newly created undo
   tablespaces was generated without a server UUID. Undo
   tablespaces should use the DefaultMasterKey if the server
   UUID is not yet generated. (Bug #29006275)

 * InnoDB: Data dictionary code did not check for a returned
   data dictionary object, which could potentially cause the
   server to exit due to a null pointer access. (Bug
   #28977444, Bug #93362)

 * InnoDB: An undo tablespace file was left behind by a
   failed CREATE UNDO TABLESPACE operation. (Bug #28966457)

 * InnoDB: A CREATE UNDO TABLESPACE statement failed on
   Windows due to an invalid character in the file name. The
   failure resulted in a hang condition due to a missing
   OS_FILE_ON_ERROR_NO_EXIT attribute in the call that
   creates the undo tablespace file. (Bug #28955676)

 * InnoDB: Modifying the value of the
   innodb_undo_log_encrypt variable was not a blocking
   operation, which could lead to the modification being
   reverted by a background thread after the operation
   appeared to have been completed successfully. (Bug
   #28952870)

 * InnoDB: An invalid debug assertion was removed from the
   temptable::Handler::primary_key_is_clustered function.
   (Bug #28949332)

 * InnoDB: An ALTER TABLE ... EXCHANGE PARTITION operation
   did not properly update column table_id values in the
   data dictionary. (Bug #28927005)

 * InnoDB: Memory leaks discovered in the innochecksum
   utility were removed. (Bug #28917614, Bug #93164)

 * InnoDB: A DDL operation that followed a failed attempt to
   create an index on a virtual column resulted in an
   assertion failure. (Bug #28825718)

 * InnoDB: A performance regression was observed for partial
   update operations on compressed BLOBs less than or equal
   to 128KB in size. (Bug #28784301)

 * InnoDB: Running aggregated queries raised Valgrind
   warnings. (Bug #28711717)

 * InnoDB: A CHECK TABLE operation raised an assertion
   failure. A pointer to a local call stack variable was not
   set back to null before a function exit. (Bug #28525110)

 * InnoDB: DDL log functions were modified to handle
   ER_TOO_MANY_CONCURRENT_TRXS errors. (Bug #28523127, Bug
   #92071)

 * InnoDB: The purge thread failed to free LOB data pages.
   (Bug #28510599)

 * InnoDB: Some DDL log table transactions were not rolled
   back prior to DDL log recovery. (Bug #28494969)

 * InnoDB: A function invoked during SHOW CREATE TRIGGER
   processing that retrieves the table name did not perform
   the expected lowercase conversion. (Bug #28351038)

 * InnoDB: The INFORMATION_SCHEMA.INNODB_FOREIGN TYPE column
   reported incorrect values. (Bug #28315651, Bug #91577)

 * InnoDB: A Linux AIO handler function failed to check if
   completed I/O events succeeded. Thanks to Wei Zhao for
   the contribution. (Bug #27850600, Bug #90402)

 * InnoDB: An assertion failure was raised in a check that
   determines if a transaction holds an implicit lock on a
   secondary index. A transaction that does not change the
   columns of a secondary index that includes virtual
   columns could be incorrectly determined to hold an
   implicit lock. (Bug #27491839)

 * InnoDB: A function called by a CREATE TABLE thread
   attempted to access a table object after it was freed by
   a background thread.
   Thanks to Yan Huang for the patch. (Bug #27373959, Bug
   #89126)

 * InnoDB: Two sessions concurrently executing an INSERT ...
   ON DUPLICATE KEY UPDATE operation generated a deadlock.
   During partial rollback of a tuple, another session could
   update it. The fix for this bug reverts fixes for Bug
   #11758237, Bug #17604730, and Bug #20040791. (Bug
   #25966845)

 * InnoDB: When the method used to access a joined table was
   const, InnoDB attempted to unlock the matching row
   multiple times. (Bug #20939184)

 * InnoDB: The INDEX_LENGTH value in
   

MySQL Community Server 8.0.16 has been released [part 1]

[Bjorn Munch]

[Due to size limitation, this announcement is split in two. This is part 1] 

Dear MySQL users,

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

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

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

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

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

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

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

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

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

Windows packages are available via the Installer for Windows:

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

along with .ZIP (no-install) packages for more advanced needs. 

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

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

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

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

The following link lists the changes in the MySQL 8.0 since
the release of MySQL 8.0.15. It may also be viewed
online at

  http://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-16.html

Enjoy!

==
Changes in MySQL 8.0.16 (2019-04-25, General Availability)


 * Account Management Notes

 * C API Notes

 * Character Set Support

 * Compilation Notes

 * Configuration Notes

 * Deprecation and Removal Notes

 * Installation Notes

 * Packaging Notes

 * Parser Notes

 * Performance Schema Notes

 * Plugin Notes

 * Security Notes

 * Spatial Data Support

 * SQL Syntax Notes

 * Test Suite Notes

 * X Plugin Notes

 * Functionality Added or Changed

 * Bugs Fixed

Account Management Notes


 * Previously, users who had the DROP ROLE privilege could
   use the DROP ROLE statement to drop locked or unlocked
   accounts. Now, users who have the DROP ROLE privilege can
   use DROP ROLE only to drop accounts that are locked
   (unlocked accounts are presumably user accounts used to
   log in to the server and not just as roles). Users who
   have the CREATE USER privilege can use DROP ROLE to drop
   accounts that are locked or unlocked. (Bug #28953158, Bug
   #93263)

 * Several changes have been made to MySQL
   account-management capabilities:

  + MySQL now incorporates the concept of user account
categories, with system and regular users
distinguished according to whether they have the new
SYSTEM_USER privilege:
   o System users are users who possess the
 SYSTEM_USER privilege. A system user can
 perform operations on both system and regular
 accounts.
   o Regular users are ordinary users who do not
 possess the SYSTEM_USER privilege. A regular
 user can perform operations on regular
 accounts, but not system accounts.
If a user has the appropriate privileges to perform
a given operation on regular accounts, SYSTEM_USER
enables the user to also perform the operation on
system accounts. SYSTEM_USER does not imply any
other privilege, so the ability to perform a given
account operation remains predicated on possession
of any other required privileges. For example, if a
user can grant the SELECT and UPDATE privileges to
regular accounts, then with SYSTEM_USER the user can
also grant SELECT and UPDATE to system accounts.
The distinction between system and regular accounts
enables better control over certain account
administration issues by protecting accounts that
have the SYSTEM_USER privilege from accounts that do
not have the privilege. For example, the CREATE USER
privilege enables not only creation of new accounts,
but modification and removal of existing accounts.
Without the system user concept, a user who has the
CREATE USER privilege can modify or drop any
existing account, including the root account. The
concept of system user enables restricting
modifications to the root account (itself a system
account) so