MySQL Connector/ODBC 5.3.13 has been released
Dear MySQL users, MySQL Connector/ODBC 5.3.13, a new version of the ODBC driver for the MySQL database management system, has been released. 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 version from 5.6. This is the sixth release of the MySQL ODBC driver 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 http://dev.mysql.com/downloads/connector/odbc/5.3.html For information on installing, please see the documentation at http://dev.mysql.com/doc/connector-odbc/en/connector-odbc-installation.html Changes in MySQL Connector/ODBC 5.3.13 (2019-04-29, General Availability) Bugs Fixed * Connector/ODBC 5.3 is now built with MySQL client library 5.7.26, which includes OpenSSL 1.0.2R. Issues fixed in the new OpenSSL version are described at http://www.openssl.org/news/vulnerabilities.html. (Bug #29489006) * 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 Cluster 7.6.10 has been released
Dear MySQL Users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance (with optional checkpointing to disk) - Transparent Auto-Sharding - Read & write scalability - Active-Active/Multi-Master geographic replication - 99.999% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http, Memcached and JavaScript/Node.js) MySQL Cluster 7.6.10 has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. MySQL Cluster 7.6 is also available from our repository for Linux platforms, go here for details: http://dev.mysql.com/downloads/repo/ The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.6/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime and agility. More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! Changes in MySQL NDB Cluster 7.6.10 (5.7.26-ndb-7.6.10) (2019-04-26, General Availability) MySQL NDB Cluster 7.6.10 is a new release of NDB 7.6, based on MySQL Server 5.7 and including features in version 7.6 of the NDB storage engine, as well as fixing recently discovered bugs in previous NDB Cluster releases. Obtaining NDB Cluster 7.6. NDB Cluster 7.6 source code and binaries can be obtained from https://dev.mysql.com/downloads/cluster/. For an overview of changes made in NDB Cluster 7.6, see What is New in NDB Cluster 7.6 (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-what-is-new-7-6.html). This release also incorporates all bug fixes and changes made in previous NDB Cluster releases, as well as all bug fixes and feature changes which were added in mainline MySQL 5.7 through MySQL 5.7.26 (see Changes in MySQL 5.7.26 (2019-04-25, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-26.html)). Bugs Fixed * NDB Disk Data: The error message returned when validation of MaxNoOfOpenFiles in relation to InitialNoOfOpenFiles failed has been improved to make the nature of the problem clearer to users. (Bug #28943749) * NDB Disk Data: Repeated execution of ALTER TABLESPACE ... ADD DATAFILE against the same tablespace caused data nodes to hang and left them, after being killed manually, unable to restart. (Bug #22605467) * NDB Cluster APIs: NDB now identifies short-lived transactions not needing the reduction of lock contention provided by NdbBlob::close() and no longer invokes this method in cases (such as when autocommit is enabled) in which unlocking merely causes extra work and round trips to be performed prior to committing or aborting the transaction. (Bug #29305592) References: See also: Bug #49190, Bug #11757181. * NDB Cluster APIs: When the most recently failed operation was released, the pointer to it held by NdbTransaction became invalid and when accessed led to failure of the NDB API application. (Bug #29275244) * When a pushed join executing in the DBSPJ block had to store correlation IDs during query execution, memory for these was allocated for the lifetime of the entire query execution, even though these specific correlation IDs are required only when producing the most recent batch in the result set. Subsequent batches require additional correlation IDs to be stored and allocated; thus, if the query took sufficiently long to complete, this led to exhaustion of query memory (error 20008). Now in such cases, memory is allocated only for the lifetime of the current result batch, and is freed and made available for re-use following completion of the batch. (Bug #29336777) References: See also: Bug #26995027. * API and data nodes running NDB 7.6 and later could not use an existing parsed configuration from an earlier release series due to being overly strict with regard to having values defined for configuration parameters new to the later release, which placed a restriction on possible upgrade paths. Now NDB 7.6 and later are less strict about having all new parameters specified explicitly in the configuration which they are served, and use hard-coded default values in such cases. (Bug #28993400) * Added DUMP 406 (NdbfsDumpRequests) to provide NDB file system information to global checkpoint and local checkpoint stall reports in the node logs. (Bug #28922609) * A race condition between the DBACC and D
MySQL Cluster 7.4.24 has been released
Dear MySQL Users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance - Transparent Auto-Sharding - Read & write scalability - Active-Active/Multi-Master geographic replication - 99.999% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http, Memcached and JavaScript/Node.js) MySQL Cluster 7.4 makes significant advances in performance; operational efficiency (such as enhanced reporting and faster restarts and upgrades) and conflict detection and resolution for active-active replication between MySQL Clusters. MySQL Cluster 7.4.24 has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.4/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime and agility. More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! == Changes in MySQL NDB Cluster 7.4.24 (5.6.44-ndb-7.4.24) (2019-04-26, General Availability) MySQL NDB Cluster 7.4.24 is a new release of MySQL NDB Cluster 7.4, based on MySQL Server 5.6 and including features in version 7.4 of the NDB storage engine, as well as fixing recently discovered bugs in previous NDB Cluster releases. Obtaining MySQL NDB Cluster 7.4. MySQL NDB Cluster 7.4 source code and binaries can be obtained from https://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL NDB Cluster 7.4, see What is New in NDB Cluster 7.4 (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is-new-7-4.html). This release also incorporates all bug fixes and changes made in previous NDB Cluster releases, as well as all bug fixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.44 (see Changes in MySQL 5.6.44 (2019-04-25, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-44.html)). Functionality Added or Changed * Building with CMake3 is now supported by the compile-cluster script included in the NDB source distribution. Bugs Fixed * When a pushed join executing in the DBSPJ block had to store correlation IDs during query execution, memory for these was allocated for the lifetime of the entire query execution, even though these specific correlation IDs are required only when producing the most recent batch in the result set. Subsequent batches require additional correlation IDs to be stored and allocated; thus, if the query took sufficiently long to complete, this led to exhaustion of query memory (error 20008). Now in such cases, memory is allocated only for the lifetime of the current result batch, and is freed and made available for re-use following completion of the batch. (Bug #29336777) References: See also: Bug #26995027. * In some cases, one and sometimes more data nodes underwent an unplanned shutdown while running ndb_restore. This occurred most often, but was not always restircted to, when restoring to a cluster having a different number of data nodes from the cluster on which the original backup had been taken. The root cause of this issue was exhaustion of the pool of SafeCounter objects, used by the DBDICT kernel block as part of executing schema transactions, and taken from a per-block-instance pool shared with protocols used for NDB event setup and subscription processing. The concurrency of event setup and subscription processing is such that the SafeCounter pool can be exhausted; event and subscription processing can handle pool exhaustion, but schema transaction processing could not, which could result in the node shutdown experienced during restoration. This problem is solved by giving DBDICT schema transactions an isolated pool of reserved SafeCounters which cannot be exhausted by concurrent NDB event activity. (Bug #28595915) * ndb_restore did not restore autoincrement values correctly when one or more staging tables were in use. As part of this fix, we also in such cases block applying of the SYSTAB_0 backup log, whose content continued to be applied directly based on the table ID, which could ovewrite the autoincrement values stored in SYSTAB_0 for unrelated tables. (Bug #27917769, Bug #27831990) References:
MySQL Connector/ODBC 8.0.16 has been released
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
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
MySQL Community Server 5.6.44 has been released
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
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 paramet
MySQL Community Server 5.7.26 has been released
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/ <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 <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
MySQL Workbench 8.0.16 has been released
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 <https://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 ve
MySQL Connector/Python 8.0.16 has been released
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
MySQL Enterprise Backup 8.0.16 has been released
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
MySQL Router 8.0.16 for MySQL Server 8.0 and 5.7 has been released
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
MySQL Community Server 8.0.16 has been released [part 2]
in INFORMATION_SCHEMA.TABLES was not updated when adding an index. (Bug #19811005) * Partitioning: Some partitioning DDL statements were improperly rejected due to name validation checks which used the wrong table identifier. (Bug #29317007) * Partitioning: While rolling back ALTER TABLE ... COALESCE PARTITION, the server sometimes attempted to lock and close partitions which had been dropped as a result of this statement. (Bug #28517446) * 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: Group Replication did not correctly handle the situation where START GROUP REPLICATION was issued when the port specified for the member's Group Replication local address was currently busy. (Bug #29347285) * Replication: If the WAIT_FOR_EXECUTED_GTID_SET() function was used with a timeout value including a fractional part (for example, 1.5), an error in the casting logic meant that the timeout was rounded down to the nearest whole second, and to zero for values less than 1 second (for example, 0.1). The casting logic has now been corrected so that the timeout value is applied as originally specified with no rounding. Thanks to Dirkjan Bussink for the contribution. (Bug #29324564, Bug #94247) * Replication: The consistency level AFTER for the system variable group_replication_consistency did not include the consistency guarantees provided by BEFORE_ON_PRIMARY_FAILOVER. These consistency guarantees, which were already implicitly present with the BEFORE and BEFORE_AND_AFTER consistency levels, are now provided with AFTER. (Bug #29315752) * Replication: On Debian-based platforms (such as Ubuntu), if the hostname resolved to 127.0.1.1 - which is the default on these platforms - it was not possible to create a cluster using the default settings. Now, in such situations a proper validation of the instance is performed before creating a cluster and adding instances to it. (Bug #29246110) * Replication: In a blocked group, if you set an invalid value for group_replication_force_members and then issued STOP GROUP_REPLICATION, the server could stop unexpectedly. (Bug #29119961) * Replication: MySQL Server's behavior when the mysql.gtid_executed table cannot be accessed has been refactored to provide appropriate error responses and actions. The MySQL server now ensures that writes are permitted to the mysql.gtid_executed table when the server is in read only or super read only mode, so that the binary log file can still be rotated in these modes. If the mysql.gtid_executed table cannot be accessed for writes, and the binary log file is rotated for any reason other than reaching the maximum file size (max_binlog_size), the current binary log file continues to be used. An error message is returned to the client that requested the rotation, and a warning is logged on the server. If the mysql.gtid_executed table cannot be accessed for writes and max_binlog_size is reached, the server responds according to its binlog_error_action setting. If IGNORE_ERROR is set, an error is logged on the server and binary logging is halted, or if ABORT_SERVER is set, the server shuts down. (Bug #29111514) * Replication: When issuing STOP GROUP_REPLICATION while the member was trying to assess whether or not it had lost majority, the server could stop unexpectedly. (Bug #29053128) * Replication: When a RESET MASTER TO statement is used to specify the starting index number for binary log files, the maximum number that you can specify has been reduced from the maximum integer value to 20. If the maximum integer value was specified, the server was not able to start up because no further binary log files could be created. The server also previously experienced a segmentation fault in that situation. (Bug #28980788, Bug #28995220) * Replication: On overloaded servers there was a possibility that when a member joined the group, the VIEW_CHANGE_LOG_EVENT event which marks that point was not logged in the correct place. This could lead to errors in the data transfer to the newly joining server and data divergence. Now, the VIEW_CHANGE_LOG_EVENT event is logged in the correct place in the binary log. In addition, warnings are logged about the delay in logging the event. (Bug #28971594) * Replication: On a replication slave with GTIDs
MySQL Community Server 8.0.16 has been released [part 1]
[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
[ANN] Mroonga 9.01 - Fast fulltext search for all languages on MySQL
Hi, Mroonga 9.01 has been released! Mroonga is a MySQL storage engine that supports fast fulltext search and geolocation search. It is CJK ready. It uses Groonga as a storage and fulltext search engine. Document: http://mroonga.org/docs/ How to install: Install Guide http://mroonga.org/docs/install.html How to upgrade: Upgrade Guide http://mroonga.org/docs/upgrade.html Blog: http://mroonga.org/en/blog/2019/03/29/mroonga-9.01.html Changes: http://mroonga.org/docs/news.html#release-9.01 Here are some topics in this release. * Improved support for more table and comment parameter about tokenizer/normalizer/indexes. * See above blog entry about details. * Added support for latest MariaDB/Percona Server. * Percona Server 5.7.25-28. * MariaDB 10.3.13. * MariaDB 10.2.23. * Added support for building bundled MariaDB package on AppVeyor. Let's search by Mroonga! Regards, -- Kentaro Hayashi -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Enterprise Backup 3.12.4 has been released
Dear MySQL users, MySQL Enterprise Backup v3.12.4, a new version of the online MySQL backup tool, is now available for download from the My Oracle Support (MOS) website as our latest GA release. This release will be available on eDelivery (OSDC) after the next upload cycle. MySQL Enterprise Backup is a commercial extension to the MySQL family of products. A brief summary of the changes in MySQL Enterprise Backup (MEB) version 3.12.4 is given below. Changes in MySQL Enterprise Backup 3.12.4 (2019-02-15) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * Information on the executed GTIDs is now includfed in the mysqlbackup output and the backup log when the backed-up server has GTIDs enabled. (Bug #25978803) * A backup became corrupted if, during the backup process, a DDL operation that took advantage of MySQL server's online DDL feature (http://dev.mysql.com/doc/refman/5.6/en/innodb-online-ddl.html) occurred. This was because mysqlbackup did not support the server feature---and it still does not. This fix avoids the error by having mysqlbackup turn the server's system variable old_alter_table to "1" at the beginning of a backup if it is "0," so that any DDL operations that take place during the backup are handled with the old table copy method. mysqlbackup then turns the variable back to "0" near the end of the backup operation. Important Notice that in cases where mysqlbackup quits unexpectedly and does not turn old_alter_table back to its original value, the user will have to turn the value back to "0" manually on the server, in order to return the server to its original configuration. This should be performed if the statement "Server system variable 'old_alter_table' was set to '0'. Setting it to '1'" appears in the early output of mysqlbackup, but the statement "Setting server system variable 'old_alter_table' back to '0'" does not appear before mysqlbackup quits. (Bug #25217215) * A new option, --skip-final-rescan, makes mysqlbackup skip the final rescan for InnoDB tables that are modified by DDL operations after the database has been locked near the end of a backup operation. This potentially shortens the duration for the lock and reduces the backup's impact on the server's normal operation. See the description for --skip-final-rescan for details. (Bug #21094221) * The output by mysqlbackup, which goes to the stderr stream and the message log, has now been improved to include the timestamps and thread IDs for all steps taken by mysqlbackup, in order to provide more information for debugging purposes. (Bug #20142619) * When there were no tables matching the regular expression specified with the --include-tables option during a backup operation, mysqlbackup still created a backup, which contained an empty folder for each database on the server. mysqlbackup now throws an error when --include-tables selects no tables to be backed up. (Bug #18114353) * During the final stage of a backup when MySQL Enterprise Backup tried to temporarily put the database into a read-only state using the FLUSH TABLES WITH READ LOCK statement in order to copy non-InnoDB files, if a long query was running on the server at the same time, the FLUSH TABLES WITH READ LOCK statement could be taking too long to finish, holding up further queries and eventually bringing down the server. A new mysqlbackup option --lock-wait-timeout can now be used to specify the timeout in seconds for the FLUSH TABLES WITH READ LOCK statement. If the timeout is exceeded, the statement is failed and the lock on the tables is released, so that queries held up by the lock can then be executed. mysqlbackup then retries the statement and continues with the backup. Default value for --lock-wait-timeout is 60 [seconds]. (Bug #14339483) * In order to minimize the impact of a hot backup on the MySQL server, the copying of the buffer pool dump files and some of the metadata files is now performed before the final phase of the backup in which the server instance is locked. This shortens the duration for the lock and reduces the backup's impact on the server's normal operation. Also, to minimize the resource used on a backup, the copying of the buffer pool dump files is no longer performed for partial and offline backups, for which the buffer pool dump is usually not very useful. Bugs Fixed * While MySQL Server interprets the system v
Re: mysql V 8.0.12 and mysqdump
> Halaasz Saandor hat am 9. Februar 2019 um 10:01 geschrieben: > > > 2019/02/08 10:32 ... Walter Harms: > > Hello list, > > i run into an unexpected problem with mysqldump: > > > > mysqldump --version > > mysqldump Ver 8.0.12 for Linux on x86_64 (MySQL Community Server - GPL) > > > > > > when i try it results in: > > mysqldump: Error: 'Lost connection to MySQL server during query' when trying > > to > > dump tablespaces > > mysqldump: Couldn't execute 'SHOW VARIABLES LIKE 'ndbinfo\_version'': MySQL > > server has gone away (2006) > > I regulary hav this problem with the command-line client (mysql.exe) and > when I asked R H gave this answer (and with the command-line client it > is much less imporant): > > Forwarded Message I found a solution with this (to set for mysqld in my.cnf): wait_timeout = 31536000 It sets the time out very high and mysqldump can now complet the query. personaly i would say this is not a propper solution as it does not solve the problem of an sql statement taking 15min to complet. re, wh -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: mysql V 8.0.12 and mysqdump
> Halaasz Saandor hat am 9. Februar 2019 um 10:01 geschrieben: > > > 2019/02/08 10:32 ... Walter Harms: > > Hello list, > > i run into an unexpected problem with mysqldump: > > > > mysqldump --version > > mysqldump Ver 8.0.12 for Linux on x86_64 (MySQL Community Server - GPL) > > > > > > when i try it results in: > > mysqldump: Error: 'Lost connection to MySQL server during query' when trying > > to > > dump tablespaces > > mysqldump: Couldn't execute 'SHOW VARIABLES LIKE 'ndbinfo\_version'': MySQL > > server has gone away (2006) > > I regulary hav this problem with the command-line client (mysql.exe) and > when I asked R H gave this answer (and with the command-line client it > is much less imporant): > > Forwarded Message > Subject: Re: ERROR 2013 (HY000): Lost connection to MySQL server during > query > Date: Mon, 06 Jan 2014 17:07:45 +0100 > From: Reindl Harald > > > Am 06.01.2014 15:36, schrieb h...@tbbs.net: > > Now that I installed 5.6.14 on our Vista machine, when using "mysql" > I often see that error-message, which under 5.5.8 I never saw. What is > going on? > > what about look in the servers logfiles > most likely "max_allowed_packet" laughable low > I do not thing so, it is onvoius that the sql statement i postet is rediciusly slow, causing mysqldump to terminate the connection. What anoys me most is the fact that the result is empty. So i could remove it from the code, but i have no idea about the consequences. NTL i will try max_allowed_packet and see what will happen. re, wh -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: mysql V 8.0.12 and mysqdump
2019/02/08 10:32 ... Walter Harms: Hello list, i run into an unexpected problem with mysqldump: mysqldump --version mysqldump Ver 8.0.12 for Linux on x86_64 (MySQL Community Server - GPL) when i try it results in: mysqldump: Error: 'Lost connection to MySQL server during query' when trying to dump tablespaces mysqldump: Couldn't execute 'SHOW VARIABLES LIKE 'ndbinfo\_version'': MySQL server has gone away (2006) I regulary hav this problem with the command-line client (mysql.exe) and when I asked R H gave this answer (and with the command-line client it is much less imporant): Forwarded Message Subject: Re: ERROR 2013 (HY000): Lost connection to MySQL server during query Date: Mon, 06 Jan 2014 17:07:45 +0100 From: Reindl Harald Am 06.01.2014 15:36, schrieb h...@tbbs.net: > Now that I installed 5.6.14 on our Vista machine, when using "mysql" I often see that error-message, which under 5.5.8 I never saw. What is going on? what about look in the servers logfiles most likely "max_allowed_packet" laughable low -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
[ANN] Mroonga 9.00 - Fast fulltext search for all languages on MySQL
Hi, Mroonga 9.00 has been released! Mroonga is a MySQL storage engine that supports fast fulltext search and geolocation search. It is CJK ready. It uses Groonga as a storage and fulltext search engine. Document: http://mroonga.org/docs/ How to install: Install Guide http://mroonga.org/docs/install.html How to upgrade: Upgrade Guide http://mroonga.org/docs/upgrade.html Blog: http://mroonga.org/en/blog/2019/02/09/mroonga-9.00.html Changes: http://mroonga.org/docs/news.html#release-9.00 Here are some topics in this release. * Added support for MariaDB 10.3.12. * Added support for MariaDB 10.2.21. * Added support for Percona Server 5.7.24-27. * Added support for Percona Server 5.6.43 rel84.3. * Added support for MySQL 5.7.25. * Added support for MySQL 5.6.43. In Groonga 9.0.0, TokenPattern, TokenTable tokenizer and remove_blank for NormalizerNFKC100 is supported. If you upgrade to Groonga 9.0.0, you can use them from Mroonga 9.00! * See http://groonga.org/docs/news.html#release-9-0-0-2019-02-09 Regards, -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
mysql V 8.0.12 and mysqdump
Hello list, i run into an unexpected problem with mysqldump: mysqldump --version mysqldump Ver 8.0.12 for Linux on x86_64 (MySQL Community Server - GPL) when i try it results in: mysqldump: Error: 'Lost connection to MySQL server during query' when trying to dump tablespaces mysqldump: Couldn't execute 'SHOW VARIABLES LIKE 'ndbinfo\_version'': MySQL server has gone away (2006) I seems it get stuck in this query: explain SELECT LOGFILE_GROUP_NAME, FILE_NAME, TOTAL_EXTENTS, INITIAL_SIZE, ENGINE, EXTRA FROM INFORMATION_SCHEMA.FILES WHERE FILE _TYPE = 'UNDO LOG' AND FILE_NAME IS NOT NULL AND LOGFILE_GROUP_NAME IS NOT NULL AND LOGFILE_GROUP_NAME IN (SELECT DISTINCT LOGFILE_GROUP _NAME FROM INFORMATION_SCHEMA.FILES WHERE FILE_TYPE = 'DATAFILE' AND TABLESPACE_NAME IN (SELECT DISTINCT TABLESPACE_NAME FROM INFORMATIO N_SCHEMA.PARTITIONS WHERE TABLE_SCHEMA IN ('kpc'))) GROUP BY LOGFILE_GROUP_NAME, FILE_NAME, ENGINE, TOTAL_EXTENTS, INITIAL_SIZE ORDER BY LOGFILE_GROUP_NAME; ++-+-+++-+-+-+-- +---+--+---+ | id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | filtered | Extra | ++-+-+++-+-+-+-- +---+--+---+ | 1 | SIMPLE | cat | NULL | index | PRIMARY | name| 194 | NULL | 1 | 100.00 | Using index; Using temporary; Using filesort; Start temporary | | 1 | SIMPLE | sch | NULL | eq_ref | PRIMARY,catalog_id | catalog_id | 202 | mysql.cat.id,const | 1 | 100.00 | Using index | | 1 | SIMPLE | tbl | NULL | ref| schema_id | schema_id | 8 | mysql.sch.id |78 | 100.00 | Using where | | 1 | SIMPLE | part| NULL | ref| table_id,table_id_2 | table_id| 8 | mysql.tbl.id | 597 |10.00 | Using where | | 1 | SIMPLE | part_ts | NULL | eq_ref | PRIMARY | PRIMARY | 8 | mysql.part.tablespace_id | 1 | 100.00 | NULL | | 1 | SIMPLE | ts | NULL | ALL| PRIMARY | NULL| NULL| NULL | 12605 | 100.00 | Using join buffer (Block Nested Loop) | | 1 | SIMPLE | tsf | NULL | ref| tablespace_id | tablespace_id | 8 | mysql.ts.id | 1 | 100.00 | Using where | | 1 | SIMPLE | sub_part| NULL | ref| parent_partition_id | parent_partition_id | 9 | mysql.part.id | 13152 | 100.00 | NULL | | 1 | SIMPLE | sub_part_ts | NULL | eq_ref | PRIMARY | PRIMARY | 8 | mysql.sub_part.tablespace _id | 1 | 100.00 | Using where | | 1 | SIMPLE | ts | NULL | eq_ref | PRIMARY,name| name| 779 | func | 1 | 100.00 | Using where | | 1 | SIMPLE | tsf | NULL | ref| tablespace_id | tablespace_id | 8 | mysql.ts.id | 1 | 100.00 | Using where; End temporary | ++-+-+++-+-+-+-- +---+--+---+ The probelm seems to happen only when i dump the whole database, single tables are ok. re, wh -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Enterprise Backup 8.0.15 has been released
Dear MySQL users, MySQL Enterprise Backup 8.0.15, 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.15 supports only the MySQL Server 8.0.15. 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.15 is given below. Enjoy! -- Changes in MySQL Enterprise Backup 8.0.15 (2019-02-01) This release contains no functional changes and is published to align version number with the MySQL Server 8.0.15 release. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Router 8.0.15 for MySQL Server 8.0 and 5.7 has been released
Dear MySQL users, MySQL Router 8.0.15 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.15. 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.15, 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.15 (2019-02-01) This release contains no functional changes and is published to align version number with the MySQL Server 8.0.15 release. -- 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.15 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.15, 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.15 (2019-02-01, General Availability) This release contains no functional changes and is published to align version number with the MySQL Server 8.0.15 release. 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/J 8.0.15 has been released
Dear MySQL users, MySQL Connector/J Version 8.0.15 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-15.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.15 GA, see the "Generally Available (GA) Releases" tab at http://dev.mysql.com/downloads/connector/j/ Enjoy! Changes in MySQL Connector/J 8.0.15 (2019-02-01, General Availability) Functionality Added or Changed * Default value of the connection property allowLoadLocalInfile has been changed to false. Applications that use the LOAD DATA LOCAL INFILE (http://dev.mysql.com/doc/refman/8.0/en/load-data.html) statement on MySQL Server needs to set this property to true explicitly. (Bug #29261254) Enjoy and thanks for the support! 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 Workbench 8.0.15 has been released
Dear MySQL users, The MySQL developer tools team announces 8.0.15 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 of platforms from our download pages at: http://dev.mysql.com/downloads/tools/workbench/ Enjoy! Changes in MySQL Workbench 8.0.15 (2019-02-01, General Availability) This release contains no functional changes and is published to align version number with the MySQL Server 8.0.15 release. On Behalf of Oracle/MySQL Release Engineering Team, Prashant Tekriwal -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/NET 8.0.15 has been released
Dear MySQL users, MySQL Connector/NET 8.0.15 is the third version to support Entity Framework Core 2.1 and the fifth 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.15, 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.15 (2019-02-01) Bugs Fixed * The client library has been modified to initialize the MySqlBulkLoader class with the local-infile capability disabled by default (see Using the BulkLoader Class (http://dev.mysql.com/doc/connector-net/en/connector-net-programming-bulk-loader.html)). (Bug #29259767) On Behalf of MySQL Release Engineering Team, Surabhi Bhat
MySQL Shell 8.0.15 for MySQL Server 8.0 and 5.7 has been released
Dear MySQL users, MySQL Shell 8.0.15 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.15. 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.15, 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.15 (2019-02-01) This release contains no functional changes and is published to align version number with the MySQL Server 8.0.15 release. On Behalf of Oracle/MySQL Release Engineering Team, Balasubramanian Kandasamy
MySQL Community Server 8.0.15 has been released
Dear MySQL users, MySQL Server 8.0.15, a new version of the popular Open Source Database Management System, has been released. MySQL 8.0.15 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.15 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.15 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.15 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/ [At the time of this announcement, the 8.0.15 Installer has not yet been uploaded but it will arrive within a few days] along with .ZIP (no-install) packages for more advanced needs. 8.0.15 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.14. It may also be viewed online at http://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-15.html Enjoy! == Changes in MySQL 8.0.15 (2019-02-01, General Availability) Bugs Fixed * Group Replication was unable to function in the 8.0.14 release of MySQL Server if IPv6 support was disabled at the operating system level, even if the replication group did not use any IPv6 addresses. The issue is fixed by this release of MySQL Server, 8.0.15. (Bug #29249542, Bug #94004) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/ODBC 5.3.12 has been released
Dear MySQL users, MySQL Connector/ODBC 5.3.12, a new version of the ODBC driver for the MySQL database management system, has been released. 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 version from 5.5. This is the sixth release of the MySQL ODBC driver 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 http://dev.mysql.com/downloads/connector/odbc/5.3.html For information on installing, please see the documentation at http://dev.mysql.com/doc/connector-odbc/en/connector-odbc-installation.html Changes in MySQL Connector/ODBC 5.3.12 (2019-01-28, 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. Bugs Fixed * Dynamic linking (-DCLIENT_STATIC_LINKING:BOOL=false) was not functioning, and updating to the most recent MySQL Server 5.7 headers restored this functionality. (Bug #28609434, Bug #92319, Bug #91841) * Calling SQLBulkOperations with no_ssps set to 0 and cursortype set to SQL_CURSOR_DYNAMIC would cause an unexpected halt when using the generic Linux binaries. (Bug #28289320) On Behalf of Oracle/MySQL Release Engineering Team, Balasubramanian Kandasamy
MySQL Cluster 7.6.9 has been released
Dear MySQL Users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance (with optional checkpointing to disk) - Transparent Auto-Sharding - Read & write scalability - Active-Active/Multi-Master geographic replication - 99.999% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http, Memcached and JavaScript/Node.js) MySQL Cluster 7.6.9 has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. MySQL Cluster 7.6 is also available from our repository for Linux platforms, go here for details: http://dev.mysql.com/downloads/repo/ The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.6/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime and agility. More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! == Changes in MySQL NDB Cluster 7.6.9 (5.7.25-ndb-7.6.9) (2019-01-22, General Availability) MySQL NDB Cluster 7.6.9 is a new release of NDB 7.6, based on MySQL Server 5.7 and including features in version 7.6 of the NDB storage engine, as well as fixing recently discovered bugs in previous NDB Cluster releases. Obtaining NDB Cluster 7.6. NDB Cluster 7.6 source code and binaries can be obtained from https://dev.mysql.com/downloads/cluster/. For an overview of changes made in NDB Cluster 7.6, see What is New in NDB Cluster 7.6 (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-what-is-new-7-6.html). This release also incorporates all bug fixes and changes made in previous NDB Cluster releases, as well as all bug fixes and feature changes which were added in mainline MySQL 5.7 through MySQL 5.7.25 (see Changes in MySQL 5.7.25 (2019-01-21, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-25.html)). Bugs Fixed * Important Change: When restoring to a cluster using data node IDs different from those in the original cluster, ndb_restore tried to open files corresponding to node ID 0. To keep this from happening, the --nodeid and --backupid options---neither of which has a default value---are both now explicitly required when invoking ndb_restore. (Bug #28813708) * Packaging; MySQL NDB ClusterJ: libndbclient was missing from builds on some platforms. (Bug #28997603) * NDB Replication: A DROP DATABASE operation involving certain very large tables could lead to an unplanned shutdown of the cluster. (Bug #28855062) * NDB Replication: When writes on the master---done in such a way that multiple changes affecting BLOB column values belonging to the same primary key were part of the same epoch---were replicated to the slave, Error 1022 occurred due to constraint violations in the NDB$BLOB_id_part table. (Bug #28746560) * NDB Cluster APIs: When the NDB kernel's SUMA block sends a TE_ALTER event, it does not keep track of when all fragments of the event are sent. When NDB receives the event, it buffers the fragments, and processes the event when all fragments have arrived. An issue could possibly arise for very large table definitions, when the time between transmission and reception could span multiple epochs; during this time, SUMA could send a SUB_GCP_COMPLETE_REP signal to indicate that it has sent all data for an epoch, even though in this case that is not entirely true since there may be fragments of a TE_ALTER event still waiting on the data node to be sent. Reception of the SUB_GCP_COMPLETE_REP leads to closing the buffers for that epoch. Thus, when TE_ALTER finally arrives, NDB assumes that it is a duplicate from an earlier epoch, and silently discards it. We fix the problem by making sure that the SUMA kernel block never sends a SUB_GCP_COMPLETE_REP for any epoch in which there are unsent fragments for a SUB_TABLE_DATA signal. This issue could have an impact on NDB API applications making use of TE_ALTER events. (SQL nodes do not make any use of TE_ALTER events and so they and applications using them were not affected.) (Bug #28836474) * Where a data node was restarted after a configuration change whose result was a decrease in the sum of MaxNoOfTables, MaxNoOfOrderedIndexes, and MaxNoOfUniqueHashIndexes, it sometimes failed with a mislea
MySQL Cluster 7.5.13 has been released
Dear MySQL Users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance (with optional checkpointing to disk) - Transparent Auto-Sharding - Read & write scalability - Active-Active/Multi-Master geographic replication - 99.999% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http, Memcached and JavaScript/Node.js) MySQL Cluster 7.5.13 has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.5/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime, and agility. More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! == Changes in MySQL NDB Cluster 7.5.13 (5.7.25-ndb-7.5.13) ( 2019-01-22, General Availability) MySQL NDB Cluster 7.5.13 is a new release of MySQL NDB Cluster 7.5, based on MySQL Server 5.7 and including features in version 7.5 of the NDB (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.html) storage engine, as well as fixing recently discovered bugs in previous NDB Cluster releases. Obtaining MySQL NDB Cluster 7.5. MySQL NDB Cluster 7.5 source code and binaries can be obtained from https://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL NDB Cluster 7.5, see What is New in NDB Cluster 7.5 (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-what-is-new-7-5.html). This release also incorporates all bug fixes and changes made in previous NDB Cluster releases, as well as all bug fixes and feature changes which were added in mainline MySQL 5.7 through MySQL 5.7.25 (see Changes in MySQL 5.7.25 (2019-01-21, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-25.html)). Bugs Fixed * Important Change: When restoring to a cluster using data node IDs different from those in the original cluster, ndb_restore tried to open files corresponding to node ID 0. To keep this from happening, the --nodeid (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-pro <http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndb-restore.html#option_ndb_restore_nodeid> grams-ndb-restore.html#option_ndb_restore_nodeid <http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndb-restore.html#option_ndb_restore_nodeid>) and --backupid (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-pro <http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndb-restore.html#option_ndb_restore_backupid> grams-ndb-restore.html#option_ndb_restore_backupid <http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndb-restore.html#option_ndb_restore_backupid>) options---neither of which has a default value---are both now explicitly required when invoking ndb_restore. (Bug #28813708) * Packaging; MySQL NDB ClusterJ: libndbclient was missing from builds on some platforms. (Bug #28997603) * NDB Replication: When writes on the master---done in such a way that multiple changes affecting BLOB (http://dev.mysql.com/doc/refman/5.7/en/blob.html) column values belonging to the same primary key were part of the same epoch---were replicated to the slave, Error 1022 occurred due to constraint violations in the NDB$BLOB_id_part table. (Bug #28746560) * When only the management server but no data nodes were started, RESTART ALL timed out and eventually failed. This was because, as part of a restart, ndb_mgmd starts a timer, sends a STOP_REQ signal to all the data nodes, and waits for all of them to reach node state SL_CMVMI. The issue arose becaue no STOP_REQ signals were ever sent, and thus no data nodes reached SL_CMVMI. This meant that the timer always expired, causing the restart to fail. (Bug #28728485, Bug #28698831) References: See also: Bug #11757421. * Running ANALYZE TABLE (http://dev.mysql.com/doc/refman/5.7/en/analyze-table.html) on an NDB table with an index having longer than the supported maximum length caused data nodes to fail. (Bug #28714864) * It was possible in certain cases for nodes to hang during an initial restart. (Bug #28698831) References: See also: Bug #27622643. * The output of ndb_config --configinfo (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-pro <http://dev.my
MySQL Cluster 7.5.13 has been released
Dear MySQL Users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance (with optional checkpointing to disk) - Transparent Auto-Sharding - Read & write scalability - Active-Active/Multi-Master geographic replication - 99.999% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http, Memcached and JavaScript/Node.js) MySQL Cluster 7.5.13 has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.5/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime, and agility. More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! == Changes in MySQL NDB Cluster 7.5.13 (5.7.25-ndb-7.5.13) ( 2019-01-22, General Availability) MySQL NDB Cluster 7.5.13 is a new release of MySQL NDB Cluster 7.5, based on MySQL Server 5.7 and including features in version 7.5 of the NDB (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.html) storage engine, as well as fixing recently discovered bugs in previous NDB Cluster releases. Obtaining MySQL NDB Cluster 7.5. MySQL NDB Cluster 7.5 source code and binaries can be obtained from https://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL NDB Cluster 7.5, see What is New in NDB Cluster 7.5 (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-what-is -new-7-5.html). This release also incorporates all bug fixes and changes made in previous NDB Cluster releases, as well as all bug fixes and feature changes which were added in mainline MySQL 5.7 through MySQL 5.7.25 (see Changes in MySQL 5.7.25 (2019-01-21, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-25.html)). Bugs Fixed * Important Change: When restoring to a cluster using data node IDs different from those in the original cluster, ndb_restore tried to open files corresponding to node ID 0. To keep this from happening, the --nodeid (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-pro grams-ndb-restore.html#option_ndb_restore_nodeid) and --backupid (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-pro grams-ndb-restore.html#option_ndb_restore_backupid) options---neither of which has a default value---are both now explicitly required when invoking ndb_restore. (Bug #28813708) * Packaging; MySQL NDB ClusterJ: libndbclient was missing from builds on some platforms. (Bug #28997603) * NDB Replication: When writes on the master---done in such a way that multiple changes affecting BLOB (http://dev.mysql.com/doc/refman/5.7/en/blob.html) column values belonging to the same primary key were part of the same epoch---were replicated to the slave, Error 1022 occurred due to constraint violations in the NDB$BLOB_id_part table. (Bug #28746560) * When only the management server but no data nodes were started, RESTART ALL timed out and eventually failed. This was because, as part of a restart, ndb_mgmd starts a timer, sends a STOP_REQ signal to all the data nodes, and waits for all of them to reach node state SL_CMVMI. The issue arose becaue no STOP_REQ signals were ever sent, and thus no data nodes reached SL_CMVMI. This meant that the timer always expired, causing the restart to fail. (Bug #28728485, Bug #28698831) References: See also: Bug #11757421. * Running ANALYZE TABLE (http://dev.mysql.com/doc/refman/5.7/en/analyze-table.html) on an NDB table with an index having longer than the supported maximum length caused data nodes to fail. (Bug #28714864) * It was possible in certain cases for nodes to hang during an initial restart. (Bug #28698831) References: See also: Bug #27622643. * The output of ndb_config --configinfo (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-pro grams-ndb-config.html#option_ndb_config_configinfo) --xml (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-pro grams-ndb-config.html#option_ndb_config_xml) --query-all (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-pro grams-ndb-config.html#option_ndb_config_query-all) now shows that configuration changes for the ThreadConfig (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
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 r
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 tr
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
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
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
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
ANN: Database Workbench 5.5.0 released and free Lite Edition for MySQL
Upscene releases Database Workbench 5.5.0 Upscene Productions is proud to announce the availability of the next version of the popular multi-DBMS development tool: " Database Workbench 5.5.0 " This new release brings you support for the latest versions of supported database systems, that includes PostgreSQL 11, InterBase 2017 and MySQL 8. There's also a new release of the free Lite Edition for MySQL: version 5.4.6 has been made available today. Database Workbench 5 comes in multiple editions with different pricing models, there's always a version that suits you! Here's the full list of changes http://www.upscene.com/go/?go=tracker=5.5.0=12 and for version 5.4.x http://www.upscene.com/go/?go=tracker=5.4.x=12 For more information, see What's new in Database Workbench 5? ( http://www.upscene.com/database_workbench/whatsnew ) Database Workbench supports MySQL, MariaDB, Firebird, Oracle, MS SQL Server, SQL Anywhere, NexusDB, PostgreSQL and InterBase, comes in multiple editions and is licensed based on selectable modules. It includes tools for database design, database maintenance, testing, data transfer, data import & export, database migration, database compare and numerous other tools. About Database Workbench Database Workbench is a database developer tool, over 12 years in the making and is being used by thousands of developers across the globe who have come to rely on it every day. From database design, implementation, to testing and debugging, it will aid you in your daily database work. About Upscene Productions Based in The Netherlands, Europe, this small but dedicated company has been providing database developers with useful tools for over 14 years. Slowly expanding the product portfolio and gaining recognition amongst InterBase and Firebird database developers, they now offer tools for a whole range of database systems, including Oracle and Microsoft SQL Server.
MySQL Cluster Manager 1.4.7 has been released
Dear MySQL Users, MySQL Cluster Manager 1.4.7 can be downloaded from the My Oracle Support (MOS) website. It will also be available on Oracle Software Delivery Cloud at http://edelivery.oracle.com <http://edelivery.oracle.com>with the next monthly update MySQL Cluster Manager is an optional component of the MySQL Cluster Carrier Grade Edition, providing a command-line interface that automates common management tasks, including the following online operations: - Configuring and starting MySQL Cluster - Upgrades - Adding and removing cluster nodes - Adding and removing site hosts - Configuration changes - Backup and restore MySQL Cluster Manager is a commercial extension to the MySQL family of products. More details can be found at http://www.mysql.com/products/cluster/mcm/. A brief summary of changes in MySQL Cluster Manager version 1.4.7 is listed below: Changes in MySQL Cluster Manager 1.4.7 (2018-12-14) * Functionality Added or Changed * Bugs Fixed *Functionality Added or Changed* * Agent: Performance has been improved for the add package command by removing unnecessary queries from its execution process. (Bug #28950231) * Agent: The initialization script for mcmd now cleans up the temporary files it creates under the tmp directory while starting new mcmd processes. (Bug #28924059) * Agent: The list hosts command now returns, in addition to Available and Unavailable, two more possible statuses for the agent of a host: + Recovery: The agent is in the process of recovering itself + Unresponsive: The agent rejected an attempt to connect (Bug #28438155) * Agent: The option --core-file (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-program-options-common.html#option_ndb_common_core-file), when used at the command line to start a node in a wild cluster, now causes the import cluster and update process commands to give a warning (that the option "may be removed on next restart of the process"), instead of causing the commands to fail. See Creating and Configuring the Target Cluster (http://dev.mysql.com/doc/mysql-cluster-manager/1.4/en/mcm-using-import-cluster-create-configure.html) for details. (Bug #28177366) * Agent: The import cluster and update process commands now support a new --remove-angel option, which kills any angel processes for the data nodes to be imported or updated and also updates the data nodes' PID files. See descriptions for the two commands for details. (Bug #28116279) * Agent: The backup cluster command finishes faster now, as some unnecessary wait time has been eliminated from the backup process. (Bug #27986443) * Agent: A new option for mcmd, --initial, allows an agent that has fallen into an inconsistent state to recover its configuration from other agents. See the description for --initial for details. (Bug #20892397) * Agent: The set, get, and reset commands now support the following command-line-only attributes, which can only be configured at the command line when outside MySQL Cluster Manager: + For ndb_mgmd: --core-file, --log-name, --verbose + For ndbd and ndbmtd: --core-file, -- --verbose * Agent: The internal mechanism for agent recovery (http://dev.mysql.com/doc/mysql-cluster-manager/1.4/en/mcm-using-restore-agent.html) has been improved, making it more robust and less error-prone. * Client: To reduce the size of the mcmd log, node events are no longer dumped into the log during a cluster restart. (Bug #28843656) * Client: The message for ERROR 5200 ("Restore cannot be performed ...") has been expanded to include the reason for the restore's failure. (Bug #25075284) * Client: The message for ERROR 5017 has been expanded to include the reason for an action being invalid for a process or cluster. (Bug #22777846) *Bugs Fixed* * Agent: During a rolling restart for a cluster (which takes place, for example, after a cluster reconfiguration), the node group IDs for some data nodes might become some invalid numbers transiently, and that might cause mcmd to throw an internal error (Error 1003). With this fix, such transient changes of node group IDs are ignored by mcmd, and no error is thrown. (Bug #28949173) * Agent: An update process command on a mysqld node failed with a timeout if the node was in the status of stopping. It was because mcmd did not retry stopping the node, and this fix makes it do so in the situation. (Bug #28913525) * Agent: After a cluster reconfiguration failed, the restart of an mcmd agent that had lost contac
Re: [ANN] Mroonga 8.09 - Fast fulltext search for all languages on MySQL
Hi, Sorry, There was wrong release information in Mroonga 8.09. The MySQL 8 is not supported. That is still being handled. On 2018/11/29 14:12, Horimoto Yasuhiro wrote: > Hi, > > Mroonga 8.09 has been released! > > Mroonga is a MySQL storage engine that supports fast fulltext search > and geolocation search. It is CJK ready. It uses Groonga as a storage > and fulltext search engine. > > Document: >http://mroonga.org/docs/ > > How to install: Install Guide >http://mroonga.org/docs/install.html > > How to upgrade: Upgrade Guide >http://mroonga.org/docs/upgrade.html > > Blog: >http://mroonga.org/en/blog/2018/11/29/mroonga-8.09.html > > Changes: >http://mroonga.org/docs/news.html#release-8.09 > > Here are some topics in this release. > > * Supported Ubuntu 18.10 (Cosmic Cuttlefish). > * Supported MariaDB 10.3.10. > * Supported MariaDB 10.2.19 > * Supported MariaDB 10.1.37 > * Supported Percona Server 5.7.23-25. > * Supported MariaDB 10.3.11. > * Supported MySQL 5.6.42. > * Supported MySQL 5.7.24. > * Supported MySQL 8. > > Regards, > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
[ANN] Mroonga 8.09 - Fast fulltext search for all languages on MySQL
Hi, Mroonga 8.09 has been released! Mroonga is a MySQL storage engine that supports fast fulltext search and geolocation search. It is CJK ready. It uses Groonga as a storage and fulltext search engine. Document: http://mroonga.org/docs/ How to install: Install Guide http://mroonga.org/docs/install.html How to upgrade: Upgrade Guide http://mroonga.org/docs/upgrade.html Blog: http://mroonga.org/en/blog/2018/11/29/mroonga-8.09.html Changes: http://mroonga.org/docs/news.html#release-8.09 Here are some topics in this release. * Supported Ubuntu 18.10 (Cosmic Cuttlefish). * Supported MariaDB 10.3.10. * Supported MariaDB 10.2.19 * Supported MariaDB 10.1.37 * Supported Percona Server 5.7.23-25. * Supported MariaDB 10.3.11. * Supported MySQL 5.6.42. * Supported MySQL 5.7.24. * Supported MySQL 8. Regards, -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Encryption-at-rest capability
Hi MySQL Community, Greetings ! I have a query regarding encryption-at-rest feature in MySQL Community Edition - What i understand is that Encryption-at-rest is supported from MySQL-5.7.11 community edition and only on file-per-table basis which means encryption at table-level can be implemented - is that correct ? Also, if you can help us understand the security compliance requirements (like PCI-DSS etc.) this encryption can satisfy, that would be great. Thanks in advance ! Please confirm ! Regards, Ven
In MySQL 8, how do you distinguish between Roles and Users in table mysql.user?
Hi there, In MySQL 8, how can you figure out if an entry in the mysql.user table is a role or a user? With regards, Martijn Tonies Upscene Productions http://www.upscene.com Database Workbench - developer tool for Oracle, MS SQL Server, PostgreSQL, SQL Anywhere, MySQL, InterBase, NexusDB and Firebird.
MySQL Cluster 7.6.8 has been released
Dear MySQL Users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance (with optional checkpointing to disk) - Transparent Auto-Sharding - Read & write scalability - Active-Active/Multi-Master geographic replication - 99.999% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http, Memcached and JavaScript/Node.js) MySQL Cluster 7.6.8, has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. MySQL Cluster 7.6 is also available from our repository for Linux platforms, go here for details: http://dev.mysql.com/downloads/repo/ The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.6/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime and agility. More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! Changes in MySQL NDB Cluster 7.6.8 (5.7.24-ndb-7.6.8) (2018-10-23, General Availability) MySQL NDB Cluster 7.6.8 is a new release of NDB 7.6, based on MySQL Server 5.7 and including features in version 7.6 of the NDB storage engine, as well as fixing recently discovered bugs in previous NDB Cluster releases. Obtaining NDB Cluster 7.6. NDB Cluster 7.6 source code and binaries can be obtained from https://dev.mysql.com/downloads/cluster/. For an overview of changes made in NDB Cluster 7.6, see What is New in NDB Cluster 7.6 (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-what-is-new-7-6.html). This release also incorporates all bug fixes and changes made in previous NDB Cluster releases, as well as all bug fixes and feature changes which were added in mainline MySQL 5.7 through MySQL 5.7.24 (see Changes in MySQL 5.7.24 (2018-10-22, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-24.html)). Functionality Added or Changed * Performance: This release introduces a number of significant improvements in the performance of scans; these are listed here: + Row checksums help detect hardware issues, but do so at the expense of performance. NDB now offers the possibility of disabling these by setting the new ndb_row_checksum server system variable to 0; doing this means that row checksums are not used for new or altered tables. This can have a significant impact (5 to 10 percent, in some cases) on performance for all types of queries. This variable is set to 1 by default, to provide compatibility with the previous behavior. + A query consisting of a scan can execute for a longer time in the LDM threads when the queue is not busy. + Previously, columns were read before checking a pushed condition; now checking of a pushed condition is done before reading any columns. + Performance of pushed joins should see significant improvement when using range scans as part of join execution. Bugs Fixed * Packaging: Expected NDB header files were in the devel RPM package instead of libndbclient-devel. (Bug #84580, Bug #26448330) * NDB Disk Data: While restoring a local checkpoint, it is possible to insert a row that already exists in the database; this is expected behavior which is handled by deleting the existing row first, then inserting the new copy of that row. In some cases involving data on disk, NDB failed to delete the existing row. (Bug #91627, Bug #28341843) * NDB Client Programs: Removed a memory leak in NdbImportUtil::RangeList that was revealed in ASAN builds. (Bug #91479, Bug #28264144) * MySQL NDB ClusterJ: When a table containing a BLOB or a TEXT field was being queried with ClusterJ for a record that did not exist, an exception ("The method is not valid in current blob state") was thrown. (Bug #28536926) * MySQL NDB ClusterJ: A NullPointerException was thrown when a full table scan was performed with ClusterJ on tables containing either a BLOB or a TEXT field. It was because the proper object initializations were omitted, and they have now been added by this fix. (Bug #28199372, Bug #91242) * When copying deleted rows from a live node to a node just starting, it is possible for one or more of these rows to have a global checkpoint index equal to zero. If this happened at the same time that a full lo
MySQL Cluster 8.0.13-dmr has been released
Dear MySQL Users, MySQL Cluster is the distributed database combining massive scalability and high availability. It provides in-memory real-time access with transactional consistency across partitioned and distributed datasets. It is designed for mission critical applications. MySQL Cluster has replication between clusters across multiple geographical sites built-in. A shared nothing architecture with data locality awareness make it the perfect choice for running on commodity hardware and in globally distributed cloud infrastructure. This storage engine provides: - In-Memory storage - Real-time performance (with optional checkpointing to disk) - Transparent Auto-Sharding - Read & write scalability - Active-Active/Multi-Master geographic replication - Transactional consistency across partitioned and distributed datasets - Parallel cross partition queries such as joins - 99.% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http, Memcached and JavaScript/Node.js) MySQL Cluster 8.0.13-dmr, has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/8.0/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime and agility. More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! Changes in MySQL NDB Cluster 8.0.13 (2018-10-23, Development Milestone) MySQL NDB Cluster 8.0.13 is a new development release of NDB 8.0, based on MySQL Server 8.0 and including features in version 8.0 of the NDB storage engine, as well as fixing recently discovered bugs in previous NDB Cluster releases. Obtaining NDB Cluster 8.0. NDB Cluster 8.0 source code and binaries can be obtained from https://dev.mysql.com/downloads/cluster/. For an overview of changes made in NDB Cluster 8.0, see What is New in NDB Cluster 8.0 (http://dev.mysql.com/doc/refman/8.0/mysql-cluster-what-is-new.html). This release also incorporates all bug fixes and changes made in previous NDB Cluster releases, as well as all bug fixes and feature changes which were added in mainline MySQL 8.0 through MySQL 8.0.13 (see Changes in MySQL 8.0.13 (2018-10-22) (http://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-13.html)). * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * Important Change; NDB Disk Data: The following changes are made in the display of information about Disk Data files in the INFORMATION_SCHEMA.FILES table: + Tablespaces and log file groups are no longer represented in the FILES table. (These constructs are not actually files.) + Each data file is now represented by a single row in the FILES table. Each undo log file is also now represented in this table by one row only. (Previously, a row was displayed for each copy of each of these files on each data node.) + For rows corresponding to data files or undo log files, node ID and undo log buffer information is no longer displayed in the EXTRA column of the FILES table. * Important Change; NDB Client Programs: Removed the deprecated --ndb option for perror. Use ndb_perror to obtain error message information from NDB error codes instead. (Bug #81705, Bug #23523957) References: See also: Bug #81704, Bug #23523926. * Important Change: Beginning with this release, MySQL NDB Cluster is being developed in parallel with the standard MySQL 8.0 server under a new unified release model with the following features: + NDB 8.0 is developed in, built from, and released with the MySQL 8.0 source code tree. + The numbering scheme for NDB Cluster 8.0 releases follows the scheme for MySQL 8.0, starting with the current MySQL release (8.0.13). + Building the source with NDB support appends -cluster to the version string returned by mysql -V, as shown here: shell≫ mysql -V mysql Ver 8.0.13-cluster for Linux on x86_64 (Source distribution) NDB binaries continue to display both the MySQL Server version and the NDB engine version, like this: shell> ndb_mgm -V MySQL distrib mysql-8.0.13 ndb-8.0.13-dmr, for Linux (x86_64) In MySQL Cluster NDB 8.0, these two version numbers are always the same. To build the MySQL 8.0.13 (or later) source w
MySQL Cluster 7.5.12 has been released
Dear MySQL Users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance (with optional checkpointing to disk) - Transparent Auto-Sharding - Read & write scalability - Active-Active/Multi-Master geographic replication - 99.999% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http, Memcached and JavaScript/Node.js) MySQL Cluster 7.5.12, has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.5/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime and agility. More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! == Changes in MySQL NDB Cluster 7.5.12 (5.7.24-ndb-7.5.12) (2018-10-23, General Availability) MySQL NDB Cluster 7.5.12 is a new release of MySQL NDB Cluster 7.5, based on MySQL Server 5.7 and including features in version 7.5 of the NDB (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.html) storage engine, as well as fixing recently discovered bugs in previous NDB Cluster releases. Obtaining MySQL NDB Cluster 7.5. MySQL NDB Cluster 7.5 source code and binaries can be obtained from https://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL NDB Cluster 7.5, see What is New in NDB Cluster 7.5 (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-what-is-new-7-5.html). This release also incorporates all bug fixes and changes made in previous NDB Cluster releases, as well as all bug fixes and feature changes which were added in mainline MySQL 5.7 through MySQL 5.7.24 (see Changes in MySQL 5.7.24 (2018-10-22, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-24.html)). Bugs Fixed * Packaging: Expected NDB header files were in the devel RPM package instead of libndbclient-devel. (Bug #84580, Bug #26448330) * MySQL NDB ClusterJ: When a table containing a BLOB (http://dev.mysql.com/doc/refman/5.7/en/blob.html) or a TEXT (http://dev.mysql.com/doc/refman/5.7/en/blob.html) field was being queried with ClusterJ for a record that did not exist, an exception ("The method is not valid in current blob state") was thrown. (Bug #28536926) * MySQL NDB ClusterJ: A NullPointerException was thrown when a full table scan was performed with ClusterJ on tables containing either a BLOB or a TEXT field. It was because the proper object initializations were omitted, and they have now been added by this fix. (Bug #28199372, Bug #91242) * When the SUMA kernel block receives a SUB_STOP_REQ signal, it executes the signal then replies with SUB_STOP_CONF. (After this response is relayed back to the API, the API is open to send more SUB_STOP_REQ signals.) After sending the SUB_STOP_CONF, SUMA drops the subscription if no subscribers are present, which involves sending multiple DROP_TRIG_IMPL_REQ messages to DBTUP. LocalProxy can handle up to 21 of these requests in parallel; any more than this are queued in the Short Time Queue. When execution of a DROP_TRIG_IMPL_REQ was delayed, there was a chance for the queue to become overloaded, leading to a data node shutdown with Error in short time queue. This issue is fixed by delaying the execution of the SUB_STOP_REQ signal if DBTUP is already handling DROP_TRIG_IMPL_REQ signals at full capacity, rather than queueing up the DROP_TRIG_IMPL_REQ signals. (Bug#26574003) * Having a large number of deferred triggers could sometimes lead to job buffer exhaustion. This could occur due to the fact that a single trigger can execute many operations---for example, a foreign key parent trigger may perform operations on multiple matching child table rows---and that a row operation on a base table can execute multiple triggers. In such cases, row operations are executed in batches. When execution of many triggers was deferred---meaning that all deferred triggers are executed at pre-commit---the resulting concurrent execution of a great many trigger operations could cause the data node job buffer or send buffer to be exhausted, leading to failure of the node. This issue is fixed by limiting the number of concurrent trigger oper
MySQL Connector/NET 8.0.13 has been released
Dear MySQL users, MySQL Connector/NET 8.0.13 is the first version to support Entity Framework Core 2.1 and the third 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. 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.13, 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.13 (2018-10-22, General Availability) * Important Changes * Functionality Added or Changed * Bugs Fixed *Important Changes* * The default value for the SslMode connection option now differs based on the protocol used to make the connection. The Preferred mode has been reintroduced in this release (see Options for Both Classic MySQL Protocol and X Protocol (http://dev.mysql.com/doc/connector-net/en/connector-net- <http://dev.mysql.com/doc/connector-net/en/connector-net-8-0-connection-options.html#connector-net-8-0-connection-options-classic-xprotocol>8-0-connection-options.html#connector-net-8-0-connection- <http://dev.mysql.com/doc/connector-net/en/connector-net-8-0-connection-options.html#connector-net-8-0-connection-options-classic-xprotocol>options-classic-xprotocol <http://dev.mysql.com/doc/connector-net/en/connector-net-8-0-connection-options.html#connector-net-8-0-connection-options-classic-xprotocol>). To summarize the defaultSslmode values in the Connector/NET 8.0 (and 7.0) releaseseries: Connector/NET 8.0.13: Preferred mode is the default for classic MySQL protocol connections only. Required mode is the default for X Protocol connections only (Preferred mode is not available for use with X Protocol). Connector/NET 8.0.8 to 8.0.12: Preferred mode is not supported for any connections. Required mode is the default for both classic MySQL protocol and X Protocol connections. Connector/NET 7.0.0 to 7.0.7: Preferred mode is the default for both classic MySQL protocol and X Protocol connections. (Bug #28687769) *Functionality Added or Changed* * Document Store: An incremental improvement was made to the performance of session creation with a connection string. (Bug #28343655) * Support for EF Core 2.1 was added to Connector/NET 8.0.13 and support for EF Core 2.0 was discontinued in the same connector version. Other versions of Connector/NET continue to support EF Core 2.0 (see Entity Framework Core Support (http://dev.mysql.com/doc/connector-net/en/connector-net- <http://dev.mysql.com/doc/connector-net/en/connector-net-entityframework-core.html>entityframework-core.html <http://dev.mysql.com/doc/connector-net/en/connector-net-entityframework-core.html>). * The ConnectionTimeout connection option and property were reimplemented as the Connect-Timeout option (and the ConnectTimeout property) for X Protocol operations. Some aspects of the timeout behavior were changed (see Options for X Protocol Only (http://dev.mysql.com/doc/connector-net/en/connector-net- <http://dev.mysql.com/doc/connector-net/en/connector-net-8-0-connection-options.html#connector-net-8-0-connection-options-xprotocol>8-0-connection-options.html#connector-net-8-0-connection- <http://dev.mysql.com/doc/connector-net/en/connector-net-8-0-connection-options.html#connector-net-8-0-connection-options-xprotocol>options-xprotocol <http://dev.mysql.com/doc/connector-net/en/connector-net-8-0-connection-options.html#connector-net-8-0-connection-options-xprotocol>). The new ConnectTimeout property was added to the MySqlX.XDevAPI.MySqlXConnectionStringBuilder class and the existing ConnectionTimeout property was removed. No modifications were made to the existing implementation of the ConnectionTimeout option (or property) for cl
MySQL Community Server 5.5.62 has been released
Dear MySQL users, MySQL Server 5.5.62 is a new version of the 5.5 production release of the world's most popular open source database. MySQL 5.5.62 is recommended for use on production systems. MySQL 5.5 includes several high-impact enhancements to improve the performance and scalability of the MySQL Database, taking advantage of the latest multi-CPU and multi-core hardware and operating systems. In addition, with release 5.5, InnoDB is now the default storage engine for the MySQL Database, delivering ACID transactions, referential integrity and crash recovery by default. MySQL 5.5 also provides a number of additional enhancements including: - Significantly improved performance on Windows, with various Windows specific features and improvements - Higher availability, with new semi-synchronous replication and Replication Heartbeat - Improved usability, with Improved index and table partitioning, SIGNAL/RESIGNAL support and enhanced diagnostics, including a new Performance Schema monitoring capability. For a more complete look at what's new in MySQL 5.5, please see the following resources: Documentation: http://dev.mysql.com/doc/refman/5.5/en/mysql-nutshell.html If you are running a MySQL production level system, we would like to direct your attention to MySQL Enterprise Edition, which includes the most comprehensive set of MySQL production, backup, monitoring, modeling, development, and administration tools so businesses can achieve the highest levels of MySQL performance, security and uptime. http://mysql.com/products/enterprise/ For information on installing MySQL 5.5.62 on new servers, please see the MySQL installation documentation at http://dev.mysql.com/doc/refman/5.5/en/installing.html For upgrading from previous MySQL releases, please see the important upgrade considerations at: http://dev.mysql.com/doc/refman/5.5/en/upgrading.html MySQL Database 5.5.62 is available in source and binary form for a number of platforms from our download pages at: http://dev.mysql.com/downloads/mysql/ The following link lists the changes in the MySQL source code since the previous released version of MySQL 5.5. It may also be viewed online at: http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-62.html This is the last update to be published for MySQL Server 5.5. To continue receiving updates for this product, you will need to upgrade to at least version 5.6. Enjoy! Changes in MySQL 5.5.62 (2018-10-22, General availability) Functionality Added or Changed * Previously, file I/O performed in the I/O cache in the mysys library was not instrumented, affecting in particular file I/O statistics reported by the Performance Schema about the binary log index file. Now, this I/O is instrumented and Performance Schema statistics are accurate. Thanks to Yura Sorokin for the contribution. (Bug #27788907, Bug #90264) * The zlib library version bundled with MySQL was raised from version 1.2.3 to version 1.2.11. MySQL implements compression with the help of the zlib library. The zlib compressBound() function in zlib 1.2.11 returns a slightly higher estimate of the buffer size required to compress a given length of bytes than it did in zlib version 1.2.3. The compressBound() function is called by InnoDB functions that determine the maximum row size permitted when creating compressed InnoDB tables or inserting rows into compressed InnoDB tables. As a result, CREATE TABLE ... ROW_FORMAT=COMPRESSED or INSERT operations with row sizes very close to the maximum row size that were successful in earlier releases could now fail. Bugs Fixed * MySQL Server and test RPM packages were missing perl-Data-Dumper as a dependency. (Bug #28144933, Bug #72926) * For the mysql client, the -b short option was associated with two long options, --no-beep and --binary-as-hex. The -b option now is associated only with --no-beep. (Bug #28093271) * During server startup/shutdown, PID files could be mishandled. (Bug #27919254) * For MEMORY tables, memory overflow errors could occur. (Bug #27799513) * When converting from a BLOB (or TEXT) type to a smaller BLOB (or TEXT) type, no warning or error was reported informing about the truncation or data loss. Now an appropriate error is issued in strict SQL mode and a warning in nonstrict SQL mode. (Bug #27788685, Bug #90266) * ALTER TABLE ... REORGANIZE PARTITION ... could result in incorrect behavior if any partition other than the last was missing the VALUES LESS THAN part of the syntax. (Bug #26791931) On Behalf of the MySQL/Oracle Release Engineering Team, Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http
MySQL Workbench 8.0.13 has been released
Dear MySQL users, The MySQL developer tools team announces 8.0.13 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.13 (2018-10-22, General Availability) * Server Support * Functionality Added or Changed * Bugs Fixed Server Support * Support for MySQL 5.5 by MySQL Workbench 8.0 was removed. If you still need to use MySQL Workbench on a MySQL 5.5 server, you can use MySQL Workbench 6.3, which is available from MySQL Product Archives (see https://downloads.mysql.com/archives/workbench/). Functionality Added or Changed * MySQL Workbench on macOS 10.14 Mojave was tested with positive results. The new Dark Mode feature is not yet compatible with all screens and should not be enabled for this release. Bugs Fixed * With valid geometry points inserted, the option to open the points in a browser failed on macOS hosts because the URL was improperly formed. (Bug #28587193, Bug #92266) * An apostrophe character (') within a table comment generated a parsing error when an attempt was made to alter the table. (Bug #28552873, Bug #92191) * Insufficient privilege was granted during the attempt to create a new MySQL Enterprise Backup user account. Although valid prerequisite backup information was provided, the validation script returned the following error message: Access denied for backup account. (Bug #28536272, Bug #92115) * When remote management with SSH was enabled, attempting to insert the required passwords in the Options file produced an error message. After the error was closed, the Administration tab became unresponsive and MySQL Workbench did not shut down properly. (Bug #28519087, Bug #92061) * An error with the following message was generated when the export operation was executed on tables from an earlier server version: Unknown table 'COLUMN_STATISTICS' in information_schema (1109). Because the version of mysqldump used with the operation can differ from that of the target server, some features may not be exported as expected when the versions are mismatched. A warning message now provides a description of the condition, along with instructions to resolve the version mismatch, or the option to continue anyway. (Bug #28471433, Bug #91640) * On Windows hosts, the history of scheduled MySQL Enterprise Backup jobs was not persisted in the dashboard between MySQL Workbench sessions. This fix eliminates the issue; however, the existing mysqlwbmeb.vbs file must be removed before scheduling new backup jobs. (Bug #28430457) * The default target version of MySQL to use with MySQL Workbench models was set to MySQL 5.6.30 and did not increment automatically. With this fix, the value now defaults to the latest version. The default target version can also be set manually (see Preferences: Modeling: MySQL (http://dev.mysql.com/doc/workbench/en/wb-preferences-mod eling.html#wb-preferences-modeling-mysql)). (Bug #28397515, Bug #91782) * Executing queries over an period of time caused the existing result grid in each query tab to be hidden when the grid was previously visible and prevented the results grid in new tabs from showing. (Bug #28361489, Bug #91265) * After copying a query into a second query editor, auto-completion did not display the related column names. Instead, when auto-completion was engaged, MySQL Workbench stopped working. (Bug #28312867, Bug #91559) * The operation to compare schemas did not appear in the menu after a valid model was opened on Linux hosts. (Bug #28249454) * The filter arrows that select objects for forward or reverse engineering within wizards generated an error instead of moving the objects as expected. (Bug #26435349, Bug #26922638, Bug #87980, Bug #25921645, Bug #86013, Bug #25852505, Bug #85837, Bug #25741519, Bug #85522) * Schema privileges in the Administration - Users and Privileges tab (Object Rights, DDL Rights, and Other Rights) were not visible with all screen resolutions. (Bug #25584920, Bug #85079) * The color used to highlight a selected item in the schema tree view did not provide enough contrast from the background
MySQL Community Server 5.6.42 has been released
Dear MySQL users, MySQL Server 5.6.42, a new version of the popular Open Source Database Management System, has been released. MySQL 5.6.42 is recommended for use on production systems. This release also incorporates all bug fixes and changes made in previous NDB Cluster releases, as well as all bug fixes and feature changes which were added in mainline MySQL 5.5 through MySQL 5.5.62 (see Changes in MySQL 5.5.62 (Not yet released, General availability) (http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-62.html)). 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.42 on new servers or upgrading to MySQL 5.6.42 from previous MySQL releases, please see http://dev.mysql.com/doc/refman/5.6/en/installing.html MySQL Server is available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/ Not all mirror sites may be up to date at this point in time, so if you can't find this version on some mirror, please try again later or choose another download site. We welcome and appreciate your feedback, bug reports, bug fixes, patches, etc: https://wikis.oracle.com/display/mysql/Contributing The following link lists the changes in the MySQL 5.6 since the release of MySQL 5.6.41. It may also be viewed online at http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-42.html Enjoy! Changes in MySQL 5.6.42 (2018-10-22, General Availability) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * Previously, file I/O performed in the I/O cache in the mysys library was not instrumented, affecting in particular file I/O statistics reported by the Performance Schema about the binary log index file. Now, this I/O is instrumented and Performance Schema statistics are accurate. Thanks to Yura Sorokin for the contribution. (Bug #27788907, Bug #90264) * The zlib library version bundled with MySQL was raised from version 1.2.3 to version 1.2.11. MySQL implements compression with the help of the zlib library. The zlib compressBound() function in zlib 1.2.11 returns a slightly higher estimate of the buffer size required to compress a given length of bytes than it did in zlib version 1.2.3. The compressBound() function is called by InnoDB functions that determine the maximum row size permitted when creating compressed InnoDB tables or inserting rows into compressed InnoDB tables. As a result, CREATE TABLE ... ROW_FORMAT=COMPRESSED or INSERT operations with row sizes very close to the maximum row size that were successful in earlier releases could now fail. If you have compressed InnoDB tables with large rows, it is recommended that you test compressed table CREATE TABLE statements on a MySQL 8.0.3 test instance prior to upgrading. Bugs Fixed * InnoDB: An ALTER TABLE operation that added a primary key produced a segmentation fault. (Bug #28395278) References: This issue is a regression of: Bug #27753193. * InnoDB: An assertion was raised during an OPTIMIZE TABLE operation. (Bug #27753193) * InnoDB: A foreign key constraint name was duplicated during a rename table operation, causing a failure during later query execution. (Bug #27545888) * InnoDB: The location of the Innodb Merge Temp File that reported by the wait/io/file/innodb/innodb_temp_file Performance Schema instrument was incorrect. (Bug #21339079, Bug #77519) * Replication: When FLUSH statements for specific log types (such as FLUSH SLOW LOGS) resulted in an error, the statements were still written to the binary log. This stopped replication because the error had occurred on the master, but did not occur on the slave. MySQL Server now checks on the outcome of these FLUSH statements, and if an error occurred, the statement is not written to the binary log. (Bug #24786290, Bug #83232) * Microsoft Windows: On Windows, uninstallation of the MySQL Server MSI package through MySQL Installer produced a
Benetl, a free ETL tool for MySQL, out in version 4.9
Dear all, Benetl, a free ETL tool for MySQL, is out in version 4.9. This new version is providing some code optimizations, tests coverage improvement. This version supports Java 1.8 and providesone bug correction (dist function now returns result as double type). You should really update. Benetl is freely dowloadable at:https://www.benetl.net You can learn more about ETL tools at: http://en.wikipedia.org/wiki/Extract,_transform,_load Thanks for your interest. Regards, -- Benoît Carpentier https://www.benetl.net Founder of Benetl and Java project manager
MySQL Connector/Node.js 8.0.13 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.13, 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.13 (2018-10-22, General availability) Functionality Added or Changed * To go with the existing asynchronous mysqlx.getSession(conn_str) method, a new synchronous mysqlx.getClient(conn_str, options) method was added that creates a connection pool handler that provides an asynchronous getSession() method to create and retrieve connections from the pool. The collection pooling options are: + enabled: enables or disables connection pooling; boolean and defaults to true. + maxSize: maximum number of connections available in the pool; positive integer and defaults to 25. + maxIdleTime: maximum number of milliseconds a connection can be idle in the queue before being closed; integer >= 0 and defaults to 0 (infinite). + queueTimeout: maximum number of milliseconds a request will wait for a connection to become available; integer >= 0 and defaults to 0 (infinite). This is different than connectTimeout that's used for non-pooling. In a pooling scenario, there might already be connections in the pool and queueTimeout controls how long to wait for a connection in the pool. Example usage: var mysqlx = require('@mysql/xdevapi') var client = mysqlx.getClient( { user: 'root', host: 'localhost', port: 33060 }, { pooling: { enabled: true, maxIdleTime: 5000, maxSize: 25, queueTimeout: 2 } } ); client.getSession() .then(session => { console.log(session.inspect()) return session.close() // the connection becomes idle in the client pool }) .then(() => { return client.getSession() }) .then(session => { console.log(session.inspect()) return client.close() // closes all connections and destroys the pool }) Closing a session attached to the pool makes the connection available in the pool for subsequent getSession() calls, while closing (destroying) the pool effectively closes all server connections. * Added a connection timeout query parameter. This defines the length of time (milliseconds) the client waits for a MySQL server to become available in the given network addresses. It was added to both the mysqlx.getSession() (non-pooling sessions) and mysqlx.getClient() (pooling sessions) interfaces. This option defaults to 1 (10 seconds). The value 0 disables the timeout so the client will wait until the underlying socket (platform dependent) times out. Similar to other option formatting rules, this option defined as connection-timeout (kebab-case) for URI definitions and connectionTimeout (camelCase) for plain JavaScript configuration objects. Example usage: const mysqlx = require('@mysql/xdevapi'); var client = mysqlx.getClient('root@localhost?connect-timeout=5000') client.getSession() .catch(err => { console.log(err.message) // "Connection attempt to the server was aborted. Timeout of 5000 ms was exceeded." }) // Or const mysqlx = require('@mysql/xdevapi'); var client = mysqlx.getClient('mysqlx://root:passwd@[localhost:33060, 127.0.0.1:33060]?connect-timeout=5000') client.getSession() .catch(err => { // connection could not be established after 10 seconds (5 seconds for each server) console.log(err.message); // All server connection attempts we re aborted. Timeout of 5000 ms was exc
MySQL Community Server 5.7.24 has been released
Dear MySQL users, MySQL Server 5.7.24, a new version of the popular Open Source Database Management System, has been released. MySQL 5.7.24 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.24 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.24 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.24 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.24 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.23. It may also be viewed online at http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-24.html Enjoy! Changes in MySQL 5.7.24 (2018-10-22, General Availability) Deprecation and Removal Notes * InnoDB; Partitioning: Support for placing table partitions in shared tablespaces is deprecated and will be removed in a future version of MySQL. Shared tablespaces include the system tablespace and general tablespaces. For information about identifying partitions in shared tablespaces and moving them to file-per-table tablespaces, see Preparing Your Installation for Upgrade http://dev.mysql.com/doc/refman/8.0/en/upgrade-prerequisites.html * InnoDB: Support for TABLESPACE = innodb_file_per_table and TABLESPACE = innodb_temporary clauses with CREATE TEMPORARY TABLE is deprecated and will be removed in a future MySQL version. Packaging Notes * Binary packages that include curl rather than linking to the system curl library now use curl 7.60.0 rather than 7.45.0. (Bug #28043702) Security Notes * Microsoft Windows: On Windows, MySQL Enterprise Edition distributions now bundle the Cyrus SASL library files libsasl.dll and saslSCRAM.dll so that the LDAP authentication plugins can use the SCRAM-SHA-1 authentication method. * MySQL Enterprise Edition now provides data masking and de-identification capabilities, implemented as a plugin library containing a plugin and a set of user-defined functions. Data masking hides sensitive information by replacing real values with substitutes. MySQL Enterprise Data Masking and De-Identification functions enable masking existing data using several methods such as obfuscation (removing identifying characteristics), generation of formatted random data, and data replacement or substitution. For example: mysql> SET @ssn = gen_rnd_ssn(); mysql> SET @masked_ssn1 = mask_ssn(@ssn); mysql> SET @masked_ssn2 = mask_outer(mask_inner (@ssn,4,5,'A'), 3,0,'B'); mysql> SELECT @ssn, @masked_ssn1, @masked_ssn2; +-+--+--+ | @ssn| @masked_ssn1 | @masked_ssn2 | +-+--+--+ | 980-31-2838 | XXX-XX-2838 | BBB-AA-2838 | +-+--+--+ For more information, see MySQL Enterprise Data Masking and De-Identification http://dev.mysql.com/doc/refman/8.0/en/data-masking.html Functionality Added or Changed * Previously, file I/O performed in the I/O cache in the mysys library was not instrumented, affecting in particular file I/O statistics reported by the Performance Schema about the binary log index file. Now, this I/O is instrumented and Performance Schema statistics are accurate. Thanks to Yura Sorokin for the contribution. (Bug #27788907, Bug #90264) * The zlib library version bundled with MySQL was raised from version 1.2.3 to version 1.2.11. MySQL implements compression with the help of the zlib library. The zlib compressBound() function in zlib 1.2.11 returns a slightly higher estimate of the buffer size required to compress a given length of bytes than it did in zlib version 1.2.3. The c
MySQL Connector/ODBC 8.0.13 has been released
Dear MySQL users, MySQL Connector/ODBC 8.0.13 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.13 (2018-10-22, General Availability) Functionality Added or Changed * Added dynamic libmysql linking support via the -DMYSQLCLIENT_STATIC_LINKING:BOOL=TRUE|FALSE option; defaults to FALSE to enable dynamic linking. Bugs Fixed * Fixed column metadata handling with Microsoft Access. (Bug #28670725, Bug #91856) * The following obsolete options were removed: NO_SCHEMA (use NO_CATALOG instead), DISABLE_SSL_DEFAULT (use SSLMODE instead), and SSL_ENFORCE (use SSLMODE instead). (Bug #28407520) * The ODBC Driver returned 0 for the SQL_MAX_SCHEMA_NAME_LEN attribute, and now returns 64 as the maximum length for a MySQL schema name. (Bug #28385722) * Because the MySQL ODBC driver ignored the SQL_RD_OFF value for the SQL_ATTR_RETRIEVE_DATA attribute, it incorrectly kept writing into the data buffers. This led to write access violation errors when data was written into the buffer when the user application explicitly requested not to write there. (Bug #28098219, Bug #91060) On Behalf of Oracle/MySQL Release Engineering Team, Kent Boortz -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Router 8.0.13 for MySQL Server 8.0 and 5.7 has been released
Dear MySQL users, MySQL Router 8.0.13 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.13. 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.13, 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.13 (2018-10-22) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * To align package names with MySQL Server, the community package name prefix changed from "mysql-router-" to "mysql-router-community-". This change also allows upgrading from MySQL Router 2.1 to 8.0. Additionally, a "mysql-router" meta package was added that redirects "mysql-router" to "mysql-router-community". Bugs Fixed * For SLES 12, MySQL binary distributions are now built using GCC 7. The lowest supported GCC version on this platform is now 5.3 (previously 4.8.5). Installing MySQL Router 8.0.13 or higher RPM packages on SLES 12 platforms requires that the GCC Devel repo is enabled, for example: shell> cd /etc/zypp/repos.d/ shell> wget https://download.opensuse.org/repositories/devel:/gcc/SLE-12/devel:gcc.repo ... shell> zypper install ./mysql-router-community-8.0.*rpm (Bug #28685857) References: See also: Bug #92147. * The log level was changed from INFO to DEBUG for the InnoDB cluster Metadata server and replicaset connections. Because MySQL Router's ttl configuration option defaults to 0.1, these each generate 10 log entries per second. (Bug #28424243) * Running MySQL Router against an invalid InnoDB cluster would report internal SQL errors, such as "Unknown database 'mysql_innodb_cluster_metadata'", rather than user-friendly information that the cluster is not set up as a metadata server. The generated error now clarifies the reason and points to related documentation. (Bug #28292073) * The --version output was aligned across all binaries to include license related text. (Bug #28262453) * On Windows, starting Router after uninstalling the Router service would cause Router to hang as it assumed the service was still enabled. (Bug #28261217) * Passing in --directory to an unwritable empty directory would yield a generic error. (Bug #28228800) * The error code ER_CON_COUNT_ERROR is now used instead of HY000 ("unknown") when the maximum number of allowed connections is exceeded. (Bug #28183810) * The metadata version (mysql_innodb_cluster_metadata.schema_version) compatibility check is now checked at runtime, when before it only happened during the bootstrap process. (Bug #28147601) * Bootstraping with --user set to the same user running the bootstrap operation would halt with a "setegid failed" error. (Bug #27698052) * An error related to running out of available threads was only logged once until Router was restarted. (Bug #27577694) * MySQL Router is now included in MySQL Server's source and monolithic binary packages. The MySQL Router standalone packages continue to exist, as before. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Enterprise Backup 8.0.13 has been released
Dear MySQL users, MySQL Enterprise Backup 8.0.13, 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.13 only supports MySQL Server 8.0.13. 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.13 is given below. Changes in MySQL Enterprise Backup 8.0.13 (2018-10-22) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * mysqlbackup now supports backup compression (the use of the --compress and --uncompress options) for incremental backups (except for incremental backups created with the --incremental-with-redo-log-only option). * mysqlbackup now supports transparent page compression for InnoDB tables. The support is enabled by setting the mysqlbackup option --compress-method=punch-hole; see description for the option for details. Bugs Fixed * mysqlbackup hung when a backup operation failed due to a full disk. With this fix, mysqlbackup quits gracefully in the situation by throwing an error. (Bug #28399821) * A mysqlbackup operation on an image stored on an OpenStack cloud storage service sometimes failed with a segmentation fault or a bad URL error. It was because of a race condition caused by an uninitiated variable, which has been eliminated by this fix. (Bug #28189239, Bug #28183729) * Backups for databases with encrypted InnoDB tables failed when the --compress option was used. (Bug #28177466) * A mysqlbackup operation on an image stored on an OpenStack cloud storage service failed with a 401 Unauthorized error when the operation took a long time and the authentication token for the cloud access expired. With this fix, a separate thread in mysqlbackup requests a new token from the OpenStack cloud service in that situation, so that the operation can continue. (Bug #27893174) * When an incremental backup was restored without using the --log-bin option, the binary log was not restored to its original location on the backed up server, but to the location specified by --log-bin earlier during the restore of the base backup. The same occurred for relay logs of incremental backups for slaves when the --relay-log option was not used. (Bug #27545745) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 8.0.13 has been released (part 2/2)
[This is part 2 of the announcement] Bugs Fixed * Important Note: The libevent library included with the MySQL Server was upgraded to version 2.1.8. (Bug #28207237) * InnoDB; Partitioning: Removed old InnoDB handler and partitioning code that referenced .frm files, and thus no longer had any purpose. (Bug #27995316) * InnoDB: An assertion was raised during a DROP TABLE operation. A thread that was accessing the table through the memcached API released metadata locks before releasing the table. (Bug #28531148) * InnoDB: The being_modified bit in a LOB reference was set but the bit modification was not logged, causing an assertion failure. (Bug #28443837) * InnoDB: Window functions returned incorrect results when the optimizer used the InnoDB storage engine for internal temporary tables. (Bug #28430650) * InnoDB: Adjusting the server time to an earlier time caused periodic redo flushes to be missed. (Bug #28430358, Bug #90670) * InnoDB: An ALTER TABLE operation that added a primary key produced a segmentation fault. (Bug #28395278) References: This issue is a regression of: Bug #27753193. * InnoDB: A conditional check was removed by removing the ReadView::complete() function and splitting its work among other functions. This change helps optimize performance on ARM 64-bit. (Bug #28385211, Bug #91759) * InnoDB: Leftover thread_mutex code was removed from InnoDB source code files. (Bug #28363673, Bug #91678) * InnoDB: Type changes were implemented to eliminate warnings that occurred when compiling InnoDB with Microsoft Visual Studio 2017. (Bug #28338720) * InnoDB: An invalid assertion was raised when a B-tree flag used to mark shared index locks was used to mark a shared-exclusive index lock. (Bug #28317172) * InnoDB: The sharp checkpoint mechanism no longer forces preflushing of dirty pages when requesting a checkpoint for the currently available LSN. The log checkpointer thread now takes the concurrency margin (the per thread margin for free space in the log) into account when determining if the next checkpoint write is required and whether to wake up page cleaners to force a sync-flush of dirty pages. Page cleaner threads take the concurrency margin into account when determining whether to flush dirty pages and how many pages to flush. (Bug #28297462) * InnoDB: A misplaced debug crash point caused a transaction timeout resulting in test failures. (Bug #28295814) * InnoDB: InnoDB error message format was modified to remove duplicate text. (Bug #28289789) * InnoDB: Unnecessary cycles of freeing and allocating memory caused JSON performance degradation on Windows. (Bug #28278737) * InnoDB: To avoid checking hardware support each time a hardware-optimized checksum is computed, asserts were converted to debug-only asserts. (Bug #28267334, Bug #91485) * InnoDB: A patch that combined Variance-Aware Transaction Scheduling (VATS) with functionality that releases read locks caused gap locks to be removed without granting locks to waiting transactions, resulting in transaction timeouts. (Bug #28261530) References: This issue is a regression of: Bug #28261530. * InnoDB: The log_checkpointer thread failed to write new checkpoints in a timely manner when the amount of redo was small. (Bug #28220222) * InnoDB: The server exited during an in-place upgrade from MySQL 5.7 to MySQL 8.0 due to an attempted eviction of a foreign-key-related table from the cache. At the end of the upgrade process, tables with FULLTEXT indexes were marked as ready for eviction without checking for foreign key relationships. (Bug #28212734, Bug #91325) * InnoDB: The format of the following Performance Schema and INFORMATION_SCHEMA table columns was modified: + data_locks.ENGINE_LOCK_ID + data_lock_waits.REQUESTING_ENGINE_LOCK_ID + data_lock_waits.BLOCKING_ENGINE_LOCK_ID + INNODB_TRX.TRX_REQUESTED_LOCK_ID The previous format was trx_id:table_id for table locks and trx_id:space_id:page_no:heap_no for record locks. The new format is trx_immutable_id:table_id:lock_immutable_id for table locks and trx_immutable_id:space_id:page_no:heap_no:lock_immutable_ id for record locks. lock_immutable_id and trx_immutable_id are 64-bit values that do not change during the lifetime of a lock or transaction, respectively, and are unique among other instance object IDs. (Bug #28176910) * InnoDB: The list of permitted lock mode descriptors used
MySQL Connector/C++ 8.0.13 has been released
Dear MySQL users, MySQL Connector/C++ 8.0.13 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" 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.13, see the "Generally Available (GA) Releases" tab at https://dev.mysql.com/downloads/connector/cpp/ Changes in MySQL Connector/C++ 8.0.13 (2018-10-22, General Availability) * Character Set Support * Packaging Notes * X DevAPI Notes * Functionality Added or Changed * Bugs Fixed Character Set Support * For connections to the server made using the legacy JDBC API (that is, not made using X DevAPI or X DevAPI for C), the default connection character set is now utf8mb4 rather than utf8. Connections to the server made using X DevAPI or X DevAPI for C continue to use the connection character set determined by the server. (Bug #28204677) Packaging Notes * Connector/C++ 32-bit MSI packages are now available for Windows. These 32-bit builds enable use of the legacy JDBC connector. * Connector/C++ compressed tar file packages are now available for Solaris. It is also possible to build Connector/C++ from source on Solaris. For platform-specific build notes, see Building Connector/C++ Applications: Platform-Specific Considerations (http://dev.mysql.com/doc/connector-cpp/8.0/en/connector-cpp-apps-platform-considerations.html). X DevAPI Notes * Connector/C++ now provides connection pooling for applications using X Protocol. This capability is based on client objects, a new type of X DevAPI object. A client can be used to create sessions, which take connections from a pool managed by that client. For a complete description, see Connecting to a Single MySQL Server Using Connection Pooling (http://dev.mysql.com/doc/x-devapi-userguide/en/connecting-connection-pool.html). X DevAPI example: using namespace mysqlx; Client cli("user:password@host_name/db_name", ClientOption::POOL_MAX_SIZE, 7); Session sess = cli.getSession(); // use sess as before cli.close(); // close session sess X DevAPI for C example: char error_buf[255]; int error_code; mysqlx_client_t *cli = mysqlx_get_client_from_url( "user:password@host_name/db_name", "{ \"maxSize\": 7 }", error_buf, _code); mysqlx_session_t *sess = mysqlx_get_session_from_client(cli); // use sess as before mysqlx_close_client(cli); // close session sess * For X DevAPI, a new connect-timeout option can be specified in connection strings or URIs to indicate a connection timeout in milliseconds. The SessionSettings::Options object supports a new CONNECT_TIMEOUT option. For X DevAPI for C, the mysqlx_opt_type_t constant is MYSQLX_OPT_CONNECT_TIMEOUT together with the OPT_CONNECT_TIMEOUT() macro. If no timeout option is specified, the default is 1 (10 seconds). A value of 0 disables the timeout. The following examples set the connection timeout to 10 milliseconds: X DevAPI examples: Session sess("user@host/db?connect-timoeut=10"); Session sess(..., SessionOption::CONNECT_TIMEOUT, 10, ...); Session sess( ..., SessionOption::CONNECT_TIMEOUT, std::chrono::milliseconds(10), ... ); X DevAPI for C example: mysqlx_session_options_t *opt = mysqlx_session_options_new(); mysqlx_session_option_set(opt, ..., OPT_CONNECT_TIMEOUT(10), ...); Functionality Added or Changed * JSON: Connector/C++ now uses RapidJSON for improved performance of operations that involve parsing JSON strings. There are no user-visible API changes for X DevAPI or X DevAPI for C. Bugs Fixed * On SLES 15, Connector/C++ installation failed if libmysqlcppcon7 was already installed. (Bug #28658120) * Applications that were statically linked to th
MySQL Community Server 8.0.13 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.13, a new version of the popular Open Source Database Management System, has been released. MySQL 8.0.13 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.13 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.13 is available in source and binary form for a number of platforms from the "Development Releases" selection of our download pages at http://dev.mysql.com/downloads/mysql/ MySQL Server 8.0.13 is also available from our repository for Linux platforms, go here for details: http://dev.mysql.com/downloads/repo/ Windows packages are available via the Installer for Windows: http://dev.mysql.com/downloads/installer/ along with .ZIP (no-install) packages for more advanced needs. 8.0.13 also comes with a web installer as an alternative to the full installer. The web installer doesn't come bundled with any actual products and instead relies on download-on-demand to fetch only the products you choose to install. This makes the initial download much smaller but increases install time as the individual products will need to be downloaded. We welcome and appreciate your feedback, bug reports, bug fixes, patches, etc.: http://bugs.mysql.com/report.php The following link lists the changes in the MySQL 8.0 since the release of MySQL 8.0.12. It may also be viewed online at http://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-13.html Enjoy! == Changes in MySQL 8.0.13 (2018-10-22) * Account Management Notes * Compilation Notes * Configuration Notes * Data Type Notes * Deprecation and Removal Notes * Error Handling * INFORMATION_SCHEMA Notes * Logging Notes * Optimizer Notes * Packaging Notes * Performance Schema Notes * Security Notes * Spatial Data Support * SQL Syntax Notes * XA Transaction Notes * X Plugin Notes * Functionality Added or Changed * Bugs Fixed Account Management Notes * It is now possible to require that attempts to change an account password be verified by specifying the current password to be replaced. This enables DBAs to prevent users from changing a password without proving that they know the current password. It is possible to establish password-verification policy globally using the password_require_current system variable, as well as on a per-account basis using the PASSWORD REQUIRE option of the CREATE USER and ALTER USER statements. Together with existing password-management capabilities, the new capability of requiring verification provides DBAs more complete control over password management. For more information, see Password Management (http://dev.mysql.com/doc/refman/8.0/en/password-management.html). Important MySQL implements the password-verification capability using a new column in 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. Compilation Notes * Solaris: MySQL now can be compiled on Solaris using gcc. (Bug #27802681) Configuration Notes * The new WITH_LTO CMake option controls whether to enable link-time optimization. Currently, this is supported only by GCC 7 and 8. (Bug #28184537, Bug #28211382) * The new WITH_RAPIDJSON CMake option controls whether to compile with the bundled or system RapidJSON library. (Bug #28024992, Bug #90867) * The CMAKE_BUILD_TYPE CMake option now supports a Release build type, which is like the RelWithDebInfo build type but omits debugging information to reduce the build size. (Bug #27874068) * The new sql_require_primary_key system variable makes it possible to have statements that create new tables or alter the structure of existing tables enforce the requirement that tables have a primary key. Enabling this variable helps avoid performance problems in row-based replication that can occur when tables have no primary key. Suppose that a table has no primary key and an update or delete modifies multiple rows. On the master server, this operation can be performed using a single table scan but, when replicated using row-based replication, results in a table scan for each row to be
[ANN] Mroonga 8.07 - Fast fulltext search for all languages on MySQL
Hi, Mroonga 8.07 has been released! Mroonga is a MySQL storage engine that supports fast fulltext search and geolocation search. It is CJK ready. It uses Groonga as a storage and fulltext search engine. Document: http://mroonga.org/docs/ How to install: Install Guide http://mroonga.org/docs/install.html How to upgrade: Upgrade Guide http://mroonga.org/docs/upgrade.html Blog: http://mroonga.org/en/blog/2018/09/29/mroonga-8.07.html Changes: http://mroonga.org/docs/news.html#release-8.07 Here are some topics in this release. * Tokenizer off option is now deprecated, use none instead * MariaDB 10.1.36 has been supported ## Tokenizer off option is now deprecated, use none instead In this release, tokenizer off option is deprecated. Use tokenizer none instead. Before: FULLTEXT INDEX (content) COMMENT 'tokenizer "off"' After: FULLTEXT INDEX (content) COMMENT 'tokenizer "none"' To keep consistency with normalizer option and PGroonga, off option has been deprecated. ## MariaDB 10.1.36 has been supported In this release, MariaDB 10.1.36 has been supported. To support MariaDB 10.1.36 changes, Mroonga has dropped support for MariaDB 10.2.2 (Shipped at Sep 27, 2016) and older MariaDB 10.2 series. Regards, -- Masafumi Yokoyama -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
[ANN] Mroonga 8.06 - Fast fulltext search for all languages on MySQL
Mroonga 8.06 has been released! Mroonga is a MySQL storage engine that supports fast fulltext search and geolocation search. It is CJK ready. It uses Groonga as a storage and fulltext search engine. Document: http://mroonga.org/docs/ How to install: Install Guide http://mroonga.org/docs/install.html Blog: http://mroonga.org/en/blog/2018/08/29/mroonga-8.06.html Changes: http://mroonga.org/docs/news.html#release-8-06 In this version, MySQL will be automatically restarted if you had already installed Mroonga and not installed Groonga 8.0.4 or later. Because Mroonga 8.06 requires Groonga 8.0.4 or later but it will not reloaded until MySQL is restarted. The main changes are as follows. * Supported utf8mb4_0900 family collation. Through this change, groonga-normalizer-mysql 1.1.3 or later and Groonga 8.0.4 or later have been required. * ref: https://github.com/groonga/groonga-normalizer-mysql#description * Supported tokenizer options. * e.g.: tokenizer "TokenNgram(\'loose_symbol\', true)" * ref: http://groonga.org/docs/news.html#release-8-0-2 * [Windows] Updated bundled MariaDB to 10.3.9. * NOTICE: Before upgrading to MariaDB 10.3, you need to dump existing MariaDB 10.1 databases. Then restore it after upgrading. * [Debian GNU/Linux] Dropped Debian 8 (jessie) support. * [Ubuntu] Dropped Ubuntu 17.10 (Artful Aardvark) support. -- Masafumi Yokoyama -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/J 5.1.47 GA has been released
Dear MySQL Users, MySQL Connector/J 5.1.47, a maintenance release of the production 5.1 branch has been released. Connector/J is the Type-IV pure-Java JDBC driver for MySQL. MySQL Connector/J is available in source and binary form from the Connector/J download pages at http://dev.mysql.com/downloads/connector/j/5.1.html and mirror sites as well as Maven-2 repositories. MySQL Connector/J (Commercial) is already available for download on the My Oracle Support (MOS) website. This release will shortly be available on eDelivery (OSDC). As always, we recommend that you check the "CHANGES" file in the download archive to be aware of changes in behavior that might affect your application. MySQL Connector/J 5.1.47 includes the following general bug fixes and improvements, also available in more detail on https://dev.mysql.com/doc/relnotes/connector-j/5.1/en/news-5-1-47.html Changes in MySQL Connector/J 5.1.47 (2018-08-17, General Availability) Version 5.1.47 is a maintenance release of the production 5.1 branch. It is suitable for use with MySQL Server versions 5.5, 5.6, 5.7, and 8.0. It supports the Java Database Connectivity (JDBC) 4.2 API. * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * The value UTF-8 for the connection property characterEncoding now maps to the utf8mb4 character set on the server and, for MySQL Server 5.5.2 and later, characterEncoding=UTF-8 can now be used to set the connection character set to utf8mb4 even if character_set_server has been set to something else on the server. (Before this change, the server must have character_set_server=utf8mb4 for Connector/J to use that character set.) Also, if the connection property connectionCollation is also set and is incompatible with the value of characterEncoding, characterEncoding will be overridden with the encoding corresponding to connectionCollation. See Using Character Sets and Unicode (http://dev.mysql.com/doc/connector-j/5.1/en/connector-j- <http://dev.mysql.com/doc/connector-j/5.1/en/connector-j-reference-charsets.html>reference-charsets.html <http://dev.mysql.com/doc/connector-j/5.1/en/connector-j-reference-charsets.html>) for details, including how to use the utf8mb3 character set now for connection. (Bug#23227334, Bug #81196) Bugs Fixed * Setting rewriteBatchedStatements=true and useLocalTransactionState=true caused transactions to be uncommitted for batched UPDATE and DELETE statements. It was due to the intermediate queries for enabling multiquery support on the server resetting the local transaction state as a side effect. With this fix, the local transaction state is preserved when the intermediate queries are executed. (Bug #27658489, Bug #89948) * Rewriting prepared INSERT statements in a multiquery batch failed with a BatchUpdateException when the statements did not contain place holders. This was due a faulty mechanism for query rewriting, which has been corrected by this fix. (Bug #25501750, Bug #84813) * When using batched prepared statements with multiple queries per statement, queries rewriting was incorrect, resulting in the wrong queries being sent to the server. (Bug #23098159, Bug #81063) * ResultSet.updateRow() failed when the character set used by a column in the ResultSet did not match that of the connection's encoding. With this fix, values for the affected columns are first converted to String before the update, so that the character set difference is properly handled. (Bug #22847443, Bug #80532) * Record updates failed for a scrollable and updatable PreparedStatement when the WHERE clause for the updater or refresher contained fractional timestamp values and the connection property sendFractionalSeconds was set to false. It was because in the situation, Connector/J did not perform the proper adjustments of the fractional parts in the WHERE clause values according to the length of the field's fractional part as defined in the database. This fix makes Connector/J perform the proper adjustment to the fractional part, so that the WHERE clause value can be properly compared to the value fetched from the database. Moreover, useJDBCCompliantTimezoneShift(), useGmtMillisForDatetimes(), and useSSPSCompatibleTimezoneShift() were applied to the WHERE clause values while they should not be, and this fix removes their applications. (Bug #22305979) * When a Java Date value was bound to a PreparedStatement parameter, attempts to format the value by a proleptic GregorianCalendar failed to make the dates proleptic, so that d
MySQL Connector/NET 6.10.8 has been released
Dear MySQL users, MySQL Connector/NET 6.10.8 is the fifth GA release with .NET Core now supporting various connection-string options and MySQL 8.0 server features. To download MySQL Connector/NET 6.10.8 GA, see the "Generally Available (GA) Releases" tab at http://dev.mysql.com/downloads/connector/net/ Changes in Connector/NET 6.10.8 (2018-08-14, General Availability) Functionality Added or Changed * Optimistic locking for database-generated fields was improved with the inclusion of the [ConcurrencyCheck, DatabaseGenerated(DatabaseGeneratedOption.Computed)] attribute. Thanks to Tony Ohagan for the patch. (Bug #28095165, Bug #91064) * All recent additions to .NET Core 2.0 now are compatible with the Connector/NET 6.10 implementation. * With the inclusion of the Functions.Like extended method, scalar-function mapping, and table-splitting capabilities, Entity Framework Core 2.0 is fully supported. Bugs Fixed * EF Core: An invalid syntax error was generated when a new property (defined as numeric, has a default value, and is not a primary key) was added to an entity that already contained a primary-key column with the AUTO_INCREMENT attribute. This fix validates that the entity property (column) is a primary key first before adding the attribute. (Bug #28293927) * EF Core: The implementation of some methods required to scaffold an existing database were incomplete. (Bug #27898343, Bug #90368) * The Entity Framework Core implementation did not render accented characters correctly on bases with different UTF-8 encoding. Thanks to Kleber kleberksms for the patch. (Bug #27818822, Bug #90316) * The Microsoft.EntityFrameworkCore assembly (with EF Core 2.0) was not loaded and the absence generated an error when the application project was built with any version of .NET Framework. This fix ensures the following support: + EF Core 1.1 with .NET Framework 4.5.2 only + EF Core 2.0 with .NET Framework 4.6.1 or later (Bug #27815706, Bug #90306) * Attempts to create a new foreign key from within an application resulted in an exception when the key was generated by a server in the MySQL 8.0 release series. (Bug #27715069) * A variable of type POINT when used properly within an application targeting MySQL 8.0 generated an SQL syntax error. (Bug #27715007) * The case-sensitive lookup of field ordinals was initialized using case-insensitive comparison logic. This fix removes the original case-sensitive lookup. (Bug #27285641, Bug #88950) * The TreatTinyAsBoolean connection option was ignored when the MySqlCommand.Prepare() method was called. (Bug #27113566, Bug #88472) * The MySql.Data.Types.MySqlGeometry constructor called with an array of bytes representing an empty geometry collection generated an ArgumentOutOfRangeException exception, rather than creating the type as expected. Thanks to Peet Whittaker for the patch. (Bug #26421346, Bug #86974) * Slow connections made to MySQL were improved by reducing the frequency and scope of operating system details required by the server to establish and maintain a connection. (Bug #22580399, Bug #80030) * All columns of type TINYINT(1) stopped returning the expected Boolean value after the connector encountered a NULL value in any column of this type. Thanks to David Warner for the patch. (Bug #22101727, Bug #78917) Nuget packages are available at: https://www.nuget.org/packages/MySql.Data/6.10.8 https://www.nuget.org/packages/MySql.Web/6.10.8 https://www.nuget.org/packages/MySql.Data.Entity/6.10.8 https://www.nuget.org/packages/MySql.Data.EntityFrameworkCore/6.10.8 https://www.nuget.org/packages/MySql.Data.EntityFrameworkCore.Design/6.10.8 Enjoy and thanks for the support! On Behalf of the MySQL/Oracle 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/ODBC 5.3.11 has been released
Dear MySQL users, MySQL Connector/ODBC 5.3.11, a new version of the ODBC driver for the MySQL database management system, has been released. 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 version from 5.5. This is the fifth release of the MySQL ODBC driver 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 http://dev.mysql.com/downloads/connector/odbc/5.3.html For information on installing, please see the documentation at http://dev.mysql.com/doc/connector-odbc/en/connector-odbc-installation.html Changes in MySQL Connector/ODBC 5.3.11 (2018-07-30, General Availability) Functionality Added or Changed * Based on MySQL Client library 5.7.23 it has the support for the new caching_sha2_password authentication method, which allows connecting to MySQL Server 8.0. Bugs Fixed * The Unicode version now uses the UTF8MB4 character set as a transport character set between the MySQL server and the ODBC driver. Because text conversions requested by the ODBC user with the CHARSET connection option are done inside the ODBC Driver after the data is received from the server, it now converts text data as UTF8MB4 to USER_CHARSET instead of UTF8 to USER_CHARSET. (Bug #28204756) * Connections to MySQL Server 8.0 could yield "Source character set not supported by client" errors during sorting and case-sensitive operations. Now known UTF8MB4 collations are used for these operations, such as utf8mb4_general_ci (known to libmysqlclient 5.7) instead of utf8mb4_tolower_ci. (Bug #28116892, Bug #90984) * MySQL Server 8.0 connections could fail with unsupported character sets and collations as utf8mb4_xx collations reported by MySQL Server 8.0 with numbers greater than 250 were unknown to libmysqlclient 5.7. Because collations affect sorting but not the data conversion, they can be substituted with known collations such as utf8mb4_general_ci (45). (Bug #28116892, Bug #90984) * Connector/ODBC is now built with MySQL client library 5.7.23, and commercial builds also use an updated OpenSSL version (v1.0.2o). Issues fixed in the new OpenSSL version are described at http://www.openssl.org/news/vulnerabilities.html. (Bug #27829777) * Reported errors that occurred while executing multiple statements with a single query were generic and without context. For example, SQLMoreResults might return "unhandled error from mysql_next_result()" instead of the error reported by MySQL Server. (Bug #11757423, Bug #49466) On Behalf of Oracle/MySQL Release Engineering Team, Kent Boortz -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Shell 8.0.12 for MySQL Server 8.0 and 5.7 has been released
Dear MySQL users, MySQL Shell 8.0.12 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.12. 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.12, 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! Changes in MySQL Shell 8.0.12 (2018-07-27, General Availability) Functionality Added or Changed * Important Change: An RPM package for installing ARM 64-bit (aarch64) binaries of MySQL Shell on Oracle Linux 7 is now available in the MySQL Yum Repository and for direct download. Known Limitation for this ARM release: You must enable the Oracle Linux 7 Software Collections Repository (ol7_software_collections) to install this package, and must also adjust the libstdc++7 path. See Yum's Platform Specific Notes (http://dev.mysql.com/doc/refman/8.0/en/linux-installatio n-yum-repo.html#yum-install-platform-specifics) for additional details. * MySQL Shell now enables you to store user credentials in an operating system specific secret store. You can then enter a MySQL user's password during connection and store it for future connections. Currently the following secret stores are supported: + MySQL login-path + MacOS keychain + Windows API (Bug #23304789, Bug #81484) * The way you access the online Shell help has been standardized. Use the \help pattern command to search the help. The scope of the command has been increased to support retrieving help for the following categories: + Class and function help for the Admin API, X DevAPI and Shell API. Previously, to retrieve help for API objects, you had to create an instance of the object and use the object.help() method. + SQL syntax help, provided that a global session object exists. Wildcards can now be used to search for help. A number of additional bugs relating to incomplete help information have also been fixed. (Bug #23255291, Bug #81277, Bug #24963435, Bug #25732663, Bug #85481, Bug #25739522, Bug #85511, Bug #25739664, Bug #85514, Bug #26393155, Bug #86950, Bug #24943074, Bug #26429399, Bug #87037, Bug #27870491, Bug #90455, Bug #27870503, Bug #90456, Bug #27875150, Bug #90474, Bug #24948933, Bug #83527) * The util.checkForServerUpgrade() operation has an additional outputFormat parameter that you can specify when running the utility. The utility can now generate output in two formats: + TEXT format, which is the default. This option provides output suitable for humans, as previously returned by the utility.
MySQL Connector/Node.js 8.0.12 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.12, 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.12 (2018-07-27, General availability) X DevAPI Notes * For compliance with the Core DevAPI, these Connector/Node.js changes were made: + Collection: Deprecated: count(). Changed: getSchema() now returns a Schema instance instead of the schema name. + CollectionModify: Deprecated: limit(x, y)'s second parameter, and arrayDelete(). + CollectionFind: Deprecated: limit(x, y)'s second parameter. Added: limit(x).offset(y). + CollectionRemove: Deprecated: limit(x, y)'s second parameter. + Table: Deprecated: count() and insert(Document) API. Updated: getSchema() now returns a Schema instance instead of the Schema name. Removed: as(). + TableSelect: Deprecated: limit(x, y)'s second parameter. Added: limit(x).offset(y). + TableDelete: Deprecated: limit(x, y)'s second parameter, and delete(x)'s parameter in favor of using where(x) instead. + TableUpdate: Deprecated: limit(x, y)'s second parameter, and update(x)'s parameter in favor of using where(x) instead. + SqlExecute: Deprecated: sqlExecute() in favor of sql(). Added: bind(). + Column: Added isNumberSigned(), getCollationName(), getCharacterSetName(), and isPadded() Bugs Fixed * The Promise returned by the session.sql().execute() method resolved to a plain JavaScript object rather than a proper Result instance. This meant it lacked access to the API with methods such as getAffectedItemsCount() and getWarnings(). (Bug #28146988) * Retrieving rows with NULL fields would emit an unexpected AssertionError. (Bug #27978594) * The session.close() method is now asynchronous by returning a JavaScript Promise, when before it returned immediately. (Bug #27893001) * The right-padding mechanism was improved. (Bug #27839295) * While calling getSession() without arguments yields an "Invalid parameter." error, passing in '{}' yielded a "Cannot read property 'length' of undefined." error. Now '{}' is allowed, and getSession() defaults to using '' as the user name. (Bug #27730748) * Improved performance for expression parsing and protocol message encoding. On Behalf of the MySQL/Oracle 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/NET 8.0.12 has been released
Dear MySQL users, MySQL Connector/NET 8.0.12 is the second general availability release of MySQL Connector/NET to add support for the new X DevAPI. The X DevAPI enables application developers to write code that combines the strengths of the relational and document models using a modern, NoSQL-like syntax that does not assume previous experience writing traditional SQL. To learn more about how to write applications using the X DevAPI, see http://dev.mysql.com/doc/x-devapi-userguide/en/index.html. For more information about how the X DevAPI is implemented in Connector/NET, see http://dev.mysql.com/doc/dev/connector-net. 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 5.7.12 or higher with the X Plugin enabled. For general documentation about how to get started using MySQL as a document store, see http://dev.mysql.com/doc/refman/5.7/en/document-store.html. To download MySQL Connector/NET 8.0.12, 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.12 (2018-07-27, General Availability) Known Limitation of This Release To create a model in Entity Framework (EF) Core v2.0 with scaffolding in this release, use the following alternative procedure: 1. Downgrade to EF Core 1.0 or 1.1 in your project, install the MySql.Data.EntityFrameworkCore.Design NuGet package, and then create your model using the scaffoldingor migration command. 2. With the model created, revert back to EF Core 2.0 in your project, update the MySql.Data.EntityFrameworkCore NuGet package, and then remove the package MySql.Data.EntityFrameworkCore.Design from your project. We are sorry for this temporary inconvenience. * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * Optimistic locking using a database-generated field was improved with the inclusion of the [ConcurrencyCheck, DatabaseGenerated(DatabaseGeneratedOption.Computed)] attribute. Thanks to Tony Ohagan for the patch. (Bug #28095165, Bug #91064) * Members of several classes in the X DevAPI were added, modified, or removed. MySqlX.XDevAPI.Collection and MySqlX.XDevAPI.Collection classes: + Remove(Object) method was marked Obsolete. + Remove(DbDoc) method was marked Obsolete. + CreateIndex() method was modified to be a direct-execute method (no longer requires .Execute() to execute). MySqlX.XDevAPI.Common.Result class: + RecordsAffected property (now obsolete) was replaced with AffectedItemsCount. + WarningCount property (now obsolete) was replaced with WarningsCount. MySqlX.XDevAPI.CRUD.FindStatement class: + GroupBy() method was added. + Having() method was added. + Limit(Int64, Int64) method was marked Obsolete. + Offset() method was added. + Sort() method was added. + OrderBy() method was removed. MySqlX.XDevAPI.CRUD.ModifyStatement class: + ArrayInsert method was added. + ArrayAppend method was added. + Unset() method was modified to accept an array of document paths. MySqlX.XDevAPI.CRUD.RemoveStatement class: + Sort() method was added. + OrderBy() method was removed. MySqlX.XDevAPI.Relational.RowResult class: + ColumnCount property was added. + ColumnNames property was added. MySqlX.XDevAPI.Relational.SqlResult class: + AutoIncrementValue property was marked Obsolete. MySqlX.XDevAPI.Relational.TableSelectStatement class: + Limit(Int64, Int64) method was marked Obsolete. + Offset() method was added. MySqlX.XDevAPI.Session class: + Commit() method was changed to be a direct-execute method and now it returns void. + Rollback() method was changed to be a direct-execute method and now it returns void. + Uri property was added. + DefaultSchema property was added. (Bug #27732098, Bug #27732175, Bug #27732235) * The MySqlX.XDevAPI.MySqlXConnectionStringBuilder class was added to provide connection-string options that apply exclusively to X Protocol connections. In addition, the Auth, SslCa, and SslCrl properties in the MySql.Data.MySqlClient.MySqlConnectionStringBuilder class were marked Obsolete. Bugs Fixed * X DevAPI: Decimal numbers passed to the DbDoc class
MySQL Cluster 7.4.21 has been released
Dear MySQL Users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance - Transparent Auto-Sharding - Read & write scalability - Active-Active/Multi-Master geographic replication - 99.999% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http, Memcached and JavaScript/Node.js) MySQL Cluster 7.4 makes significant advances in performance; operational efficiency (such as enhanced reporting and faster restarts and upgrades) and conflict detection and resolution for active-active replication between MySQL Clusters. MySQL Cluster 7.4.21, has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.4/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime and agility. More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! Changes in MySQL NDB Cluster 7.4.21 (5.6.41-ndb-7.4.21) (2018-07-27, General Availability) MySQL NDB Cluster 7.4.21 is a new release of MySQL NDB Cluster 7.4, based on MySQL Server 5.6 and including features in version 7.4 of the NDB storage engine, as well as fixing recently discovered bugs in previous NDB Cluster releases. Obtaining MySQL NDB Cluster 7.4. MySQL NDB Cluster 7.4 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL NDB Cluster 7.4, see What is New in NDB Cluster 7.4 (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is <http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is-new-7-4.html>-new-7-4.html <http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is-new-7-4.html>). This release also incorporates all bug fixes and changes made in previous NDB Cluster releases, as well as all bug fixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.41 (see Changes in MySQL 5.6.41 (Not yet released, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-41.html)). Bugs Fixed * NDB Cluster APIs: When Ndb::dropEventOperation() tried to clean up a pending event, it failed to clear a pointer to the list of GCI operations being deleted and discarded (Gci_ops object), so that this pointer referred to a deleted object. GCI operations arriving after this could then be inserted as part of the next such list belonging to the now-deleted object, leading to memory corruption and other issues. (Bug #90011, Bug #27675005) * NDB attempted to drop subscriptions which had already been dropped, leading to a data node shutdown with Error 2341. (Bug #27622643) * An NDB online backup consists of data, which is fuzzy, and a redo and undo log. To restore to a consistent state it is necessary to ensure that the log contains all of the changes spanning the capture of the fuzzy data portion and beyond to a consistent snapshot point. This is achieved by waiting for a GCI boundary to be passed after the capture of data is complete, but before stopping change logging and recording the stop GCI in the backup's metadata. At restore time, the log is replayed up to the stop GCI, restoring the system to the state it had at the consistent stop GCI. A problem arose when, under load, it was possible to select a GCI boundary which occurred too early and did not span all the data captured. This could lead to inconsistencies when restoring the backup; these could be be noticed as broken constraints or corrupted BLOB entries. Now the stop GCI is chosen is so that it spans the entire duration of the fuzzy data capture process, so that the backup log always contains all data within a given stop GCI. (Bug #27497461) References: See also: Bug #27566346. On Behalf of MySQL Release Engineering team, Surabhi Bhat
MySQL Community Server 5.5.61 has been released
Dear MySQL users, MySQL Server 5.5.61 is a new version of the 5.5 production release of the world's most popular open source database. MySQL 5.5.61 is recommended for use on production systems. MySQL 5.5 includes several high-impact enhancements to improve the performance and scalability of the MySQL Database, taking advantage of the latest multi-CPU and multi-core hardware and operating systems. In addition, with release 5.5, InnoDB is now the default storage engine for the MySQL Database, delivering ACID transactions, referential integrity and crash recovery by default. MySQL 5.5 also provides a number of additional enhancements including: - Significantly improved performance on Windows, with various Windows specific features and improvements - Higher availability, with new semi-synchronous replication and Replication Heartbeat - Improved usability, with Improved index and table partitioning, SIGNAL/RESIGNAL support and enhanced diagnostics, including a new Performance Schema monitoring capability. For a more complete look at what's new in MySQL 5.5, please see the following resources: Documentation: http://dev.mysql.com/doc/refman/5.5/en/mysql-nutshell.html If you are running a MySQL production level system, we would like to direct your attention to MySQL Enterprise Edition, which includes the most comprehensive set of MySQL production, backup, monitoring, modeling, development, and administration tools so businesses can achieve the highest levels of MySQL performance, security and uptime. http://mysql.com/products/enterprise/ For information on installing MySQL 5.5.61 on new servers, please see the MySQL installation documentation at http://dev.mysql.com/doc/refman/5.5/en/installing.html For upgrading from previous MySQL releases, please see the important upgrade considerations at: http://dev.mysql.com/doc/refman/5.5/en/upgrading.html MySQL Database 5.5.61 is available in source and binary form for a number of platforms from our download pages at: http://dev.mysql.com/downloads/mysql/ The following link lists the changes in the MySQL source code since the previous released version of MySQL 5.5. It may also be viewed online at: http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-61.html Enjoy! Changes in MySQL 5.5.61 (2018-07-27, General availability) Bugs Fixed * A heap overflow vulnerability in the MySQL client library was fixed. (Bug #27980823) * An unencrypted connection could result from a client connection attempt specifying that an encrypted connection was required, if the server was not configured to support SSL. (Bug #27759871) * With automatic_sp_privileges enabled, the EXECUTE and ALTER ROUTINE privileges were not correctly granted to routine creators. (Bug #27407480) * Mishandling of internal privilege structures could cause a server exit. (Bug #27230925) * The UNION of a user-defined variable and a DECIMAL column produced an incorrect result when using a UTF8 character set. (Bug #27197235) * mysqldump exited abnormally for large --where option values. (Bug #26171967, Bug #86496, Bug #27510150) * For MyISAM tables, particular sequences of INSERT and DELETE statements could cause table corruption. (Bug #25541037) On Behalf of the MySQL/Oracle 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/J 8.0.12 has been released
Dear MySQL users, MySQL Connector/J Version 8.0.12 is the second GA release of the 8.0 branch of MySQL Connector/J. It is suitable for use with MySQL Server versions 5.5, 5.6, 5.7, and 8.0. 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-12.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.12 GA, see the "Generally Available (GA) Releases" tab at http://dev.mysql.com/downloads/connector/j/ Enjoy! Changes in MySQL Connector/J 8.0.12 (2018-07-27, General Availability) Version 8.0.12 is the latest General Availability release of the 8.0 series of MySQL Connector/J. It is suitable for use with MySQL Server versions 8.0, 5.7, 5.6, and 5.5. * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * X DevAPI: The following changes have been made to the API: + Removed ModifyStatement.arrayDelete() and ModifyStatement.merge(). + Renamed Colletion.find().limit().skip() to Colletion.find().limit().offset(). + To simplify the class hierarchy and to have the class names reflect better the classes' functions, the following changes have been made: o The FindParams class has been renamed to FilterParams o The AbstractFindParams class has been renamed to AbstractFilterParams o The DocFindParams class has been renamed to DocFilterParams o The TableFindParams class has been renamed to TableFilterParams Notice that the methods in the original FilterParams class have been moved under the new AbstractFilterParams class. (Bug #28027459) * X DevAPI: Connector/J now uses synchronous client sockets (java.net.Socket) by default to communicate with MySQL servers for X Protocol connections. While asynchronous sockets can still be used by setting the connection property xdevapi.useAsyncProtocol=true, this is not recommended, as it might result in performance degradation for Connector/J. (Bug #27522054) * X DevAPI: Connector/J now gives provision for the use of a custom socket factory for X Protocol connections to MySQL Servers using Unix domain sockets. See Section 6.8, "Connecting Using Unix Domain Sockets" for details. * Connector/J now retrieves the MySQL keyword list from the INFORMATION_SCHEMA.KEYWORDS ( http://dev.mysql.com/doc/refman/8.0/en/keywords-table.html ) table on the MySQL server when a connection session is established. The list can then be accessed by calling DatabaseMetaData.getSQLKeywords(). * To simplify the code, the ReadableProperty and ModifiableProperty classes have been consolidated into the RuntimeProperty class. Bugs Fixed * X DevAPI: When creating an X DevAPI session using a Properties map instead of a connection string, referring to property keys like host, port, and protocol in lowercase caused a NullPointerException. With the fix, both upper and lower cases can now be used. (Bug#27652379) * X DevAPI: When using the getConnection() method with the mysqlx: scheme in the connection URL, Connector/J returned an ordinary JDBC connection instead of an X-Protocol connection. (Bug #26089880) * If wait_timeout was set on the server and the Connector/J had the connection property interactiveClient=false, or if interactive_timeout was set on the server and Connector/J had the connection property interactiveClient=true, a connection is invalidated when it has idled for a longer time than the set timeout. When such a timeout occurred, Connector/J threw a CJCommunicationsException, without indicating it was a timeout. With this fix, the error message returned explains the issue and suggests how to avoid it. (Bug#27977617, Bug #90753) * When an application tried to connect to a non-MySQL database through some JDBC driver and Connector/J happened to be on the class path also, Connector/J threw a SQLNonTransientConnectionException, which prevented the application from connecting to its database. With this fix, Connector/J returns null whenever a connection string does not start with jdbc:mysql: or mysqlx:, so connections to non-MySQL databases are not blocked. (Bug#26724154, Bug #87600) * A was
MySQL Cluster 7.2.34 has been released
Dear MySQL Users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance (with optional checkpointing to disk) - Transparent Auto-Sharding - Read & write scalability - Active-Active/Multi-Master geographic replication - 99.999% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http and Memcached) MySQL Cluster 7.2.34, has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.2/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime and agility. More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! == Changes in MySQL NDB Cluster 7.2.34 (5.5.61-ndb-7.2.34) (2018-07-27, General Availability) MySQL NDB Cluster 7.2.34 is a new release of NDB Cluster, incorporating new features in the NDB storage engine, and fixing recently discovered bugs in previous MySQL NDB Cluster 7.2 development releases. Obtaining MySQL NDB Cluster 7.2. MySQL NDB Cluster 7.2 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. This release also incorporates all bug fixes and changes made in previous NDB Cluster releases, as well as all bug fixes and feature changes which were added in mainline MySQL 5.5 through MySQL 5.5.61 (see Changes in MySQL 5.5.61 (2018-07-27, General availability) (http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-61.html)). Bugs Fixed * NDB attempted to drop subscriptions which had already been dropped, leading to a data node shutdown with Error 2341. (Bug #27622643) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Cluster 7.5.11 has been released
Dear MySQL Users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance (with optional checkpointing to disk) - Transparent Auto-Sharding - Read & write scalability - Active-Active/Multi-Master geographic replication - 99.999% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http, Memcached and JavaScript/Node.js) MySQL Cluster 7.5.11, has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. MySQL Cluster 7.5 is also available from our repository for Linux platforms, go here for details: http://dev.mysql.com/downloads/repo/ The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.5/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime and agility. More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! Changes in MySQL NDB Cluster 7.5.11 (5.7.23-ndb-7.5.11) (2018-07-27, General Availability) MySQL NDB Cluster 7.5.11 is a new release of MySQL NDB Cluster 7.5, based on MySQL Server 5.7 and including features in version 7.5 of the NDB (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.html) storage engine, as well as fixing recently discovered bugs in previous NDB Cluster releases. Obtaining MySQL NDB Cluster 7.5. MySQL NDB Cluster 7.5 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL NDB Cluster 7.5, see What is New in NDB Cluster 7.5 (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-what-is-new-7-5.html). This release also incorporates all bug fixes and changes made in previous NDB Cluster releases, as well as all bug fixes and feature changes which were added in mainline MySQL 5.7 through MySQL 5.7.23 (see Changes in MySQL 5.7.23 (2018-07-27, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-23.html)). Bugs Fixed * ndbinfo Information Database: It was possible following a restart for (sometimes incomplete) fallback data to be used in populating the ndbinfo.processes (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-processes.html) table, which could lead to rows in this table with empty process_name values. Such fallback data is no longer used for this purpose. (Bug #27985339) * MySQL NDB ClusterJ: ClusterJ could not be built from source using JDK 9. (Bug #27977985) * NDB attempted to drop subscriptions which had already been dropped, leading to a data node shutdown with Error 2341. (Bug #27622643) * An NDB (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.html) online backup consists of data, which is fuzzy, and a redo and undo log. To restore to a consistent state it is necessary to ensure that the log contains all of the changes spanning the capture of the fuzzy data portion and beyond to a consistent snapshot point. This is achieved by waiting for a GCI boundary to be passed after the capture of data is complete, but before stopping change logging and recording the stop GCI in the backup's metadata. At restore time, the log is replayed up to the stop GCI, restoring the system to the state it had at the consistent stop GCI. A problem arose when, under load, it was possible to select a GCI boundary which occurred too early and did not span all the data captured. This could lead to inconsistencies when restoring the backup; these could be be noticed as broken constraints or corrupted BLOB (http://dev.mysql.com/doc/refman/5.7/en/blob.html) entries. Now the stop GCI is chosen is so that it spans the entire duration of the fuzzy data capture process, so that the backup log always contains all data within a given stop GCI. (Bug #27497461) References: See also: Bug #27566346. * For NDB tables, when a foreign key was added or dropped as a part of a DDL statement, the foreign key metatdata for all parent tables referenced should be reloaded in the handler on all SQL nodes connected to the cluster, but this was done only on the mysqld on which the statement was executed. Due to this, any subsequent queries relying on foreign key metadata from the corresponding parent tables could return inconsistent results. (Bug #27439587) References: See also: Bug #82989, Bug #24666177. * The internal function Bitmask
MySQL Community Server 5.6.41 has been released
Dear MySQL users, MySQL Server 5.6.41, a new version of the popular Open Source Database Management System, has been released. MySQL 5.6.41 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.41 on new servers or upgrading to MySQL 5.6.41 from previous MySQL releases, please see http://dev.mysql.com/doc/refman/5.6/en/installing.html MySQL Server is available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/ Not all mirror sites may be up to date at this point in time, so if you can't find this version on some mirror, please try again later or choose another download site. We welcome and appreciate your feedback, bug reports, bug fixes, patches, etc: https://wikis.oracle.com/display/mysql/Contributing The following link lists the changes in the MySQL 5.6 since the release of MySQL 5.6.40. It may also be viewed online at http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-41.html Enjoy! Changes in MySQL 5.6.41 (2018-07-27, General Availability) * Security Notes * Functionality Added or Changed * Bugs Fixed Security Notes * The linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.2o. 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 #28025379) Functionality Added or Changed * Previously, for the --ssl-verify-server-cert option, the client checked whether the host name that it used for connecting matched the Common Name value in the certificate but not the Subject Alternative Name value. Now, if MySQL was built using OpenSSL 1.0.2 or higher, the client checks whether the host name matches either the Subject Alternative Name value or the Common Name value in the server certificate. (Bug #16211011, Bug #68052, Bug #27511233, Bug #89578) Bugs Fixed * InnoDB: A schema mismatch error reported during an import tablespace operation failed to print mismatched table flags in a readable format. (Bug #27542720) * InnoDB: A DDL operation failed to wait for a FULLTEXT index optimization operation to finish. (Bug #27326796) References: This issue is a regression of: Bug #24938374. * InnoDB: A failing assertion occurred after initiating a memcached get operation. (Bug #26876594) * InnoDB: A corrupt index ID encountered during a foreign key check raised an assertion. (Bug #26654685) * Replication: When a transaction larger than the binary log transaction cache size (binlog_cache_size) was flushed to a temporary file during processing, and the flush failed due to a lack of space in the temporary directory, the flush error was not handled correctly. No message was written to the error log, and the binary log cache was not cleared after the transaction was rolled back. Now, in this situation, the server takes an appropriate action based on the binlog_error_action setting (shut down the server or halt logging), and writes a message to the error log. When the transaction is rolled back, the server checks for flush errors and clears the binary log cache if any occurred. (Bug #27399620, Bug #89272) * Replication: When GTIDs are in use for replication, replicated transactions that are filtered out on the slave are persisted. If binary logging is enabled on the slave, the filtered-out transaction is written to the binary log as a Gtid_log_event followed by an empty transaction containing only BEGIN and COMMIT statements. If binary logging is disabled, the GTID of the filtered-out transaction is written to the mysql.gtid_executed table. This process ensures that there are no gaps in the set of executed GTIDs, and that the filtered-out transactions are not retrieved again if
MySQL Community Server 5.7.23 has been released
Dear MySQL users, MySQL Server 5.7.23, a new version of the popular Open Source Database Management System, has been released. MySQL 5.7.23 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.23 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.23 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.23 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.23 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.22. It may also be viewed online at http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-23.html Enjoy! Changes in MySQL 5.7.23 (2018-07-27, General Availability) Audit Log Notes * For new MySQL installations, the USER and HOST columns in the audit_log_user table used by MySQL Enterprise Audit now have definitions that better correspond to the definitions of the User and Host columns in the mysql.user system table. For upgrades to an installation for which MySQL Enterprise Audit is already installed, it is recommended that you alter the table definitions as follows: ALTER TABLE mysql.audit_log_user DROP FOREIGN KEY audit_log_user_ibfk_1; ALTER TABLE mysql.audit_log_filter ENGINE=InnoDB; ALTER TABLE mysql.audit_log_filter CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin; ALTER TABLE mysql.audit_log_user ENGINE=InnoDB; ALTER TABLE mysql.audit_log_user CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin; ALTER TABLE mysql.audit_log_user MODIFY COLUMN USER VARCHAR(32); ALTER TABLE mysql.audit_log_user ADD FOREIGN KEY (FILTERNAME) REFERENCES mysql.audit_log_filter(NAME); (Bug #23706056) Compilation Notes * Solaris: MySQL now can be compiled on Solaris using gcc. (Bug #27802681) MySQL Enterprise Notes * The MySQL Enterprise Firewall firewall_whitelist table now contains a primary key column named ID. (Bug #27164826) Security Notes * The linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.2o. 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 #28025379) * In MySQL 5.7, the default authentication plugin is mysql_native_password. As of MySQL 8.0, the default authentication plugin is changed to caching_sha2_password. To enable MySQL 5.7 clients to connect to 8.0 and higher servers using accounts that authenticate with caching_sha2_password, the MySQL 5.7 client library and client programs now support the caching_sha2_password client-side authentication plugin. This improves MySQL 5.7 client connect-capability compatibility with respect to MySQL 8.0 and higher servers, despite the differences in default authentication plugin. For more information, see Caching SHA-2 Pluggable Authentication (http://dev.mysql.com/doc/refman/5.7/en/caching-sha2-pluggable-authentication.html). SQL Syntax Notes * Explicit ASC or DESC qualifiers for GROUP BY clauses are now deprecated and will be removed in a future MySQL version. Functionality Added or Changed * Previously, for the --ssl-mode=VERIFY_IDENTITY or --ssl-verify-server-cert option, the client checked whether the host name that it used for connecting matched the Common Name value in the certificate but not the Subject Alternative Name value. Now, if the client uses OpenSSL 1.0.2 or higher, the client checks whether the host name matches either
MySQL Community Server 8.0.12 has been released (part 2/2)
[Due to size limitation, this announcement is split in two. This is part 2] Bugs Fixed * Important Change; JSON: The JSON_TABLE() function now automatically decodes base-64 values and prints them using the character set given by the column specification. (Bug #90157, Bug #27729112) References: See also: Bug #89847, Bug #27613276. * Important Change: MySQL now allows a query having a WITH ROLLUP modifier to use DISTINCT. See SELECT Syntax (http://dev.mysql.com/doc/refman/8.0/en/select.html), for more information. (Bug #87450, Bug #26640100) * Important Change: MySQL now allows the use of ORDER BY with grouping functions in SELECT. statements. (Bug #86312, Bug #27063525) * Important Change: MySQL now allows ORDER BY to be used in a query having a WITH ROLLUP modifier. For more information, see SELECT Syntax (http://dev.mysql.com/doc/refman/8.0/en/select.html). (Bug #86311, Bug #26073513) * InnoDB: New columns added to INFORMATION_SCHEMA.INNODB_TABLES and INFORMATION_SCHEMA.INNODB_COLUMNS tables in 8.0.12 did not appear after upgrading to 8.0.12. (Bug #28065244) * InnoDB: Large object (LOB) version numbers stored in LOB index entries were left uninitialized at 0 instead of initialized at 1. (Bug #28046298) * InnoDB: Adding a column to a table with a generated column raised an invalid assertion. (Bug #28040201) * InnoDB: An attempt to access freed memory during a checkpoint operation caused the server to exit. (Bug #28039477) * InnoDB: An assertion failure occurred when starting the server with experimental system variables that were unintentionally exposed in normal MySQL builds. (Bug #27899424, Bug #90526, Bug #27898396, Bug #90523, Bug #27898344, Bug #90522) * InnoDB: An invalid system variable setting raised an assertion. (Bug #27898284) * InnoDB: Attempting to move a table from a discarded file-per-table tablespace to a shared tablespace raised an assertion. The operation now produces an error instead. (Bug #27861972) * InnoDB: Potential failures related to page allocation for large objects (LOBs) were not sufficiently handled. (Bug #27852003) * InnoDB: The ngram full-text search parser permitted comma and period characters to be tokenized as words, which caused an inconsistency between boolean and natural language mode search results. Comma and period characters are no longer tokenized. (Bug #27847697) * InnoDB: Checksum mismatches and other issues were caused by concurrent modification of a tablespace header page, and attempting to place a lock on a partially initialized page. (Bug #27823064) * InnoDB: An I/O error returned by an fsync() operation is now treated as a hard error. (Bug #27805553, Bug #90296) * InnoDB: In a single thread, two minitransactions latched the first page of a large object value (LOB) while another thread attempted to allocate the page, causing a deadlock. (Bug #2959) * InnoDB: After upgrading to MySQL 8.0.12, table columns including the FTS_DOC_ID column were missing from the INFORMATION_SCHEMA.INNODB_COLUMNS table. (Bug #27774145) * InnoDB: An invalid assertion was raised when the optimizer chose a prefix index defined on a virtual column. (Bug #27755892) References: This issue is a regression of: Bug #19806106. * InnoDB: An in-memory table object for a table being truncated could be opened under improper metadata locking protection. A new method of preserving the AUTOINC counter value during a TRUNCATE PARTITION operation was implemented. (Bug #27754995) * InnoDB: The Variance-Aware Transaction Scheduling algorithm (VATS) tracks the number of transactions waiting for another transaction. In the case of a deadlock, the method by which the number of waiting transactions is approximated produced inflated values. (Bug #27646322) * InnoDB: Attempting to acquire an InnoDB ticket while holding a victim transaction lock caused a lock order violation. (Bug #27626681) References: This issue is a regression of: Bug #23476050. * InnoDB: An attempt to read a zero-length BLOB value raised an assertion failure during recovery. The BLOB value was not yet completely inserted. (Bug #27617389) * InnoDB: A race condition occurred when acquiring a table lock for a table that was already in memory. (Bug #27586419, Bug #27577704) References: This issue is a regression of: Bug #26848711. * InnoDB: After restarting the server, attempting to create an encrypted table returned a generic error from
MySQL Enterprise Backup 8.0.12 has been released
Dear MySQL users, MySQL Enterprise Backup 8.0.12, 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.12 supports only the MySQL Server 8.0. For any earlier versions of the 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. For additional MySQL Enterprise Backup 8.0 documentation, see the MySQL Enterprise Backup User's Guide (Version 8.0.12) (http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/). A brief summary of the changes in MySQL Enterprise Backup (MEB) version 8.0.12 is given below. Changes in MySQL Enterprise Backup 8.0.12 (2018-07-27) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * Important Change: Starting from release 8.0.12, the storage engine of the mysql.backup_history table on a backed-up server has switched from CSV to InnoDB. For a MySQL 8.0.12 server that has its database restored from a backup of an earlier server version, MySQL Enterprise Backup 8.0.12 automatically migrates the table when it performs its first backup task on the server. See After restoring an earlier backup to MySQL 8.0.12 or later (http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/mysqlbackup.privileges.html#meb-restore-to-8.0.12) for the new user privileges required by mysqlbackup for the mandatory migration to happen. * Important Change: When working with a Group Replication (http://dev.mysql.com/doc/refman/8.0/en/group-replication.html) setup, mysqlbackup now makes the backup history available to all members of the server group by making sure that the backup_history table is updated on a primary node after each mysqlbackup operation. With the implementation of this feature, the new user privilege of SELECT on performance_schema.replication_group_members is now required by mysqlbackup to work with any server, even when it does not belong to a Group Replication setup. See Grant MySQL Privileges to Backup Administrator (http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/mysqlbackup.privileges.html) for details. * Version information for mysqlbackup is now printed to the stdout instead of the stderr stream when the --version or --help option is used. (Bug #27253989) * OAuth is now supported for Oracle Cloud Storage client authentication. Two new options, --cloud-storage-url and --cloud-oauth-token, have been introduced for the purpose. See Cloud Storage Options (http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/backup-cloud-options.html) for details. Bugs Fixed * Backups for a server failed when it had ANSI_QUOTES in its values for sql_mode. (Bug #27939774) * The maximum value that could be set for the --safe-slave-backup-timeout option was 2700 (seconds), which automatically replaced any larger value. With this fix, there is no longer a maximum limition, even though a high value is not recommended; see the description of --safe-slave-backup-timeout for details. (Bug #27883020) * Restoring an incrementation backup on top of a data directory restored using a compressed backup failed. It was because mysqlbackup did not set is_compressed=0 in the backup_variables.txt file inside the restored data directory. (Bug #27787988) * When mysqlbackup performed sanity checks on InnoDB tablespaces and found a space ID mismatch for an FSP header and a page header, the name of the problematic tablespace was not given in the error report. (Bug #27752703) * If an ALTER TABLE (http://dev.mysql.com/doc/refman/8.0/en/alter-table.html) statement was executed on the server before an incremental backup was taken, a server restored with the backup on which the incremental backup was applied (using the apply-incremental-backup command) could not be started, as the .ibd file of the altered table was missing in the restored data. (Bug #27735134) * After a server has been restored using an incremental backup created with the --incremental-with-redo-log-only option, it could not be started. (Bug #27722525) * mysqlbackup issued a warning whenever the number of files specified in the system variable innodb_data_file_path of the server to be backed up exceeded 100. With this fix, a warning is issued only if the number of InnoDB data files to be opened exceeds the number specified
MySQL Community Server 8.0.12 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.12, a new version of the popular Open Source Database Management System, has been released. MySQL 8.0.12 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.12 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.12 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.12 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.12 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.11. It may also be viewed online at http://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-12.html Enjoy! Changes in MySQL 8.0.12 (2018-07-27) * Audit Log Notes * Compilation Notes * Configuration Notes * Function Notes * Logging Notes * MySQL Enterprise Notes * Optimizer Notes * Packaging Notes * Performance Schema Notes * Plugin Notes * Security Notes * Spatial Data Support * SQL Syntax Notes * X Plugin Notes * Functionality Added or Changed * Bugs Fixed Audit Log Notes * For new MySQL installations, the USER and HOST columns in the audit_log_user table used by MySQL Enterprise Audit now have definitions that better correspond to the definitions of the User and Host columns in the mysql.user system table. For upgrades to an installation for which MySQL Enterprise Audit is already installed, it is recommended that you alter the table definitions as follows: ALTER TABLE mysql.audit_log_user DROP FOREIGN KEY audit_log_user_ibfk_1; ALTER TABLE mysql.audit_log_filter CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_as_ci; ALTER TABLE mysql.audit_log_user CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_as_ci; ALTER TABLE mysql.audit_log_user MODIFY COLUMN USER VARCHAR(32); ALTER TABLE mysql.audit_log_user ADD FOREIGN KEY (FILTERNAME) REFERENCES mysql.audit_log_filter(NAME) ; (Bug #23706056) Compilation Notes * Microsoft Windows: For OpenSSL 1.1, the library names have changed for Windows. The CMake configuration code now accounts for this. Also, it is now possible on Windows to use -DWITHOUT_SERVER=1 to build 32-bit client binaries. (Bug #28170711, Bug #91223) * The minimum version of the Boost library for server builds is now 1.67.0. (Bug #27866110) Configuration Notes * For RelWithDebInfo builds on Linux, REPRODUCIBLE_BUILD now defaults to ON. (Bug #27483447) * The default value for the slave_pending_jobs_size_max system variable has increased from 16M to 128M. On a multi-threaded slave ( with slave_parallel_workers > 0), this value sets the maximum amount of memory that is made available to slave worker queues holding events that have not yet been applied. The potentially larger memory usage should be taken into account when calculating the resources required to deploy a multi-threaded slave. Masters and single-threaded slaves are not affected by this setting. The new default is double the recently increased default value specified by the max_allowed_packet system variable (now 64M). The value of slave_pending_jobs_size_max is a soft limit, so events larger than its value (consisting of one or more packets) can be queued and processed. However, a large transaction is held until all the slave workers have empty queues, and then processed. All subsequent transactions are held until the large transaction has been completed. The delay to clear the queues of all the slave workers and the wait to queue subsequent transactions can cause lag on the replication slave and decreased concurrency of the slave workers. The value of slave_pending_jobs_size_
MySQL Workbench 8.0.12 has been released
Dear MySQL users, The MySQL developer tools team announces 8.0.12 as our first general availability (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 of platforms from our download pages at: http://dev.mysql.com/downloads/tools/workbench/ Enjoy! Changes in MySQL Workbench 8.0.12 (2018-07-27, General Availability) Known limitation of this release: Importing spatial data into a MySQL 8.0 server does not work currently, due to an outstanding library update. Older versions of the server are not affected. * Installation Notes * Functionality Added or Changed * Bugs Fixed Installation Notes * Because the Microsoft Visual C++ 2017 Redistributable installer deletes the Microsoft Visual C++ 2015 Redistributable registry keys that identify its installation, standalone MySQL MSIs may fail to detect the Microsoft Visual C++ 2015 Redistributable if both it and the Microsoft Visual C++ 2017 Redistributable are installed. The solution is to repair the Microsoft Visual C++ 2017 Redistributable via the Windows Control Panel to recreate the registry keys needed for the runtime detection. Unlike the standalone MSIs, MySQL Installer for Windows contains a workaround for the detection problem. (Bug #28345281, Bug #91542) Functionality Added or Changed * Important Change: MySQL model files last saved before MySQL Workbench 6.3 are no longer supported unless the models can be upgraded for use with the 6.3 release series. * All editions of MySQL Workbench and the bundled libraries were upgraded to use OpenSSL 1.0.2o. (Bug #27829782, Bug #28326884) * libgnome-keyring was depreciated and replaced with libsecret in this release on Linux platforms. Some users with existing stored passwords will be prompted to enter a password after upgrading. (Bug #27635281, Bug #89898, Bug #20291538, Bug #75345) * SSH tunneling support was added to the MySQL Workbench Migration Wizard and also to the wbcopytables command-line utility for copying data. (Bug #27556268, Bug #89671) * Performing multiple data export operations while the Administration - Data Export tab stays open now preserves custom file paths, rather than switching to the default paths for re-export operations. Exported files are automatically renamed with an incremental numeric suffix to enable repeated export. In addition, a new dialog box prompts for confirmation before overwriting an existing exported file when the same path and file names are reused. (Bug #27029840) * OGRFree() was deprecated and replaced with CPLFree(). Thanks to Christian Hesse for the patch. (Bug #26086599, Bug #86339) * The SWIG prerequisite listed in the INSTALL document provided with source distributions was updated to the latest version. (Bug #25811732, Bug #85717) * Support for the --incremental-with-redo-log-only option was added to create backups directly from the redo log. (Bug #24960233) * The option to skip secure authorization is no longer available in the advanced options that apply to data import and export operations. The --skip-secure-auth option was removed in the MySQL 5.7 release. (Bug #21697062, Bug #78060) * The character set and collation pairings available after selecting Create a new schema in the connected server (from the main toolbar) now are sorted alphabetically in lists. (Bug #21681041, Bug #78079) * A new SQL export option in the Forward Engineering SQL Script wizard sorts tables alphabetically in the generated script, rather than sorting tables according to foreign-key references by default. (Bug #18551598, Bug #72289) * MySQL Workbench now supports the Chinese character set gb18030. (Bug #18547307) * The SQL editor supports online renaming of indexes with the ALTER TABLE statement. For example: ALTER TABLE `sakila`.`actor` RENAME INDEX `idx_actor_last_name` TO `id x_actor_last_`; (Bug #18547288) * MySQL Workbench now uses utf8mb4 as the connection and client character set, replacing utf8mb3. Bugs Fixed * Some of the controls and data were not shown within the Administration-Users and Privileges tab. (Bug #28246905, Bug #91414) * An attempt to add a column to an existing multicolumn index (primary key) of a table caused MySQL Workbench to stop working. (Bug #28244024, Bug #91371
MySQL Connector/C++ 8.0.12 has been released
Dear MySQL users, MySQL Connector/C++ 8.0.12 is the second GA 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" 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/ Note: For X DevAPI applications, Connector/C++ 8.0 requires MySQL Server 5.7.12 or higher with X Plugin enabled. For applications that use the legacy JDBC API, Connector/C++ 8.0 can use MySQL Server 5.5 or higher, and X Plugin is not required. https://dev.mysql.com/doc/refman/5.7/en/document-store.html To download MySQL Connector/C++ 8.0.12, see the "Generally Available (GA) Releases" tab at https://dev.mysql.com/downloads/connector/cpp/ Changes in MySQL Connector/C++ 8.0.12 (2018-07-27, General Availability) * Installation Notes * Packaging Notes * Security Notes * X DevAPI Notes * Bugs Fixed Installation Notes * Because the Microsoft Visual C++ 2017 Redistributable installer deletes the Microsoft Visual C++ 2015 Redistributable registry keys that identify its installation, standalone MySQL MSIs may fail to detect the Microsoft Visual C++ 2015 Redistributable if both it and the Microsoft Visual C++ 2017 Redistributable are installed. The solution is to repair the Microsoft Visual C++ 2017 Redistributable via the Windows Control Panel to recreate the registry keys needed for the runtime detection. Unlike the standalone MSIs, MySQL Installer for Windows contains a workaround for the detection problem. Packaging Notes * An RPM package for installing ARM 64-bit (aarch64) binaries of Connector/C++ on Oracle Linux 7 is now available in the MySQL Yum Repository and for direct download. Known Limitation for this ARM release: You must enable the Oracle Linux 7 Software Collections Repository (ol7_software_collections) to install this package, and must also adjust the libstdc++7 path. See Yum's Platform Specific Notes (http://dev.mysql.com/doc/refman/8.0/en/linux-installation-yum-repo.html#yum-install-platform-specifics) for additional details. * Installers for Connector/C++ are now available in these formats: MSI packages (Windows); RPM packages (Linux); DMG packages (macOS). Security Notes * yaSSL is no longer included in Connector/C++ source distributions. wolfSSL may be used as a functionally equivalent alternative that has a GPLv2-compatible license. In addition, wolfSSL (like OpenSSL) supports the TLSv1.2 protocol, which yaSSL does not. To build Connector/C++ using wolfSSL, use the -DWITH_SSL=path_name CMake option, where path_name indicates the location of the wolfSSL sources. For more information, see Source Installation System Prerequisites (http://dev.mysql.com/doc/connector-cpp/8.0/en/connector-cpp-installation-source-prerequisites.html), and Connector/C++ Source-Configuration Options (http://dev.mysql.com/doc/connector-cpp/8.0/en/connector-cpp-source-configuration-options.html). X DevAPI Notes * Connector/C++ now supports NOWAIT and SKIP LOCKED lock contention modes to be used with lockExclusive() and lockShared() clauses of CRUD find/select operations (see Locking Read Concurrency with NOWAIT and SKIP LOCKED (http://dev.mysql.com/doc/refman/8.0/en/innodb-locking-reads.html#innodb-locking-reads-nowait-skip-locked)), and a default lock contention mode. The following list names the permitted constants. For each item, the first and second constants apply to X DevAPI and X DevAPI for C, respectively. + LockContention::DEFAULT, LOCK_CONTENTION_DEFAULT: Block the query until existing row locks are released. + LockContention::NOWAIT, LOCK_CONTENTION_NOWAIT: Return an error if the lock cannot be obtained immediately. + LockContention::SKIP_LOCKED, LOCK_CONTENTION_SKIP_LOCKED: Execute the query immediately, excluding from the query items that are locked. For X DevAPI and X DevAPI for C applications, lock mode methods accept these lock contention constants as a parameter. For X DevAPI ap
MySQL Cluster 7.6.6 GA has been released
Dear MySQL Users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance (with optional checkpointing to disk) - Transparent Auto-Paritioning (Sharding) - Read & write scalability - Transactional consistency across partitioned and distributed datasets - Parallel cross partition queries such as joins - Active-Active/Multi-Master geographic replication - 99.% High Availability with on-line maintenance and no single point of failure - NoSQL and SQL APIs (including C++, Java, http, Memcached and JavaScript/Node.js) MySQL Cluster 7.6.6 GA, has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.6/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime and agility. More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! Changes in MySQL NDB Cluster 7.6.6 (5.7.22-ndb-7.6.6) (2018-05-31, General Availability) MySQL NDB Cluster 7.6.6 is a new release of NDB 7.6, based on MySQL Server 5.7 and including features in version 7.6 of the NDB storage engine, as well as fixing recently discovered bugs in previous NDB Cluster releases. Obtaining NDB Cluster 7.6. NDB Cluster 7.6 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in NDB Cluster 7.6, see What is New in NDB Cluster 7.6 (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-what-is-new-7-6.html). This release also incorporates all bug fixes and changes made in previous NDB Cluster releases, as well as all bug fixes and feature changes which were added in mainline MySQL 5.7 through MySQL 5.7.22 (see Changes in MySQL 5.7.22 (2018-04-19, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-22.html)). Functionality Added or Changed * When performing an NDB backup, the ndbinfo.logbuffers table now displays information regarding buffer usage by the backup process on each data node. This is implemented as rows reflecting two new log types in addition to REDO and DD-UNDO. One of these rows has the log type BACKUP-DATA, which shows the amount of data buffer used during backup to copy fragments to backup files. The other row has the log type BACKUP-LOG, which displays the amount of log buffer used during the backup to record changes made after the backup has started. One each of these log_type rows is shown in the logbuffers table for each data node in the cluster. Rows having these two log types are present in the table only while an NDB backup is currently in progress. (Bug #25822988) * Added the --logbuffer-size option for ndbd and ndbmtd, for use in debugging with a large number of log messages. This controls the size of the data node log buffer; the default (32K) is intended for normal operations. (Bug #89679, Bug #27550943) * The previously experimental shared memory (SHM) transporter is now supported in production. SHM works by transporting signals through writing them into memory, rather than on a socket. NDB already attempts to use SHM automatically between data nodes and API nodes sharing the same host. To enable explicit shared memory connections, set the UseShm SHM configuration parameter to true. When explicitly defining shared memory as the connection method, it is also necessary to identify the nodes at either end of the connection (NodeId1 and NodeId2 parameters), and to provide a shared memory key (ShmKey). In addition, to improve performance, it is also possible to set a spin time (ShmSpinTime) for the SHM transporter. Configuration of SHM is otherwise similar to that of the TCP transporter. NDB Cluster Shared-Memory Connections (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-shm-definition.html) , provides additional information. * The SPJ kernel block now takes into account when it is evaluating a join request in which at least some of the tables are used in inner joins. This means that SPJ can eliminate requests for rows or ranges as soon as it becomes known that a preceding request did not return any results for a parent row. This saves both the data nodes and the SPJ block from having to handle requests and result rows which never take part in a result row from an inner join.
[ANN] Mroonga 8.03 - Fast fulltext search for all languages on,MySQL
Mroonga 8.03 has been released! Mroonga is a MySQL storage engine that supports fast fulltext search and geolocation search. It is CJK ready. It uses Groonga as a storage and fulltext search engine. Document: http://mroonga.org/docs/ How to install: Install Guide http://mroonga.org/docs/install.html Blog: http://mroonga.org/en/blog/2018/05/29/mroonga-8.03.html Changes: http://mroonga.org/docs/news.html#release-8.03 The main changes are as follows. There are no big changes in this release. * [Docker] Added quick start guide link to Docker Hub. * http://mroonga.org/docs/install/docker.html * The contributors are helping to maintain monthly. Thank you! * [CentOS Supported MariaDB 10.3.7. * [CentOS] Supported MariaDB 10.2.15 and 10.1.33 (backported to 8.03). * [Windows] Supported MariaDB 10.1.33. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Cluster Manager 1.4.6 has been released
Dear MySQL Users, MySQL Cluster Manager 1.4.6 can be downloaded from the My Oracle Support (MOS) website. It will also be available on Oracle Software Delivery Cloud at http://edelivery.oracle.com with the next monthly update MySQL Cluster Manager is an optional component of the MySQL Cluster Carrier Grade Edition, providing a command-line interface that automates common management tasks, including the following online operations: - Configuring and starting MySQL Cluster - Upgrades - Adding and removing cluster nodes - Adding and removing site hosts - Configuration changes - Backup and restore MySQL Cluster Manager is a commercial extension to the MySQL family of products. More details can be found at http://www.mysql.com/products/cluster/mcm/. A brief summary of changes in MySQL Cluster Manager version 1.4.6 is listed below: Changes in MySQL Cluster Manager 1.4.6 (2018-05-09) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * Agent: The list backups command has been extended with a new --agent option for listing agent backups created with the backup agents command. See the option description for details. (Bug #27168819, Bug #27850905) Bugs Fixed * Agent: The collect logs command failed to include logs that had been rotated with the rotate log command. (Bug #27918231) * Agent: A list backups command failed with an Error: 1159 (timeout reading communication packets) from one of the mcmd agents when it had a huge number of backups to list. With this fix, mcmd has been optimized to enumerate a larger number of backups. (Bug #27868499) * Agent: The mcmd agent quit unexpectedly if the cluster's global configuration file (config.ini usually) contained a [system] section. It was because in MySQL Cluster Manager, the handling for the [system] section was missing, which has now been added by this fix. The addition also allows mcmd to set the name attribute in the [system] section, which is required for MySQL Enterprise Monitor 4.0 to monitor the cluster. (Bug #27638138, Bug #27519205) * Agent: The collect logs command hung if a host was referenced earlier with the localhost IP address 127.0.0.1 in the create site or create cluster command. (Bug #27551932) * Agent: The create cluster command was successful even if the format of an IP address submitted with it as a hostname was inconsistent with the format used earlier with the add hosts command (for example, a host was added to a site as 127.0.0.1, and then added to a cluster as 127.0.01). A subsequent attempt to start the cluster failed. This fix added consistency check for the host names, so that inconsistent IP addresses are now rejected. (Bug #27551776) * Agent: When a maintenance restart occurred for a cluster node while mcmd was shutting down, the node remained in the starting stage indefinitely. With this fix, a node restart will not be attempted when mcmd is shutting down. (Bug #27513481) * Agent: An Internal error occurred when mcmd tried to set the MySQL Server system variable audit_log_read_buffer_size with a set command. It was because of the wrong data type used internally for the variable, which has now been fixed. (Bug #27413635) * Agent: mcmd quit unexpectedly sometimes when running a restore cluster command. It was due to a race condition in which mcmd started executing the restore before the required ndbapi node was ready for the task. This fix added checks to eliminate the race condition. (Bug #27342271) On behalf of MySQL Release Engineering Team, Surabhi Bhat
MySQL for Visual Studio 1.2.8 has been released
Dear MySQL users, The MySQL Windows Experience Team is proud to announce the release of MySQL for Visual Studio 1.2.8. This is a maintenance release for 1.2.x. It can be used for production environments. MySQL for Visual Studio is a product that includes all of the Visual Studio integration functionality to create and manage MySQL databases when developing .NET applications. MySQL for Visual Studio is installed using the MySQL Installer for Windows which comes in 2 versions: * Full (386.6 MB) which includes a complete set of MySQL products with their binaries included in the downloaded bundle. * Web (1.7 MB - a network install) which will just pull MySQL for Visual Studio over the web and install it when run. You can download MySQL Installer from our official Downloads page at http://dev.mysql.com/downloads/installer/. MySQL for Visual Studio can also be downloaded by using the product standalone installer found at http://dev.mysql.com/downloads/windows/visualstudio/. Changes in MySQL for Visual Studio 1.2.8 (2018-05-04, General Availability) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * When Microsoft Visual Studio receives a request to register (or unregister) MySQL for Visual Studio within the IDE during the installation, Visual Studio might not execute the command properly if the host is running Windows 7. This fix identifies when Visual Studio does not register MySQL for Visual Studio as requested and then provides an alert to perform the registration manually from the Developer Command Prompt for Visual Studio using the following command: devenv /updateconfiguration /log (Bug #27365261, Bug #87902) * MySQL for Visual Studio now supports the MySQL 8.0 release series (requires Connector/Net 6.9.12, 6.10.7, or 8.0.11) including: + MySQL data dictionary, which uses INFORMATION_SCHEMA tables rather than tables in the mysql database (see MySQL Data Dictionary (http://dev.mysql.com/doc/refman/8.0/en/data-dictionary.html)). + The caching_sha2_password authentication plugin introduced in MySQL 8.0 (see Caching SHA-2 Pluggable Authentication (http://dev.mysql.com/doc/refman/8.0/en/caching-sha2-pluggable-authentication.html)). In addition, MySQL for Visual Studio now requires that .NET Framework 4.5.2 (or later) be installed for use within Visual Studio 2012 and Visual Studio 2013. Bugs Fixed * The Website Configuration Tool was unable to add an ADO.NET entity data model to an ADO.NET web application successfully. In addition to aligning the web.config file with the installed version of Connector/Net, this fix also disables the Entity Framework 5 selection when the installed connector no longer includes a provider for EF5 (Connector/Net 6.10 and higher). (Bug #27593219) * Queries made with a valid MySQL connection received no response from the server. (Bug #27584991) * When the MySQL for Visual Studio parser was unable to parse an SQL statement, it generated an unhandled exception that caused Visual Studio to exit unexpectedly. This fix enables the parser to handle exceptions properly and updates the parser to include support for CREATE USER syntax in the MySQL 8.0 release series. (Bug #27580303) * The version for the MySql.Web assembly was incorrectly extracted, which prevented the assembly from loading properly and the MySQL Website Configuration Tool from launching. (Bug #27450530) * Attempting to open the MySQL Web Configuration Tool, with MySQL Connector/Net and MySQL for Visual Studio prerequisites installed properly, displayed an error message instead of opening the tool. (Bug #27365141, Bug #88570) On Behalf of MySQL Release Engineering Team, Surabhi Bhat -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
[ANN] Mroonga 8.02 - Fast fulltext search for all languages on MySQL
Hi, Mroonga 8.02 has been released! Mroonga is a MySQL storage engine that supports fast fulltext search and geolocation search. It is CJK ready. It uses Groonga as a storage and fulltext search engine. Document: http://mroonga.org/docs/ How to install: Install Guide http://mroonga.org/docs/install.html How to upgrade: Upgrade Guide http://mroonga.org/docs/upgrade.html Blog: http://mroonga.org/en/blog/2018/04/29/mroonga-8.02.html Changes: http://mroonga.org/docs/news.html#release-8.02 Here is a topic in this release. * Supported Ubuntu 18.04 LTS (Bionic Beaver). * [CentOS][Percona Server] Supported upgrading from "< 5.6.34" and "< 5.7.21". * detail: https://github.com/mroonga/mroonga/commit/555d6683bd2a095180fb278faffbe611bf62a8a3 * Fixed a crash bug when some complex condition in `ORDER BY` such as `ORDER BY 1 + 1, id, content`. * Fixed a bug that `MATCH AGAINST` condition is ignored if SQL containing such as`AND (x = 1 OR x = 2)` when condition push down is enabled. * Fixed a memory leak for column caches. Regards, -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
MySQL Cluster 7.6.5-dmr has been released
Dear MySQL Users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance (with optional checkpointing to disk) - Transparent Auto-Sharding - Read & write scalability - Active-Active/Multi-Master geographic replication - 99.999% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http, Memcached and JavaScript/Node.js) MySQL Cluster 7.6.5-dmr, has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.6/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime and agility. More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! Changes in MySQL NDB Cluster 7.6.5 (5.7.20-ndb-7.6.5) (2018-04-20, Development Milestone 5) MySQL NDB Cluster 7.6.5 is a new release of NDB 7.6, based on MySQL Server 5.7 and including features in version 7.6 of the NDB storage engine, as well as fixing recently discovered bugs in previous NDB Cluster releases. Obtaining NDB Cluster 7.6. NDB Cluster 7.6 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in NDB Cluster 7.6, see What is New in NDB Cluster 7.6 (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-what-is-new-7-6.html). This release also incorporates all bug fixes and changes made in previous NDB Cluster releases, as well as all bug fixes and feature changes which were added in mainline MySQL 5.7 through MySQL 5.7.20 (see Changes in MySQL 5.7.20 (2017-10-16, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-20.html)). Bugs Fixed * NDB Client Programs: On Unix platforms, the Auto-Installer failed to stop the cluster when ndb_mgmd was installed in a directory other than the default. (Bug #89624, Bug #27531186) * NDB Client Programs: The Auto-Installer did not provide a mechanism for setting the ServerPort parameter. (Bug #89623, Bug #27539823) * Writing of LCP control files was not always done correctly, which in some cases could lead to an unplanned shutdown of the cluster. This fix adds the requirement that upgrades from NDB 7.6.4 (or earlier) to this release (or a later one) include initial node restarts. (Bug #26640486) On Behalf of the MySQL/Oracle 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 Cluster 7.4.20 has been released
Dear MySQL Users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance - Transparent Auto-Sharding - Read & write scalability - Active-Active/Multi-Master geographic replication - 99.999% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http, Memcached and JavaScript/Node.js) MySQL Cluster 7.4 makes significant advances in performance; operational efficiency (such as enhanced reporting and faster restarts and upgrades) and conflict detection and resolution for active-active replication between MySQL Clusters. MySQL Cluster 7.4.20, has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.4/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime and agility. More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! == Changes in MySQL NDB Cluster 7.4.20 (5.6.40-ndb-7.4.20) (2018-04-20, General Availability) MySQL NDB Cluster 7.4.20 is a new release of MySQL NDB Cluster 7.4, based on MySQL Server 5.6 and including features in version 7.4 of the NDB storage engine, as well as fixing recently discovered bugs in previous NDB Cluster releases. Obtaining MySQL NDB Cluster 7.4. MySQL NDB Cluster 7.4 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL NDB Cluster 7.4, see What is New in NDB Cluster 7.4 (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is-new-7-4.html). This release also incorporates all bug fixes and changes made in previous NDB Cluster releases, as well as all bug fixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.40 (see Changes in MySQL 5.6.40 (2018-04-19, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-40.html)). Bugs Fixed * NDB Cluster APIs: The maximum time to wait which can be specified when calling either of the NDB API methods Ndb::pollEvents() or pollEvents2() was miscalculated such that the method could wait up to 9 ms too long before returning to the client. (Bug #88924, Bug #27266086) * Race conditions sometimes occurred during asynchronous disconnection and reconnection of the transporter while other threads concurrently inserted signal data into the send buffers, leading to an unplanned shutdown of the cluster. As part of the work fixing this issue, the internal templating function used by the Transporter Registry when it prepares a send is refactored to use likely-or-unlikely logic to speed up execution, and to remove a number of duplicate checks for NULL. (Bug #2908, Bug #25128512) References: See also: Bug #20112700. On Behalf of Oracle/MySQL Release Engineering Team, Daniel Horecki -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Cluster 7.5.10 has been released
Dear MySQL Users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance (with optional checkpointing to disk) - Transparent Auto-Sharding - Read & write scalability - Active-Active/Multi-Master geographic replication - 99.999% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http, Memcached and JavaScript/Node.js) MySQL Cluster 7.5.10, has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. MySQL Cluster 7.5 is also available from our repository for Linux platforms, go here for details: http://dev.mysql.com/downloads/repo/ The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.5/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime and agility. More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! Changes in MySQL NDB Cluster 7.5.10 (5.7.22-ndb-7.5.10) (2018-04-20, General Availability) MySQL NDB Cluster 7.5.10 is a new release of MySQL NDB Cluster 7.5, based on MySQL Server 5.7 and including features in version 7.5 of the NDB (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.html) storage engine, as well as fixing recently discovered bugs in previous NDB Cluster releases. Obtaining MySQL NDB Cluster 7.5. MySQL NDB Cluster 7.5 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL NDB Cluster 7.5, see What is New in NDB Cluster 7.5 (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-what-is-new-7-5.html). This release also incorporates all bug fixes and changes made in previous NDB Cluster releases, as well as all bug fixes and feature changes which were added in mainline MySQL 5.7 through MySQL 5.7.22 (see Changes in MySQL 5.7.22 (2018-04-19, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-22.html)). Bugs Fixed * NDB Cluster APIs: A previous fix for an issue, in which the failure of multiple data nodes during a partial restart could cause API nodes to fail, did not properly check the validity of the associated NdbReceiver object before proceeding. Now in such cases an invalid object triggers handling for invalid signals, rather than a node failure. (Bug #25902137) References: This issue is a regression of: Bug #25092498. * NDB Cluster APIs: Incorrect results, usually an empty result set, were returned when setBound() (http://dev.mysql.com/doc/ndbapi/en/ndb-ndbindexscanoperation-setbound.html) was used to specify a NULL bound. This issue appears to have been caused by a problem in gcc, limited to cases using the old version of this method (which does not employ NdbRecord (http://dev.mysql.com/doc/ndbapi/en/ndb-ndbrecord.html)), and is fixed by rewriting the problematic internal logic in the old implementation. (Bug #89468, Bug #27461752) * In some circumstances, when a transaction was aborted in the DBTC block, there remained links to trigger records from operation records which were not yet reference-counted, but when such an operation record was released the trigger reference count was still decremented. (Bug #27629680, Bug #27629680) * ANALYZE TABLE (http://dev.mysql.com/doc/refman/5.7/en/analyze-table.html) used excessive amounts of CPU on large, low-cardinality tables. (Bug #27438963) * Queries using very large lists with IN were not handled correctly, which could lead to data node failures. (Bug #27397802) * A data node overload could in some situations lead to an unplanned shutdown of the data node, which led to all data nodes disconnecting from the management and nodes. This was due to a situation in which API_FAILREQ was not the last received signal prior to the node failure. As part of this fix, the transaction coordinator's handling of SCAN_TABREQ signals for an ApiConnectRecord in an incorrect state was also improved. (Bug #27381901) References: See also: Bug #47039, Bug #11755287. * In a two-node cluster, when the node having the lowest ID was started using --nostart (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndbd.html#option_ndbd_nostart), API clients could not connect, failing with Could not alloc node id at HOST port PORT_NO: No free node id found for mysqld(API). (Bug #27225212) *
MySQL Cluster 7.3.21 has been released
Dear MySQL Users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance (with optional checkpointing to disk) - Transparent Auto-Sharding - Read & write scalability - Active-Active/Multi-Master geographic replication - 99.999% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http, Memcached and JavaScript/Node.js) MySQL Cluster 7.3.21, has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.3/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime and agility. More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! == Changes in MySQL NDB Cluster 7.3.21 (5.6.39-ndb-7.3.21) (2018-04-20, General Availability) MySQL NDB Cluster 7.3.21 is a new release of NDB Cluster, based on MySQL Server 5.6 and including features from version 7.3 of the NDB storage engine, as well as fixing a number of recently discovered bugs in previous NDB Cluster releases. Obtaining MySQL NDB Cluster 7.3. MySQL NDB Cluster 7.3 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL NDB Cluster 7.3, see What is New in NDB Cluster 7.3( http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is-new-7-3.html ). This release also incorporates all bug fixes and changes made in previous NDB Cluster releases, as well as all bug fixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.40 (see Changes in MySQL 5.6.40 (2018-04-19, General Availability)( http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-40.html )). Bugs Fixed * NDB Cluster APIs: Incorrect results, usually an empty result set, were returned when setBound() was used to specify a NULL bound. This issue appears to have been caused by a problem in gcc, limited to cases using the old version of this method (which does not employ NdbRecord), and is fixed by rewriting the problematic internal logic in the old implementation. (Bug #89468, Bug #27461752) * Queries using very large lists with IN were not handled correctly, which could lead to data node failures. (Bug #27397802) * ndb_restore --print_data --hex did not print trailing 0s of LONGVARBINARY values. (Bug #65560, Bug #14198580) On Behalf of Oracle/MySQL Release Engineering Team Prashant Tekriwal
MySQL Connector/Python 8.0.11 has been released
Dear MySQL users, MySQL Connector/Python 8.0.11 is the first GA release version of the MySQL Connector Python 8.0 series. This series adds support for the new X DevAPI. The X DevAPI enables application developers to write code that combines the strengths of the relational and document models using a modern, NoSQL-like syntax that does not assume previous experience writing traditional SQL. To learn more about how to write applications using the X DevAPI, see http://dev.mysql.com/doc/x-devapi-userguide/en/. For more information about how the X DevAPI is implemented in MySQL Connector/Python, and its usage, seehttp://dev.mysql.com/doc/dev/connector-python. Please note that the X DevAPI requires MySQL Server version 5.7.12 or higher with the X Plugin enabled. For general documentation about how to get started using MySQL as a document store, see http://dev.mysql.com/doc/refman/5.7/en/document-store.html. To download MySQL Connector/Python 8.0.11, see the "General Available (GA) releases" tab athttp://dev.mysql.com/downloads/connector/python/ Enjoy! Changes in MySQL Connector/Python 8.0.11 (2018-04-19) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * X DevAPI: Previously, when documents without an _id attribute were added to a collection, Connector/Python automatically generated _id for them. Now a MySQL 8 server generates the _id attribute unless a document already contains one. The generated IDs resulting from a document-add operation can be obtained using the new get_generated_ids() method. This capability requires a MySQL 8.0 server. Because MySQL 5.7 does not support document ID generation, the document-add operation returns an error if you do not define the _id's. Incompatibility: The get_generated_ids() method replaces the now removed get_document_ids(). (Bug #27627366) * Added NOWAIT and SKIP_LOCKED support to the ReadStatement.lock_shared() and ReadStatement.lock_exclusive() methods. Example usage: lock_exclusive(mysqlx.LockContention.SKIP_LOCKED). * The C extension (cext) is now enabled by default, as the use_pure option changed from True to False by default. If the C extension is not available on the system then the Python implementation is used instead, and use_pure is set to True. * Added the X DevAPI SHA256_MEMORY authentication mechanism. Example mysqlx.get_session() usages: ?auth=SHA256_MEMORY via a connection string, "auth": mysqlx.Auth.SHA256_MEMORY via a dictionary, or auth=mysqlx.Auth.SHA256_MEMORY via method parameters. Bugs Fixed * Warnings are now stored as a list of dictionaries instead of a list of tuples. In other words, get_warnings() returns the likes of [{"level": _level_, "code": _code_, "msg": _msg_}] instead of [(_level_, _code_, _msg_))]. (Bug #27639119) * The mapped MySQL Server error codes were synced with MySQL Server 8.0.11. (Bug #27634885) * Removed upsert functionality from InsertStatement as it can only be used by collections, so upsert remains available to AddStatement. (Bug #27589450) * MySQLConverter.escape() functionality was added to create_schema()'s count mechanism. (Bug #27528842) * When using prepared statements, string columns were returned as bytearrays instead of strings. The returned value is now a string decoded using the connection's charset (defaults to 'utf8'), or as a bytearray if this conversion fails. (Bug #27364914) * The result from JSON_TYPE() was returned as a bytearray instead of a string. The returned value is now a string decoded using the connection's charset (defaults to 'utf8'), or as a bytearray if this conversion fails. (Bug #24948205, Bug #83516) * JSON integer values were cast to bytes in Python instead of integers. (Bug #24948186, Bug #83513) On Behalf of Oracle/MySQL Release Engineering Team Prashant Tekriwal
MySQL Connector/Net 8.0.11 has been released
Dear MySQL users, MySQL Connector/Net 8.0.11 is the first general availability release of MySQL Connector/Net to add support for the new X DevAPI. The X DevAPI enables application developers to write code that combines the strengths of the relational and document models using a modern, NoSQL-like syntax that does not assume previous experience writing traditional SQL. To learn more about how to write applications using the X DevAPI, see http://dev.mysql.com/doc/x-devapi-userguide/en/index.html. For more information about how the X DevAPI is implemented in Connector/Net, see http://dev.mysql.com/doc/dev/connector-net. Please note that the X DevAPI requires at least MySQL Server version 5.7.12 or higher with the X Plugin enabled. For general documentation about how to get started using MySQL as a document store, see http://dev.mysql.com/doc/refman/5.7/en/document-store.html. To download MySQL Connector/Net 8.0.11, see http://dev.mysql.com/downloads/connector/net/ Changes in MySQL Connector/Net 8.0.11 (2018-04-19) Functionality Added or Changed * X DevAPI: Connector/Net now supports the NOWAIT and SKIP_LOCKED locking options introduced in the MySQL 8.0 release series (see SELECT Syntax (http://dev.mysql.com/doc/refman/5.7/en/select.html)). The following changes were made to the Connector/Net API: + The LockContention enumeration (with values Default=0, NoWait=1 and SkipLocked=2) was added. The Default enumeration member represents the previous behavior of waiting for the row locks to be released. + The existing LockShared() and LockExclusive() method signatures were modified to include the new LockContention parameter. Both methods are members of the MySqlX.XdevAPI.CRUD.FindStatement and MySqlX.XdevAPI.Relational.TableSelectStatement classes. + Usage examples: // Default behavior - waits for the row locks to release LockShared() LockShared(LockContention.Default) LockExclusive() LockExclusive(LockContention.Default) // New - fails if the rows are locked LockShared(LockContention.NoWait) LockExclusive(LockContention.NoWait) // New - succeeds excluding the locked rows from the result LockShared(LockContention.SkipLocked) LockExclusive(LockContention.SkipLocked) * X DevAPI: Previously, when documents without an _id attribute were added to a collection, Connector/Net automatically generated IDs for them. Now the server generates the _id attribute, unless a document already contains one. The generated IDs resulting from a document-add operation can be obtained using the new Result.GeneratedIds property, which returns a list. This capability requires a MySQL 8.0 GA server. If the server does not support document ID generation, the document-add operation returns an error indicating that document IDs were missing. Incompatibility: The GeneratedIds property replaces the DocumentId and DocumentIds properties, which are now removed. * X DevAPI: Support for the SHA256_MEMORY authentication mechanism was added to enable non-PLAIN insecure connections (without SSL) for user accounts with caching_sha2_password, which is the default authentication plugin introduced in the MySQL 8.0 release series. The changes related to this support include: + New synonyms for the auth connection string option: authentication and authentication mode (see General Options (http://dev.mysql.com/doc/connector-net/en/connector-net-connection-options.html#connector-net-connection-options-general)). + A new authentication mode for the MySqlAuthenticationMode enumeration: SHA256_MEMORY. In addition, the Default member now has a new synonym: Auto=0. + A new class: MySql.Data.MySqlClient.Authentication.Sha256MemoryAu thenticationPlugin. * Support was added for the new caching_sha2_password padding mechanism introduced in the MySQL 8.0 release series. The new padding mechanism is enabled when all of the following conditions apply: + The user account is set with the caching_sha2_password authentication plugin. + SSL is disabled explicitly (SslMode=none). + The AllowPublicKeyRetrieval connection option is enabled (AllowPublicKeyRetrieval=true). When enabled, the new padding mechanism is used to encode the password during RSA key encryption, which applies the correct padding to match the server. Bugs Fixed * Attempting to open the MySQL Web Configuration Tool, with Connector/Net and MySQL for Visual Studio prerequisites installed properly, displayed an error message instead
MySQL Connector/C++ 8.0.11 GA has been released
Dear MySQL users, MySQL Connector/C++ 8.0.11 is the first GA 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++ applications using X DevAPI or plain C applications using XAPI. To learn more about how to write applications using X DevAPI, see "X DevAPI User Guide" https://dev.mysql.com/doc/x-devapi-userguide/en/ and "X DevAPI Reference" at https://dev.mysql.com/doc/dev/connector-cpp/devapi_ref.html For more information about using plain C XAPI see "XAPI 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/ Note For X DevAPI or XAPI applications, Connector/C++ 8.0 requires MySQL Server 5.7.12 or higher with X Plugin enabled. For applications that use the legacy JDBC API, Connector/C++ 8.0 can use MySQL Server 5.5 or higher, and X Plugin is not required. https://dev.mysql.com/doc/refman/5.7/en/document-store.html To download MySQL Connector/C++ 8.0.11, see the "Generally Available(GA) Releases" tab at https://dev.mysql.com/downloads/connector/cpp/ Changes in MySQL Connector/C++ 8.0.11 (2018-04-19, General Availability) For MySQL Connector/C++ 8.0.11 and higher, Commercial and Community distributions require the Visual C++ Redistributable for Visual Studio 2015 to work on Windows platforms. The Redistributable is available at the Microsoft Download Center (http://www.microsoft.com/en-us/download/default.aspx); install it before installing Connector/C++. Functionality Added or Changed * Incompatible Change: When documents without an _id attribute are added to a collection, the server now automatically generates IDs for them. The server determines the ID format, which should be considered opaque from the API perspective (they are no longer UUID-based). As before, no _id attribute is generated if a document already contains one. User-provided document IDs must not conflict with IDs of other documents in the collection. This capability requires a MySQL 8.0 GA server. If the server does not support document ID generation, the document-add operation returns an error indicating that document IDs were missing. For X DevAPI, the generated IDs resulting from a document-add operation can be obtained using the new Result.getGeneratedIds() method, which returns a list. For XAPI, the generated IDs can be obtained using the new mysqlx_fetch_generated_id() function, which returns IDs one by one for successive calls, until it returns NULL to indicate no more generated IDs are available. For both X DevAPI and XAPI, document IDs specified explicitly in added documents are not returned. Incompatibility: The getGeneratedIds() method replaces getDocumentId() and getDocumentIds(), which are now removed. The mysqlx_fetch_generated_id() function replaces mysqlx_fetch_doc_id(), which is now removed. * A patch operation has been implemented that enables specifying a JSON-like object that describes the changes to apply to documents in a collection. For X DevAPI, the CollectionModify operation supports a new patch() clause for patching documents. For XAPI, there are two new functions: mysqlx_collection_modify_patch() directly executes patching on documents in a collection that satisfy given criteria. mysqlx_set_modify_patch() adds a patch operation to a modify statement created with the mysql_collection_modify_new() function. * For connections to the server made using the legacy JDBC API (that is, not made using X DevAPI or XAPI), Connector/C++ 8.0 now supports an OPT_GET_SERVER_PUBLIC_KEY connection option that enables requesting the RSA public key from the server. For accounts that use the caching_sha2_password or sha256_password authentication plugin, this key can be used during the connection process for RSA key-pair based password exchange with TLS disabled. This capability requires a MySQL 8.0 GA server, and is supported only for Connector/C++ built using OpenSSL. Bugs Fixed * Single-document methods such as Collection.replaceOne() did not accept expr() as the document specification, but instead treated it as a plain JSON string. (Bug #27677910) * Compiling X DevAPI and XAPI test programs failed with an error. (Bug #27610760) * Connecting with an incorrect SSL_CA value could result in a memory leak. (Bug #27434254) * For debug builds, specifying a document as _id raised an