MySQL Connector/C++ 8.0.14 has been released
Dear MySQL users, MySQL Connector/C++ 8.0.14 is a new release version of the MySQL Connector/C++ 8.0 series. Connector/C++ 8.0 can be used to access MySQL implementing Document Store or in a traditional way, using SQL queries. It allows writing both C++ and plain C applications using X DevAPI and X DevAPI for C. It also supports the legacy API of Connector/C++ 1.1 based on JDBC4. To learn more about how to write applications using X DevAPI, see "X DevAPI User Guide" at https://dev.mysql.com/doc/x-devapi-userguide/en/ See also "X DevAPI Reference" at https://dev.mysql.com/doc/dev/connector-cpp/devapi_ref.html and "X DevAPI for C Reference" at https://dev.mysql.com/doc/dev/connector-cpp/xapi_ref.html For generic information on using Connector/C++ 8.0, see https://dev.mysql.com/doc/dev/connector-cpp/ 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/C++ 8.0.14, see the "Generally Available (GA) Releases" tab at https://dev.mysql.com/downloads/connector/cpp/ == Changes in MySQL Connector/C++ 8.0.14 (2019-01-21) * Configuration Notes * Packaging Notes * X DevAPI Notes Configuration Notes * These CMake options have been added to enable more fine-grained specification of installation directories. All are relative to CMAKE_INSTALL_PREFIX: + CMAKE_INSTALL_LIBDIR: Library installation directory. + CMAKE_INSTALL_INCLUDEDIR: Header file installation directory. + CMAKE_INSTALL_DOCDIR: Documentation installation directory. (Bug #28045358) Packaging Notes * Previously, MySQL Connector/C++ binary distributions included a BUILDINFO.txt file that contained information about the build environment used to produce the distribution. Binary distributions now include a file named INFO_BIN that provides similar information, and an INFO_SRC file that provides information about the product version and the source repository from which the distribution was produced. Source distributions include the INFO_SRC file only. * MySQL Connector/C++ now is compatible with MSVC 2017, while retaining compatibility with MSVC 2015: + Previously, Connector/C++ binary distributions were compatible with projects built using MSVC 2015. Binary distributions now are compatible with projects built using MSVC 2017 or 2015. DLLs have a -vs14 suffix in their names to reflect that they are compatible with MSVC 2015, but can also be used in MSVC 2017 projects. + Previously, Connector/C++ source distributions could be built using MSVC 2015. Source distributions now can be built using MSVC 2017 or 2015. + Previously, the MSI installer accepted the Visual C++ Redistributable for Visual Studio 2015. The MSI installer now accepts the Visual C++ Redistributable for Visual Studio 2017 or 2015. * Installers for Connector/C++ are now available as Debian packages. See Installing Connector/C++ from a Binary Distribution (http://dev.mysql.com/doc/connector-cpp/8.0/en/connector-cpp-installation-binary.html). X DevAPI Notes * Connector/C++ now provides collection counting methods for applications that use X DevAPI for C: + mysqlx_collection_count(): The number of documents in a collection without filtering. mysqlx_collection_t *c1 = mysqlx_get_collection(schema, "c1", 1); ulong64_t documents; mysqlx_collection_count(c1, ); + mysqlx_table_count(): The number of rows in a table without filtering. mysqlx_table_t *t1 = mysqlx_get_table(schema, "t1", 1); ulong64_t rows; mysqlx_table_count(t1, ); + mysqlx_get_count(): The number of remaining cached rows held at the moment. After a row is consumed by a fetch function, the number of cached rows decreases. mysqlx_stmt_t *stmt = mysqlx_sql_new(session, query, strlen(query)); mysqlx_result_t *res = mysqlx_execute(stmt); ulong64_t row_count; mysqlx_get_count(res, _count); mysqlx_get_count() is similar in all respects to mysqlx_store_result() except that the behavior differs after fetching rows when reaching zero number of rows in the cache: o mysqlx_get_count() returns zero through the parameter and finishes with RESULT_OK. o mysqlx_store_result() does not return anything through the parameter (which
MySQL Shell 8.0.14 for MySQL Server 8.0 and 5.7 has been released
Dear MySQL users, MySQL Shell 8.0.14 is a maintenance release of MySQL Shell 8.0 Series (a component of the MySQL Server). The MySQL Shell is provided under Oracle's dual-license. MySQL Shell 8.0 is highly recommended for use with MySQL Server 8.0 and 5.7. Please upgrade to MySQL Shell 8.0.14. MySQL Shell is an interactive JavaScript, Python and SQL console interface, supporting development and administration for the MySQL Server. It provides APIs implemented in JavaScript and Python that enable you to work with MySQL InnoDB cluster and use MySQL as a document store. The AdminAPI enables you to work with MySQL InnoDB cluster, providing an integrated solution for high availability and scalability using InnoDB based MySQL databases, without requiring advanced MySQL expertise. For more information about how to configure and work with MySQL InnoDB cluster see https://dev.mysql.com/doc/refman/en/mysql-innodb-cluster-userguide.html The X DevAPI enables you to create "schema-less" JSON document collections and perform Create, Update, Read, Delete (CRUD) operations on those collections from your favorite scripting language. For more information about how to use MySQL Shell and the MySQL Document Store support see https://dev.mysql.com/doc/refman/en/document-store.html For more information about the X DevAPI see https://dev.mysql.com/doc/x-devapi-userguide/en/ If you want to write applications that use the the CRUD based X DevAPI you can also use the latest MySQL Connectors for your language of choice. For more information about Connectors see https://dev.mysql.com/doc/index-connectors.html. For more information on the APIs provided with MySQL Shell see https://dev.mysql.com/doc/dev/mysqlsh-api-javascript/8.0/ and https://dev.mysql.com/doc/dev/mysqlsh-api-python/8.0/ Using MySQL Shell's SQL mode you can communicate with servers using the legacy MySQL protocol. Additionally, MySQL Shell provides partial compatibility with the mysql client by supporting many of the same command line options. For full documentation on MySQL Server, MySQL Shell and related topics, see https://dev.mysql.com/doc/mysql-shell/8.0/en/ For more information about how to download MySQL Shell 8.0.14, see the "Generally Available (GA) Releases" tab at http://dev.mysql.com/downloads/shell/ We welcome and appreciate your feedback and bug reports, see http://bugs.mysql.com/ Enjoy and thanks for the support! == Changes in MySQL Shell 8.0.14 (2019-01-21) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * When started from the command line, MySQL Shell prints information about the product, information about the session (such as the default schema and connection ID), warning messages, and any errors that are returned during startup and connection. You can now suppress printing of information that you do not need by using the --quiet-start[=1|2] mysqlsh command-line option. With a value of 1 (the default when the option is specified), information about the MySQL Shell product is not printed, but session information, warnings, and errors are printed. With a value of 2, only errors are printed. As part of this work, the printed information was tidied up so that the information about the MySQL Shell product is printed before the information about the session. Also, the handling of error printing was normalized to send diagnostic data to stderr, and errors to stdout. (Bug #28833718, Bug #28855291) * MySQL Shell connections using classic MySQL protocol now support compression for information sent between the client and the server. You can specify compression when you start MySQL Shell and connect using command line options, or in a URI string or a key-value pair when you create a session using other interfaces. You can also use the MySQL Shell configuration option defaultCompress to enable compression for every global session. For MySQL Shell connections that use Unix socket files, the --socket command line option can now be specified with no argument to connect using the default Unix socket file for the protocol. (Bug #28730149) * The Cluster.status() operation has been extended to enable you to display information about the underlying Group Replication group used by the cluster. Now you can retrieve information from all members of a cluster without having to connect to each member individually. To see information about the groupName and memberId; and general statistics about the number of transactions checked, proposed, and rejected by members issue: Cluster.status(extended:true) To see information about recovery and regular transaction I/O,
MySQL Community Server 5.7.25 has been released
Dear MySQL users, MySQL Server 5.7.25, a new version of the popular Open Source Database Management System, has been released. MySQL 5.7.25 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.25 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.25 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.25 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.25 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.24. It may also be viewed online at http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-25.html Enjoy! Changes in MySQL 5.7.25 (2019-01-21, General Availability) * Deprecation and Removal Notes * Pluggable Authentication * Security Notes * Functionality Added or Changed * Bugs Fixed Deprecation and Removal Notes * The resolveip and resolve_stack_dump utilities are now deprecated and will be removed in MySQL 8.0. nslookup, host, or dig can be used instead of resolveip. Stack traces from official MySQL builds are always symbolized, so there is no need to use resolve_stack_dump. Pluggable Authentication * If the LDAP port number is configured as 636 or 3269, the plugin now uses LDAPS (LDAP over SSL) instead of LDAP. The port number is settable using the authentication_ldap_sasl_server_port or authentication_ldap_simple_server_port system variable. (LDAPS differs from startTLS.) (Bug #28743563) * Previously, for LDAP authentication with proxying, LDAP authentication plugins used the first group name returned by the LDAP server as the MySQL proxy user account name. The authentication string for a MySQL account now can specify a list of groups to match, in preference order, and can optionally map the matching group name to a specified MySQL proxy user name. See LDAP Pluggable Authentication (http://dev.mysql.com/doc/refman/5.7/en/ldap-pluggable-authentication.html). Security Notes * The linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.2q. 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) Functionality Added or Changed * Microsoft Windows: The access control granted to clients on the named pipe created by the MySQL server now is set to the minimum necessary for successful communication on Windows. Newer MySQL client software can open named pipe connections without any additional configuration. If older client software cannot be upgraded immediately, the new named_pipe_full_access_group server system variable can be used to give a Windows group the necessary permissions to open a named pipe connection. Membership in the full-access group should be restricted and temporary. Bugs Fixed * InnoDB: A dangling pointer caused a memory leak. (Bug #28693568) * InnoDB: An ON DELETE CASCADE operation on table with a foreign key constraint and an indexed virtual column caused the server to exit. (Bug #28470805) * InnoDB: An incorrectly written DML log involving a virtual column value raised an assertion. (Bug #28448853) * InnoDB: Using the O_DIRECT_NO_FSYNC innodb_flush_method setting could cause the system to hang due to file system metadata becoming unsynchronized. To prevent this issue from occurring in O_DIRECT_NO_FSYNC mode, InnoDB now calls fsync() after creating a new file, after increasing file size, and after closing a file. The fsync() system call is
MySQL Workbench 8.0.14 has been released
Dear MySQL users, The MySQL developer tools team announces 8.0.14 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/changes-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 ofplatforms from our download pages at: http://dev.mysql.com/downloads/tools/workbench/ Enjoy! Changes in MySQL Workbench 8.0.14 (2019-01-21, General Availability) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * The following new functions were added to the Workbench GRT module: + activateDiagram() Opens the selected EER diagram for use with the exportPNG, exportSVG, exportPS, and exportPDF functions. + exportDiagramToPng(, ) Performs a PNG export of an EER diagram to the path provided without activating it. (Bug #28853802, Bug #92985) * MySQL Workbench now supports macOS 10.14 Mojave, including full compatibility with the Dark Mode color scheme. (Bug #28831956, Bug #92902) * The Adv. Find tab operation that searched an open EER diagram by database objects only was removed. (Bug #28740047) * All editions of MySQL Workbench and the bundled libraries were upgraded to use OpenSSL 1.0.2q. (Bug #28695759) * Keyboard access was added to the home screen tab to enable navigation using the Tab and Enter keys. In addition, the screen view now scrolls to display a selected item if the item was off-screen when highlighted with the Tab key. On Windows and Linux hosts, the Application key and Ctrl+F10 now open a menu of commands (context menu) related to the selection. * Two redundant features were removed from all platforms: + The connection information pop-up sheet on the home screen tab Instead, open Manage Connections from the Database menu (or Edit Connection from the context menu of each connection) to view connection details. + The merge icon (two arrows pointing at each other) located in the Navigation area of the side panel Content from the Administration and Schemas tabs were merged or split when this icon was toggled. Now, the administration section links and schema tree appear in separate tabs only. Bugs Fixed * Valid decimal data within a Microsoft SQL Server table generated an error when used with the MySQL Workbench Migration Wizard. (Bug #28962023, Bug #93293) * The InnoDB status shown within the Administration - Dashboard tab displayed the wrong usage percent. (Bug #28919419) * A conflicting dependency was removed that prevented the mysql-connector-c++-devel package installation when MySQL Workbench was installed first. (Bug #28915929, Bug #93172) * The on-screen process of editing a stored procedure did not prompt to save the changes. (Bug #28880743, Bug #93068) * A new table added to an existing model caused MySQL Workbench to stop working. (Bug #28879925, Bug #93067) * The alter-table operation when applied to partitioned tables on Windows caused MySQL Workbench to stop working. (Bug #28856542, Bug #92990) * Characters from Cyrillic character sets when included in the path to SSH key files caused valid connection attempts to fail without producing a clear error message. These characters now are permitted within the path. (Bug #28814329, Bug #92847) * Connections made to a remote MySQL server over SSH did not recover properly after the network was interrupted temporarily. (Bug #28806660, Bug #90884) * New accounts created to use standard authentication were instead created to require strong password encryption when the default_authentication_plugin server system variable was configured with the caching_sha2_password value. (Bug #28777856, Bug #92740) * The default user name, newuser, was not accepted when it was used to create a new account. (Bug #28776902, Bug #92738) * The operation to migrate a Microsoft SQL Server schema produced an error when it encountered problematic tables during the reverse-engineering step. (Bug #28747888, Bug #92659) * A table editor tab that was opened by clicking the table icon from within the sidebar (Schemas tab) displayed the correct SELECT * FROM query and results, but the query text did not line up along the left margin as expected. (Bug #28730407) * Context-menu actions (New Tab, Save Tab,
MySQL Connector/NET 8.0.14 has been released
Dear MySQL users, MySQL Connector/NET 8.0.14 is the second version to support Entity Framework Core 2.1 and the fourth general availability release of MySQL Connector/NET to add support for the new XDevAPI, 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 XDevAPI, see http://dev.mysql.com/doc/x-devapi-userguide/en/index.html. For more information about how the XDevAPI 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 XDevAPI 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.14, 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.14 (2019-01-21) *Functionality Added or Changed* * The internal method called by the MySqlX.XDevAPI.Relational.Table.Count, MySqlX.XDevAPI.Collection.Count, and MySqlX.XDevAPI.Collection.Count methods were moved to a standardized location within the library. * The auth connection option (along with aliases authentication and authentication mode) was removed from the MySqlBaseConnectionStringBuilder class. This option now is available for X Protocol connections only. * The following obsolete (deprecated) members of Connector/NET 8.0 API classes were removed: + Collection.Remove(Object) method + Collection.Remove(DbDoc) method + FindStatement.Limit(Int64, Int64) method + MySqlParameterCollection.Add(String, Object) method + TableSelectStatement.Limit(Int64, Int64) method + BaseResult.WarningCount property + MySqlBaseConnectionStringBuilder.Auth property + Result.RecordsAffected property + SqlResult.AutoIncrementValue property + SqlResult.RecordsAffected property On Behalf of MySQL Release Engineering Team, Surabhi Bhat
MySQL Connector/J 8.0.14 has been released
Dear MySQL users, MySQL Connector/J Version 8.0.14 is the GA release of the 8.0 branch of MySQL Connector/J. It is suitable for use with MySQL Server versions 8.0, 5.7, 5.6, and 5.5. It supports the Java Database Connectivity (JDBC) 4.2 API, and implements the X DevAPI. This release includes the following new features and changes, also described in more detail on https://dev.mysql.com/doc/relnotes/connector-j/8.0/en/news-8-0-14.html As always, we recommend that you check the "CHANGES" file in the download archive to be aware of changes in behavior that might affect your application. To download MySQL Connector/J 8.0.14 GA, see the "Generally Available (GA) Releases" tab at http://dev.mysql.com/downloads/connector/j/ Enjoy! Changes in MySQL Connector/J 8.0.14 (2019-01-21, General Availability) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * Important Change: For MySQL Server 8.0.14 and later, 5.7.25 and later, 5.6.43 and later, and 5.5.63 and later, minimal permissions on named pipes are granted to clients that use them to connect to the server. Connector/J, however, can only use named pipes when granted full access on them. As a workaround, the MySQL Server that Connector/J wants to connect to must be started with the system variable named_pipe_full_access_group; see the description for the system variable for more details. (Bug #28971500) * X DevAPI: getDefaultSchema() now returns null when no default schema has been set for the Session. * Connector/J now has a new property for building from source, com.mysql.cj.build.verbose, which controls the verbosity of the build process' output. Its default value is false, which makes the output considerably shorter comparing with earlier versions of Connector/J. (Bug #28970166) * The method ResultSet.getBoolean() now returns FALSE when the designated column is of data type CHAR or VARCHAR and contains an "N" or "n". This makes Connector/J 8.0 behaves like Connector/J 5.1 when it comes to converting strings to booleans. (Bug #28706219, Bug #92574) * Connector/J is now capable of reading and, if needed, ignoring any initial notice packets sent by X Plugin before an X Protocol connection is established. Bugs Fixed * X DevAPI: Connector/J returned a NullPointerException when an application tried to establish an XProtocol connection using a Windows named pipe, which is not supported. With this fix, an XProtoclException is returned instead. This fix also makes sure that instead of a NullPointerException, a proper exception is thrown when an application tries to establish a Classic MySQL Protocol connection with a named pipe, but the named pipe is not specified at connection or it cannot be found on the specified path. (Bug #28606708) * X DevAPI: Adding an empty document with executeAsync() resulted in an ERROR 5013 (Missing row data for Insert). With this fix, no error or warning is returned in the case. (Bug #23045642) * Collection.count() returned a wrong error message when the collection did not exist. (Bug #28924137) * The source code of Connector/J contains non-ASCII characters, which might cause encoding issues during compilation if the system did not also use a UTF-8 locale. With this fix, the build script now handles non-ASCII characters well regardless of the system locale. (Bug #28894344) * A memory leak occurred if Connector/J was loaded via the bootstrap class path instead of the main application classpath. It was because AbandonedConnectionCleanupThread failed to initialize its internal thread in that case, so that references for closed connections were not cleaned up, and their number kept growing. This fix repairs the clean up process for closed connections and also makes the process thread safe. (Bug #28747636, Bug #92508) * clearInputStream() returned a NullPointerException when the mysqlSocket, mysqlInput, or mysqlOutput object it tried to retrieve was null. With this fix, an IOExcpetion is thrown instead in the situation. Thanks to Henning Schmiedehausen for contributing to the fix. (Bug #28731795, Bug #92625) * Updating a result set returned by a server-side prepared statement with SELECT ... FOR UPDATE (http://dev.mysql.com/doc/refman/8.0/en/select.html) resulted in an SQLException. (Bug #28692243, Bug #92536) * When the connection property zeroDateTimeBehavior was set to CONVERT_TO_NULL, Connector/J converted a TIME (http://dev.mysql.com/doc/refman/8.0/en/time.html) type value of 00:00:00 to null. With this fix,
MySQL Connector/ODBC 8.0.14 has been released
Dear MySQL users, MySQL Connector/ODBC 8.0.14 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 any MySQL server version from 5.5. 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 Changes in MySQL Connector/ODBC 8.0.14 (2019-01-21, General Availability) Functionality Added or Changed * A new ENABLE_LOCAL_INFILE connection option was added to the connection string, DSN, and GUI. Disabled by default, set ENABLE_LOCAL_INFILE=1 to enable LOAD DATA operations. This toggles the MYSQL_OPT_LOCAL_INFILE mysql_options() option. The connection string overrides the DSN value if both are set. * MySQL Connector/ODBC is now compatible with MSVC 2017, while retaining compatibility with MSVC 2015: + Previously, Connector/ODBC binary distributions were compatible with projects built using MSVC 2015. Binary distributions now are compatible with projects built using MSVC 2017 or 2015. + Previously, Connector/ODBC source distributions could be built using MSVC 2015. Source distributions now can be built using MSVC 2017 or 2015. + Previously, the MSI installer accepted the Visual C++ Redistributable for Visual Studio 2015. The MSI installer now accepts the Visual C++ Redistributable for Visual Studio 2017 or 2015. * 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. Source distributions include the INFO_SRC file only. 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 Enterprise Backup 8.0.14 has been released
MySQL Enterprise Backup 8.0.14, 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.14 supports only the MySQL Server 8.0.14. 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.14 is given below. -- Changes in MySQL Enterprise Backup 8.0.14 (2019-01-21, General Availability) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * mysqlbackup now supports encrypted binary and relay log. See Working with Encrypted Binary and Relay Logs (http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/advanced.encrypted-binlog-relaylog.html) for details. * mysqlbackup now supports the --ssl-fips-mode option, which controls whether mysqlbackup operates in FIPS mode. See FIPS Support (http://dev.mysql.com/doc/refman/8.0/en/fips-mode.html) for details. Bugs Fixed * An apply-incremental-backup operation failed with an error (RDR1 ERROR: Unable to remove relaylog files from full backup) when the incremental backup was created with the --compress option. (Bug #28366241) * mysqlbackup quit unexpectedly during an apply-incremental-backup operation if the backed up server had been started using relative paths for --datadir and --log-bin. (Bug #28334521) * Attempts to restore a backup of a MySQL 5.7 Server to a MySQL 8.0 Server resulted in a strange error message (Server_version is not obtained). With this fix, mysqlbackup now indicates that the operation is not supported. For related information, see Restoring a Backup with a Database Upgrade or Downgrade (http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/restore-upgrade.html). (Bug #27952379) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Router 8.0.14 for MySQL Server 8.0 and 5.7 has been released
Dear MySQL users, MySQL Router 8.0.14 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.14. 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.14, 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.14 (Not yet released) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * A new dynamic configuration bootstrap feature was added that tracks the current MySQL InnoDB cluster Metadata servers. This replaces the existing bootstrap_server_addresses option with the new dynamic_config option in mysqlrouter.conf. MySQL Router now tracks and stores active MySQL InnoDB cluster Metadata server addresses and loads them if Router is restarted. Previously, metadata server information was defined during Router's initial bootstrap operation and stored statically as bootstrap_server_addresses in the configuration file. This new dynamic_config option is generated by --bootstrap and is defined under mysqlrouter.conf's [DEFAULT] section. Its value points to a generated JSON file named state.json that's initialized with InnoDB cluster Metadata server addresses and the group replication ID; and additional information is added and updated while Router is running. The bootstrap process no longer defines bootstrap_server_addresses because dynamic_config replaces its functionality; and these two options cannot be set at the same time. For backwards compatibility, if only bootstrap_server_addresses is set then it functions as it did in previous Router versions and this new dynamic configuration functionality is not used. (Bug #28082857, Bug #91029) * MySQL Router now persistently tracks the metadata server addresses rather than only using the static list defined in the configuration file using the destinations option. Bugs Fixed * The --version output was aligned with MySQL Server's layout. (Bug #28899194) * Linking Router against libmsyqlclient that was built with DBUG enabled led to slow Router shutdown procedures. (Bug #28656618) * Fixed a thread shutdown race condition. (Bug #28610484) * Sending mysqlrouter a SIGTERM would take at least 100ms to shut down. Now a concurrent plugin shutdown queue was added to speed up the shutdown process. (Bug #28570122) * A metadata-cache API method was added to check the initialization status. Routing plugins use this during initialization to safely register the callbacks after metadata-cache is initialized. (Bug #28569717) * Installing MySQL Server with Router from source or building a tarball with "make package" would create a top level "data/" directory as part of the "Router" component. Due to possible collisions with MySQL Server, "data/" was changed to "var/lib/mysqlrouter". (Bug #28537733) * The connection error counter that blocks clients after max_connect_errors connection errors did not reset after a successful connection. (Bug #27995042, Bug #90809) -- 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.14 has been released
Dear MySQL users, MySQL Connector/Node.js is a new Node.js driver for use with the X DevAPI. This release, v8.0.14, 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.14 (2019-01-21, General Availability) Functionality Added or Changed * Removed deprecation notices from the count() methods. * Setting the default schema via the connection now sets the default schema on the server; meaning, subsequent queries executed using session.sql() do not need to specify the schema. Bugs Fixed * Setting the default schema with the connection URI using a schema name that contained special characters (that would need to be percent-encoded) would result in the percent-encoded name being used instead of the original one (e.g. "%25%26%5E*%5E_" instead of "%&^*^_"). (Bug #28990682) * An error is once again thrown if sslOption's 'ca' is different than the certificate authority used to sign the server certificate, or if the server certificate has been revoked. (Bug #28977649) * Attempting to use false-like values such as 0, false, null, and undefined would emit errors when updating or inserting documents in a collection or rows in a table. Additionally, now boolean values become numeric values (true=1, false=0) while null and undefined are converted to MySQL's NULL type. (Bug #28970727, Bug #93315) * Collection.existsInDatabase() always returned true if any other collection existed in the database. (Bug #28745240) * Configuring a default schema from the connection string would create the schema if it did not exist. Now, an "Unknown database" error is thrown instead. * An unexpected notice could result in an unexpected halt of the client. 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 Community Server 8.0.14 has been released (part 2/2)
[This is part 2 of the announcement] Bugs Fixed * Important Change: Importing a dump from a MySQL 5.7 server to a server running MySQL 8.0 often failed with ER_WRONG_VALUE_FOR_VAR when an SQL mode not supported by the 8.0 server was used. This could happen frequently due to the fact that NO_AUTO_CREATE_USER is enabled by default in MySQL 5.7 but not supported in MySQL 8.0. The behavior of the server in such circumstances now depends on the setting of the pseudo_slave_mode system variable. If this is false, the server rejects the mode setting with ER_UNSUPPORTED_SQL_MODE. If pseudo_slave_mode is true, the server ignores the unsupported mode and gives a warning. Note that mysqlbinlog sets pseudo_slave_mode to true prior to executing any SQL. (Bug #90337, Bug #27828236) * InnoDB: MySQL would not start on Solaris X86. The static thread-local 'tables' variable in the TempTable storage engine was not properly initialized. (Bug #28987365) * InnoDB: Latching logic used during deadlock detection was simplified. (Bug #28904966) * InnoDB: An invalid record offset for an old version of a clustered index record raised a debug assertion. (Bug #28825617) References: This issue is a regression of: Bug #25540277. * InnoDB: The minimum DML delay imposed when the length of the history list exceeds innodb_max_purge_lag was decreased from 5000 microseconds to 5 microseconds. (Bug #28813453) * InnoDB: An incorrect lock order caused a deadlock when one thread attempted to drop a table while another created an encrypted tablespace. (Bug #28774259) * InnoDB: ALTER TABLESPACE failed to ignore unsupported tablespace attributes. (Bug #28656611) * InnoDB: Implicit to explicit lock conversion logic was simplified and optimized. (Bug #28637472) * InnoDB: A fragment page allocation failure raised an assertion. (Bug #28615893) * InnoDB: Incorrectly placed debug points caused flushed LOB pages to be considered corrupt. (Bug #28607368) * InnoDB: The TempTable storage engine incorrectly created temporary files in the system temporary directory instead of the directory defined by the tmpdir variable. (Bug #28598943) * InnoDB: Attempting to drop a table with a name similar to that of a full-text search auxiliary table caused an assertion failure. (Bug #28577083) * InnoDB: A function called by an UPDATE query did not account for virtual columns. (Bug #28560650) * InnoDB: An incorrect key was defined for the buffer pool zip hash mutex. (Bug #28556539) * InnoDB: Deadlock handling for background transactions that involve the mysql.innodb_table_stats and mysql.innodb_index_stats tables was modified. The tables were incorrectly included in an assertion that is triggered when internal tables are included in a deadlock cycle. (Bug #28523042, Bug #92069) * InnoDB: Setting innodb_spin_wait_delay to a high value caused an assertion failure when attempting to shut down the server. To prevent this failure from occurring, the innodb_spin_wait_delay maximum value was reduced to 1000. (Bug #28489407, Bug #91973) * InnoDB: An ON DELETE CASCADE operation on table with a foreign key constraint and an indexed virtual column caused the server to exit. (Bug #28470805) * InnoDB: An incorrectly written DML log involving a virtual column value raised an assertion. (Bug #28448853) * InnoDB: A RENAME TABLE operation failed when run on a table created outside of the MySQL data directory using the DATA DIRECTORY clause. (Bug #28341514) * InnoDB: ALTER TABLE ... EXCHANGE PARTITION permitted partitions with different virtual column definitions to be exchanged, which resulted in an assertion when InnoDB later attempted to read from a nonexistent virtual column. (Bug #28235668) * InnoDB: A counter was added for redo log write and flush requests that occur during transaction commit. The counter is used by the log writer thread to compute the average time between consecutive requests. When the average time is greater than 100 microseconds, log writer threads do not use spin delay and instead wait on request events with a 10 microsecond timeout limit. A log writer thread implementation issue that could cause a hang was also fixed. (Bug #28062382, Bug #28444247, Bug #28616442, Bug #90890) * InnoDB: An assertion was raised when attempting to add rollback segments to newly added undo tablespace that was not fully initialized. (Bug #27914054) * InnoDB: Foreign key constraints were ignored after a
MySQL Community Server 8.0.14 has been released (part 1/2)
[Due to size limitation, this announcement is split in two. This is part 1] Dear MySQL users, MySQL Server 8.0.14, a new version of the popular Open Source Database Management System, has been released. MySQL 8.0.14 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.14 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.14 is available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/mysql/ MySQL Server 8.0.14 is also available from our repository for Linux platforms, go here for details: http://dev.mysql.com/downloads/repo/ Windows packages are available via the Installer for Windows: http://dev.mysql.com/downloads/installer/ along with .ZIP (no-install) packages for more advanced needs. 8.0.14 also comes with a web installer as an alternative to the full installer. The web installer doesn't come bundled with any actual products and instead relies on download-on-demand to fetch only the products you choose to install. This makes the initial download much smaller but increases install time as the individual products will need to be downloaded. We welcome and appreciate your feedback, bug reports, bug fixes, patches, etc.: http://bugs.mysql.com/report.php The following link lists the changes in the MySQL 8.0 since the release of MySQL 8.0.13. It may also be viewed online at http://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-14.html Enjoy! == Changes in MySQL 8.0.14 (2019-01-21, General Availability) * Account Management Notes * Audit Log Notes * Compilation Notes * Component Notes * Configuration Notes * Deprecation and Removal Notes * Function Notes * Logging Notes * Optimizer Notes * Packaging Notes * Performance Schema Notes * Pluggable Authentication * Security Notes * Spatial Data Support * SQL Syntax Notes * Thread Pool Notes * X Plugin Notes * Functionality Added or Changed * Bugs Fixed Account Management Notes * Previously, each MySQL user account was permitted to have a single password. MySQL now permits an account to have dual passwords, designated as primary and secondary passwords. This capability enables phased password changes to be performed seamlessly in complex multiple-server systems, without downtime. To support dual-password capability, the ALTER USER and SET PASSWORD statements now have a RETAIN CURRENT PASSWORD clause that saves the current password as the secondary password when you assign an account a new primary password. ALTER USER also has a DISCARD OLD PASSWORD clause to discard a secondary password that is no longer needed. See Password Management (http://dev.mysql.com/doc/refman/8.0/en/password-management.html). Important The implementation of dual-password capability involves a change to the structure of the mysql.user system table. If you upgrade to this MySQL release from an earlier version, you must run mysql_upgrade (and restart the server) to incorporate this system database change. Until this is done, password changes are not possible. Audit Log Notes * The audit API now enables applications to add their own message events to the audit log using the new audit_api_message_emit component, which includes an audit_api_message_emit_udf() user-defined function. See The Audit Message Component (http://dev.mysql.com/doc/refman/8.0/en/audit-api-message-emit.html). Compilation Notes * The minimum version of the Boost library for server builds is now 1.68.0. (Bug #28478497) Component Notes * A new host_application_signal component service is available to enable server components to deliver signals to the host application. For example, the service enables replication components to send a shutdown signal to the server. Configuration Notes * The content of the .gitignore file has been cleaned up. Much of this file was inherited from its .bzrignore predecessor and was not relevant. One implication of this cleanup is that in-source builds are disallowed. (Bug #28341794, Bug #91626) * MySQL Server now permits a TCP/IP port to be configured specifically for administrative connections. This provides an alternative to the single administrative connection that is permitted on the network interfaces used for ordinary connections even when max_connections
MySQL Community Server 5.6.43 has been released
Dear MySQL users, MySQL Server 5.6.43, a new version of the popular Open Source Database Management System, has been released. MySQL 5.6.43 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.43 on new servers or upgrading to MySQL 5.6.43 from previous MySQL releases, please see http://dev.mysql.com/doc/refman/5.6/en/installing.html MySQL Server 5.6.43, 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.42. It may also be viewed online at http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-43.html Enjoy! Changes in MySQL 5.6.43 (2019-01-21, General Availability) Security Notes * The linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.2q. 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) Functionality Added or Changed * Microsoft Windows: The access control granted to clients on the named pipe created by the MySQL server now is set to the minimum necessary for successful communication on Windows. Newer MySQL client software can open named pipe connections without any additional configuration. If older client software cannot be upgraded immediately, the new named_pipe_full_access_group server system variable can be used to give a Windows group the necessary permissions to open a named pipe connection. Membership in the full-access group should be restricted and temporary. Bugs Fixed * Replication: A patch to correct the handling of quotes for identifiers in ROLLBACK TO SAVEPOINT statements in the binary log was not correctly applied to subsequent MySQL versions. (Bug #28569645) * Replication: In some circumstances, the CHANGE MASTER TO statement could not be used on a replication slave if the master info log had been changed from a table (master_info_repository=TABLE) into a file (master_info_repository=FILE). (Bug #28529558) * Replication: The value returned by a SHOW SLAVE STATUS statement for the total combined size of all existing relay log files (Relay_Log_Space) could become much larger than the actual disk space used by the relay log files. The I/O thread did not lock the variable while it updated the value, so the SQL thread could automatically delete a relay log file and write a reduced value before the I/O thread finished updating the value. The I/O thread then wrote its original size calculation, ignoring the SQL thread's update and so adding back the space for the deleted file. The Relay_Log_Space value is now locked during updates to prevent concurrent updates and ensure an accurate calculation. (Bug #26997096, Bug #87832) * Replication: If the relay log index file was temporarily locked for viewing by a backup process for a replication slave, and MySQL Server also attempted to access the file at that time for rename or delete operations, the backup completed with warnings, but MySQL Server experienced an unexpected halt. MySQL Server now retries the file access operation a number of times in case this or a similar scenario is the explanation and the file becomes available again before long. (Bug #25839610) * The server permitted creation of databases with the same name as redo log files, which could result in unexpected server behavior. Such names are no longer permitted as database names. (Bug #28867993) * Comparing log file names as strings using the memcmp() function resulted in uninitialized memory
