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.4.24 has been released
See also: Bug #27832033. * ndb_restore employed a mechanism for restoring autoincrement values which was not atomic, and thus could yield incorrect autoincrement values being restored when multiple instances of ndb_restore were used in parallel. (Bug #27832033) References: See also: Bug #27917769, Bug #27831990. * An NDB table having both a foreign key on another NDB table using ON DELETE CASCADE and one or more TEXT or BLOB columns leaked memory. (Bug #27484882) * When executing the redo log in debug mode it was possible for a data node to fail when deallocating a row. (Bug #93273, Bug #28955797) 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/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.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/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 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 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 Connector/Node.js 8.0.13 has been released
eeded for each selected server. }); In a multi-host scenario, the connect-timeout value applies to each individual host. Bugs Fixed * Improved the handling of X Protocol global notices by properly logging and then ignoring non-fatal errors, and making the connection unusable for subsequent operations in the case of a fatal error. (Bug #28653781) * Calling getCollationName() on non-textual fields, such as INT, threw the following error "TypeError: Cannot read property 'collation' of undefined". (Bug #28608923) * The fields() method did not function with valid expressions generated by the expr() method. (Bug #28409639) * The returned Session.inspect() object now includes the 'user' property in addition to the 'dbUser' property but containing the same value. (Bug #28362115) 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 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 Shell 8.0.12 for MySQL Server 8.0 and 5.7 has been released
uster() and retrieve a cluster without quorum a warning is issued in addition to the log message. (Bug #27148943) * The memberSslMode option could be used with cluster.addInstance() and cluster.rejoinInstance() operations but if you specified a different value than the one used at cluster creation an error was thrown. Now set the SSL mode at the cluster level only, in other words when issuing dba.createCluster(). The memberSslMode option has been removed from cluster.addInstance() and cluster.rejoinInstance(). (Bug #27062122) * When you issued dba.configureLocalInsance() on an instance, it configured the disabled_storage_engines variable with the MyISAM, BLACKHOLE, FEDERATED, CSV, and ARCHIVE storage engines to ensure that the storage engine was set to InnoDB, as required by Group Replication. The change to this option was not being reported correctly by AdminAPI, and hence the required restart after changing the disabled_storage_engines variable was not clear. This change was deemed a recommendation, rather than a requirement, hence dba.configureLocalInsance() no longer configures disabled_storage_engines. (Bug #26754410) * Creating a cluster using an account which was missing the global grant option failed with an ambiguous error message, even though dba.checkInstanceConfiguration() did not return any errors. Now when you create a cluster, the account being used to administer the cluster is checked to ensure that it has the global grant option. (Bug #25966235) * MySQL Shell is able to automatically reconnect global session when running in the interactive mode, but AdminAPI methods lacked this feature. This resulted in you having to reconnect manually. Now, the AdminAPI methods which utilize the global session object have been improved in order to detect an interrupted session and trigger the reconnection mechanism. The Cluster object uses its own internal session instance, which does not support automatic reconnection. If connection to the cluster is lost, you need to manually recreate the Cluster object. (Bug #24702489) * In the event of a whole cluster stopping unexpectedly, upon reboot the memberSslMode was not preserved. In a cluster where SSL had been disabled, upon issuing dba.rebootClusterFromCompleteOutage() this could prevent instances from rejoining the cluster. (Bug #90793, Bug #27986413) 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/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 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 Cluster 7.6.6 GA has been released
drop a foreign key, it did not perform any filtering for foreign keys, making it possible for it to attempt retrieval of an index or trigger instead, leading to a spurious Error 723 (No such table). 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.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 Community Server 5.7.22 has been released
A DATE column in the inner table of the join was part of a multi-column primary key. Every column in the inner table's primary key was compared with another value; this could be either a literal or a column value. (Bug #25949639) * Using the C API, when trying to execute an INSERT prepared statement with CURSOR_TYPE_READ_ONLY set, the client hung. (Bug #25701141, Bug #85105) * Large --ssl-cipher values could cause client programs to exit. (Bug #25483593) * MySQL client programs could exit unexpectedly if malformed client/server protocol packets were received. (Bug #25471090) * Incorrect handling by the CONNECTION_CONTROL plugin of an internal hash led to spurious messages in the error log and eventual server exit. (Bug #25052009) * Conversion of JSON documents to string could be slow if the document was large and contained many signed integers. (Bug #24586888) * For debug builds, a missing error check on the result of a subquery that accessed a JSON value could raise an assertion. (Bug #22522073) * DO turned error signals into warnings. (Bug #17043030, Bug #69647) * The audit_log plugin did not log placeholder values for prepared statements. (Bug #16617026) * When an on-disk temporary table was created from an in-memory temporary table, the indexes remained uninitialized for the new on-disk table. (Bug #88601, Bug #27214153) * When a stored procedure contained a statement referring to a view which in turn referred to another view, the procedure could not be invoked successfully more than once. (Bug #87858, Bug #26864199) References: See also: Bug #26627136. * A CREATE TABLE ... SELECT statement with a UNION in the SELECT failed in strict mode for a DATE column declared as NOT NULL. (Bug #87711, Bug #27068222) * Prepared statements using nested sub-selects were not always handled correctly. (Bug #87484, Bug #26657904) * Manipulation of a value returned by the JSON_MERGE() function using JSON_SET() sometimes produced an invalid result. (Bug #80787, Bug #22961128) 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/Java 5.1.46 GA has been released
MySQL 8.0 Server. Bugs Fixed * When Connector/J 5.1.44 or earlier connected to MySQL 5.7.20 or later, warnings are issued because Connector/J used the deprecated system variables tx_isolation and tx_read_only. These SQL-level warnings, returned from a SHOW WARNINGS statement, might cause some applications to throw errors and stop working. With this fix, the deprecated variables are no longer used for MySQL 5.7.20 and later; also, to avoid similar issues, a SHOW WARNINGS statement is no longer issued for the use of deprecated variables. (Bug #27029657, Bug #88227) * When the default database was not specified for a connection, the connection attributes did not get stored in the session_connect_attrs table in the Performance Schema of the MySQL Server. (Bug #22362474, Bug #79612) 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/Python 8.0.6-rc has been released
Dear MySQL users, MySQL Connector/Python 8.0.6-rc is the first release candidate 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, see http://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.6-rc, see the "Development Releases" tab at http://dev.mysql.com/downloads/connector/python/ Enjoy! Changes in MySQL Connector/Python 8.0.6 (2018-02-01, Release Candidate) Functionality Added or Changed * A new bdist_wheel distutils command was added to build a Connector/Python wheel package. A new --static option was added that enables static linking for the C extension variant. * X DevAPI: In the process of refining the definition of the X DevAPI to cover the most relevant usage scenarios, the following API components have been removed from the X DevAPI implementation for Connector/Python: + API components that support session configurations. The mysqlx.config namespace and all members of the namespace. + The create_table, drop_table, create_view, drop_view, and alter_view methods from the Schema class. * A Pylint test was added for the mysqlx module. * A new Modify.patch() method was added to the X DevAPI as a way to change several document attributes in one operation; otherwise known as a JSON Merge Patch via RFC 7386. * The create_index() method was added to the Collection API. * The transaction API was extended to allow setting savepoints. The following methods have been added to the Session object: + set_savepoint([name]): executes the SAVEPOINT name SQL statement to generate a savepoint. If a name is not provided (or None), one is generated. The SAVEPOINT statement sets a named transaction savepoint with a name of identifier. If the current transaction has a savepoint with the same name, the old savepoint is deleted and a new one is set. + release_savepoint(name): executes the RELEASE name SQL statement to release a savepoint. The RELEASE SAVEPOINT statement removes the named savepoint from the set of savepoints of the current transaction. No commit or rollback occurs. It returns an error if the savepoint does not exist. + rollback_to(name): executes the ROLLBACK TO name SQL statement to rollback a savepoint. The ROLLBACK TO identifier command reverts the state of the transaction back to what was when executed the command SAVEPOINT identifier. Names passed to these functions are checked to make sure that the name is not null or an empty string. Names such as '', "", ``, and so on, are not allowed even though they are allowed by the server. For more information, see SAVEPOINT, ROLLBACK TO SAVEPOINT, and RELEASE SAVEPOINT Syntax (http://dev.mysql.com/doc/refman/5.7/en/savepoint.html). Bugs Fixed * On Enterprise Linux 7, SSL connections could fail due to the Python 2.7.9 or higher requirement. Since EL7 backported the SSL module from Python 3 (PEP466) into its default Python 2.7.5, SSL connections are now enabled on EL7. (Bug #27368032) * MySQL Server 8.0 utf8mb4 collations were missing from Connector/Python. (Bug #27277964) * The LICENSE and README files were missing from the C extension ( "cext") builds. (Bug #26912787) * Python 3.6 is now officially supported and tested. 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/Java 8.0.9-rc has been released
at your applications continue to work smoothly with the latest MySQL 8.0 Server. * Connector/J now takes advantage of the MySQL Server 8.0 data dictionary by making the connection property useInformationSchema true by default; this makes Connector/J, by default, access the data dictionary more efficiently by querying tables in the INFORMATION_SCHEME. See INFORMATION_SCHEMA and Data Dictionary Integration (http://dev.mysql.com/doc/refman/8.0/en/data-dictionary-information-schema.html) for details. Users can still set useInformationSchema to false, but for MySQL 8.0.3 and later, some data dictionary queries might then fail, due to deprecations of older data dictionary features. * In the past, query texts were always passed as strings to QueryInterceptor methods, even if the texts were not actually used by them. Now, only suppliers for the texts are passed, and the texts are only extracted by get() calls on the suppliers. Bugs Fixed * The connection property nullNamePatternMatchesAll, when set to false (which was the default value), caused some DatabaseMetaData methods to throw an error when a null search string was used with them. The behavior was not compliant with the JDBC specification, which requires that a search criterion be ignored when a null search string is used for it. The connection property has now been removed from Connector/J 8.0. (Bug #26846249, Bug #87826) * Trying to print the query in a PreparedStatement using the toString() method after it has been closed resulted in an exception (No operations allowed after statement closed) being thrown. (Bug #26748909) * When working with MySQL Server 8.0, an update or delete statement for a CONCUR_UPDATABLE ResultSet failed when the ResultSet's primary keys included a boolean column and the character set used was not latin1. (Bug #26266731) * Connector/J failed to recognize a server greeting error it received during a handshake with the server and parsed the error message as a normal greeting packet, causing an ArrayIndexOutOfBoundsException to be thrown. (Bug #24924097) 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 Community Server 5.7.21 has been released
imizer chose a loose index scan even though the unique index had no index extensions. (Bug #25989915, Bug #86165, Bug #26532061, Bug #87207) References: This issue is a regression of: Bug #21749123, Bug #78244. * Restarting the LDAP server could cause LDAP authentication plugins that used a connection pool to fail to authenticate properly. (Bug #25989788) * CREATE USER IF NOT EXISTS was not written to the binary log if the user existed. This could result in inconsistent replication behavior if the user did not exist on slave servers. A similar issue occurred for ALTER USER IF EXISTS. To avoid inconsistencies, these statements now are written to the binary log. (Bug #25813089, Bug #85733) * Incorrect handling of internal memory buffers could cause a server exit. (Bug #25737271) * MySQL did not compile with GCC 7. (Bug #25643811, Bug #26825211) * Executing a stored procedure containing a statement that created a table from the contents of certain SELECT statements could result in a memory leak. (Bug #25586773) * When an UPDATE required a temporary table having a primary key larger than 1024 bytes and that table was created using InnoDB, the server could exit. (Bug #25153670) * For geometry calculations, invalid input parameters could lead to an incorrect result buffer and cause an assertion to be raised or a server exit. (Bug #25062396) * Under some conditions, the audit_log plugin could recursively lock a mutex, resulting in an unresponsive server. (Bug #24437533) * In some cases, the optimizer chose a loose index scan (QUICK_GROUP_MIN_MAX_SELECT) for a GROUP BY query even when there was a predicate with a disjunction. This is fixed by not performing a range scan when the condition in the WHERE clause results in more than one disjoint range tree. (Bug #24423143) * Setting the MYSQL_GROUP_SUFFIX environment variable had no effect. (Bug #23072792) * Queries with many left joins were slow if join buffering was used (for example, using the block nested loop algorithm). (Bug #18898433, Bug #72854) * A prepared statement containing an ORDER BY list that referred to a parameter was not always handled correctly. (Bug #87863, Bug #26867652) * The server handled triggers and generated columns incorrectly. (Bug #86637, Bug #26251621) 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 Workbench 6.3.10 GA has been released
Dear MySQL users, The MySQL developer tools team announces 6.3.10 as our GA release for MySQL Workbench 6.3. For the full list of changes in this revision, visit http://dev.mysql.com/doc/relnotes/workbench/en/changes-6-3.html For discussion, join the MySQL Workbench Forums: http://forums.mysql.com/index.php?152 Download MySQL Workbench 6.3.10 GA now, for Windows, macOS 10.11+, Oracle Linux 7, Fedora 26 and 27, Ubuntu 16.04 and 17.10 or sources, from: http://dev.mysql.com/downloads/tools/workbench/ Enjoy! Changes in MySQL Workbench 6.3.10 (2017-11-15) Bugs Fixed * Performance information within the Administration - Dashboard tab demonstrated a slow rate of refresh on hosts running macOS High Sierra. (Bug #26921498) * Tooltips within the Administration - Dashboard tab did not display when the mouse pointer was paused over each performance graph and the host was running macOS High Sierra. (Bug #26921467) * Table objects did not display with the Show Selection button during the migration process on hosts running macOS High Sierra. As a result, source objects could not be selected for inclusion or exclusion. (Bug #26921431) * Queries executed with the Limit Rows value set to "Don't Limit" did not display rows in the result grid on hosts running macOS High Sierra. (Bug #26921372) * Executing a query in MySQL Workbench on a host running macOS High Sierra failed to load the result grid completely, which prevented result data from appearing within the Result Grid tab. (Bug #26826418, Bug #87714) * Performing a keyword search in the EER Diagram Editor on hosts running macOS High Sierra caused MySQL Workbench to exit unexpectedly. (Bug #26428849, Bug #87020) * Forward engineering a physical database design did not operate as expected on hosts running macOS High Sierra. (Bug #25979928, Bug #86146) 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 Community Server 5.7.20 has been released
ions. (Bug #25510805) * mysqlpump displayed incorrect progress information about the number of tables dumped. (Bug #25432850) * Some mysqldump warnings went to the standard output rather than the standard error output and consequently were written to the dump file. (Bug #2538, Bug #82992) * LOAD DATA failed to accept multibyte characters that followed an escape sequence. (Bug #25147988, Bug #83950, Bug #25865525) * A server error occurred when a full text search result exceeded the innodb_ft_result_cache_limit setting. The patch for this bug also backports a related patch (Bug #21140111). (Bug #25033538) * If a stored function was considered a constant by the optimizer, calling it from a subquery in a NOT IN condition in the WHERE clause could cause a server exit. (Bug #23577867) * A mysqldump memory leak was fixed. Thanks to Yura Sorokin for the patch. (Bug #23531150, Bug #81714) * Incorrect results or a server exit could result when a query used Batched Key Access optimization and a virtual generated column was part of the join buffer. (Bug #23169112) * If a session rolled back to a savepoint and then was killed, the statements up to the point of the savepoint could be committed. (Bug #22350047, Bug #79596) * For clients that used Connector/Python and authenticated using the sha256_password plugin, the server could handle connections incorrectly. (Bug #21421642) 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 5.1.43 has been released
Dear MySQL Users, MySQL Connector/J 5.1.43, 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 Java is available in source and binary form from the Connector/J download pages at http://dev.mysql.com/downloads/connector/j/5.1.html and mirror sites as well as Maven-2 repositories. MySQL Connector Java (Commercial) is already available for download on the My Oracle Support (MOS) website. This release will be available on eDelivery (OSDC) in next month's upload cycle. As always, we recommend that you check the "CHANGES" file in the download archive to be aware of changes in behavior that might affect your application. MySQL Connector/J 5.1.43 includes the following general bug fixes and improvements, also available in more detail on http://dev.mysql.com/doc/relnotes/connector-j/en/news-5-1-43.html Changes in MySQL Connector/J 5.1.43 (2017-07-21) Version 5.1.43 is a maintenance release of the production 5.1 branch. It is suitable for use with MySQL Server versions 5.5, 5.6, and 5.7. It supports the Java Database Connectivity (JDBC) 4.2 API. Functionality Added or Changed * Update the time zone mappings using the latest IANA and CLDR time zone databases. (Bug #25946965) * A new option for the loadBalancingStrategy connection property called serverAffinity has been added. The servers listed in the new connection property serverAffinityOrder (which should be a subset of the servers in the host list of the connection URL) are contacted in the order they are listed until a server is available or until the list of servers is exhausted, at which point a random load-balancing strategy is used with the hosts not listed by serverAffinityOrder. See descriptions for loadBalancingStrategy and serverAffinityOrder in Driver/Datasource Class Names, URL Syntax and Configuration Properties for Connector/J (http://dev.mysql.com/doc/connector-j/5.1/en/connector-j-reference-configuration-properties.html) for details. (Bug #20182108) Bugs Fixed * Secure JDBC connections did not fall back to the default truststore when a custom one was not provided. (Bug #26243128) * Connector/J failed a number of regression tests in the testsuite related to geographic information system (GIS) functions because of changes to GIS support by the MySQL server. The fix corrects the tests. (Bug #26239946, Bug #26140577) * Attempts to connect to a server started with collation utf8mb4_de_pb_0900_ai_ci resulted in null pointer exceptions. (Bug #26090721) * In com/mysql/jdbc/ServerPreparedStatement.java, the arguments resultSetType and resultSetConcurrency for a call of Connection.preparedStatement() were swapped. (Bug #25874048, Bug #85885) * A NullPointerException was returned when getDate(), getTime(), or getTimestamp() was called with a null Calendar. This fix makes Connector/J throw an SQLException in the case. (Bug #25650305) * Some JDBC proxied objects were missing the proper handling of the equals() methods, thus even comparison of one of these proxied objects to its own self with equals() yielded false. This patch introduces proper handling for the equals() method in all the relevant proxies. (Bug #21931572, Bug #78313) * A server-side prepared statement was not closed when the same statement was being prepared again while the original statement was being cached. This was caused by the silent replacement of the cache entry of the old statement by the new. When this happened repeatedly, it caused eventually the complaint that max_prepared_stmt_count was exceeded. This fix makes sure that when a cache entry for a statement replaces an older one, the older statement is immediately closed. (Bug #20066806, Bug #74932) 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.3.18 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.18, 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.18 (5.6.37-ndb-7.3.18) (2017-07-18, General Availability) MySQL NDB Cluster 7.3.18 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 bugfixes and changes made in previous NDB Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.37 (see Changes in MySQL 5.6.37 (2017-07-17, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-37.html)). Functionality Added or Changed * Important Change; MySQL NDB ClusterJ: The ClusterJPA plugin for OpenJPA is no longer supported by NDB Cluster, and has been removed from the distribution. (Bug #23563810) Bugs Fixed * NDB Replication: Added a check to stop an NDB replication slave when configuration as a multi-threaded slave is detected (for example, if slave_parallel_workers is set to a nonzero value). (Bug #21074209) * Backup .log files contained log entries for one or more extra fragments, due to an issue with filtering out changes logged by other nodes in the same node group. This resulted in a larger .log file and thus use of more resources than necessary; it could also cause problems when restoring, since backups from different nodes could interfere with one another while the log was being applied. (Bug #25891014) * Error 240 is raised when there is a mismatch between foreign key trigger columns and the values supplied to them during trigger execution, but had no error message indicating the source of the problem. (Bug #23141739) References: See also: Bug #23068914, Bug #85857. * ALTER TABLE .. MAX_ROWS=0 can now be performed only by using a copying ALTER TABLE statement. Resetting MAX_ROWS to 0 can no longer be performed using ALGORITHM=INPLACE or the ONLINE keyword. (Bug #21960004) * When compiling the NDB kernel with gcc version 6.0.0 or later, it is now built using -flifetime-dse=1. (Bug #85381, Bug #25690926) On Behalf of the MySQL/Oracle Release Engineering Team, Kent Boortz & Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.7.19 has been released
ults. (Bug #24595639) * The server could dereference a null pointer when a deterministic function returning LONGTEXT was used in a subquery. (Bug #24595581) * Incorrect behavior could occur for INSERT statements executed in stored-program or prepared-statement context, if the VALUES part of an ON DUPLICATE KEY UPDATE clause referred to a BLOB value in the INSERT column list. (Bug #24538207, Bug #25361251, Bug #25530880, Bug #25684790) * systemd support scripts in Debian packages contained hardcoded references to the data directory, making it difficult to change the data directory using --datadir. (Bug #24398446, Bug #82417) * MySQL failed to compile under macOS 10.10.5 using Clang. (Bug #24352163, Bug #82340) * If a REPLACE statement tried to update a row in a table containing a virtual generated column of type BLOB, subsequent DML statements could behave incorrectly. (Bug #23573575) * Compiler flags were adjusted to eliminate numerous warnings that occurred when compiling the keyring_file plugin using Clang. (Bug #22834591, Bug #80524) * If enabling the Event Scheduler caused an event defined as ON COMPLETION NOT PRESERVE to be dropped because its execution time had passed, the drop event was not written to the binary log, causing slaves not to replicate it and replication failure if an event of the same name was created later. (Bug #22150112) * LOAD XML INFILE performance became noticeably slower when the XML file being read contained a great many spaces, such as those introduced by indenting or pretty-printing. Now all leading whitespace is trimmed from each such value before reading it into memory. (Bug #16212207) On Behalf of the MySQL/ORACLE RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL for Excel 1.3.7 has been released
Dear MySQL users, The MySQL Windows Experience Team is proud to announce the release of MySQL for Excel version 1.3.7. This is a maintenance release for 1.3.x. It can be used for production environments. MySQL for Excel is an application plug-in enabling data analysts to very easily access and manipulate MySQL data within Microsoft Excel. It enables you to directly work with a MySQL database from within Microsoft Excel so you can easily do tasks such as: * Importing MySQL Data into Excel * Exporting Excel data directly into MySQL to a new or existing table * Editing MySQL data directly within Excel MySQL for Excel is installed using the MySQL Installer for Windows. The MySQL Installer comes in 2 versions - Full which includes a complete set of MySQL products with their binaries included in the download. - Web (network install) which will just pull the MySQL for Excel over the web and install it when run. You can download MySQL Installer from our official Downloads page at http://dev.mysql.com/downloads/installer/ The MySQL for Excel product can also be downloaded by using the product standalone installer found at this link http://dev.mysql.com/downloads/windows/excel/ Changes in MySQL for Excel 1.3.7 (2017-05-24) Functionality Added or Changed * The way MySQL for Excel shares data-editing sessions among users and between computers was improved. (Bug #25509085, Bug #73314) * The Append Excel Data to Table operation was updated with new advanced options to manage the behavior of rows containing unique key values that are duplicates of those in the database. (Bug #25479653, Bug #83801) * Added a new global option that specifies how to format spatial data as text: Well-Known Text, Keyhole Markup Language, Geography Markup Language, or GeoJSON. (Bug #22081263) * Enhanced the logic that migrates stored MySQL connections to the MySQL Workbench connections.xml file. In previous versions, the migration was offered and if not done at that moment, the dialog to migrate was shown every time MySQL for Excel was launched. There was no way to choose to continue storing MySQL connections in the MySQL for Excel configuration folder, instead of merging them with MySQL Workbench. Now, the Connections Migration dialog offers a way to postpone the migration by one hour, one day, one week, one month, or indefinitely. If the migration is postponed, the dialog is shown again after that time elapses. If the migration is postponed indefinitely, then an option is added to the Options dialog that permits the migration of connections to be done manually, as long as MySQL Workbench is installed. * Support for MySQL Fabric was removed. Bugs Fixed * SSL connections when created with MySQL Workbench should be inactive within MySQL for Excel, which does not support SSL connections. (Bug #25962564) * Selecting a schema containing at least one stored procedure for a MySQL 8.0 or 8.1 connection emitted an error. (Bug #25962347) * Empty string values within Excel column data that were used in an export or append-data operation caused the generated SQL queries to have no value, instead of an empty value corresponding to the data type of the target column (for example: 0 for Integer; false for Bool if the column does not allow NULL values, or NULL otherwise). (Bug #25509312, Bug #84851) * MySQL data could not be refreshed or edited directly in an Excel worksheet by different users or from different computers, which reduced the ability to share data-editing sessions among users or between computers. This fix alters the way connection information is stored by migrating the connection details for related import and edit-data operations from the user settings file to the XML parts of a workbook when the workbook is opened, and if the workbook supports XML parts and the connection information related to that workbook is found in the user settings file. (Bug #25509085, Bug #73314) * User-selected data types that replaced the detected values of a column were lost when the First Row Contains Column Names check box was selected or deselected in preparation for an export-data operation. This fix retains the selected value when the data type is set manually to override the automatically detected type and the check box is selected or deselected. It further adds a new action to reset the column back to automatic detection. (Bug #25492772, Bug #84802) * A portion of the preview area that should be displayed during import, export, and append data operations was concealed by other fields. (Bug
MySQL Community Server 5.5.56 has been released
Dear MySQL users, MySQL Server 5.5.56 is a new version of the 5.5 production release of the world's most popular open source database. MySQL 5.5.56 is recommended for use on production systems. Binary packages for MySQL 5.5.56 are identical to those for MySQL 5.5.55, except for the version number. The change in 5.5.56 for Bug #25942414 is applicable only to those who build from source. 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.56 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.56 is available in source and binary form for a number of platforms from our download pages at: http://dev.mysql.com/downloads/mysql/ The following section lists changes in MySQL since the release of MySQL 5.5.55. http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-56.html Enjoy! Changes in MySQL 5.5.56 (2017-05-02) Security Notes * For the WITH_SSL CMake option, no is no longer a permitted value or the default value. The default is now bundled. Consequently, MySQL now is always built with SSL support. (Bug #25942414) On Behalf of the MySQL/ORACLE RE 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.8 has been released
Dear MySQL users,
MySQL Connector/ODBC 5.3.8, 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 fourth 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).
Also, Connector/ODBC 5.3 introduces a GTK+-based setup library
providing a GUI DSN setup dialog on some Unix-based systems, currently
included in the Debian 7/8, EL6/OL6, EL7/OL7 (64-bit only), Fedora 24/25,
FreeBSD 10/11, SLES 12, Ubuntu 12/14/16 packages. Other new
features in the 5.3 driver are FileDSN and Bookmarks support.
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
Enjoy!
The MySQL Connectors team at Oracle
Changes in MySQL Connector/ODBC 5.3.8 (2017-04-28)
Security Notes
* Security Fix: The linked OpenSSL library for
Connector/ODBC Commercial 5.3.8 has been updated from
version 1.0.2j to version 1.0.2k. Versions of OpenSSL
prior to 1.0.2k are reported to be vulnerable to
2017-3731
(http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3731),
CVE-2017-3732
(http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3732), and
CVE-2017-7055
(http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7055).
This change does not affect the Oracle-produced MySQL
Community build of Connector/ODBC 5.3.8, which uses the
yaSSL library instead. (Bug #25615448, CVE-2017-3731,
CVE-2017-3732, CVE-2017-7055)
Bugs Fixed
* When error 2006 ("MySQL server has gone away") occurred,
Connector/ODBC wrongly returned the SQL_NO_DATA error.
(Bug #25671389)
* When the SQL_TIMESTAMP_STRUCT was used, if the date
portion of a timestamp was populated but the time portion
was uninitialized, queries involving the timestamp would
fail with a Date overflow error. With this fix, the
uninitialized time value is simply ignored. (Bug
#25386024)
* Segmentation faults occurred when catalog, column, or
table names that were too long were passed as arguments
to metadata functions like
SQLColumnPrivileges(),SQLColumns(),SQLTablePrivileges()
and SQLTables(). With this fix, proper errors are
returned in those cases. (Bug #18796005)
* An assertion error occurred when calling
SQLSetDescField() with SQL_DESC_COUNT as FieldIdentifier,
irrespective of the record number set. (Bug #18641633)
* Connector/ODBC quit unexpectedly when a negative column
number was passed as an argument for the SQLGetData()
method. (Bug #18636600)
* When server-side prepared statements were enabled, using
the prefetch option caused SQL syntax errors to be
returned for queries that contained parameter markers.
(Bug #17386788)
* After the attribute SQL_ATTR_MAX_ROWS had been set for a
certain statement handler, a new statement handler also
had the same value set automatically. The fix makes sure
a new statement handler returns all rows by default. (Bug
#17259397, Bug #69554)
* If the NO_INFORMATION_SCHEMA connection option was set,
the SQLTables() function did not return the catalog
correctly when a wildcard or SQL_ALL_CATALOGS was used in
its arguments. (Bug #14005343)
References: See also: Bug #13914518.
On behalf of the Oracle MySQL RE Team,
Hery Ramilison
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql
MySQL Shell 1.0.9 GA has been released
Dear MySQL Users, This is the first GA version of MySQL Shell (a component of the MySQL Server). The MySQL Shell is provided under Oracle's dual-license. MySQL Shell is an interactive JavaScript, Python and SQL console interface, supporting development and administration for the MySQL Server. It provides scriptable API that supports the creation and management of MySQL InnoDB clusters, as well as a modern fluent CRUD API for the MySQL Document Store. The AdminAPI provides an integrated solution for high availability and scalability using InnoDB based MySQL databases, without requiring advanced MySQL expertise. The Document Store DevAPI enables developers and DBAs to create "schema-less" JSON document collections and perform Create, Update, Read, Delete (CRUD) operations on those collections with little to no knowledge of the SQL language. Additionally, MySQL Shell provides partial compatibility with the mysql command line client by supporting many of the same command line options. As with the mysql command line, MySQL Shell can also be used to connect to and send SQL commands to pre-5.7.12 versions of the MySQL server using the standard MySQL network protocol. For more information about how to configure and work with an InnoDB cluster see https://dev.mysql.com/doc/refman/en/mysql-innodb-cluster-userguide.html 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 full documentation on MySQL Server, MySQL Shell and related topics, see http://dev.mysql.com/doc/refman/en/ If you want to write applications that use the the CRUD based X DevAPI use the latest MySQL Connectors for your language of choice. You can also find documentation about Connectors in the MySQL documentation site. For more information about how to download MySQL Shell, see 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 1.0.9 (2017-04-12) Functionality Added or Changed * In SQL mode, support was added for \G to display the SQL result vertically. The --vertical (or -E) command line option was added to display all result sets vertically. This sets the shell.options.outputFormat variable to "vertical". (Bug #24848230) Bugs Fixed * The MYSQLPROVISION environment variable is no longer supported or required by MySQL Shell. (Bug #25733261) * mysqlprovision copyright text was missing the current year. (Bug #25725965) * Access to schema objects using property syntax (db.collection) was not automatically available. (Bug #25721628) * The mysqlprovision binary was not built by default when compiling from source. (Bug #25699824) * Executing print with the --execute option could cause MySQL Shell to stop unexpectedly. (Bug #25684798) * SQL import operations would fail if multiple-line comments were present in the SQL being imported. (Bug #25637606) * When using dba.configureLocalInstance(), error messages generated due to a configuration file update failure would not report the cause of failure but a misleading error message of its core code. (Bug #25593140) * On Windows, error handling was improved to better notify the user when the system's Python does not support SSL. (Bug #25534469) * dba.checkInstanceConfiguration() was not documented in the dba global variable help. (Bug #25487579) * A dissolved cluster object was not being correctly set as invalid, meaning it was possible to access its methods and properties. The fix ensures that dissolved cluster objects are correctly detected and a new error similar to Can't call function 'function_name' is generated when executed on a dissolved cluster. (Bug #25141048) * Global DB object properties could change their semantics at runtime. For example, the property giving the schema name could later be displayed as a table object. This was related to how cached objects were given precedence. Now, on object retrieval, the cache is only accessed if the requested member is not a fixed member of the class. (Bug #24964342) * The addInstance() method did not function on remote MySQL instances. (Bug #24832550) * MySQL Shell was not detecting changes made manually to the cluster topology to use Group Replication multi-primary mode (group_replication_single_primary_mode=OFF). MySQL Shell was not showing the read-write abilities of the instances. (Bug #24756046) * On Unix, MySQL Shell was showing the password used to run the command in the operating system process list. On behalf of the MySQL Shell and MySQL Release Team, Kent Boortz &
MySQL Community Server 5.7.18 has been released
22874167, Bug #80607) * The rpl.rpl_key_rotation test case did not synchronize properly with the master server. Thanks to Laurynas Biveinis for the patch. (Bug #22838596, Bug #80531) * Queries that used an aggregate function with DISTINCT could produce incorrect results. (Bug #22686994, Bug #80310) * For RPM packages, the default error-log location in the deployed /etc/my.cnf file differed from the location in the installed logrotate script, causing logrotate to fail. (Bug #22322685) * After performing inserts in a table containing an AUTO_INCREMENT column and then performing a SELECT operation, the LAST_INSERT_ID() returns the correct value, but the value of the mysql_insert_id() C API function was being reset to 0. (Bug #22028117, Bug #78778) * With the use_index_extensions flag of the optimizer_switch system variable disabled, some SELECT DISTINCT queries could return incorrect results. (Bug #21749123, Bug #78244) * Debian packages were missing an AppArmor-related include file and incorrectly were marked dependent on AppArmor (making it impossible to disable AppArmor by uninstalling it). (Bug #20768958) * In a replication environment, SET PASSWORD or ALTER USER could fail to execute on the slave due to failure to parse the hash string correctly. (Bug #20228478) * On non-Linux Unix systems, the mysql.server startup script used the Linux command pidof rather than pgrep. (Bug #13788154, Bug #64342) * Starting multiple instances of mysqld_safe after an abnormal server exit could result in one mysqld_safe instance killing another. As a consequence of the bug fix, the mysqld_safe.pid file is no longer used. (Bug #11751149, Bug #41908) * The --help message for mysqld_safe was corrected to mention that the --no-defaults, --defaults-file, and --defaults-extra-file options, if given, must be the first argument. (Bug #11745176, Bug #11192) * The bounds check for the XML parser position stack for each level (which has a fixed depth) used the size of the array as the upper limit, and so was off by one. This is fixed by decreasing the allowable depth by one, which actually matches the maximum number of elements in the position stack. (Bug #83871, Bug #25111907) References: See also: Bug #14040071, Bug #15948580. * Timestamps for server-side prepared statements could be written to the binary log up to a second behind timestamps for the corresponding nonprepared statements, leading to time value differences between master and slave servers. (Bug #74550, Bug #19894382, Bug #25187670) On Behalf of the MySQL/ORACLE RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL for Visual Studio 1.2.7 has been released
Dear MySQL users, The MySQL Windows Experience Team is proud to announce the release of MySQL for Visual Studio 1.2.7. 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.7 (2017-04-10) Functionality Added or Changed * Removed Support for Microsoft Visual Studio 2010. * Added support for Microsoft Visual Studio 2017. Bugs Fixed * The MySQL Data Export Tool exported data from the wrong schema when a second schema was selected and then deselected. In addition, all selected schemas were deselected when a single schema was deselected. (Bug #25713981, Bug #2366) * Script files did not accept most keyboard input after the file was saved for the first time. (Bug #25713638, Bug #24751945) What Is New In MySQL for Visual Studio 1.2 --- - New MySQL Project Items for creating data views in Windows Forms and ASP.NET MVC web applications. - A new option in web configuration tool for the ASP.NET Personalization Provider (this feature requires MySQL Connector/NET 6.9 or newer). - A new option in web configuration tool for the ASP.NET Site Map Provider (this feature requires MySQL Connector/NET 6.9 or newer). - A new option for the MySQLSimpleMembership provider in the web configuration tool. (This feature requires MySQL Connector/NET or newer). MySQL Windows Forms Project Item --- This Project Item is available on the Add New Item dialog in Visual Studio when adding a new item to an existing project. The dialog presented to create the MySQL Windows Forms Project Item automates the generation of a Windows Form, representing a view for MySQL data available through an existing Entity Framework's model entity containing a MySQL table or view. Different view types are available to present the data: * Single-column: A form that contains one control by each existing column in the table with navigation controls and that allows CRUD operations.All controls can include validations for numeric and DateTime data types. * Grid: A form with a data grid view that contains navigation controls. * Master-detail: A form with a single control layout for the Parent table and a data grid view to navigate through child table's data. Supported with C# or Visual Basic language. This feature requires Connector/NET 6.7.5, 6.8.3 or 6.9.x. For more details on the features included check the documentation at: https://dev.mysql.com/doc/connector-net/en/visual-studio-project-items-forms.html MySQL ASP.NET MVC Project Item --- This Project Item is available on the Add New Item dialog in Visual Studio when adding a new item to an existing project. The dialog presented to create the MySQL ASP.NET MVC Item automates the generation of a controller and its corresponding view, representing a view for MySQL data available through an existing Entity Framework's model entity containing a MySQL table or view. The MVC versions supported by this wizard are 3 when using Visual Studio 2010 or 2012, and 4 when using Visual Studio 2013 or greater. The generation of the MVC items is done by creating an Entity Framework data model either with Entity Framework version 5 or 6 depending on the user's selection. Supported with C# or Visual Basic language. This feature requires Connector/NET 6.7.5, 6.8.3 or 6.9.x. For more details on the features included check the documentation at: https://dev.mysql.com/doc/connector-net/en/visual-studio-project-items-mvc.html New option in web configuration tool for the ASP.NET Personalization Provider --- Personalization provider allows to store personalization state-state data regarding the content and layout of Web Parts pages-generated by the Web Parts personalization service using MySQL as a
MySQL Cluster Manager 1.4.2 has been released
with the complaint from mcmd that those processes were already stopped, even if they were actually running. That also made it impossible to reconfigure those processes when StopOnError was true. This happened because the failed stop command had left those processes' metadata in an incorrect state. With this fix, the process restart is allowed despite the value of StopOnError. (Bug #24712504) * Agent: Hostnames referenced in the error messages returned by mcmd were always in lower case. With this fix, the hostname is always referred to as it is; moreover, mcmd now always refers to a hostname or the IP address used in creating the cluster. (Bug #21375132) * Agent: A restore cluster command hung, when an mcmd agent failed and the other agents kept waiting to receive messages from it. With the fix, the other agents detect the failure and return an error to the user. (Bug #16907088) * Agent: When a cluster was being started, if a data node failed shortly after it was started and mcmd was still in the process of starting an SQL node, even if the SQL node was started successfully at the end, mcmd might forever lose connection to the SQL node. It happened when the user mcmd required for the mcmd agent did not get created on the SQL node. With this fix, the mcmd user is always created on the SQL node despite a failure of the start cluster command. (Bug #13436550) On behalf of the Oracle MySQL RE Team, -Sreedhar S & Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Utilities 1.6.5 GA has been released
tion for the mysqlreplicate, mysqlrplcheck, and mysqlrplms utilities. (Bug #21497923) * Enabled the use of the --exclude option for the mysqlrplsync utility. (Bug #21270853, Bug #77359) * Corrected a logic error when detecting and setting READ_ONLY mode on the candidate server during promotion for failover. (Bug #21201454, Bug #76522) * When the mysqldiff utility compared columns for indexes, it failed to take into account cardinality changes. That is, if the cardinality of one column differed from the corresponding column in the compared table, the index was considered different. This fix eliminates unnecessarily changes to indexes by the utility when cardinality differences are detected. (Bug #20857151, Bug #76619) * Removed password() function usage in the MySQL Utilities library for MySQL 5.7.6 or later. (Bug #20807296) * The mysqlfailover utility did not remove the failover_console table correctly on exit when run with the --daemon=start option. (Bug #20524886) * Improved the --force option for the mysqldiff utility to allow checks to continue when missing objects are detected. (Bug #20511130, Bug #75822) * Removed an extraneous difference in GRID format output of the mysqldbcompare utility when column sizes differ. (Bug #18763591) * Corrected PEP8 warnings and errors on the utilities code base. (Bug #18755438) * Corrected an issue in which the mysqldbexport utility produced output with inconsistent table and database names. (Bug #18733683) Reporting Bugs -- We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ Enjoy! On Behalf of the MySQL/ORACLE RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Cluster 7.5.5 has been released
eaks; this could later
result in persistent RowId already allocated errors (NDB
Error 899). (Bug #23723110)
References: See also: Bug #19506859, Bug #13927679.
* when a parent NDB
(http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.html)
table in a foreign key relationship was updated, the
update cascaded to a child table as expected, but the
change was not cascaded to a child table of this child
table (that is, to a grandchild of the original parent).
This can be illustrated using the tables generated by the
following CREATE TABLE
(http://dev.mysql.com/doc/refman/5.7/en/create-table.html)
statements:
CREATE TABLE parent(
id INT PRIMARY KEY AUTO_INCREMENT,
col1 INT UNIQUE,
col2 INT
) ENGINE NDB;
CREATE TABLE child(
ref1 INT UNIQUE,
FOREIGN KEY fk1(ref1)
REFERENCES parent(col1) ON UPDATE CASCADE
) ENGINE NDB;
CREATE TABLE grandchild(
ref2 INT,
FOREIGN KEY fk2(ref2)
REFERENCES child(ref1) ON UPDATE CASCADE
) ENGINE NDB;
Table child is a child of table parent; table grandchild
is a child of table child, and a grandchild of parent. In
this scenario, a change to column col1 of parent cascaded
to ref1 in table child, but it was not always propagated
in turn to ref2 in table grandchild. (Bug #83743, Bug
#25063506)
* The NDB binlog injector thread used an injector mutex to
perform two important tasks:
1. Protect against client threads creating or dropping
events whenever the injector thread waited for
pollEvents().
2. Maintain access to data shared by the injector
thread with client threads.
The first of these could hold the mutex for long periods
of time (on the order of 10ms), while locking it again
extremely quickly. This could keep it from obtaining the
lock for data access ("starved") for unnecessarily great
lengths of time.
To address these problems, the injector mutex has been
refactored into two---one to handle each of the two tasks
just listed.
It was also found that initialization of the binlog
injector thread held the injector mutex in several places
unnecessarily, when only local thread data was being
initialized and sent signals with condition information
when nothing being waited for was updated. These unneeded
actions have been removed, along with numerous previous
temporary fixes for related injector mutex starvation
issues. (Bug #83676, Bug #83127, Bug #25042101, Bug
#24715897)
References: See also: Bug #82680, Bug #20957068, Bug
#24496910.
* When ndbmtd was built on Solaris/SPARC with version 5.3
of the GNU tools, data nodes using the resulting binary
failed during startup. (Bug #83500, Bug #24941880)
References: See also: Bug #83517, Bug #24947597.
* MySQL Cluster failed to compile using GCC 6. (Bug #83308,
Bug #24822203)
* When a data node was restarted, the node was first
stopped, and then, after a fixed wait, the management
server assumed that the node had entered the NOT_STARTED
state, at which point, the node was sent a start signal.
If the node was not ready because it had not yet
completed stopping (and was therefore not actually in
NOT_STARTED), the signal was silently ignored.
To fix this issue, the management server now checks to
see whether the data node has in fact reached the
NOT_STARTED state before sending the start signal. The
wait for the node to reach this state is split into two
separate checks:
+ Wait for data nodes to start shutting down (maximum
12 seconds)
+ Wait for data nodes to complete shutting down and
reach NOT_STARTED state (maximum 120 seconds)
If either of these cases times out, the restart is
considered failed, and an appropriate error is returned.
(Bug #49464, Bug #11757421)
* CMake now avoids configuring the
-fexpensive-optimizations option for GCC versions for
which the option triggers faulty shift-or optimizations.
(Bug #24947597, Bug #83517)
On Behalf of the MySQL/ORACLE RE 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 5.7.17 has been released
optimizer determines this to be an "impossible WHERE" condition. (Bug #21032418, Bug #76933) * The return value from an fread() call was not checked. (Bug #20671150) * An in-place ALTER TABLE operation failed to report an error when adding a DATE or DATETIME column under these conditions: a) the column was NOT NULL and no default value was supplied; b) strict and NO_ZERO_DATE SQL modes were enabled; c) the table was not empty. An ALTER TABLE operation failed with an error rather than a warning when adding a DATE or DATETIME column under these conditions: a) the column was NOT NULL and no default value was supplied; b) strict SQL mode was enabled and NO_ZERO_DATE SQL mode was not enabled; c) the table was not empty. (Bug #16888677) On Behalf of the MySQL/ORACLE RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/Python 2.0.5 GA has been released
Dear MySQL users, MySQL Connector/Python 2.0.5 GA is a new GA version of 2.0 release series of the pure Python database driver for MySQL. It can be used for production environments. MySQL Connector/Python version 2.0.5 is compatible with MySQL Server versions 5.5 and greater. Python 2.6 and greater as well as Python 3.3 and greater are supported. Python 2.4, 2.5 and 3.1, 3.2 are not supported. MySQL Connector/Python 2.0.5 is available for download from: http://dev.mysql.com/downloads/connector/python/#downloads The ChangeLog file included in the distribution contains a brief summary of changes in MySQL Connector/Python 2.0.5. For a more complete list of changes, see below or online at: http://dev.mysql.com/doc/relnotes/connector-python/en/ Changes in MySQL Connector/Python 2.0.5 (2016-10-26) Bugs Fixed * A potential SQL injection vector was eliminated. (Bug #22529828, Bug #24816150) Documentation The manual of MySQL Connector/Python is available online here: http://dev.mysql.com/doc/connector-python/en/index.html It is also available for download in various formats here: http://dev.mysql.com/doc/index-connectors.html Reporting Bugs We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ Enjoy ! On behalf of the MySQL Connector/Python and the MySQL/ORACLE RE 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 5.7.16 has been released
Dear MySQL users, MySQL Server 5.7.16, a new version of the popular Open Source Database Management System, has been released. MySQL 5.7.16 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.16 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.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 5.7.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 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.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 section lists the changes in MySQL 5.7 since the release of MySQL 5.7.15. It may also be viewed online at http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-16.html Enjoy! Changes in MySQL 5.7.16 (2016-10-12) Security Notes * Incompatible Change: For STANDALONE and WIN builds, the default secure_file_priv value has changed from the empty string to NULL. This is a secure-by-default setting because it disables import and export operations. To permit those operations, set secure_file_priv to the path name of the directory to use for those operations. (Bug #24679907, Bug #24695274, Bug #24707666) * The linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.1u. For a description of issues fixed in this version, see 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 #24753389) Functionality Added or Changed * yaSSL was upgraded to version 2.4.2. This upgrade corrects issues with: Potential AES side channel leaks; DSA padding for unusual sizes; the SSL_CTX_load_verify_locations() OpenSSL compatibility function failing to handle long path directory names. (Bug #24512715, Bug #24740291) On Behalf of the MySQL/ORACLE RE 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 1.0.4 m3 Development Release has been released
Dear MySQL users,
MySQL Connector/Node.js is a new Node.js driver for use with the X
DevAPI. This release, v1.0.4 M3, is the third development release of the
MySQL Connector/Node.js 1.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/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
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.
Changes in MySQL Connector/Node.js 1.0.4 (2016-10-10 Milestone 3)
Functionality Added or Changed
* Changed package name from 'mysqlx' to '@mysql/xdevapi'.
* The connector can be installed into your project using
Node.js's npm tool. Install from the download file by
issuing:
npm install mysql-connector-nodejs-1.0.4.tar.gz
Or install directly from the npm repository by issuing:
npm install @mysql/xdevapi
For more information on npm see http://npmjs.com.
Bugs Fixed
* The Connector/Node.JS version number can now be retrieved
from the API. For example,
"ver=require('@mysql/mysqlx/package').version;". (Bug
#24571220)
* Added the Schema.getCollectionAsTable() method.
* Added the Collection.count() and Table.count() methods.
* Added support for the Common URI format.
* Added View DDL support.
Enjoy and thanks for the support!
On Behalf of the MySQL/ORACLE RE 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 5.7.15 has been released
as cleartext. (Bug #22922023) * A prepared statement that used a parameter in the select list of a derived table that was part of a join could cause a server exit. (Bug #22392374, Bug #24380263) * MEDIUMINT columns used in operations with long integer values could result in buffer overflow. (Bug #19984392) * A spurious ER_NO_SUCH_TABLE error could occur when attempting to execute a prepared CREATE TABLE ... SELECT statement that used a temporary table in the FROM clause and called a stored function. The same error could occur for a nonprepared version of the statement if used in a stored procedure when the procedure was re-executed. (Bug #16672723, Bug #68972) * EINTR handling in the client library has been fixed so that interrupted read and write calls are retried. Previously, EINTR was ignored. (Bug #82019, Bug #23703570) On Behalf of the MySQL/ORACLE RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Utilities 1.6.4 GA has been released
ology setup for multi-source replication, which could fail to detect that the slave is connected to the master specified if that master was not on the primary (first) replication channel. The utility now iterates through the slave status to check for the requested master in the list. If not found, the original error(s) are generated, otherwise the master is matched to one of the replication channels, and progress continues. (Bug #22543517) * Corrects an issue when exporting tables with bit fields in SQL format, where bit fields were being exported as strings instead of being encoded, like b'???'. Export now correctly formats the SQL statements in the output to properly handle bit fields. (Bug #22495193, Bug #79837) * Installation packaging code was modified to function with Mac OS X 10.11 (El Capitan). Installation no longer fails, and users can now install MySQL Utilities on El Capitan. (Bug #22393353, Bug #79700) * Corrects a problem with mysqluc where pressing the delete key failed to position the cursor in the correct location. The cursor location is now fixed, and the delete and arrow keys work properly. (Bug #22076859, Bug #78893) * Removed the "CREATE database" statement from the diff output for mysqldiff and mysqldbcompare for cases where the database name is the only difference. That is, the different output should not show a difference when comparing db1 to db2 when the only difference is the name of the database. However, the difference is shown for differences in quote usage and if decorators differ, such as the character set. (Bug #21222808, Bug #77058) * Corrected an issue when copying users that were created with the "IDENTIFIED WITH" authentication plugin option. The utility would copy the user, but not copy the authentication plugin setting, making it impossible to copy users with the plugin. The utility now captures the plugin name and assigns it to the new user. An error is thrown if the plugin is not on the destination machine or is inactive. A warning is also issued if the user attempts to assign a password to a new user when the source user has an authentication plugin. In this case, the utility will use the password and not the authentication plugin for the new user. (Bug #17666275, Bug #70745) Reporting Bugs -- We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ Enjoy! On Behalf of the MySQL/ORACLE RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Utilities 1.6.4 GA has been released
detect that the slave is connected to the master specified if that master was not on the primary (first) replication channel. The utility now iterates through the slave status to check for the requested master in the list. If not found, the original error(s) are generated, otherwise the master is matched to one of the replication channels, and progress continues. (Bug #22543517) * Corrects an issue when exporting tables with bit fields in SQL format, where bit fields were being exported as strings instead of being encoded, like b'???'. Export now correctly formats the SQL statements in the output to properly handle bit fields. (Bug #22495193, Bug #79837) * Installation packaging code was modified to function with Mac OS X 10.11 (El Capitan). Installation no longer fails, and users can now install MySQL Utilities on El Capitan. (Bug #22393353, Bug #79700) * Corrects a problem with mysqluc where pressing the delete key failed to position the cursor in the correct location. The cursor location is now fixed, and the delete and arrow keys work properly. (Bug #22076859, Bug #78893) * Removed the "CREATE database" statement from the diff output for mysqldiff and mysqldbcompare for cases where the database name is the only difference. That is, the different output should not show a difference when comparing db1 to db2 when the only difference is the name of the database. However, the difference is shown for differences in quote usage and if decorators differ, such as the character set. (Bug #21222808, Bug #77058) * Corrected an issue when copying users that were created with the "IDENTIFIED WITH" authentication plugin option. The utility would copy the user, but not copy the authentication plugin setting, making it impossible to copy users with the plugin. The utility now captures the plugin name and assigns it to the new user. An error is thrown if the plugin is not on the destination machine or is inactive. A warning is also issued if the user attempts to assign a password to a new user when the source user has an authentication plugin. In this case, the utility will use the password and not the authentication plugin for the new user. (Bug #17666275, Bug #70745) Reporting Bugs -- We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ Enjoy! On Behalf of the MySQL/ORACLE RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.7.14 has been released
ould cause a server exit when selecting from the global_status Performance Schema table. (Bug #81065, Bug #23097305) * A compilation error was corrected for a make_link() call when compiling in C++11 mode. Thanks for Daniel Black for the contribution. (Bug #80996, Bug #23080289) * Two mysql-test-run.pl tests (ctype_gb18030_binlog and ctype_ldml) failed to produce repeatable output due to improper cleanup. Thanks to Daniel Black for the patch. (Bug #80896, Bug #23021095) * MySQL failed to build with GCC 6 using the default mode for C++ of -std=gnu++14. The CMake configuration has been adjusted to explicitly set the mode to -std=gnu++03 for GCC 6. (Bug #80371, Bug #22732697) * Ubuntu packages create the root user account using the auth_socket authentication plugin to achieve secure-by-default installation if installation was done with a blank root password. However, auth_socket was being used even if the password was not blank. (Bug #80137, Bug #22594846, Bug #23321113, Bug #81518) * Compiling the InnoDB memcached plugin did not work on some platforms where MySQL was configured using -DWITH_LIBEVENT=system. (Bug #80073, Bug #22573379, Bug #23567441) * The client-side plugin deinitialization function signature was changed from int (*deinit)() to int (*deinit)(void) to avoid warnings when compiling with -Wstrict-prototypes. (Bug #78177, Bug #21680094, Bug #81419, Bug #23282498) On Behalf of the MySQL/ORACLE RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/NET 6.8.8 has been released
Dear MySQL users, MySQL Connector/Net 6.8.8 is a maintenance release for the 6.8.x series of the .NET driver for MySQL. It can be used for production environments. It is appropriate for use with MySQL server versions 5.5-5.7. It is now available in source and binary form from http://dev.mysql.com/downloads/connector/net/#downloadsandmirrorsites (note that not all mirror sites may be up to date at this point-if you can't find this version on some mirror, please try again later or choose another download site.) Changes in MySQL Connector/Net 6.8.8 (2016-07-01) Functionality Added or Changed * Added TLS support for TLSv1.1 and TLSv1.2 when connecting to MySQL Server 5.7. Bugs Fixed * Improvements were made to how the connector handles aborted connections. (Bug #23346197, Bug #80997) * With Entity Framework 6, building a table with a primary key would not enclose the key name in quotes, which caused a syntax error. (Bug #22696180, Bug #22696207, Bug #76292) * The connector was not disposing the transaction returned by DBContext.Database.BeginTransaction() when exiting a using code block. (Bug #22514355, Bug #22514363) * The connector did not attempt to enumerate stored procedures via mysql.proc(). Instead it looked up stored procedures in INFORMATION_SCHEMA.ROUTINES. This could have led to performance degradation in certain scenarios. (Bug #20960373, Bug #23528155, Bug #74116) The documentation is available at: http://dev.mysql.com/doc/connector-net/en/ Nuget packages are available at: https://www.nuget.org/packages/MySql.Data/6.8.8 https://www.nuget.org/packages/MySql.Data.Entity/6.8.8 https://www.nuget.org/packages/MySql.Web/6.8.8 Enjoy and thanks for the support! On behalf of the MySQL Connector/NET and the MySQL/ORACLE RE Team. Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/J 6.0.3 m2 Development Release has been released
roperty file and the Connector/J classes. (Bug #22353759, Bug #79343) * After a failed call of a stored procedure, any subsequent X DevAPI call resulted in a hang. (Bug #22038729) * At every connection, Connector/J got the sql_mode variable from the server and tried to parse it as a number; because sql_mode is not a number (except for very old versions of MySQL), an NumberFormatException was always thrown and then caught by the code. This fix refactored the code to avoid the unnecessary throwing and catching of the error. (Bug #21181466, Bug #77171) * The exception message in CallableStatement() for incorrect output parameter registration gave little detail and the wrong error code. (Bug #18068303, Bug #71131) * On very fast servers with other third-party components accessing the data, a ConcurrentModificationException was sometimes thrown. This fix prevents the exception by adding a synchronization to ConnectionImpl.closeAllOpenStatements(), and by refactoring part of the code inside the method. (Bug #16736619, Bug #59462) * When working with MySQL server 5.5 and 5.6, because Connector/J did not check the version number of the server it was connected to, errors and failures occurred when there was an attempt to use certain version-dependent features (for example, using fractional seconds for servers earlier than 5.6.4). With this fix, the proper exceptions are thrown in those cases. Documentation -- Online: http://dev.mysql.com/doc/connector-j/6.0/en/index.html Reporting Bugs --- We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ On Behalf of the MySQL/ORACLE RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/J 6.0.3 m2 Development Release has been released
making Connector/J use the same class loader for both the property file and the Connector/J classes. (Bug #22353759, Bug #79343) * After a failed call of a stored procedure, any subsequent X DevAPI call resulted in a hang. (Bug #22038729) * At every connection, Connector/J got the sql_mode variable from the server and tried to parse it as a number; because sql_mode is not a number (except for very old versions of MySQL), an NumberFormatException was always thrown and then caught by the code. This fix refactored the code to avoid the unnecessary throwing and catching of the error. (Bug #21181466, Bug #77171) * The exception message in CallableStatement() for incorrect output parameter registration gave little detail and the wrong error code. (Bug #18068303, Bug #71131) * On very fast servers with other third-party components accessing the data, a ConcurrentModificationException was sometimes thrown. This fix prevents the exception by adding a synchronization to ConnectionImpl.closeAllOpenStatements(), and by refactoring part of the code inside the method. (Bug #16736619, Bug #59462) * When working with MySQL server 5.5 and 5.6, because Connector/J did not check the version number of the server it was connected to, errors and failures occurred when there was an attempt to use certain version-dependent features (for example, using fractional seconds for servers earlier than 5.6.4). With this fix, the proper exceptions are thrown in those cases. Documentation -- Online: http://dev.mysql.com/doc/connector-j/6.0/en/index.html Reporting Bugs --- We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ On Behalf of the MySQL/ORACLE RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/Node.js 1.0.3 m2 Development Release has been released
Dear MySQL users, MySQL Connector/Node.js is a new Node.js driver for use with the X DevAPI. This release, v1.0.3 M2, is the second development release of the MySQL Connector/Node.js 1.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/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 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. Changes in MySQL Connector/Node.js 1.0.3 (2016-06-21 Milestone 2) Bugs Fixed * Connector/Node.JS was unable to create a session when SSL was enabled. (Bug #23118665) Enjoy and thanks for the support! On Behalf of the MySQL/ORACLE RE 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 5.7.13 has been released
s. (Bug #78254, Bug #21762656) * Failure of UNINSTALL PLUGIN could lead to inaccurate or confusing errors for subsequent INSTALL PLUGIN operations. (Bug #74977, Bug #20085672) * mysqld_multi displayed misleading error messages when it was unable to execute my_print_defaults. (Bug #74636, Bug #19920049) * Previously, upgrading the server using an RPM package (including installation using yum) required upgrading the client package to the same MySQL version, which may be undesirable for some installations. This rule has been relaxed so that upgrading to a General Availability (GA) server version requires only that some GA client version be installed, which is less likely to require a client upgrade. (Bug #72230, Bug #18518216) * mysqldump failed silently with no error message when it encountered an error while executing FLUSH LOGS. (Bug #71783, Bug #18284273) On Behalf of the MySQL/ORACLE RE 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 5.7.13 has been released
ading the client package to the same MySQL version, which may be undesirable for some installations. This rule has been relaxed so that upgrading to a General Availability (GA) server version requires only that some GA client version be installed, which is less likely to require a client upgrade. (Bug #72230, Bug #18518216) * mysqldump failed silently with no error message when it encountered an error while executing FLUSH LOGS. (Bug #71783, Bug #18284273) On Behalf of the MySQL/ORACLE RE 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 5.1.39 has been released
od. (Bug #22352812, Bug #79598) * At every connection, Connector/J got the sql_mode variable from the server and tried to parse it as a number; because sql_mode is not a number (except for very old versions of MySQL), an NumberFormatException was always thrown and then caught by the code. This fix refactored the code to avoid the unnecessary throwing and catching of the error. (Bug #21181466, Bug #77171) * When inserting multiple timestamp values into a table with useLegacyDatetimeCode=false and useCursorFetch=true, after a null value had been inserted, further inserts could not change a timestamp's value. This fix makes sure the binding of the value is reset before a new insert takes place. (Bug #20685487, Bug #75956) * The exception message in CallableStatement() for incorrect output parameter registration gave little detail and the wrong error code. (Bug #18068303, Bug #71131) * Calling getTimestamp() on a timestamp column resulted in a java.sql.SQLException (Cannot convert value ... to TIMESTAMP). That was due to the missing metadata for each row in the ResultSet. This fix ensures that the metadata is no longer missing. (Bug #16738378, Bug #56479) * On very fast servers with other third-party components accessing the data, a ConcurrentModificationException was sometimes thrown. This fix prevents the exception by adding a synchronization to ConnectionImpl.closeAllOpenStatements(), and by refactoring part of the code inside the method. (Bug #16736619, Bug #59462) Documentation -- Online: http://dev.mysql.com/doc/connector-j/5.1/en/ Reporting Bugs --- We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ On Behalf of the MySQL/ORACLE RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/NET 7.0.2 m1 Development Release has been released
Dear MySQL users, MySQL Connector/Net 7.0.2 M1 is the first development release of MySQL Connector/Net to add support for the new X DevAPI. The X DevAPI enables application developers to write code that combines the strengths of the relational and document models using a modern, NoSQL-like syntax that does not assume previous experience writing traditional SQL. To learn more about how to write applications using the X DevAPI, see http://dev.mysql.com/doc/x-devapi-userguide/en/index.html. For more information about how the X DevAPI is implemented in Connector/Net, see http://dev.mysql.com/doc/dev/connector-net. Please note that the X DevAPI requires at least MySQL Server version 5.7.12 or higher with the X Plugin enabled. For general documentation about how to get started using MySQL as a document store, see http://dev.mysql.com/doc/refman/5.7/en/document-store.html. Changes in MySQL Connector/Net 7.0.2 (2016-04-11, Milestone 1) Functionality Added * Added support for the new X DevAPI Nuget packages are available at: https://www.nuget.org/packages/MySql.Data/7.0.2-DMR https://www.nuget.org/packages/MySql.Data.Entity/7.0.2-DMR https://www.nuget.org/packages/MySql.Fabric/7.0.2-DMR https://www.nuget.org/packages/MySql.Web/7.0.2-DMR Enjoy and thanks for the support! On behalf of the MySQL Release Team -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/J 6.0.2 m1 Development Release has been released
Dear MySQL users, MySQL Connector/J 6.0.2 m1 Development Release is a developer milestone release for the 6.0.x series. It is the first public release of the current Connector/J 6.0 development branch, providing an insight to upcoming features. Although some of these are still under development, this release includes the following new features and changes (in comparison to the current Connector/J 5.1 production release), also available in more detail on http://dev.mysql.com/doc/relnotes/connector-j/en/news-6-0-2.html: As always, we recommend that you check the "CHANGES" file in the download archive to be aware of changes in behavior that might affect your application. Enjoy! Changes in MySQL Connector/J 6.0.2 (2016-04-11, Milestone 1) Version 6.0.2 Milestone 1 is the first development release of the 6.0 branch of MySQL Connector/J. The major features of Connector/J 6.0 include: * Supports MySQL 5.5, 5.6, and 5.7. * Supports the JDBC 4.2 specification. * Supports the Java 8 platform (use Connector/J 5.1 for Java 7 or earlier). * Supports 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 the X DevAPI User's Guide (http://dev.mysql.com/doc/x-devapi-userguide/en/). For more information about how the X DevAPI is implemented in Connector/J, MySQL Connector/J X DevAPI Reference (http://dev.mysql.com/doc/dev/connector-j). 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). For other significant changes from Connector/J 5.1 to 6.0, see Changes in Connection Properties (http://dev.mysql.com/doc/connector-j/6.0/en/connector-j-properties-changed.html) and Changes in the Connector/J API (http://dev.mysql.com/doc/connector-j/6.0/en/connector-j-api-changes.html). Connector/J 6.0.2 includes all the bug fixes that have been incorporated into Connector/J 5.1.38, plus the fixes described below. Bugs Fixed * FabricMySQLDataSource.getConnection() threw a null pointer exception when a master failover took place. (Bug #22598938) * The OSGi manifest file in the Connector/J JAR file did not expose the MySQL Fabric packages, so the Fabric-related classes could not be resolved even though they were present in the JAR file. (Bug #22385172) Documentation -- Online: http://dev.mysql.com/doc/connector-j/6.0/en/index.html Reporting Bugs --- We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ On Behalf of the MySQL/ORACLE RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.6.30 has been released
set to "ROW," as the server tried to get information for table creation for a child table before it was opened. With this fix, the server skips getting information for the table in the situation. (Bug #20574550) * Replication: If a query on a master generated an error and partial results were written to the binary log, for example due to a DROP TABLE IF EXISTS statement applying to multiple tables that would break foreign key constraints, when a slave configured with replication filters encountered the query it could be incorrectly binary logged. This caused errors such as: Last_SQL_Error: Query caused different errors on master and slave. Error on master: message (format)='Cannot delete or update a parent row: a foreign key constraint fails' error code=1217 ; Error on slave: actual message='no error', error code=0. Default database: 'db1'. Query: 'DROP TABLE IF EXISTS `table1` /* generated by server */' There were two fixes required for this bug. + If a DROP TABLE statement used to drop a single table fails, to avoid partial results causing this bug the query is not written to the binary log. If a DROP TABLE statement used to drop a list of tables fails, any partial results it generates are written to the binary log with an error. + When a query that generates an error as expected was received by a slave but it was skipped due to replication filters, the slave was incorrectly checking the error. The fix for Bug #76493 ensures that this comparison of the expected error from the master with the actual error from the slave does not happen. (Bug #77684, Bug #21435502) References: See also Bug #20797764. * Integer overflow could occur during client handshake processing, leading to a server exit. (Bug #22722946) * The System-V initialization script for RHEL6 or older failed to enable the mysqld service by default. (Bug #22600974) * When ExtractValue() found no match for the supplied expression, it returned NULL instead of an empty string as expected. This issue affected MySQL 5.6.28 and 5.6.29 only. (Bug #22552615) * Improper host name checking in X509 certificates could permit man-in-the-middle attacks. (Bug #22295186, Bug #22738607) * A boolean mode full-text search caused a segmentation fault. (Bug #22176795) * Concurrent selecting and flushing of a FEDERATED table while killing connections accessing it could result in a server exit. (Bug #21918190) * Executing GRANT PROXY statements after altering the definition of the mysql.user system table could result in a server exit. (Bug #21699037) * Certain error messages included part of the SQL statement that produced them, possibly exposing data. (Bug #21682356) * The Performance Schema assumed that tables named using a #sql prefix were temporary and could be ignored. But it is possible to create nontemporary tables using that prefix. The Performance Schema now uses table attributes other than the name to identify temporary tables. (Bug #21105475, Bug #22532368, Bug #79934) * Character set conversion operations on NULL parameters to prepared statements could cause a server exit. (Bug #18823979) * Loose Index Scan was not chosen for queries that had an equality condition. (Bug #18109609) * A MySQL 5.6 server exited during startup if used with a 5.7 data directory due to the change in 5.7 of the mysql.plugin table from MyISAM to InnoDB. A safe shutdown now occurs in this circumstance. (Bug #79290, Bug #22216779) * For INSERT and UPDATE operations that caused FOREIGN KEY constraint violations, errors were reported rather than warnings when the IGNORE keyword was used. (Bug #78853, Bug #22037930) * For some queries, an Index Merge access plan was chosen over a range scan when the cost for the range scan was the same or less. (Bug #77209, Bug #21178196) * Certain queries could raise an assertion when a internal string operation produced a NULL pointer rather than an empty string. (Bug #74500, Bug #19875294, Bug #13358486, Bug #79988, Bug #22551116) * EXPLAIN for SELECT ... FOR UPDATE statements acquired locks. (Bug #72858, Bug #18899860) * Processlist state information was not updated correctly for LOAD DATA INFILE and could show a state different from executing. (Bug #69375, Bug #16912362) On Behalf of the MySQL/ORACLE RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Utilities 1.6.3 BETA has been released
Dear MySQL users, This is the BETA release for Utilities 1.6. MySQL Utilities version 1.6.3 is compatible with MySQL Server versions 5.5 and greater. Python v2.6 and v2.7 are supported. MySQL Utilities v1.6.3 BETA is available for download from http://dev.mysql.com/downloads/tools/utilities/ A brief summary of changes is listed below. Please check the CHANGES.txt file inside the distribution for a more complete list of changes. MySQL Utilities provides a collection of command-line utilities that are used for maintaining and administering MySQL servers, including: • Admin Utilities (Clone, Copy, Compare, Diff, Export, Import, User Management) • Replication Utilities (Setup, Configuration, Verification) • General Utilities (Disk Usage, Redundant Indexes, Manage Meta & Audit Data) • And more Changes in MySQL Utilities 1.6.3 (2016-03-22) Bugs Fixed * The --exclude option for the mysqldbexport command did not function. (Bug #22781266) * The mysqlfailover and mysqlrpladmin utilities did not function with MySQL 5.7 Servers. During the failover process, they failed with the following error: "Errors: Missing gtid_executed system variable." (Bug #22617526, Bug #80189) * The mysqlrplsync and mysqldbcopy utilities did not function with MySQL 5.7 when used in a topology with a master. The problem was due to table locking, and began occurring when session_variables was moved to PERFORMANCE_SCHEMA in MySQL 5.7.6. The master UUID is now retrieved before locking the tables. (Bug #22608528, Bug #22628187, Bug #80200) * Several man pages were missing from the RPM package. (Bug #21905774, Bug #78580) * The mysqldbcompare utility now checks if MySQL servers are aliases. (Bug #21845449, Bug #78446) * Using the mysqlauditgrep utility with the --format option would throw an exception when the audit log file contained Unicode characters, and when the format was changed to something other than the default RAW. The error looked similar to "UnicodeEncodeError: 'ascii' codec can't encode characters in position". (Bug #21841353) * With the mysqldbcompare utility, using the same connection information for both --server1 and --server2 with the --all option would raise an AttributeError error. (Bug #21839348, Bug #78439) * The mysqldbexport utility's --exclude option was ignored for data when passing in either the data or both value. (Bug #21784538) * Several utilities (the daemon utilities, mysqlfailover, and mysqlrplms) created pid files with the default permissions on *nix systems (0777). The permissions are now more restrictive. (Bug #21653496) * MySQL Utilities failed to execute when the sql_mode option included "ANSI_QUOTES". (Bug #21653352, Bug #78132) * Executing the mysqldbcompare utility to find differences between two databases on different hosts could fail with an error similar to "Unread result found". (Bug #21572065, Bug #73841) * The MySQL utilities did not function with .mylogin.cnf as of MySQL Server 5.6.25. (Bug #21343759, Bug #77550) * The Windows MSI 64-bit package, by default, installed in "Program Files (x86)\" on a 64-bit system, instead of "Program Files\". (Bug #20876820) * The mysqldiskusage utility incorrectly calculated disk usage, leading to an inaccurate result. (Bug #76703) Reporting Bugs -- We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ Enjoy! On Behalf of the MySQL/ORACLE RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.6.29 has been released
ed procedure had a variable declared as TEXT or BLOB and data was copied to that variable using SELECT ... INTO syntax from a TEXT or BLOB column. (Bug #22203532, Bug #22232332, Bug #21941152) * CREATE TEMPORARY TABLE .. SELECT statements involving BIT columns that resulted in a column type redefinition could cause a server exit or an improperly created table. (Bug #21902059) * Added Microsoft Visual Studio 2015 support. Changes include using the native (added in VS 2015) timespec library if it exists, renamed lfind/lsearch and timezone/tzname to avoid redefinition problems, set TMPDIR to "" by default as P_tmpdir no longer exists, deprecated std::hash_map in favor of std::unordered_map, and added Wix Toolset 3.10 support. (Bug #21770366) References: See also Bug #21657078. * With character_set_server=utf16le, some values of ft_boolean_syntax could cause a server exit for full-text searches. (Bug #21631855) * With LOCK TABLES in force, an attempt to open a temporary MERGE table consisting of a view in its list of tables (not the last table in the list) caused a server exit. (Bug #20691429) * For certain prepared statements, the optimizer could transform join conditions such that it used a pointer to a temporary table field that was no longer available after the initial execution. Subsequent executions caused a server exit. (Bug #19941403) * Repeated execution of ALTER TABLE v1 CHECK PARTITION as a prepared statement, where v1 is a view, led to a server exit. In addition, output for some administrative operations, when they are attempted on a view, changes from "Corrupt" to "Operation failed". These include ANALYZE TABLE, OPTIMIZE TABLE, and REPAIR TABLE, and ALTER TABLE statements that perform ANALYZE PARTITION, CHECK PARTITION, OPTIMIZE PARTITION, and REPAIR PARTITION operations. (Bug #19817021) * Valgrind detected some possibly unsafe use of string functions in code used for asymmetric encryption. (Bug #19688135) * SSL connections ignored any change made by passing the MYSQL_OPT_READ_TIMEOUT option to the mysql_options() C API function. (Bug #17618162) * Solaris packages failed to note the dependency of the MySQL client library on the libstlport library. (Bug #79778, Bug #22504264) * Using systemd to start mysqld failed if configuration files contained multiple datadir lines. Now the last datadir line is used. (Bug #79613, Bug #22361702) * If server was started with --thread-handling=no-threads, no foreground thread was created for a client connection. The Performance Schema did not account for the possibility of no foreground threads for queries on the session_connect_attrs table, causing an assertion to be raised. (Bug #78292, Bug #21765843) * ALTER TABLE ... CONVERT TO CHARACTER SET operations that used the INPLACE algorithm were ineffective if the table contained only numeric data types. Also, such operations failed to clean up their temporary .frm file. (Bug #77554, Bug #21345391) * Heavy SHOW PROCESSLIST or SELECT ... FROM INFORMATION_SCHEMA.PROCESSLIST activity could result in the server accepting more than max_connections connections. (Bug #75155, Bug #20201006) * When used with the libmysqld embedded server, the mysql_stmt_execute() C API function failed with a malformed communication packet error, even for simple prepared statements. (Bug #70664, Bug #17883203) On Behalf of the MySQL/ORACLE RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/C++ 1.1.7 has been released
Dear MySQL Users, A new GA (general availability) version of MySQL Connector/C++ has been made available: MySQL Connector/C++ 1.1.7 GA. The MySQL Connector/C++ provides a C++ API for connecting client applications to the MySQL Server 5.5 or newer. You can download the production release at: http://dev.mysql.com/downloads/connector/cpp/1.1.html MySQL Connector C++ (Commercial) will be available for download on the My Oracle Support (MOS) website. This release will be available on eDelivery (OSDC) in next month's upload cycle. The MySQL driver for C++ offers an easy to use API derived from JDBC 4.0. MySQL Workbench has used it successfully for years. We have improved the driver since the last GA release. Please see the documentation and the CHANGES file in the source distribution for a detailed description of bugs that have been fixed. Bug descriptions are also listed below. Enjoy! == Changes in MySQL Connector/C++ 1.1.7 Configuration Notes * Binary distributions for this release of MySQL Connector/C++ were linked against libmysqlclient from MySQL 5.7.10, except for OS X 10.8/10.9, for which distributions were linked against MySQL 5.7.9. This enables Connector/C++ to take advantage of features present in recent client library versions. Some examples: + Support for the MySQL JSON data type is available. Current versions of MySQL Workbench require JSON support, so to build MySQL Workbench 6.3.5 or higher from source, it is necessary to use a version of Connector/C++ at least as recent as 1.1.7. + Applications will attempt to establish a secure (encrypted) connection by default whenever the server is enabled to support secure connections, and fall back to an unencrypted connection otherwise. (This is as described at Configuring MySQL to Use Secure Connections (http://dev.mysql.com/doc/refman/5.7/en/using-secure-connections.html).) To enforce a secure connection, such that an error occurs if secure connections are not available, applications can enable the sslEnforce connection option. To build Connector/C++ from source, you must use either a General Availability version of MySQL 5.7 (5.7.9 or higher) or Connector/C 6.1.8 or higher. Set the MYSQL_DIR CMake option appropriately at configuration time as necessary. (Bug #22351273) Security Notes * The linked OpenSSL library for Connector/C++ Commercial has been updated to version 1.0.1q. Issues fixed in the new OpenSSL version are described at http://www.openssl.org/news/vulnerabilities.html. This change does not affect Oracle-produced MySQL Community builds of Connector/C++, which use the yaSSL library instead. Spatial Data Support * The required version of the Boost library for Connector/C++ builds has been raised to 1.56.0. Bugs Fixed * MySQL_Prepared_ResultSet::relative() failed to fetch the record due to a missing proxy->fetch() call. (Bug #21152054) * During Connector/C++ builds, the MySQL Server CXXFLAGS and CFLAGS values were used rather than the system default values. To specify explicitly to use the server values, enable the new USE_SERVER_CXXFLAGS CMake option. (Bug #77655, Bug #21391025) On Behalf of the MySQL/ORACLE RE Team -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/J 5.1.38 has been released
Hello all, MySQL Connector Java 5.1.38, a maintenance release of the production 5.1 branch, has been released. Connector/J is a Type-IV pure-Java JDBC driver for MySQL. It is suitable for use with MySQL server versions 5.5, 5.6, and 5.7. It is also the first release of MySQL Connector/J to support the Java Database Connectivity (JDBC) 4.2 API. MySQL Connector Java is available in source and binary form from the Connector/J download pages at http://dev.mysql.com/downloads/connector/j/5.1.html MySQL Connector Java (Commercial) is available for download on the My Oracle Support (MOS) website. This release will be available on eDelivery (OSDC) in next month's upload cycle. As always, we recommend that you check the "CHANGES" file in the download archive to be aware of changes in behavior that might affect your application. MySQL Connector/J 5.1.38 includes the following general bug fixes and improvements, also available in more detail on http://dev.mysql.com/doc/relnotes/connector-j/en/news-5-1-38.html : Changes in MySQL Connector/J 5.1.38 (2015-12-07) Functionality Added or Changed * When connecting to a MySQL server 5.7 instance that supports TLS, Connector/J now prefers a TLS over a plain TCP connection. (Bug #21947042) * Two new connection properties, allowSlaveDownConnections and readFromMasterWhenNoSlaves, have been introduced for configuring replication-aware connections. See Configuring Master/Slave Replication with Connector/J (http://dev.mysql.com/doc/connector-j/en/connector-j-master-slave-replication-connection.html) and the entries for the new properties in Driver/Datasource Class Names, URL Syntax and Configuration Properties for Connector/J (http://dev.mysql.com/doc/connector-j/en/connector-j-reference-configuration-properties.html) for details. (Bug #21286268) Bugs Fixed * In a Fabric environment, a ClassCastException resulted when a stored procedure was called with an INOUT parameter. This was because in this situation, what was being cast was a proxied version of the object. This fix extracts the underlying object from its proxy, allowing it to be cast to the implementing class. (Bug #22096981) * getTypeInfo() erroneously returned a PRECISION value of "255" instead of "65535" for the data type VARBINARY. (Bug #21978216) * A deadlock was observed when in the same server group, two concurrent threads were using different Fabric connections, and one executed a failover procedure while the other simultaneously called a method that acquired a lock on the underlying replication connection instance monitor. This fix revised the locking mechanism of replication connections, in order to prevent the observed deadlocks. (Bug #21966391, Bug #21934573, Bug #78710) * State information of a Fabric group was not updated by Connector/J after a local cache's Time to Live (TTL) expired, which resulted in the client not recognizing any topology changes happening to the group like a master failover, a server rejoining, and so on. (Bug #21296840, Bug #17910835) * Connector/J threw an AbstractMethodError when a JDBC 4 functionality (for example, createBlob()) was used on a replication-aware connection. This has been fixed by putting replication connections under the multi-host connection proxy structure that Connector/J has been using for load-balanced and fail-over connections. (Bug #11763419) References: See also Bug #11763401. * After the initial call of Connection.setReadOnly() following the creation of a replication-aware connection, subsequent calls of Connection.setReadOnly() could not change the nature of the connection. This has been fixed by putting replication connections under the multi-host connection proxy structure that Connector/J has been using for load-balanced and fail-over connections. (Bug #11763401) References: See also Bug #11763419. Documentation -- Online: http://dev.mysql.com/doc/connector-j/en/index.html Reporting Bugs --- We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ On Behalf of the MySQL/ORACLE RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.6.28 has been released
packages were installed. (Bug #22005375) * Possible buffer overflow from incorrect use of strcpy() and sprintf() was corrected. (Bug #21973610) * MySQL RPM packages for RHEL5 failed to create the mysql system user. (Bug #21950975) * For Debian package control files, libnuma-dev was added to Build-Depends to enable NUMA support. (Bug #21822631) * Selecting DECIMAL values into user-defined variables could cause a server exit. (Bug #21819304) * Concurrent FLUSH PRIVILEGES and REVOKE or GRANT statements could produce a small time window during which invalid memory access to proxy user information could occur, leading to a server exit. (Bug #21602056) * Starting the server with the query_alloc_block_size system variable set to certain negative values on a machine without enough memory could result in out-of-memory errors. (Bug #21503595) * Using UNINSTALL PLUGIN to uninstall the daemon_example plugin could cause a server exit. (Bug #21467458) * FLUSH DES_KEY_FILE failed to reload the DES key file. (Bug #21370329) * If an error occurred during the setup phase of subquery materialization used to compute an IN predicate, cleanup of the temporary table did not happen, leading to Valgrind errors. (Bug #21346081) * Queries rejected by MySQL Enterprise Firewall were truncated to 512 characters when written to the error log. (Bug #20948270) * A server exit could occur for the second execution of a prepared statement for which an ORDER BY clause referred to a column position. (Bug #20755389) * Repeated execution of a prepared statement could cause a server exit if the default database was changed. (Bug #20447262) * Outer references do not work as arguments to MATCH(), but the server did not properly detect them. Now it does and raises an error. (Bug #20007383) References: See also Bug #21140088. * Valgrind errors were produced during row comparator setup. (Bug #19929406) * After failure to create a temporary table during join processing and releasing the table descriptor, an attempt to access the now-invalid descriptor could cause a server exit. (Bug #19918299) * Type conversion failure for DECIMAL values could cause a server exit. (Bug #19912326, Bug #20013538) * INSERT DELAYED could cause a server exit for tables partitioned with a character column as the key and for which the expression required a character set conversion. (Bug #19894161) * During a filesort for an UPDATE statement, the optimizer could access a stale pointer, resulting in a server exit. (Bug #19893908) * A server exit could occur when updating a view using an ALL comparison operator on a subquery that selects from an indexed column in the main table. (Bug #19434916) * Some stress test files in the mysql-test/suite/innodb_stress directory had the executable file mode set although they were not script files. (Bug #78403, Bug #21822413) * The server initialization script used for the service mysql status command on Linux sometimes incorrectly reported that the server was stopped. (Bug #77696, Bug #21768876) On Behalf of the MySQL/ORACLE RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Cluster 7.4.8 has been released
handled in a transactional manner. (Bug #20713499) * Cluster API: While executing dropEvent(), if the coordinator DBDICT failed after the subscription manager (SUMA block) had removed all subscriptions but before the coordinator had deleted the event from the system table, the dropped event remained in the table, causing any subsequent drop or create event with the same name to fail with NDB error 1419 Subscription already dropped or error 746 Event name already exists. This occurred even when calling dropEvent() with a nonzero force argument. Now in such cases, error 1419 is ignored, and DBDICT deletes the event from the table. (Bug #21554676) * Cluster API: If the total amount of memory allocated for the event buffer exceeded approximately 40 MB, the calculation of memory usage percentages could overflow during computation. This was due to the fact that the associated routine used 32-bit arithmetic; this has now been changed to use Uint64 values instead. (Bug #78454, Bug #21847552) * Cluster API: The nextEvent2() method continued to return exceptional events such as TE_EMPTY, TE_INCONSISTENT, and TE_OUT_OF_MEMORY for event operations which already had been dropped. (Bug #78167, Bug #21673318) * Cluster API: After the initial restart of a node following a cluster failure, the cluster failure event added as part of the restart process was deleted when an event that existed prior to the restart was later deleted. This meant that, in such cases, an Event API client had no way of knowing that failure handling was needed. In addition, the GCI used for the final cleanup of deleted event operations, performed by pollEvents() and nextEvent() when these methods have consumed all available events, was lost. (Bug #78143, Bug #21660947) * Cluster API: The internal value representing the latest global checkpoint was not always updated when a completed epoch of event buffers was inserted into the event queue. This caused subsequent calls to Ndb::pollEvents() and pollEvents2() to fail when trying to obtain the correct GCI for the events available in the event buffers. This could also result in later calls to nextEvent() or nextEvent2() seeing events that had not yet been discovered. (Bug #78129, Bug #21651536) On Behalf of the MySQL/ORACLE RE 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.8 has been released
handled in a transactional manner. (Bug #20713499) * Cluster API: While executing dropEvent(), if the coordinator DBDICT failed after the subscription manager (SUMA block) had removed all subscriptions but before the coordinator had deleted the event from the system table, the dropped event remained in the table, causing any subsequent drop or create event with the same name to fail with NDB error 1419 Subscription already dropped or error 746 Event name already exists. This occurred even when calling dropEvent() with a nonzero force argument. Now in such cases, error 1419 is ignored, and DBDICT deletes the event from the table. (Bug #21554676) * Cluster API: If the total amount of memory allocated for the event buffer exceeded approximately 40 MB, the calculation of memory usage percentages could overflow during computation. This was due to the fact that the associated routine used 32-bit arithmetic; this has now been changed to use Uint64 values instead. (Bug #78454, Bug #21847552) * Cluster API: The nextEvent2() method continued to return exceptional events such as TE_EMPTY, TE_INCONSISTENT, and TE_OUT_OF_MEMORY for event operations which already had been dropped. (Bug #78167, Bug #21673318) * Cluster API: After the initial restart of a node following a cluster failure, the cluster failure event added as part of the restart process was deleted when an event that existed prior to the restart was later deleted. This meant that, in such cases, an Event API client had no way of knowing that failure handling was needed. In addition, the GCI used for the final cleanup of deleted event operations, performed by pollEvents() and nextEvent() when these methods have consumed all available events, was lost. (Bug #78143, Bug #21660947) * Cluster API: The internal value representing the latest global checkpoint was not always updated when a completed epoch of event buffers was inserted into the event queue. This caused subsequent calls to Ndb::pollEvents() and pollEvents2() to fail when trying to obtain the correct GCI for the events available in the event buffers. This could also result in later calls to nextEvent() or nextEvent2() seeing events that had not yet been discovered. (Bug #78129, Bug #21651536) On Behalf of the MySQL/ORACLE RE 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 5.1.37 has been released
Bug #75670) * When a lock wait timeout occurred, an SQLException was thrown while an SQLTransientException should be thrown instead. It was due to a wrong SQLState number used in the code, which has now been fixed. (Bug #16634180) * When the time zone on the MySQL server was configured to "GMT" but the client was in a different time zone, Connector/J would make wrong adjustments for event timestamps when working with the server. (Bug #11758179, Bug #50348) Documentation -- Online: http://dev.mysql.com/doc/connector-j/en/index.html Reporting Bugs --- We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ On Behalf of the MySQL/ORACLE RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.6.27 has been released
_os system variable indicated 10.8. (Bug #75581, Bug #20400501) * The optimizer could incorrectly assume an out-of-memory condition while optimizing a range scan for the OR operator, resulting in overestimation of the number of qualifying rows. (Bug #75248, Bug #20229614) * On platforms where the char is unsigned, the server was unable to parse collation definitions that included non-7-bit ASCII characters. Affected platforms include ARM and PowerPC. Thanks to Alexey Kopytov for the patch. (Bug #74891, Bug #20928289, Bug #20928289) * The Performance Schema events_statements_history table could have an ERRORS column value of 0 when other columns indicated there were errors. (Bug #74614, Bug #19929832) * View creation from a UNION failed with a duplicate-column error if a SELECT statement in the UNION other than the first used the same column name multiple times. (Bug #74539, Bug #19886430) * Empty XML elements having the form were not handled correctly by the LOAD XML statement. (Bug #67542, Bug #16171518) On Behalf of the MySQL/ORACLE RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/Python 2.1.3 GA has been released
Dear MySQL users, MySQL Connector/Python 2.1.3 GA is the first GA version of 2.1 release series of the pure Python database driver for MySQL. It can be used for production environments. MySQL Connector/Python version 2.1.3 GA is compatible with MySQL Server versions 5.5 and greater. Python 2.6 and greater as well as Python 3.3 and greater are supported. Python 2.4, 2.5 and 3.1, 3.2 are not supported. MySQL Connector/Python 2.1.3 is available for download from: http://dev.mysql.com/downloads/connector/python/#downloads The ChangeLog file included in the distribution contains a brief summary of changes in MySQL Connector/Python 2.1.3. For a more complete list of changes, see below or online at: http://dev.mysql.com/doc/relnotes/connector-python/en/ Enjoy! Changes in MySQL Connector/Python 2.1.3 (2015-09-24): Functionality Added or Changed * Connector/Python is now compatible with Django 1.8. (Bug #76752, Bug #20987205) Bugs Fixed * When using the C Extension with raise_on_warnings=True, errors were not thrown as exceptions when an executed statement produced an error, and it was not possible to reuse the cursor if the statement produced a result set. (Bug #21536507) * When using the C Extension, character decoding of identifiers (database, table, column names) in result sets could fail. (Bug #21535573) * When using the C Extension with the auth_plugin option, connect() calls failed. (Bug #21529781) * In connections for which consume_results=True, callproc() could hang. (Bug #21492815) * Connections failed if the password began or ended with spaces because they were being stripped before the connection attempt. (Bug #21492428) * Connection failure occurred for accounts authenticated with the sha256_password authentication plugin that had a blank password. (Bug #21420906) * The Connector/Python C Extension could exit when fetching a result set containing many NULL values. (Bug #21420633) * Connector/Python failed to complete the connection handshake with MySQL Server 5.5.8. (Bug #21090014) * RPM packages of Connector/Python were missing some required __init_py__ files. (Bug #77819, Bug #21505096) * Connector/Python hung until timeout if the query it was running was killed. (Bug #76156, Bug #20653441) * Writing to a table with a BinaryField from Django resulted in a UnicodeDecodeError exception. (Bug #75175, Bug #21054559) * Stripping NoneType objects from Django resulted in an AttributeError exception. (Bug #74675, Bug #21054556) Documentation Online:http://dev.mysql.com/doc/connector-python/en/index.html The source distribution includes the manual in various formats under the docs/ folder. Reporting Bugs We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ Posting in GitHub is in progress and will appear shortly. On Behalf of the MySQL/ORACLE RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Utilities 1.6.2 Beta has been released
rpl_admin_gtid test set the gtid_purged variable on the master server to create a controllable scenario where a slave server was missing GTIDs from the server. However, this was a faulty behavior from the server that was fixed in 5.6.22 and 5.7.6 via Bug #19012085. (Bug #20161135) * The mysqldbimport utility was unable to import multiple databases from a single file if the file format was not SQL, such as CSV. (Bug #20070400) * The mysqldiff failed to generate correct ALTER statements that differentiated between DEFAULT NULL and DEFAULT ''. (Bug #75236, Bug #20227070) Reporting Bugs -- We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ Enjoy! On Behalf of the MySQL/ORACLE RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.6.26 has been released
and the slave. The fix uses the binlog_error_action variable to decide how to handle this situation. If binlog_error_action=ABORT_SERVER, then the server aborts after informing the client with an ER_BINLOGGING_IMPOSSIBLE error. If binlog_error_action=IGNORE_ERROR, then the error is ignored and binary logging is disabled until the server is restarted again. The same is mentioned in the error log file, and the transaction is committed inside the storage engine without being added to the binary log. (Bug #76795, Bug #20938915) * Replication: When using GTIDs, a multi-threaded slave which had relay_log_recovery=1 and that stopped unexpectedly could encounter a relay-log-recovery cannot be executed when the slave was stopped with an error or killed in MTS mode error upon restart. The fix ensures that the relay log recovery process checks if GTIDs are in use or not. If GTIDs are in use, the multi-threaded slave recovery process uses the GTID protocol to fill any unprocessed transactions. (Bug #73397, Bug #19316063) * Replication: When two slaves with the same server_uuid were configured to replicate from a single master, the I/O thread of the slaves kept reconnecting and generating new relay log files without new content. In such a situation, the master now generates an error which is sent to the slave. By receiving this error from the master, the slave I/O thread does not try to reconnect, avoiding this problem. (Bug #72581, Bug #18731252) * Compilation failed when building MySQL without the Performance Schema. (Bug #21229433) * Incorrect cost calculation for the semi-join Duplicate Weedout strategy could result in a server exit. (Bug #21184091) * MySQL Enterprise Firewall recorded prepared statements as they were received by the server, not as normalized digests. (Bug #20929568) * Identifiers in normalized statements were sometimes quoted and sometimes not, an inconsistency that caused matching failure for statement digests and digest texts. This caused problems for MySQL Enterprise Firewall and for Performance Schema aggregation by digest. Identifiers now are quoted consistently. (Bug #20896539) * For MySQL Enterprise Firewall operation, max_digest_length had to be larger than mysql_firewall_max_query_size or normalized statements were truncated. (Bug #20894024) * Enabling MySQL Enterprise Firewall and binary logging could result in the server reading freed memory. (Bug #20848324) * For large values of max_digest_length, the Performance Schema could encounter an overflow error when computing memory requirements, resulting in a server exit. (Bug #20738072) * The Spencer regex library used for the REGEXP operator could be subject to heap overflow in some circumstances. (Bug #20642505) * A buffer-overflow error could occur for mysqlslap during option parsing. (Bug #20605441) * An off-by-one error in string-copying code could result in a buffer overflow. (Bug #20359808) * For some status variables that should monotonically increase, SHOW GLOBAL STATUS in one session could show them as decreasing when other concurrent sessions changed user or disconnected. (Bug #18591145) * mysql-systemd-start failed if datadir was set in /etc/my.cnf. (Bug #77357, Bug #21262883) * A call to the MySQL Enterprise Firewall sp_set_firewall_mode() stored procedure with an invalid user name produced an error but added the user to the firewall_users table anyway. (Bug #76914, Bug #21021875) * Ubuntu packages were missing dependencies for killall and psmisc. (Bug #76716, Bug #20893836) * When choosing join order, the optimizer could incorrectly calculate the cost of a table scan and choose a table scan over a more efficient eq_ref join. (Bug #71584, Bug #18194196) On Behalf of the MySQL/ORACLE RE 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 5.1.36 has been released
after its holding pooled connection had already been closed, the subsequent fireStatementEvent() call would run into a NullPointerException. This fix prevents the problem by having JDBC4MySQLPooledConnection initializing statementEventListeners properly and never setting it to null, thus allowing it to be used all the time as a monitor lock. (Bug #16444069, Bug #62452) Documentation -- Online: http://dev.mysql.com/doc/connector-j/en/index.html Reporting Bugs --- We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ On Behalf of the MySQL/ORACLE RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.6.25 has been released
could lead to excessive memory use when there were large numbers of empty InnoDB tables. (Bug #72322, Bug #18592390) * Queries that included a HAVING clause based on nondeterministic functions could produce incorrect results. (Bug #69638, Bug #17055185) * For logging of prepared statements to the general query log, the Execute line was logged after statement execution, not before. (Bug #69453, Bug #16953758, Bug #20536590) * MySQL failed to compile using OpenSSL 0.9.8e. (Bug #68999, Bug #16861371) On Behalf of the MySQL RE team at Oracle Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/Python 2.1.2 Beta has been released
Dear MySQL users, MySQL Connector/Python 2.1.2-Beta is a Beta version of 2.1 release series of the pure Python database driver for MySQL. It is intended to introduce users to the new features. This release is not feature complete but it should be stable enough for users to understand the new features and how we expect them to work. As is the case with all non-GA releases, it should not be used in any production environment. MySQL Connector/Python version 2.1.2-Beta is compatible with MySQL Server versions 5.5 and greater. Python 2.6 and greater as well as Python 3.3 and greater are supported. Python 2.4, 2.5 and 3.1, 3.2 are not supported. MySQL Connector/Python 2.1.2-Beta is available for download from: http://dev.mysql.com/downloads/connector/python/#downloads The ChangeLog file included in the distribution contains a brief summary of changes in MySQL Connector/Python 2.1.2. For a more complete list of changes, see below or online at: http://dev.mysql.com/doc/relnotes/connector-python/en/ = Changes in MySQL Connector/Python 2.1.2 (2015-04-30) Functionality Added or Changed * Previously, connections from Connector/Python to Fabric were always made using the XML-RPC protocol. It is now possible to connect using the MySQL client/server protocol. To specify the protocol, use the protocol value in the the fabric dictionary argument for the connect() method. Permitted protocol values are xmlrpc (the default) and mysql. With mysql, the default port becomes 32275, although that can be changed with an explicit port value. For more information, see Requesting a Fabric Connection (http://dev.mysql.com/doc/mysql-utilities/1.5/en/connecto r-python-fabric-connect.html). Bugs Fixed * Connector/Python could raise an AttributeError exception for Fabric connections with MySQL Utiliies 1.5.4 or 1.6.1. (Bug #20834643) * For connections that use the C Extension, an error occurred for attempts to create a cursor with buffered=True. (Bug #20811802) * The Connector/Python version checker for MySQL did not handle nonnumeric suffixes. During the build process, if the --with-mysql-api option was given, the check failed for installed versions of MySQL such as 5.7.6-m16. (Bug #20365619) * The setup.py install command did not retain the value provided by the --install-lib option. (Bug #20217174) * Encoding failure could occur for prepared cursors with UTF-8 statement parameters. (Bug #75542, Bug #20407036) * Values of the SET data type were not translated correctly if empty. (Bug #75402, Bug #20301989) * HASH sharding for Fabric failed. (Bug #75287, Bug #20324089) * Queries that produced a large result could result in an IndexError: bytearray index out of range exception. (Bug #74933, Bug #20462427) * The Django backend was creating excessive connections (immediately when each DatabaseWrapper object was created rather than waiting until the object actually needed the connection.) (Bug #74696, Bug #19972427) * Error messages containing non-ASCII characters caused an exception to be raised. (Bug #74345, Bug #19803702) * The Django backend sometimes failed to properly convert SafeText objects, which then appeared in queries. (Bug #74336, Bug #20106629) * When using the callproc() cursor method, warnings generated by statements executed within the procedure or generated by the procedure itself were not available to the client. (Bug #74252, Bug #19777815) * Connection pooling did not work when using MySQL Fabric. (Bug #73445, Bug #19331658) Documentation Online:http://dev.mysql.com/doc/connector-python/en/index.html The source distribution includes the manual in various formats under the docs/ folder. Reporting Bugs We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ Enjoy ! On Behalf of the MySQL RE team at Oracle Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.5.43 has been released
references. (Bug #18782905, Bug #19892803) * Starting the server with start service or mysqld_safe could result in failure to use the correct plugin directory. (Bug #17619241) * Creating a FEDERATED table with an AUTO_INCREMENT column using a LIKE clause results in a server exit. (Bug #12671631) On behalf of Oracle/MySQL RE 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 5.1.35 has been released
, Bug #74998) * Calling getString() after rs.relative() had been called with an argument smaller than -1 resulted in a null pointer exception, because rs.relative() could not handle the argument properly. (Bug #19536760) * All occurrences of the StringBuffer class in the Connector/J code has been replaced with the StringBuilder class, in order to improve code performance. (Bug #19465516, Bug #73595) * Quoted identifiers in some SQL statements were not properly escaped. (Bug #18925727) * A java.sql.date value was stored incorrectly on the server and also returned incorrectly if the client and the server were in different time zones when useLegacyDatetimeCode=false or useTimezone=true. This was due to the time-zone conversion performed by Connector/J on the SQL DATE type. To avoid the issue, a new property noTimezoneConversionForDateType has been created for Connector/J, which is set to true by default, preventing Connector/J to perform the kind of time-zone conversion that caused this bug. In addition, another new property cacheDefaultTimezone has been created: when it is set to true (by default), Connector/J caches the time zone first obtained from the client and uses it throughout the time the application is running. When it is set to false, Connector/J becomes aware of time zone changes in the client at runtime that are initiated by calling java.util.TimeZone.setDefault(zone). (Bug #18028319, Bug #71084) * A deadlock occurred when concurrent prepared statements making use of timestamp objects were executed in a single connection. To avoid this, the locking mechanism involved has been changed, so that the calendar object for the session is only locked when it is actually being used. (Bug #15936413, Bug #67760) * There was an unnecessary call of targetCalendar.setTime() in the newSetTimestampInternal() method of the PreparedStatement.java class, which modified the user-supplied Calendar object and might cause side effects for the client application. The unnecessary call has now been eliminated by the fix put in for Bug #18028319/Bug #71084. (Bug #11761585, Bug #54095) Documentation -- Online: http://dev.mysql.com/doc/connector-j/en/index.html Reporting Bugs --- We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ On Behalf of the MySQL/ORACLE RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Utilities 1.6.1 Alpha has been released
#19644057, Bug #73968) * Generated logs now contain the version of the MySQL Utilities and connected MySQL server. (Bug #19614037) * On Windows, the test suite (MUT) failed to kill the spawned servers after running the tests, if the path for the base MySQL server included spaces. (Bug #19348330) * When a table contained a composite Primary Key, the mysqldbcompare utility generated INSERT/UPDATE/DELETE statements that omitted the AND clause between each field. (Bug #19340701, Bug #73449) * When comparing databases with the mysqldbcompare utility, quote characters within resulting SQL transformation statements were not escaped. As a result, the statements were not valid and could not be executed directly in a client tool, as intended. (Bug #19313139, Bug #73415) * MySQL Utilities now reflects the SSL behavior introduced for the MySQL client in MySQL 5.7.3. Setting --ssl=1 now causes the MySQL connection to fail if an encrypted connection can not be established. (Bug #19031182) * The mysqldbcopy utility was not able to copy table rows that contained single quotes in text columns. (Bug #18955235, Bug #72951) * The conversion to CSV performed with the --format=CSV option for several utilities was applying an incorrect line terminator on POSIX (non-Windows) systems. In particular, \r\n was used instead of \n. (Bug #18792076) * The mysqldbcompare utility failed to execute when a large invalid value was passed into the --span-key-size option. (Bug #18763262) * In MySQL, a BTREE index A is considered redundant of a BTREE index B if and only if index A is a leftmost prefix of index B. Having a common partial prefix is not enough. The mysqlindexcheck utility had an issue and was considering two BTREE indexes as redundant if they had a common partial prefix. mysqlindexcheck now correctly checks if a BTREE index is a leftmost prefix of the other index. (Bug #18718660) * The mysqldbcompare utility executed the full algorithm twice to search for data differences when the --show-reverse option was used, instead of only repeating the part that generated the differences in the reverse direction. This had a notable performance impact for larger databases. (Bug #18717843) * mysqlfabric would print a JSON-like output as a result, but this was potentially confusing as it was not JSON. Valid JSON is now used. (Bug #18110179, Bug #71445) * The exit code of mysqlfabric group create ... was 0 for both the success and the error cases. Now, 0 is only returned on success. (Bug #18110165, Bug #71444) * The mysqldbimport utility did not issue an error when a non-existing file was specified while multiprocessing support was enabled. Also, without concurrency (the multiprocess option enabled), a verbose Traceback was printed instead of a more readable error message. Now, a friendly error message is generated for both cases. (Bug #18042411) Documentation - Online: http://dev.mysql.com/doc/index-utils-fabric.html The source distribution includes the manual pages for each utility under the docs/ folder. Reporting Bugs -- We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ Enjoy! On Behalf of the MySQL/ORACLE RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.5.42 has been released
Dear MySQL users, MySQL Server 5.5.42 is a new version of the 5.5 production release of the world's most popular open source database. MySQL 5.5.42 is recommended for use on production systems. MySQL 5.5 includes several high-impact enhancements to improve the performance and scalability of the MySQL Database, taking advantage of the latest multi-CPU and multi-core hardware and operating systems. In addition, with release 5.5, InnoDB is now the default storage engine for the MySQL Database, delivering ACID transactions, referential integrity and crash recovery by default. MySQL 5.5 also provides a number of additional enhancements including: - Significantly improved performance on Windows, with various Windows specific features and improvements - Higher availability, with new semi-synchronous replication and Replication Heartbeat - Improved usability, with Improved index and table partitioning, SIGNAL/RESIGNAL support and enhanced diagnostics, including a new Performance Schema monitoring capability. For a more complete look at what's new in MySQL 5.5, please see the following resources: MySQL 5.5 is GA, Interview with Tomas Ulin: http://dev.mysql.com/tech-resources/interviews/thomas-ulin-mysql-55.html Documentation: http://dev.mysql.com/doc/refman/5.5/en/mysql-nutshell.html Whitepaper: What's New in MySQL 5.5: http://www.mysql.com/why-mysql/white-papers/whats-new-in-mysql-5-5/ 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.42 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.42 is available in source and binary form for a number of platforms from our download pages at: http://dev.mysql.com/downloads/mysql/ The following section lists the changes in the MySQL source code since the previous released version of MySQL 5.5. It may also be viewed online at: http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-42.html Enjoy! Changes in MySQL 5.5.42 (2015-02-02) Functionality Added or Changed * Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they provide weak encryption. (Bug #19820550) * yaSSL was upgraded to version 2.3.7. (Bug #19695101, Bug #20201864) * The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. (Bug #18366947) Bugs Fixed * InnoDB: A multiple-table delete operation caused the server to halt. (Bug #19815702) * Replication: If a DROP DATABASE statement failed on the master, mismatched tables could be left on the slave, breaking replication. This was caused by the DROP TABLE statement being binary logged if at least one table was deleted during the DROP DATABASE operation. The fix ensures that in such a situation the DROP TABLE statement is binary logged with the IF EXISTS option. (Bug #74890, Bug #20041860) * Unlocking a temporary table after locking and truncating it could cause a server exit. (Bug #19786309) * The Enterprise Encryption plugin could mishandle string arguments. (Bug #19688008) * FLUSH TABLES on a FEDERATED table failed if the table had been idle longer than the wait_timeout time plus the TCP keepalive time. (Bug #17599258) * Selecting all columns from INFORMATION_SCHEMA.TABLES did not reopen tables if they were in the table cache, but selecting a subset of those columns under the same conditions did reopen tables. (Bug #16869534) * MySQL failed to compile with GCC 4.9.1 in debug mode. (Bug #74710, Bug #19974500) * A file created for an internal temporary table could cause problems if the file was orphaned for some reason and the file name was reused for later queries. (Bug #32917, Bug #11747548) On behalf of Oracle/MySQL RE 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 6.8.4 has been released
Dear MySQL users, MySQL Connector/Net 6.8.4 is a maintenance release for the 6.8.x series of the .NET driver for MySQL. It can be used for production environments. It is appropriate for use with MySQL server versions 5.5-5.7. It is now available in source and binary form from http://dev.mysql.com/downloads/connector/net/#downloadsandmirrorsites (note that not all mirror sites may be up to date at this point-if you can't find this version on some mirror, please try again later or choose another download site.) Changes in MySQL Connector/Net 6.8.4 (2014-11-11) Bugs Fixed * Generated code that matched against the start of a VARCHAR/CHAR column now correctly uses LIKE instead of location functions for the LINQ to Entity operators StartsWith, Contains, and EndsWith. Locate functions do not make use of indexes placed on the VARCHAR/CHAR columns, which caused significant performance degradation. (Bug #19783747, Bug #19680236, Bug #72058) * Creating a Geometry Column with an SRID value would not save the value to the table. (Bug #19783444, Bug #19137999, Bug #19476721, Bug #71869) * Generated SQL was missing several clauses, such as OrderBy, GroupBy, and Skip), in cases that involved the let keyword, or in other scenarios that were translated into a DbApplyExpression. (Bug #19698010, Bug #19783760, Bug #73549) * LINQ to Entities queries failed for the cases that contained a predicate using IList.Contains with an argument of DbCastExpression, DbConstantExpression, DbParameterReferenceExpression. (Bug #19690370, Bug #19783755, Bug #73643) * A SELECT query that had a nullable DATETIME field in a child .Any() clause with an .OrderBy() would fail and emit a NotImplementedException exception. (Bug #19681723, Bug #19795751, Bug #70722) * The query optimization routine would return statements with invalid table aliases when nested queries were being optimized. This would throw an Unknown column exception. (Bug #19681348, Bug #72004) * The Feature will be installed when required option was removed from the features list in the Connector/Net installer due to it not supporting on-demand installations because of dependencies with the assemblies. (Bug #19670596, Bug #19681113) * The fluent API DbModelBuilder.HasColumnType had no effect in Entity Framework 6. (Bug #19476922, Bug #19456229, Bug #19462808) * Creating a Model First or Database First model using MySQL 5.7 would set ProviderManifestToken to 5.6. (Bug #19475012) * Setting a Primary Key GUID identity in Code First in Entity Framework 6 did not function with MySQL server 5.7. Inserting a row with a valid value for the GUID generated an error, even when it had a trigger set to the correct value. As a workaround, it was necessary to redeclare the column definition to accept a dummy default, such as default ''. (Bug #19456452, Bug #19462811, Bug #19476995) * Non Primary Keys declared as Identity GUID did not have their GUID's automatically generated. (Bug #19456415, Bug #19461919, Bug #19477029) * LINQ to Entities queries that used Views with the Take operator were not correctly generated. This problem affected EF Database First scenarios. (Bug #19356006, Bug #19789288, Bug #72148) * Calling MySqlConnection.GetSchema(PROCEDURES WITH PARAMETERS, ...) would generate an error about a non-existent index. This affected Intellisense when completing stored procedures. (Bug #19289402) * Adding a new column to an existing model as identity and PK failed when applying the migration. The generated error was: Incorrect table definition; there can be only one auto column and it must be defined as a key. (Bug #19268382, Bug #19286383) * When using Entity Framework 4.3 Code first Identifiers for Migrations and Entity Framework 6, generated foreign key (http://dev.mysql.com/doc/refman/5.6/en/glossary.html#glo s_foreign_key) identifiers could be longer than 64 characters, causing MySQLException errors. The fix renames any too-long identifiers using the name format FK_guid, where guid is a global unique identifier generated at runtime. (Bug #19211564, Bug #19483128) References: This bug is a regression of Bug #67285. * In Visual Studio, Connector/Net did not read the millisecond portion of a time value for a field of type TIME(3). (Bug #19211409, Bug #18111085) * When the connection limit was exceeded, MySqlConnection.Open() would leave the TCP connections in a CLOSE_WAIT state, but now closes them. (Bug #18665388, Bug #72025) * When a client refreshed a web page associated with an expired session and if the ASP.NET project was using SessionState ... regenerateExpiredSessionId=true ..., a duplicate entry exception was generated from the MySqlSessionProvider. (Bug
MySQL Cluster 7.4.2 has been released
Dear MySQL Users, MySQL Cluster 7.4.2 (Milestone Release) is a public milestone release for MySQL Cluster 7.4. 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.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.2 DMR can be downloaded from the Development Releases tab at 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. As with any other pre-production release, caution should be taken when installing on production level systems or systems with critical data. More information on the Development Milestone Release process can be found at http://dev.mysql.com/doc/mysql-development-cycle/en/development-milestone-releases.html More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! == Changes in MySQL Cluster NDB 7.4.2 (5.6.21-ndb-7.4.2 2014-11-05) MySQL Cluster NDB 7.4.2 is a new release of MySQL Cluster, based on MySQL Server 5.6 and including features under development for version 7.4 of the NDB storage engine, as well as fixing a number of recently discovered bugs in previous MySQL Cluster releases. Obtaining MySQL Cluster NDB 7.4. MySQL Cluster NDB 7.4 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL Cluster NDB 7.4, see MySQL Cluster Development in MySQL Cluster NDB 7.4 (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-development-5-6-ndb-7-4.html). This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.21 (see Changes in MySQL 5.6.21 (2014-09-23) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-21.html). Functionality Added or Changed * After adding new data nodes to the configuration file of a MySQL Cluster having many API nodes, but prior to starting any of the data node processes, API nodes tried to connect to these missing data nodes several times per second, placing extra loads on management nodes and the network. To reduce unnecessary traffic caused in this way, it is now possible to control the amount of time that an API node waits between attempts to connect to data nodes which fail to respond; this is implemented in two new API node configuration parameters StartConnectBackoffMaxTime and ConnectBackoffMaxTime. Time elapsed during node connection attempts is not taken into account when applying these parameters, both of which are given in milliseconds with approximately 100 ms resolution. As long as the API node is not connected to any data nodes as described previously, the value of the StartConnectBackoffMaxTime parameter is applied; otherwise, ConnectBackoffMaxTime is used. In a MySQL Cluster with many unstarted data nodes, the values of these parameters can be raised to circumvent connection attempts to data nodes which have not yet begun to function in the cluster, as well as moderate high traffic to management nodes. For more information about the behavior of these parameters, see Defining SQL and Other API Nodes in a MySQL Cluster (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-api-definition.html). (Bug#17257842) Bugs Fixed * Online downgrades to MySQL Cluster NDB 7.3 failed when a MySQL Cluster NDB 7.4 master attempted to request a local checkpoint with 32 fragments from a data node already running NDB 7.3, which supports only 2 fragments for LCPs. Now in such cases, the NDB 7.4 master determines how many fragments the data node can handle before making the request. (Bug#19600834) * The server side of an NDB transporter disconnected an
MySQL Utilities 1.5.3 has been released
Dear MySQL users, MySQL Utilities version 1.5.3 is a GA release for Utilities 1.5. MySQL Utilities version 1.5.3 is compatible with MySQL Server versions 5.5 and greater. Python v2.6 and v2.7 are supported. In addition to server utilities, MySQL Utilities also contains MySQL Fabric: a framework for managing a collection of MySQL servers. MySQL Fabric is deployed as a separate service daemon that contains support for high-availability and sharding. MySQL Utilities and Fabric require Connector/Python 2.0.0 or higher. The management framework maintains a database of the routing and state information for the servers making up the system and provides an easy-to-use command line interface for adding, removing and organizing servers. High-availability is provided by continuously monitoring the servers and executing slave promotion when the master crashes and just as importantly automatically updates the state and routing information that gets messages to the right server. MySQL Fabric comes with built-in support for sharding either using ranges or consistent hashing and supports the sharding of multiple tables to ensure that rows with matching sharding keys are stored in the same shard. MySQL Fabric also contains support for global tables that are duplicated on all shards as well as the ability to synchronize schema updates across all of the servers. To provide high performance and avoid latency, transactions are directly routed by Fabric-aware connectors rather than routing via an external proxy. The connectors dispatch transactions to the correct shard, perform load-balancing, and handle read-write splitting. Currently there exists Fabric-aware versions of Connector/Python, Connector/Java, and Connector/PHP (through a Fabric-aware mysqlnd_ms plugin). MySQL Utilities v1.5.3 GA is available for download from http://dev.mysql.com/downloads/tools/utilities/ A brief summary of changes is listed below. Please check the CHANGES.txt file inside the distribution for a more complete list of changes. Changes in MySQL Utilities 1.5.3 (2014-11-04) Bugs Fixed * The MySQL Fabric installer failed to properly check for the required Connector/Python version. (Bug #19807933, Bug #74339) * Setting up a MySQL Fabric backing store would fail when the target MySQL instance used a unicode character set as the default. (Bug #19785686, Bug #74192) * The MySQLServer object created connections with use_unicode=False, and as a consequence some statements returned fields in the bytearray format, as opposed to the expected strings or unicode fields. This unexpected field data type would sometimes cause problems with several modules, such as replication and high availability. (Bug #19774543, Bug #74255) * MySQL Fabric was improved to support AWS and Trove. Changes include no longer assuming that hosts have UUIDs, and plugin support was also added. (Bug #19589254) * The mysqldbcompare utility options related to comparing all databases on two servers were accidentally removed (e.g., --all, --exclude, and --regexp in a previous release, and they have since been restored. Additionally, the error handling and validation routines were improved. (Bug #19430737, Bug #73551) Documentation - Online: http://dev.mysql.com/doc/mysql-utilities/1.5/en/ The source distribution includes the manual pages for each utility under the docs/ folder. Reporting Bugs -- We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ Enjoy! On Behalf of the MySQL/ORACLE Utilities and 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/Python 2.0.2 GA has been released
Dear MySQL users, MySQL Connector/Python 2.0.2 GA is the second GA version of 2.0 release series of the pure Python database driver for MySQL. It can be used for production environments. MySQL Connector/Python version 2.0.2 is compatible with MySQL Server versions 5.5 and greater. Python 2.6 and greater as well as Python 3.3 and greater are supported. Python 2.4, 2.5 and 3.1, 3.2 are not supported. MySQL Connector/Python 2.0.2 is available for download from: http://dev.mysql.com/downloads/connector/python/#downloads The ChangeLog file included in the distribution contains a brief summary of changes in MySQL Connector/Python 2.0.2. For a more complete list of changes, see below or online at: http://dev.mysql.com/doc/relnotes/connector-python/en/ = Changes in MySQL Connector/Python 2.0.2 (2014-11-03) Bugs Fixed * If the pool_size and pool_name connection arguments were specified using the option file (as opposed to being passed explicitly to the connect call), the pooled connection was successfully created, but an exception was raised when closing it. (Bug #19549363) * The Django backend raised an exception when converting -00-00 00:00:00 to None. (Bug #73940, Bug #19667984) * Using a connection_created signal defined in django.db.backends.signals caused a maximum recursion depth reached runtime error. (Bug #73847, Bug #19584116) * The type_code in cursor.description did not compare equal to any of the type objects defined in mysql.connector.dbapi. (Bug #73798, Bug #19584051) * Data corruption occurred when inserting sufficiently large data in a table with a TEXT type column using prepared statements, due to incorrect encoding of the data length while sending the prepared statement packet. (Bug #73690, Bug #19522948) * When the character set was binary, character set conversion could occur. Conversion is no longer done and binary data is returned as is. (Bug #71909, Bug #19500097) Documentation The manual of MySQL Connector/Python is available online here: http://dev.mysql.com/doc/connector-python/en/index.html It is also available for download in various formats here: http://dev.mysql.com/doc/index-connectors.html Reporting Bugs We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ Enjoy ! On behalf of the MySQL Connector/Python and the MySQL/ORACLE RE 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.1 has been released
writes and increased control over these also make up a large part of this work. A new ndbinfo view disk_write_speed_aggreagate_node provides information about the speed of disk writes for each LDM thread that is in use. The DiskRestartCheckpointSpeed and DiskRestartCheckpointSpeedRestart configuration parameters have been deprecated, and are subject to removal in a future MySQL Cluster release. This release adds the data node configuration parameters MinDiskWriteSpeed, MaxDiskWriteSpeed, MaxDiskWriteSpeedOtherNodeRestart, and MaxDiskWriteSpeedOwnRestart to control write speeds for LCPs and backups when the present node, another node, or no node is currently restarting. For more information, see The ndbinfo disk_write_speed_aggregate_node Table (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-ndbinfo-disk-write-speed-aggregate-node.html) , and the descriptions of the MySQL Cluster configuration parameters named previously. + Reporting of MySQL Cluster start phases has been improved, with more frequent printouts. New and better information about the start phases and their implementation has also been provided in the sources and documentation. See Summary of MySQL Cluster Start Phases (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-start-phases.html). * Information about memory usage by individual fragments can now be obtained from the memory_per_fragment view added in this release to the ndbinfo information database. This information includes pages having fixed, and variable element size, rows, fixed element free slots, variable element free bytes, and hash index memory usage. For information, see The ndbinfo memory_per_fragment Table (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-ndbinfo-memory-per-fragment.html). * Cluster Replication: Using the ndb_slave_conflict_role server system variable introduced in this release, it is now possible to set the roles of primary and secondary explicitly and dynamically when using conflict detection and resolution with a circular or active-active MySQL Cluster Replication setup. This variable can take any one of the values PRIMARY, SECONDARY, PASS, or NULL (the default). (PASS enables a passthrough state in which the effects of any conflict resolution function are ignored.) This can be useful when it is necessary to fail over from the MySQL Cluster acting as the primary. The slave SQL thread must be stopped when the value of this variable is changed. In addition, it is not possible to change it directly between PASS and either of PRIMARY or SECONDARY. For more information, see the description of ndb_slave_conflict_role as well as MySQL Cluster Replication Conflict Resolution (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-replication-conflict-resolution.html). * Cluster Replication: A number of changes and improvements have been made to exceptions tables for MySQL Cluster Replication conflict detection and resolution. A reserved column name namespace is now employed for metacolumns, which allows the recording of an arbitrary subset of main table columns that are not part of the table's primary key. The names of all metacolumns in the exception table should now be prefixed with NDB$. It is no longer necessary to record the complete primary key. Matching of main table columns to exceptions table columns is now performed solely on the basis of name and type. In addition, you can now record in the exceptions table the values of columns which not part of the main table's primary key. Existing exceptions tables continue to be supported. For additional information, see MySQL Cluster Replication Conflict Resolution (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-replication-conflict-resolution.html). On Behalf of the MySQL Cluster and the Oracle/MySQL RE Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Utilities 1.5.2 has been released
) * Commands accept either a UUID or an address (i.e. host:port) to specify a server. The code was ignoring that a wrong address could be provided, and in consequence the execution could hang. The address is now validated before it is used. If the server belongs to a group, the address is checked against the information stored in the state store. If the server is not part of a group, Fabric will try to access the server until a timeout is reached. The default value for this timeout is defined through the option unreachable_timeout in the servers section in the configuration file, and it affects the following commands: + server lookup_uuid address [--timeout=NONE] ... + server clone group_id destn_address [--timeout=NONE] ... + group add group_id address [--timeout=NONE] ... (Bug #19172889, Bug #73233) * The mysqldbcompare utility failed when comparing two databases while using the SQL difftype. (Bug #19174364, Bug #72181) * Some of try/exception blocks were catching the DatabaseError exception and raising a new exception without propagating information from the original problem. The error messages were improved by adding information about the server where the error originated, and the caught DatabaseError information is merged into the appropriate objects. (Bug #18999358, Bug #18370950, Bug #73019) * The --force option was removed from the mysqlfabric utility. It was removed to help alleviate confusion about its purpose. Its functionality was replaced by clearer status messages that are always printed out. (Bug #18991971, Bug #72931) * The --skip-innodb option is used by the utilities, but this option is ignored in MySQL 5.7+. A warning is now issued for this scenario. (Bug #18753983, Bug #72633) * The mysqldiff utility's --skip-table-options option would fail when comparing two tables with different column ordering, or when also setting the --difftype option to SQL. (Bug #18632836, Bug #72178) * The RPM installation failed to check for the required Connector/Python version, and having the incorrect version installed caused mysqlfabric manage setup to fail. (Bug #18450008) Documentation - Online: http://dev.mysql.com/doc/mysql-utilities/1.5/en/ The source distribution includes the manual pages for each utility under the docs/ folder. Reporting Bugs -- We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ Enjoy! On Behalf of the MySQL/ORACLE Utilities and 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/Python 2.0.1 GA has been released
Dear MySQL users, MySQL Connector/Python 2.0.1 GA is the first GA version of 2.0 release series of the pure Python database driver for MySQL. It can be used for production environments. MySQL Connector/Python version 2.0.1 is compatible with MySQL Server versions 5.5 and greater. Python 2.6 and greater as well as Python 3.3 and greater are supported. Python 2.4, 2.5 and 3.1, 3.2 are not supported. MySQL Connector/Python 2.0.1 is available for download from: http://dev.mysql.com/downloads/connector/python/#downloads The ChangeLog file included in the distribution contains a brief summary of changes in MySQL Connector/Python 2.0.1. For a more complete list of changes, see below or online at: http://dev.mysql.com/doc/relnotes/connector-python/en/ = Changes in MySQL Connector/Python 2.0.1 (2014-09-24) Functionality Added or Changed * Connector/Python is now compatible with Django 1.7. (Bug #72746, Bug #19163169) * RANGE_STRING is now supported as a sharding type. This is similar to the regular RANGE sharding type, but instead of an integer key, requires a UTF-8 encoded string. For example: cnx.set_property(tables=[employees.employees], key=u'employee_name', mode=fabric.MODE_READONLY) Only Unicode strings are supported. Any other type given when using a shard defined using RANGE_STRING causes a ValueError to be raised. * RANGE_DATETIME is now supported as a sharding type. This is similar to the regular RANGE sharding type, but instead of an integer key, requires a datetime or date object. For example, to get the shard which holds employees hired after the year 2000, you could do the following, with lower bounds set as group1/1980-01-01, group2/2000-01-01: cnx.set_property(tables=[employees.employees], key=datetime.date(2000, 1, 1), mode=fabric.MODE_READONLY) If the lower bounds included a time, it would have been like this: cnx.set_property(tables=[employees.employees], key=datetime.datetime(2000, 1, 1, 12, 0, 0), mode=fabric.MODE_READONLY) Only datetime.datetime and datetime.date values are supported. Any other type given when using a shard defined using RANGE_DATETIME causes a ValueError to be raised. Bugs Fixed * Connector/Python failed to catch an exception when SSL capability was found to be unavailable. (Bug #19440592) * Multiple [connector_python] option groups sometimes caused an error. (Bug #19170287) * Date and time query formatting was fixed for the Django backend. (Bug #19179711) * An error failed to occur if an option file was named multiple times. (Bug #19169143) * Some valid Connector/Python connection options were not recognized when specified in the [connector_python] option group. (Bug #19168737) * An exception was raised when a cursor tried to convert LINESTRING data as UTF-8 data. Now such values are returned without decoding. (Bug #73187, Bug #19164627) * With Python 2, Connector/Python could truncate digits of floating-point values. (Bug #73266, Bug #19225481) * Binding None (NULL) to a parameter marker in a prepared statement did not work. (Bug #73370, Bug #19282158) * !include and !includedir directives in option files were not handled properly. (Bug #73660, Bug #19481761) * Connector/Python now supports a shutdown() method that, unlike disconnect(), closes the client connection without attempting to send a QUIT command to the server first. Thus, it will not block if the connection is disrupted for some reason such as network failure. (Bug #72691, Bug #18798953) Documentation Online:http://dev.mysql.com/doc/connector-python/en/index.html The source distribution includes the manual in various formats under the docs/ folder. Reporting Bugs We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ Enjoy ! On behalf of the MySQL Connector/Python and the MySQL/ORACLE RE Team, Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL for Excel 1.3.2 GA has been released
Dear MySQL users, The MySQL Windows Experience Team is proud to announce the release of MySQL for Excel version 1.3.2. This is a GA release for 1.3.x. It can be used for production environments. MySQL for Excel is an application plug-in enabling data analysts to very easily access and manipulate MySQL data within Microsoft Excel. It enables you to directly work with a MySQL database from within Microsoft Excel so you can easily do tasks such as: * Importing MySQL Data into Excel * Exporting Excel data directly into MySQL to a new or existing table * Editing MySQL data directly within Excel As this is a GA version the MySQL for Excel product can be downloaded at this link http://dev.mysql.com/downloads/windows/excel/ Changes in MySQL for Excel 1.3.2 (2014-09-22, General Availability) This section documents all changes and bug fixes applied to MySQL for Excel since the release of 1.3.1. Several new features were added the 1.3.x branch, for more information see What Is New In MySQL for Excel 1.3 (http://dev.mysql.com/doc/mysql-for-excel/en/mysql-for-excel-what- is-new-1-3.html). Known limitation: Upgrading from versions MySQL for Excel 1.2.0 and lower is not possible due to a bug fixed in MySQL for Excel 1.2.1. In that scenario, the old version (MySQL for Excel 1.2.0 or lower) must be uninstalled first. Upgrading from version 1.2.1 works correctly. Functionality Added or Changed * Excel tables created from stored procedures can now be refreshed. (Bug #19129583, Bug #73151) * Several fields next to checkboxes were updated to automatically be focused and selected when the corresponding checkbox or radio button is checked. * A new global option called Preview MySQL table data before an Edit Data session is opened was added. When checked (default), the data of a selected MySQL table to be edited is shown in a preview dialog before the Edit Data session is opened. If the option is unchecked, no preview takes place and the Edit Data session is simply opened. A new context menu option called Preview Data was also added, and it is available when right-clicking a MySQL table or view that is listed in the DB Objects selection panel. The option opens the Preview Data dialog and shows the first 10 (by default) rows of the selected table or view. In previous versions, the Import Data dialog was always displayed when an Edit Data was started, the Preview Data dialog replaces it to avoid confusion about the type of operation being performed. * MySQL for Excel now handles the managed Fabric connection type that was introduced in MySQL Workbench 6.2. New icons were introduced for SSH and managed Fabric connections. Connections that are not of the type native, native_socket, or native_sshtun, will not be listed in the connections listing under the Welcome Panel. * A single PivotTable can now be created for the entire Excel data model when importing multiple MySQL tables, which allows analyzing the related Excel tables within a single PivotTable. The Excel data model contains all Excel tables at the time the single PivotTable is created, so if previous imports were already performed, the data model may show more tables than the imported ones in the last multiple import operation. The option to create a PivotTable for each imported table is still present, but single PivotTable creation is selected by default. * The generated summary row added by the Add Summary Fields option when importing MySQL data is now bold and includes a thick border, as to differentiate from actual data. * When importing multiple database objects, the ability to add related tables to the directly related tables (i.e. indirectly related tables) was added by right-clicking a table in the related tables list (at the right side of the dialog) and choosing Add Related Tables from the context menu. * The Schema Selection panel now includes collation information for the listed schemas that can be shown by right-clicking the Schemas list and choosing Display Schema Collations from the context menu. * Changed the way stored procedure result sets are laid out in a Excel worksheet when all of them are imported horizontally or vertically, and when PivotTables are created for each result set. Instead of skipping one row or column, the necessary rows and columns are skipped so the created PivotTables for the result sets do not collide. Bugs Fixed * Duplicate edit session connection information would be saved to the settings.config file, which generated a Editing not possible error message after using the Work Offline option. Closing an unsaved workbook now opens an Excel Save As dialog. (Bug #19347634) * The Append Excel Data to Table operation failed when the number of columns did not match, even when the data was
MySQL Connector/NET 6.9.3 GA has been released
Dear MySQL users, MySQL Connector/Net 6.9.3 is the first GA release for the 6.9.x series of the .NET driver for MySQL. It can be used for production environments. It is appropriate for use with MySQL server versions 5.5-5.7. It is now available in source and binary form from http://dev.mysql.com/downloads/connector/net/#downloadsandmirrorsites (note that not all mirror sites may be up to date at this point-if you can't find this version on some mirror, please try again later or choose another download site.) Changes in MySQL Connector/Net 6.9.3 (2014-09-03, General Availability) Bugs Fixed * Adding a new column to an existing model as identity and PK failed when applying the migration. The generated error was: Incorrect table definition; there can be only one auto column and it must be defined as a key. (Bug #19286383) * Calling MySqlConnection.GetSchema(PROCEDURES WITH PARAMETERS, ...) would generate an error about a non-existent index. This affected Intellisense when completing stored procedures. (Bug #19289402) The documentation is available at: http://dev.mysql.com/doc/refman/5.7/en/connector-net.html Enjoy and thanks for the support! On behalf of the MySQL Connector/NET and the MySQL/ORACLE RE Team. Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Cluster Manager 1.3.2 has been released
-import-config.html) command if it was managing more than one cluster at the time. (Bug #19380825) * Agent: During a recovery for a MySQL Cluster Manager agent that uses IP addresses instead of hostnames, the agent sent out an excessive amount of information, the processing of which slowed down the restart process considerably. This fix changes the way the IP addresses are handled, reducing the amount of sent information to a much more reasonable level. (Bug #19269735) * Agent: Upgrade from MySQL Cluster Manager 1.2.4 (to 1.3.1) failed if the last command executed before the upgrade was any one of backup cluster (http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-backup-cluster.html) , restore cluster (http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-restore-cluster.html) , abort backup (http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-abort-backup.html) , or import cluster (http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-cluster.html). This has been fixed, and users of version 1.2.4 can now upgrade to version 1.3.2. (Bug #19199645) * Agent: The MySQL Cluster Manager agent sometimes got SIGABRT errors while executing SQL statements. (Bug #19032927) * Agent: mcmd crashed due to an out-of-memory error after a combination of the following conditions: + An abrupt failure of one of the site machines, instead of a clean stop. + Only a minority of the agents are available. + Some unmanaged SQL slots came into use and changed their states to connected, and the changes are reported by a ndb_mgmd process. (Bug #18781345) * Client: Restoration of a cluster failed when the cluster contained both API nodes with and without specified hostnames. (Bug #19313429) * Client: If a mysqld process was specified in a create cluster statement using the mysqld@* syntax (with no host specified), the show status --process commands would never show the process as connected, even when it was. (Bug #19152161) * Client: When using the show status (http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-show-status.html) command with the --backup option, the MySQL Cluster Manager client sometimes accepted an additional option, which was actually meaningless. This fix makes the client throw an error when any other option is used in combination with --backup. (Bug #19032714) * Client: MySQL Cluster Manager threw an error when the add package (http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-add-package.html) command was run with the argument for the --basedir option being double quoted, complaining the path did not exist. It was because MySQL Cluster Manager took the double quotes literally, as parts of the path name. (Bug #18973711) * Client: On Windows platforms, the MySQL Cluster Manager client's response to the list hosts command was very slow when any one of the MySQL Cluster Manager agents was down. (Bug #18966650) * Client: When using the import config (http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-config.html) command, some process level settings in the cluster's config.ini file were imported as instance level settings. (Bug #18651663) * Client: When the configuration of a running cluster was being imported, the import config (http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-config.html) command took the settings from the global session variables instead of the configuration files of the cluster and the MySQL servers. This fix makes MySQL Cluster Manager import the settings from the configuration files, and only use values of the global session variables when it cannot find, open, or access the configuration files. (Bug #18652366) You can also find more information on the contents of this release in the change log: http://dev.mysql.com/doc/relnotes/mysql-cluster-manager/1.3/en/mcm-news-1-3-2.html The user manual can be found at: http://dev.mysql.com/doc/index-cluster.html Your feedback is greatly appreciated! Please report any problems you have at https://bug.oraclecorp.com/ Enjoy! On Behalf of the MySQL/ORACLE RE Team, 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.4 has been released
Dear MySQL users, MySQL Connector/ODBC 5.3.4, 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 third 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). Also, Connector/ODBC 5.3 introduces a GTK+-based setup library providing a GUI DSN setup dialog on some Unix-based systems, currently included in the Oracle Linux 6 and Debian 6 binary packages. Other new features in the 5.3 driver are FileDSN and Bookmarks support. 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/refman/5.6/en/connector-odbc-installation.html Enjoy! The MySQL Connectors team at Oracle - Changes in MySQL Connector/ODBC 5.3.4 (2014-07-18) Security Notes * Security Fix: The linked OpenSSL library for Connector/ODBC Commercial 5.3.4 has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224 (http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-02 24). This change does not affect the Oracle-produced MySQL Community build of Connector/ODBC 5.3.4, which uses the yaSSL library instead. (CVE-2014-0224) Functionality Added or Changed * Introduced a new DSN configuration option, rsakey, for specifying the full-path name of the PEM file that contains the RSA public key for using the SHA256 authentication plugin of MySQL. See Connector/ODBC DSN Configuration Options (http://dev.mysql.com/doc/connector-odbc/en/connector-odbc-con figuration-connection-parameters.html#codbc-dsn-config-options ) for details. * Added NULL handle checks in functions exported by Connector/ODBC. -- Hery Ramilison MySQL/ORACLE Release Engineering Team -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/NET 6.9.2 RC has been released
Dear MySQL users, MySQL Connector/Net 6.9.2 a new version of the all-managed .NET driver for MySQL has been released. This is a RC release for 6.9.x and is not recommended for production environments. It is appropriate for use with MySQL server versions 5.5-5.7. It is now available in source and binary form from http://dev.mysql.com/downloads/connector/net/#downloadsandmirrorsites (note that not all mirror sites may be up to date at this point-if you can't find this version on some mirror, please try again later or choose another download site.) Changes in MySQL Connector/Net 6.9.2 (2014-07-18 Release Candidate) Bugs Fixed * Creating a Geometry Column with an SRID value would not save the value to the table. (Bug #19137999, Bug #71869) * Added async/await compatible methods * Added the SiteMap and Personalization configuration web providers to the MySql.Web Nuget package. The documentation is available at: http://dev.mysql.com/doc/refman/5.7/en/connector-net.html Nuget Packages: https://www.nuget.org/packages/MySql.Data/6.9.2-rc1 https://www.nuget.org/packages/MySql.Data.Entity/6.9.2-rc1 https://www.nuget.org/packages/MySql.Web/6.9.2-rc1 Enjoy and thanks for the support! On behalf of the MySQL Connector/NET and the MySQL/ORACLE RE Team. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL for Visual Studio 1.2.2 RC has been released
Dear MySQL users, MySQL for Visual Studio is a product including all of the Visual Studio integration. The 1.2.2 version is a release candidate release of this product which is feature complete but still can contain minor bugs and is not suitable for production environments. This version is appropriate for use with MySQL server versions 5.5-5.6. As this is a release candidate version of the MySQL for Visual Studio product, it can be downloaded only by using the product standalone installer at this link http://dev.mysql.com/downloads/windows/visualstudio/ The 1.2.2 version includes the following new features (2014-07-15): - A new MySQL Project Wizard for creating Windows Forms applications. - A new MySQL Project Wizard for creating ASP.NET MVC web applications. - A new option in web configuration tool for the ASP.NET Personalization Provider (this feature requires Connector/Net 6.9). - A new option in web configuration tool for the ASP.NET Site Map Provider (this feature requires Connector/Net 6.9). MySQL Project Wizard for Windows Forms. -- The Windows Forms Project Wizard is available at the Visual Studio New Project dialog, either at the MySQL category or by filtering by name. It also can be accessed by using the MySQL Toolbar inside Visual Studio. This wizard automates the generation of a .NET Windows Forms Application that is connected to a MySQL data source. A Typed DataSet or an Entity Framework Model can also be generated to link the Application to the MySQL Database. The user can select one or more tables that exists in the database. Each table can have a different type of view. The types of views that are available in this version are: Single Layout: A form that contains one control by each existing column in the table with navigation controls and that allows CRUD operations. All controls can include data typed validations for Numeric types and Datetime types. Grid layout: A form with a Grid that contains navigation controls. Master-Detail: A form with a single controls layout for the Parent table and a grid to navigate in the child table. Supported with C# or Visual Basic language. This feature requires Connector/Net 6.7.5, 6.8.3 or 6.9.x For more details on the features included check the documentation at : For Windows Forms Wizard: http://dev.mysql.com/doc/connector-net/en/connector-net-visual-studio-windows-forms.html For MVC Wizard: http://dev.mysql.com/doc/connector-net/en/connector-net-visual-studio-mvc-project-wizard.html MySQL Project Wizard for ASP.NET MVC -- The ASP.NET MVC Project Wizard is available at the Visual Studio New Project dialog, either at the MySQL category or by filtering by name. It also can be accessed by using the MySQL Toolbar inside Visual Studio. This wizard automates the generation of an ASP.NET MVC. The MVC versions supported for this wizard are 3 when using Visual Studio 2010 or 2012, and 4 when using Visual Studio 2013. The Web Application includes the MySQL Membership configuration to manage ASP.NET authentication. The login and create user views are generated by the wizard and it also includes the generation of multiple browsable views for each one of the tables selected for the application generation. The generation of the MVC items is done by creating an Entity Framework data model either with Entity Framework version 5 or 6 depending on the user's selection. Supported with C# or Visual Basic language. This feature requires Connector/Net 6.7.5, 6.8.3 or 6.9.x For more details on the features included check the documentation at : New option in web configuration tool for the ASP.NET Personalization Provider -- Personalization provider allows to store personalization state-state data regarding the content and layout of Web Parts pages-generated by the Web Parts personalization service using MySQL as a data source. This feature requires Connector/Net 6.9.x New option in web configuration tool for the ASP.NET Site Map Provider -- Site Map provider allows to show a hierarchical list of links that describe the structure of a site. This feature requires Connector/Net 6.9.x For discussion, join the MySQL for Visual Studio forums: http://forums.mysql.com/list.php?174 Download MySQL for Visual Studio 1.2.2 RC from: http://dev.mysql.com/downloads/windows/visualstudio/ Quick links - MySQL for Visual Studio documentation http://dev.mysql.com/doc/connector-net/en/connector-net-visual-studio.html - Bugs: http://bugs.mysql.com - Forums: http://forums.mysql.com/index.php?174 - Blog: http://blogs.oracle.com/MySqlOnWindows/ Enjoy and thanks for the support! MySQL for Visual Studio Team. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Cluster 7.1.32 has been released
is LCP_STATUS_IDLE, then all the tables should have an LCP status of TLS_COMPLETED. When an LCP starts, the global LCP status is LCP_INIT_TABLES and the thread starts setting all the NDB tables to TLS_ACTIVE. If any tables are not ready for LCP, the LCP initialization procedure continues with CONTINUEB signals until all tables have become available and been marked TLS_ACTIVE. When this initialization is complete, the global LCP status is set to LCP_STATUS_ACTIVE. This bug occurred when the following conditions were met: + An LCP was in the LCP_INIT_TABLES state, and some but not all tables had been set to TLS_ACTIVE. + The master node failed before the global LCP state changed to LCP_STATUS_ACTIVE; that is, before the LCP could finish processing all tables. + The NODE_FAILREP signal resulting from the node failure was processed before the final CONTINUEB signal from the LCP initialization process, so that the node failure was processed while the LCP remained in the LCP_INIT_TABLES state. Following master node failure and selection of a new one, the new master queries the remaining nodes with a MASTER_LCPREQ signal to determine the state of the LCP. At this point, since the LCP status was LCP_INIT_TABLES, the LCP status was reset to LCP_STATUS_IDLE. However, the LCP status of the tables was not modified, so there remained tables with TLS_ACTIVE. Afterwards, the failed node is removed from the LCP. If the LCP status of a given table is TLS_ACTIVE, there is a check that the global LCP status is not LCP_STATUS_IDLE; this check failed and caused the data node to fail. Now the MASTER_LCPREQ handler ensures that the tabLcpStatus for all tables is updated to TLS_COMPLETED when the global LCP status is changed to LCP_STATUS_IDLE. (Bug #18044717) * The logging of insert failures has been improved. This is intended to help diagnose occasional issues seen when writing to the mysql.ndb_binlog_index table. (Bug #17461625) * Employing a CHAR column that used the UTF8 character set as a table's primary key column led to node failure when restarting data nodes. Attempting to restore a table with such a primary key also caused ndb_restore to fail. (Bug #16895311, Bug #68893) * Cluster Replication: When using NDB$EPOCH_TRANS, conflicts between DELETE operations were handled like conflicts between updates, with the primary rejecting the transaction and dependents, and realigning the secondary. This meant that their behavior with regard to subsequent operations on any affected row or rows depended on whether they were in the same epoch or a different one: within the same epoch, they were considered conflicting events; in different epochs, they were not considered in conflict. This fix brings the handling of conflicts between deletes by NDB$EPOCH_TRANS with that performed when using NDB$EPOCH for conflict detection and resolution, and extends testing with NDB$EPOCH and NDB$EPOCH_TRANS to include delete-delete conflicts, and encapsulate the expected result, with transactional conflict handling modified so that a conflict between DELETE operations alone is not sufficient to cause a transaction to be considered in conflict. (Bug #18459944) * Cluster API: When an NDB data node indicates a buffer overflow via an empty epoch, the event buffer places an inconsistent data event in the event queue. When this was consumed, it was not removed from the event queue as expected, causing subsequent nextEvent() calls to return 0. This caused event consumption to stall because the inconsistency remained flagged forever, while event data accumulated in the queue. Event data belonging to an empty inconsistent epoch can be found either at the beginning or somewhere in the middle. pollEvents() returns 0 for the first case. This fix handles the second case: calling nextEvent() call dequeues the inconsistent event before it returns. In order to benefit from this fix, user applications must call nextEvent() even when pollEvents() returns 0. (Bug #18716991) * Cluster API: The pollEvents() method returned 1, even when called with a wait time equal to 0, and there were no events waiting in the queue. Now in such cases it returns 0 as expected. (Bug #18703871) On behalf of the MySQL Cluster and the Oracle/MySQL RE Team, Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL for Excel 1.3.1 RC has been released
Dear MySQL users, The MySQL Windows Experience Team is proud to announce the release of MySQL for Excel version 1.3.1. This is a RC release for 1.3.x. MySQL for Excel is an application plug-in enabling data analysts to very easily access and manipulate MySQL data within Microsoft Excel. It enables you to directly work with a MySQL database from within Microsoft Excel so you can easily do tasks such as: * Importing MySQL Data into Excel * Exporting Excel data directly into MySQL to a new or existing table * Editing MySQL data directly within Excel As this is a RC version the MySQL for Excel product can be downloaded only by using the product standalone installer at this link http://dev.mysql.com/downloads/windows/excel/ Changes in MySQL for Excel 1.3.1 (Not yet released, RC) This section documents all changes and bug fixes applied to MySQL for Excel since the release of 1.3.0. Several new features were added the 1.3.x branch, for more information see What Is New In MySQL for Excel (http://dev.mysql.com/doc/refman/5.6/en/mysql-for-excel-what-is-new.html). Known limitations: * Upgrading from versions MySQL for Excel 1.2.0 and lower is not possible due to a bug fixed in MySQL for Excel 1.2.1. In that scenario, the old version (MySQL for Excel 1.2.0 or lower) must be uninstalled first. Upgrading from version 1.2.1 works correctly. * PivotTables are normally placed to the right (skipping one column) of the imported data, they will not be created if there is another existing Excel object at that position. Functionality Added or Changed * When reopening a saved Excel workbook that contains imported MySQL data, MySQL for Excel attempts to reconnect the Excel tables with the corresponding MySQL databases where the imported MySQL data was imported from. If the MySQL connections are not found, then a new dialog prompts you to either ignore, create, or delete the missing connections. Ignore allows you to work offline, and the dialog will open the next time the Excel workbook is opened. (Bug #18961860, Bug #72966) * Control + A now selects all tables and views in the Database Objects selection panel. (Bug #18961544, Bug #72963) Bugs Fixed * Data could not be imported from a remote MySQL server. (Bug #19012634, Bug #73040) * The Edit Connection dialog was not populated with information from the selected MySQL connection. (Bug #18968777, Bug #72990) * In Excel 2013, importing the same table twice in the same Excel worksheet failed after deleting the Excel table linked to in the first report. (Bug #18962670, Bug #72976) * Data could not be imported to the left of previously imported data if the new data intersected with the existing import. (Bug #18962617, Bug #72975) * After importing data, clicking Refresh All from the Data tab would fail to refresh the data, and it generated an Initialization of the data source failed error. (Bug #18962538, Bug #72974) * When exporting data, a duplicate entry was sent to the MySQL server when data was exported to a new table with the First Row Contains Column Names checkbox deselected. The generated error was similar to Error while inserting rows... MySQL Error 1062: Duplicate entry '1' for key 'PRIMARY'. (Bug #18962470, Bug #72973) * With the Create a Pivot Table with the imported data option enabled, Data Import failed to create a PivotTable for tables that contained a large data set. (Bug #18962371, Bug #72972) * When importing tables, the Pick related Tables or Views feature did not function in Excel 2007 or Excel 2010, but did in Excel 2013. (Bug #18962354, Bug #72971) * For new columns, the Export Data dialog would not accept manually typed in data types that contained a parenthesis, such as ENUM. (Bug #18962214, Bug #72970) * Line and LinearRing were removed from the list of valid data types, so they no longer appear in the Data Export data type form. (Bug #18962184, Bug #72969) * Hovering over elements in the MySQL connecting and object listing could cause the text of each item to be bold. (Bug #18962130, Bug #72968) * Imported data would not refresh if the table name was changed in Excel during the import. The table name is no longer used to verify the MySQL connection. (Bug #18961806, Bug #72964) * Edit Sessions would fail to restore with sessions that contained tables with zero DATETIME values. Edit Sessions would also fail to restore when MySQL for Excel was started on a currently opened Excel workbook. (Bug #18889495, Bug #72842) * Attempting to import a table with ENUM values would fail with an Input string was not in a correct format. error. (Bug #18728748, Bug #72434) References: See also Bug #18962214, Bug #72970. Quick links: You can access the MySQL for Excel documentation at
MySQL for Visual Studio 1.2.1 beta has been released
Dear MySQL users, MySQL for Visual Studio is a product including all of the Visual Studio integration previously available as part of Connector/Net. The 1.2.1 version is a beta release of this product which is feature complete but still can contain minor bugs and is not suitable for production environments. This version is appropriate for use with MySQL Server versions 5.5-5.6. MySQL Server 5.7 is also compatible but not fully supported yet. As this is a beta version the MySQL for Visual Studio product can be downloaded only by using the product standalone installer at this link http://dev.mysql.com/downloads/windows/visualstudio/ The 1.2.1 version includes the following new features: - A new MySQL Project Wizard for creating Windows Forms applications. - A new MySQL Project Wizard for creating ASP.NET MVC 3/4 web applications. - A new option in web configuration tool for the ASP.NET Personalization Provider (this feature requires Connector/Net 6.9). - A new option in web configuration tool for the ASP.NET Site Map Provider (this feature requires Connector/Net 6.9). MySQL Project Wizard for Windows Forms -- This wizard automates the generation of a .NET Windows Forms Application that is connected to a MySQL data source and supports CRUD operations. A Typed DataSet or an Entity Framework Model can also be generated to link the Application to the MySQL Database. In this version only one table can be selected in the wizard. This limitation will be replaced with a multiple tables wizard in the 1.2.2 upcoming version. Within the Wizard the user can select one of three options for the View type: Single Layout: A form that contains one control by each existing column in the table with navigation controls and that allows CRUD operations. All controls can include data typed validations for Numeric types and Datetime types. Grid layout: A form with a Grid that contains navigation controls. Master-Detail: A form with a single controls layout for the Parent table and a grid to navigate in the child table. Supported with C# or Visual Basic language. This feature requires Connector/Net 6.7.5, 6.8.3 or 6.9.x. For more details on the features included check the documentation at : http://dev.mysql.com/doc/connector-net/en/connector-net-windows-forms.html MySQL Project Wizard for ASP.NET MVC 3 -- The ASP.NET MVC Project Wizard is available at the Visual Studio New Project dialog, either at the MySql category or by filtering by name. It also can be accessed by using the MySQL Toolbar inside Visual Studio. This wizard automates the generation of an ASP.NET MVC 3/4 application that includes the MySQL Membership configuration to manage ASP.NET authentication. The login and create user views are generated by the wizard and it also includes the generation of multiple browsable views for each one of the tables selected for the application generation. The generation of the MVC items is done also with the creation of an Entity Framework data model either with Entity Framework version 5 or 6 depending on the user's selection. Supported with C# or Visual Basic language. This feature requires Connector/Net 6.7.5, 6.8.3 or 6.9.x. For more details on the features included check the documentation at : http://dev.mysql.com/doc/connector-net/en/connector-net-windows-mvc-template.html New option in web configuration tool for the ASP.NET Personalization Provider - Personalization provider allows to store personalization state-state data regarding the content and layout of Web Parts pages-generated by the Web Parts personalization service using MySQL as a data source. This feature requires Connector/Net 6.9.x. http://dev.mysql.com/doc/connector-net/en/connector-net-website-config.html New option in web configuration tool for the ASP.NET Site Map Provider -- Site Map provider allows to show a hierarchical list of links that describe the structure of a site. This feature requires Connector/Net 6.9.x. http://dev.mysql.com/doc/connector-net/en/connector-net-website-config.html For discussion, join the MySQL for Visual Studio forums: http://forums.mysql.com/list.php?174 Download MySQL for Visual Studio 1.2.1 beta from: http://dev.mysql.com/downloads/windows/visualstudio/ Quick links - MySQL for Visual Studio documentation http://dev.mysql.com/doc/connector-net/en/connector-net-visual-studio.html - Bugs: http://bugs.mysql.com - Forums: http://forums.mysql.com/index.php?174 - Blog: http://blogs.oracle.com/MySqlOnWindows/ Enjoy and thanks for the support! MySQL for Visual Studio Team. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/C 6.1.5 has been released
. Shared library names now include 18.3 where appropriate. Bugs Fixed * Calling mysql_get_server_version() with an invalid connection handler argument caused the client to exit. Now it returns 0 and reports a CR_COMMANDS_OUT_OF_SYNC error. (Bug #18053212) * The C client library could leak memory when client plugins were used. (Bug #17933308) * On Windows, calling mysql_thread_init() call without mysql_init() caused the client to exit. Now it returns a nonzero result because it is an error to call mysql_thread_init() before the client library is initialized with mysql_library_init(). (Bug #17514920) * There was a difference in certificate handling by yaSSL and OpenSSL (used for Community and Enterprise, respectively). OpenSSL expected a blank certificate to be sent when not all of the --ssl-ca, --ssl-cert, and --ssl-key options were specified, and yaSSL did not do so. To resolve this, yaSSL has been modified to send a blank certificate when an option is missing. (Bug #68788, Bug #16715064) -- Hery Ramilison MySQL/ORACLE Release Engineering Team -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/J 5.1.31 has been released
#16708231, Bug #67803) * When closing a server-prepared statement twice and cachePrepStmts=true, the second call closed the statement as expected. However, if a call of Connection.prepareStatement() was made again with exactly same SQL string, Connector/J obtained the closed statement from the cache and failed by throwing an exception. With this fix, ServerPreparedStatement.close() detects and ignores subsequent close() calls on cached statements that have already been closed. (Bug #16004987, Bug #66947) Thanks, On behalf of Oracle/MySQL Build Team, Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Utilities 1.4.3 GA (including MySQL Fabric) has been released
Dear MySQL users, This is the GA release for Utilities 1.4 and the first GA release for MySQL Fabric. MySQL Utilities version 1.4.3 is compatible with MySQL Server versions 5.1 and greater, but should work with earlier versions (greater than v4.1). Python v2.6 and v2.7 are supported. In addition to server utilities, MySQL Utilities also contains MySQL Fabric: a framework for managing a collection of MySQL servers. MySQL Fabric is deployed as a separate service daemon that contains support for high-availability and sharding. The management framework maintains a database of the routing and state information for the servers making up the system and provides an easy-to-use command line interface for adding, removing and organizing servers. High-availability is provided by continuously monitoring the servers and executing slave promotion when the master crashes and just as importantly automatically updates the state and routing information that gets messages to the right server. MySQL Fabric comes with built-in support for sharding either using ranges or consistent hashing and supports the sharding of multiple tables to ensure that rows with matching sharding keys are stored in the same shard. MySQL Fabric also contains support for global tables that are duplicated on all shards as well as the ability to synchronize schema updates across all of the servers. To provide high performance and avoid latency, transactions are directly routed by Fabric-aware connectors rather than routing via an external proxy. The connectors dispatch transactions to the correct shard, perform load-balancing, and handle read-write splitting. Currently there exists Fabric-aware versions of Connector/Python, Connector/Java, and Connector/PHP (through a Fabric-aware mysqlnd_ms plugin). MySQL Utilities v1.4.3 is available for download from http://dev.mysql.com/downloads/tools/utilities/ A brief summary of changes is listed below. Please check the CHANGES.txt file inside the distribution for a more complete list of changes. Bugs Fixed (2014-05-27) -- * Due to the several changes in the high-availability and sharding sub-systems, the automatic routine to automatically find the lockable objects for a given procedure was not always valid. The consequence was that some procedures may have tried to update the same group concurrently when they should have been serialized. (Bug #18712020, Bug #72553) * When executing mysqlfabric manage setup, some of the generated CREATE TABLE statements were explicitly requesting the InnoDB engine and ignoring the default-storage-engine option, thus preventing use of NDB as a state store. (Bug #18648779) * Any empty password definition (password = ) in the configuration file would emit errors. (Bug #18524482, Bug #72149) * The FailoverDaemon class from the failover_daemon module was refactored to extend the Daemon class, so that the duplicated code was removed. (Bug #18546744) * Remote commands were authenticating the request twice, both before and after the command was sent to Fabric. This meant unnecessary requests were made to the state store. (Bug #18477189) * Executing mysqlfabric manage setup would sometimes halt with a connection error due to a short timeout. (Bug #18458461) * Commands failed if the protocol.xmlrpc.user option was not provided in the configuration file or from the command-line. Now, the user admin is the default. (Bug #18459012) * A group add with a server as localhost:32274 caused Fabric to hang, as 32274 is the port used by Fabric. (Bug #18454737, Bug #72119) * A PROMOTE after RESET MASTER would cause Fabric to hang. Now, SHOW SLAVE STATUS is used to check whether the slave has processed all of the entries in the relay log. (Bug #18454679, Bug #72118) * The mysqldbcompare utility was not correctly checking differences for different rows internally associated to the same span key. Only the first difference was displayed. (Bug #18477410) * Optimizations to the mysqldbcompare utility include: + A new step was added to the data consistency check, now executing a CHECKSUM TABLE first (which is faster when no differences are expected). The current comparison algorithm is only execute if this preliminary full table checksum fails. A new --skip-checksum-table option was added to skip this new step that otherwise is executed by default. + The BINARY type is used instead of CHAR to store hash values in a more optimized way. + Unnecessary keys were removed from the temporary table (including the primary key). + ENGINE=MyISAM is now used for the temporary compare table. (Bug #18483844) * The temporary table created by the mysqldbcompare utility was missing an index for the 'span' column, meaning that the
MySQL Connector/Python 1.1.7 has been released
Dear MySQL users, MySQL Connector/Python 1.1.7 is a new version of the pure Python database driver for MySQL. MySQL Connector/Python version 1.1 is compatible with MySQL Server versions 5.5 and greater, but should work with earlier versions greater than 4.1. Python 2.6 and greater as well as Python 3.1 and greater are supported. Python 2.4 and 2.5 are not supported. MySQL Connector/Python 1.1.7 is available for download from http://dev.mysql.com/downloads/connector/python/#downloads The ChangeLog file included in the distribution contains a brief summary of changes in MySQL Connector/Python 1.1. For a more complete list of changes, see below or online at: http://dev.mysql.com/doc/relnotes/connector-python/en/ Enjoy! The MySQL Connectors team at Oracle = Changes in MySQL Connector/Python 1.1.7 (2014-05-13) Bugs Fixed * Commercial Debian Connector/Python packages included a copyright file containing a GPL license. (Bug #18422727) * In prepared statements, Unicode arguments in Python 2 and bytes arguments in Python 3 were causing errors, as were the symbols of character sets other than utf8 or ascii. (Bug #71482, Bug #18144971) * For Django, introspecting to get the primary key of MySQL tables could fail in Python 3. (Bug #72001, Bug #18380100) On Behalf of the MySQL RE team at Oracle, 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.2.7 has been released
was longer than 256 characters or its argument for column name was longer than 129 characters. This fix makes Connector/ODBC throw a proper error for those situations. (Bug #17358838) * A memory leak occurred in SQLProcedureColumns() when no function or procedure column satisfying the selection condition existed. (Bug #17298721) * An assertion failure occurred in SQLDescribeCol() if the column number used is larger than the number of columns in the result set. (Bug #17311065) * A segmentation fault occurred in myodbc_casecmp() when the provided query was empty. (Bug #17085344) * When using Connector/ODBC in Microsoft Access, sorting a column in the data view might crash the program. (Bug #17071780, Bug #69550) * When the connection option FLAG_NO_INFORMATION_SCHEMA was used, calling the SQLFetch function after the SQLForeignKeys function returned bad results. (Bug #16920750) * When building Connector/ODBC on some 64-bit systems other than x86_64 (e.g. ppc64), CMake did not recognize that it was a 64-bit system and incorrectly used lib instead of lib64 as directory name for installing the dynamic library. This fix implements a two-step approach, making CMake check for the system architecture by reading the value of CMAKE_SIZEOF_VOID_P and also by checking the existence of the /usr/lib64 folder. (Bug #16785424) * The function SQLForeignKeys() did not work if the connection option NO_I_S was set. (Bug #13712420, Bug #64307) Built against the MySQL server 5.6.18 client library. -- Hery Ramilison MySQL/ORACLE Release Engineering Team Oracle, the MySQL team, www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/ODBC 5.3.2 GA has been released
is thrown, and when an hour value is larger than 23. (Bug #17613161) * If the catalog name given to SQLSetConnectAttr() was too long, calling SQLConnect() or SQLDriverConnect() crashed the connection, and calling SQLGetConnectAttr() returned null for the catalog name. (Bug #17587913) * A memory leak occurred in SQLExecute() when the connection was killed by another thread. (Bug #17587617) * SQLDescribeCol() returned a memory allocation failure error when called without a resultset. This fix makes sure the proper error is returned. (Bug #17588101) * The DMG installer for Connector/ODBC failed on OS X 10.8 and 10.9. This fix corrects the wrong identification for the drive type, which caused the installation problem. (Bug #17512040, Bug #70422) * A memory leak occurred in SQLSetStmtAttr(). (Bug #17441507) * A segmentation fault occurred when SQLColumns()'s argument for table name was longer than 256 characters or its argument for column name was longer than 129 characters. This fix makes Connector/ODBC throw a proper error for those situations. (Bug #17358838) * A memory leak occurred in SQLProcedureColumns() when no function or procedure column satisfying the selection condition existed. (Bug #17298721) * An assertion failure occurred in SQLDescribeCol() if the column number used is larger than the number of columns in the result set. (Bug #17311065) * A segmentation fault occurred in myodbc_casecmp() when the provided query was empty. (Bug #17085344) * When using Connector/ODBC in Microsoft Access, sorting a column in the data view might crash the program. (Bug #17071780, Bug #69550) * When the connection option FLAG_NO_INFORMATION_SCHEMA was used, calling the SQLFetch function after the SQLForeignKeys function returned bad results. (Bug #16920750, Bug #64307) * When building Connector/ODBC on some 64-bit systems other than x86_64 (e.g. ppc64), CMake did not recognize that it was a 64-bit system and incorrectly used lib instead of lib64 as directory name for installing the dynamic library. This fix implements a two-step approach, making CMake check for the system architecture by reading the value of CMAKE_SIZEOF_VOID_P and also by checking the existence of the /usr/lib64 folder. (Bug #16785424) * The function SQLForeignKeys() did not work if the connection option NO_I_S was set. (Bug #13712420, Bug #64307) * Implemented a workaround for a control issue with GtkComboBox and GtkComboBoxEntry, in which the dialog control intercepted the keyboard signals, so that focus could be set to other controls using the keyboard. -- Hery Ramilison MySQL/ORACLE Release Engineering Team -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/C 6.1.3 has been released
of the Windows MSI package occurred in the default folder because registry search logic was hardcoded to use the 32-bit registry. (Bug #17515067) * A client crash occurred if mysql_set_server_option() or several other C API functions were called before mysql_real_connect(). (Bug #17338958) On Behalf of Oracle/MySQL RE 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 5.1.73 has been released
in grant tables are stored in lowercase, but mysql_install_db could fail to observe this convention, leading to accounts that could not be dropped with DROP USER. (Bug #62255, Bug #12917164, Bug #62254, Bug #12917151) On behalf of Oracle MySQL RE 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.1 beta has been released
Dear MySQL users, MySQL Connector/ODBC 5.3.1 beta, 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 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 since 4.1 (It will not work with 4.0 or earlier releases.) This is the second release of the MySQL ODBC driver conforming to the ODBC 3.8 specification. It contains the minimally required implementation of the standard with key 3.8 features, which include self-identification as a ODBC 3.8 driver, streaming of output parameters (supported for binary types only), support of the SQL_ATTR_RESET_CONNECTION connection attribute (for the Unicode driver only). Also Connector/ODBC 5.3 introduces a GTK+-based setup library providing GUI DSN setup dialog on some Unix based systems, currently included in the Oracle Linux 6 and Debian 6 binary packages. Other new features in the 5.3 driver are FileDSN and Bookmarks support. Keep in mind that this is a beta release, and as with any other pre-production release, caution should be taken when installing on production level systems or systems with critical data. Not all of the features planned for the final Connector/ODBC 5.3 release are implemented. 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/refman/5.6/en/connector-odbc-installation.html Enjoy! The MySQL Connectors team at Oracle - Changes in MySQL Connector/ODBC 5.3.1 (2013-11-27) Functionality Added or Changed * Implemented the SQL_ATTR_RESET_CONNECTION connection attribute, newly introduced in ODBC 3.8. See the ODBC specifications for details. Currently, the connection attribute is supported by the Unicode driver, but not the ANSI driver. Bugs Fixed * Calling SQLBulkOperations() without setting SQLSetStmtAttr resulted in a segmentation fault. (Bug #17714290) * A memory leak occurred when using Connector/ODBC to update the contents of a row. (Bug #17653461, Bug #70662) * A bad memory access occurred in the ssps_get_out_params function in my_prepared_stmt.c, when a call was made to a stored procedure with any IN parameters coming after the last OUT or INOUT parameter. (Bug #17640929, Bug #70642) * A memory leak occurred in SQLConnect() when it was invoked after a call of SQLSetConnectAttr() that used the parameter SQL_ATTR_CURRENT_CATALOG. (Bug #17586844) * A memory leak occurred in SQLSetStmtAttr(), because statement deallocation was missing. (Bug #17441507) * A segmentation fault occurred when SQLColumns()'s table argument is longer than 256 characters, or its column argument is longer than 129 characters. This fix makes Connector/ODBC return a proper error for the situation. (Bug #17358838) * A memory leak occurred in SQLProcedureColumns() when no function or procedure column satisfying the selection condition existed. (Bug #17298721) * An assertion failure occurred in SQLDescribeCol() if the column number used is larger than the number of columns in the result set. (Bug #17311065) * The function SQLPutData() gave an error when handling a Unicode string that had SQL_NTS given as its string length. (Bug #14810497, Bug #66943) * From Connector/ODBC version 5.2.2 onwards, the function SQLForeignKeys() did not work if the connection option NO_INFORMATION_SCHEMA was set. (Bug #13712420, Bug #64307) -- Hery Ramilison MySQL/ORACLE Release Engineering Team -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.1.72 has been released
Dear MySQL users, MySQL Server 5.1.72, a new version of the popular Open Source Database Management System, has been released. MySQL 5.1.72 is recommended for use on production systems. For an overview of what's new in MySQL 5.1, please see http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html For information on installing MySQL 5.1.72 on new servers or upgrading to MySQL 5.1.72 from previous MySQL releases, please see http://dev.mysql.com/doc/refman/5.1/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. The following section lists the changes in the MySQL source code since the previous released version of MySQL 5.1. It may also be viewed online at http://dev.mysql.com/doc/relnotes/mysql/5.1/en/news-5-1-72.html Enjoy! Changes in MySQL 5.1.72 (September 20, 2013) Bugs Fixed * InnoDB: The row_sel_sec_rec_is_for_clust_rec function would incorrectly prepare to compare a NULL column prefix in a secondary index with a non-NULL column in a clustered index. (Bug #17312846) * InnoDB: An incorrect purge would occur when rolling back an update to a delete-marked record. (Bug #17302896) * InnoDB: InnoDB would rename a user-defined foreign key constraint containing the string _ibfk_ in its name, resulting in a duplicate constraint. (Bug #17076737, Bug #69693, Bug #17076718, Bug #69707) * InnoDB: Rolling back an INSERT after a failed BLOB write would result in an assertion failure. The assertion has been modified to allow NULL BLOB pointers if an error occurs during a BLOB write. (Bug #16971045) * InnoDB: The srv_master_thread background thread, which monitors server activity and performs activities such as page flushing when the server is inactive or in a shutdown state, runs on a one second delay loop. srv_master_thread would fail to check if the server is in a shutdown state before sleeping. (Bug #13417564, Bug #63276) * InnoDB: An infinite loop could occur in buf_page_get_gen when handling compressed-only pages. (Bug #12560151, Bug #61132) * Within a stored program, comparison of the value of a scalar subquery with an IN clause resulted in an error for the first execution and raised an assertion for the second execution. (Bug #17029399) * The my_strtoll10() function could incorrectly convert some long string-format numbers to numeric values and fail to set the overflow flag. (Bug #16997513) * For queries that accessed an INFORMATION_SCHEMA table in a subquery, and attempt to lock a mutex that had already been locked could cause a server crash. (Bug #11765744) * For DIV expressions, assignment of the result to multiple variables could cause a server crash. (Bug #59241, Bug #11766191) References: See also Bug #8457. * mysqldump wrote SET statements as SET OPTION, which failed when reloaded because the deprecated OPTION keyword has been removed from SET syntax. (Bug #67507, Bug #15844882) * If one connection changed its default database and simultaneously another connection executed SHOW PROCESSLIST, the second connection could access invalid memory when attempting to display the first connection's default database. memory. (Bug #58198, Bug #11765252) On behalf of Oracle MySQL RE 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 5.6.12 has been released
were too short to hold some of the URLs in the help content. These columns are now created as type TEXT to accommodate longer URLs. (Bug #61520, Bug #12671635) * mysqld --help and mysqld --verbose --help performed unnecessary logging. (Bug #68578, Bug #16442113) * InnoDB does not support full-text parser plugins, but failed to report an error if they were specified. Now an ER_INNODB_NO_FT_USES_PARSER error is returned. (Bug #62004, Bug #12843070) * If Loose Index Scan was used to evaluate a query that compared an integer column to an integer specified as a quoted string (for example, col_name = '1'), the query could return incorrect results. (Bug #68473, Bug #16394084) * IF() function evaluations could produce different results when executed in a prepared versus nonprepared statement. (Bug #45370, Bug #11753852) * If a function such as AES_DECRYPT() that requires SSL support failed, the error could affect later calls to functions that require SSL support. (Bug #68340, Bug #16315767) * In a MySQL server newer than MySQL 5.5 using a nonupgraded mysql.user table (for which mysql_upgrade had not been run), statements to set passwords caused a server exit due to a faulty check for the password_expired column. (Bug #68385, Bug #16339767) * It is now possible to suppress installation of the mysql-test directory after compiling MySQL from source by invoking CMake with the INSTALL_MYSQLTESTDIR option explicitly set to empty: cmake . -DINSTALL_MYSQLTESTDIR= Previously, attempts to do this resulted in an error. (Bug #58615, Bug #11765629) * When only counting events but not timing them, Performance Schema would report MIN_TIMER_WAIT values as a large number instead of 0. (Bug #68768, Bug #16552425) * Using range access with an index prefix could produce incorrect results. (Bug #68750, Bug #16540042) * For debug builds, metadata locking for CREATE TABLE ... SELECT could raise an assertion. (Bug #68695, Bug #16503173) * A new CMake option, WITH_EDITLINE, is provided to indicate whether to use the bundled or system libedit/editline library. The permitted values are bundled (the default) and system. WITH_EDITLINE replaces WITH_LIBEDIT, which has been removed. (Bug #68558, Bug #16430208) * When specified in an option file, the plugin-dir client option was ignored. (Bug #68800, Bug #16680313) * Indexes on derived tables that were used during the first invocation of a stored procedure were not used in subsequent invocations. (Bug #68350, Bug #16346367) * For DELETE and UPDATE statements, EXPLAIN displayed NULL in the ref column for some cases where const is more appropriate. (Bug #68299, Bug #16296268) * The optimizer could choose a poor execution plan for queries with ORDER BY ... LIMIT. (Bug #69013, Bug #16697792) On Behalf of Oracle MySQL/ORACLE RE Team Hery Ramilison Oracle/MySQL Release Engineer -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.1.68 has been released
component in MySQL 5.5, 5.6, and higher. Since InnoDB and MySQL Server development cycles are fully integrated and synchronized, now the value returned by the innodb_version variable is the same as for the version variable. (Bug #13463493, Bug #63435) * Partitioning: When used with a table having multiple columns in its primary key, but partitioned by KEY using a column that was not part of the primary key as the partitioning column, a query using an aggregate function and DISTINCT such as SELECT SUM(DISTINCT pk_column_1) FROM table WHERE pk_column_2 = constant was not handled correctly. (Bug #14845133) References: See also Bug #14495351. This bug was introduced by Bug #13025132. * Replication: Repeated execution of CHANGE MASTER TO statements using invalid MASTER_LOG_POS values could lead to errors and possibly a crash on the slave. Now in such cases, the statement fails with a clear error message. (Bug #11764602, Bug #57454) * Replication: If the disk becomes full while writing to the binary log, the server hangs until space is freed up manually. It was possible after was done for the MySQL server to fail, due to an internal status value being set when not needed. Now in such cases, rather than trying to set this status, a warning is written in the error log instead. (Bug #11753923, Bug #45449) * Microsoft Windows: Dynamic file names (with colons) are no longer allowed. Static file names using the Alternate Data Stream (ADS) NTFS functionality of Microsoft Windows may continue to be used. (Bug #11761752) * It was possible in theory for UpdateXML() to return NULL incorrectly. (Bug #15948580) References: See also Bug #13007062. * For MEMORY tables with HASH indexes, DELETE sometimes failed to delete all applicable rows. (Bug #51763, Bug #11759445) Thanks, On behalf of the MySQL/ORACLE Build Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/Python 1.0.8 has been released
Dear MySQL users, MySQL Connector/Python v1.0.8 is a new version of the 1.0 production release of the pure Python database driver for MySQL. MySQL Connector/Python version 1.0 is compatible with MySQL Server versions 5.5 and greater, but should work with earlier versions (greater than v4.1). Python v2.6 and greater as well as Python v3.1 and greater are supported. Python v2.4 and v2.5 are known to work, but are not officially supported. MySQL Connector/Python v1.0.8 is available for download from http://dev.mysql.com/downloads/connector/python/#downloads A brief summary of changes in MySQL Connector/Python v1.0 is listed below. Please check the ChangeLog file inside the distribution for a more complete list of changes or online at: http://dev.mysql.com/doc/relnotes/connector-python/en/ Changes in MySQL Connector/Python v1.0.8 Bug Fixes: * Fixed MySQLConnection.ping() so it only reconnects when the reconnect argument is set to True. (Bug #15915243, Bug #67650) * Fixed storing multiple results after calling stored procedures which are using arguments. (Bug #15916486, Bug #67710) * Fixed handling MySQL errors when doing handshake. (Bug #15836979) * Fixed support for connecting to MySQL using IPv6 addresses. (Bug #15876886, Bug #15927825) * Fixed reading the header of MySQL packets. Previously, we were reading the MySQL packet headers as 4 (or 7) bytes long buffers from the socket. When we did have the correct length, we would immediately raise an exception. We now keep reading data from the socket until we got the full header or bail out on errors. (Bug #14829471, Bug #67303) * Fixed the error message when the TCP/IP port number is not a valid integer. Strings are first converted to integer and raise an error with a proper error when this fails. (Bug #13808727, Bug #64543) * Fixed authenticating for Python v2 using usernames and/or passwords which contain Unicode characters using Python v2. (Bug #14843456, Bug #67306) * Fixed reporting of socket errors. (Bug #14802017) * Fixed executemany() to support the pyformat parameter style. (Bug #14754894, Bug #67146). The regular expression parsing the INSERT statement did not work when pyformat markers where used, that is, '%(c1)s' for example. This is now fixed so both ANSI C printf and Python extended format codes can be used by MySQLCursor.executemany(). Documentation - Online: http://dev.mysql.com/doc/connector-python/en/index.html The source distribution includes the manual in various formats under the docs/ folder. Reporting Bugs -- We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ Enjoy! On Behalf of the MySQL build team at Oracle Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.5.29 has been released
this was a remote possibility). (Bug #14621627) * Within a stored program, memory allocated to hold condition information was not released until program exit, leading to excessive memory use. (Bug #14640599) * Improper memory cleanup could cause the server to exit. (Bug #14536113) * Granting or revoking the PROXY privilege caused the server to exit if the server was started with --skip-name-resolve. (Bug #14211140) * CREATE USER and DROP USER could fail to flush the privileges, requiring FLUSH PRIVILEGES to be used explicitly. (Bug #13864642) * Access to INFORMATION_SCHEMA tables through a view could leak memory. (Bug #13734987) * A memory leak could occur for queries containing a subquery that used GROUP BY on an outer column. (Bug #13724099) * On Microsoft Windows with CMake 2.6, the build process would not stop if the create_initial_db step failed. (Bug #13713525) * The test in mysqld_safe for the presence of the --plugin_dir option and assignment of a default value to it were performed before the actual argument parsing took place. (Bug #13548161) * CHECK TABLE and REPAIR TABLE could crash if a MyISAM table had a corrupt key (.MYI) file. Now the server produces an error. (Bug #13556441) * Improper memory cleanup could cause the server to exit. (Bug #13340270) * A memory leak occurred due to failure to clean up after QUICK_INDEX_MERGE_SELECT/Unique. (Bug #12694872, Bug #14542543) * The number of connection errors from a given host as counted by the server was periodically reset, with the result that max_connect_errors was never reached and invalid hosts were never blocked from trying to connect. (Bug #11753779) References: See also Bug #38247, Bug #43006, Bug #45584, Bug #45606. * During optimization, ZEROFILL values may be converted to string constants. However, CASE expressions did not handle switching data types after the planning stage, leading to CASE finding a null pointer instead of its argument. (Bug #57135, Bug #11764313) * In debug builds, an InnoDB assertion was overly aggressive about prohibiting an open range. (Bug #66513, Bug #14547952) * On Windows, the Perl version of mysql_install_db created system tables in the mysql database that were not populated properly. (Bug #65584, Bug #14181049) * mysqld_safe ignored the value of the UMASK environment variable, leading to behavior different from mysqld with respect to the access mode of created files. Now mysqld_safe (and mysqld_multi) attempt to approximate the same behavior as mysqld. (Bug #57406, Bug #11764559) * LAST_INSERT_ID(expr) did not work for expr values greater than the largest signed BIGINT value. (Bug #20964, Bug #11745891) On behalf of the MySQL/ORACLE Build Team Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
