MySQL Connector/Node.js 8.0.16 has been released
#29436892) * Executing client.close() would not close all associated connections in the connection pool. (Bug #29428477) * connectTimeout instead of maxIdleTime determined whether idle connections in the connection pool were reused rather than creating new connections. (Bug #29427271) * Released connections from the connection pool were not being reset and reused; instead new connections were being made. (Bug #29392088) * Date values in documents were converted to empty objects when inserted into a collection. (Bug #29179767, Bug #93839) * A queueTimeout value other than 0 (infinite) prevented the acquisition of old released connections from the connection pool. (Bug #29179372, Bug #93841) On Behalf of MySQL/ORACLE RE Team Gipson Pulla -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.6.44 has been released
Dear MySQL users, MySQL Server 5.6.44, a new version of the popular Open Source Database Management System, has been released. MySQL 5.6.44 is recommended for use on production systems. For an overview of what's new in MySQL 5.6, please see http://dev.mysql.com/doc/refman/5.6/en/mysql-nutshell.html Starting with 5.6.11, Microsoft Windows packages for MySQL 5.6 are available both as a "full" installer and as a "web" installer. The full installer is significantly larger and comes bundled with the latest software releases available. This bundle makes it easy to download and configure a full server and development suite. The web installer doesn't come bundled with any actual products and instead relies on download-on-demand to fetch only the products you choose to install. This makes the initial download much smaller but increases install time as the individual products will need to be downloaded. For information on installing MySQL 5.6.44 on new servers or upgrading to MySQL 5.6.44 from previous MySQL releases, please see http://dev.mysql.com/doc/refman/5.6/en/installing.html MySQL Server 5.6.44, is available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/mysql We welcome and appreciate your feedback, bug reports, bug fixes, patches, etc: http://bugs.mysql.com/report.php The following link lists the changes in the MySQL 5.6 since the release of MySQL 5.6.43. It may also be viewed online at http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-44.html Enjoy! Changes in MySQL 5.6.44 (2019-04-25, General Availability) Beginning with MySQL 5.6.44, Oracle no longer provides binaries for SUSE 11. Security Notes * The linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.2r. Issues fixed in the new OpenSSL version are described at http://www.openssl.org/news/vulnerabilities.html. This change does not affect the Oracle-produced MySQL Community build of MySQL Server, which uses the yaSSL library instead. (Bug #28988091) Bugs Fixed * Important Note: The libevent library included with the MySQL Server was upgraded to version 2.1.8. (Bug #28207237, Bug #29041505, Bug #29055011) * InnoDB: The INDEX_LENGTH value in INFORMATION_SCHEMA.TABLES was not updated when adding an index. (Bug #19811005) * Partitioning: An AUTO_INCREMENT key added to a partitioned table by an ALTER TABLE statement using ALGORITHM=INPLACE restarted on each partition. (Bug #92241, Bug #28573894) * Replication: If an applier thread was stopped while it was in the process of opening a table, no error was set, which could result in a segmentation fault or assertion depending on the build type. Error handling is now correctly activated in this situation. (Bug #28864557) * Replication: If a storage engine has the capability to log in STATEMENT format but not in ROW format, when binlog_format is set to STATEMENT, an unsafe SQL statement should be logged and a warning message should be written to the error log. However, such statements were instead not executed and an error message was written to the error log, which is the correct behavior when binlog_format is set to MIXED or ROW. The issue has now been corrected so that unsafe statements are logged with a warning as expected when binlog_format is set to STATEMENT. (Bug #28429993, Bug #73936) * Microsoft Windows: Validity testing for the named_pipe_full_access_group system variable did not account for NULL values. (Bug #29256690) * MySQL 5.6 did not build with maintainer mode enabled with GCC 7. (Bug #29048768) * A damaged mysql.user table could cause a server exit. (Bug #28986737) * mysqladmin shutdown did not wait for mysqld to shut down. (Bug #28466137, Bug #91803) References: This issue is a regression of: Bug #25364806. * Some status variable values could temporarily increase before returning to their original value. (Bug #27839644, Bug #90351) * The binary file for the udf_example user-defined function was omitted from binary distributions. (Bug #26115002, Bug #29178542) * Compiling the InnoDB memcached plugin did not work on some platforms where MySQL was configured using -DWITH_LIBEVENT=system, for libevent version 2.0 or higher. (Bug #80073, Bug #22573379, Bug #23567441) On Behalf of MySQL/ORACLE RE Team Gipson Pulla -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/J 8.0.15 has been released
Dear MySQL users, MySQL Connector/J Version 8.0.15 is the GA release of the 8.0 branch of MySQL Connector/J. It is suitable for use with MySQL Server versions 8.0, 5.7, 5.6, and 5.5. It supports the Java Database Connectivity (JDBC) 4.2 API, and implements the X DevAPI. This release includes the following new features and changes, also described in more detail on https://dev.mysql.com/doc/relnotes/connector-j/8.0/en/news-8-0-15.html As always, we recommend that you check the "CHANGES" file in the download archive to be aware of changes in behavior that might affect your application. To download MySQL Connector/J 8.0.15 GA, see the "Generally Available (GA) Releases" tab at http://dev.mysql.com/downloads/connector/j/ Enjoy! Changes in MySQL Connector/J 8.0.15 (2019-02-01, General Availability) Functionality Added or Changed * Default value of the connection property allowLoadLocalInfile has been changed to false. Applications that use the LOAD DATA LOCAL INFILE (http://dev.mysql.com/doc/refman/8.0/en/load-data.html) statement on MySQL Server needs to set this property to true explicitly. (Bug #29261254) Enjoy and thanks for the support! On Behalf of MySQL/ORACLE RE Team Gipson Pulla -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.6.43 has been released
uninitialized memory read errors. The comparison now uses the strncmp() function. Thanks to Zsolt Parragi and Laurynas Biveinis for their contributions. (Bug #28178776, Bug #90238) * The transformation of IN subquery predicates into semijoins was not handled correctly for a very large number of tables. (Bug #28004674) * Executing a prepared statement to do a multiple-row insert with large number of placeholders consumed excessive memory and could execute slowly. (Bug #27703912) * The parser accepted invalid SET statement syntax in trigger definitions that could result in a server exit. (Bug #27595603) * MyISAM index corruption could occur for bulk-insert and table-repair operations that involve the repair-by-sorting algorithm and many (more than 450 million) rows. (Bug #26929724, Bug #88003, Bug #28483283) * When a subquery contained a UNION, the count of the number of subquery columns was calculated incorrectly. (Bug #24899924) * A query employing a dynamic range and an index merge could use more memory than expected. (Bug #89953, Bug #27659490) On Behalf of MySQL/ORACLE RE Team Gipson Pulla -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.7.24 has been released
le uses a table scan. (Bug #28145710, Bug #91080) * 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) * The WITH_GMOCK CMake option did not handle Windows path names properly. (Bug #28061409, Bug #90964) * Group lookups for LDAP authentication plugins could fail if the user had insufficient privileges. Now, group search operations bind again using root credentials if those are available. (Bug #28016008) * Generated columns having indexes and that used a string function were not always populated correctly. (Bug #27973409) * Stored program definitions in mysqldump dump files sometimes included the NO_AUTO_CREATE_USER SQL mode. Because that mode has been removed in MySQL 8.0, loading such a dump file into a MySQL 8.0 server failed. mysqldump now removes NO_AUTO_CREATE_USER from the definition of dumped stored programs. (Bug #27931181, Bug #90624) * Very long table keys were handled incorrectly on replication slaves. (Bug #27930505) * During server startup/shutdown, PID files could be mishandled. (Bug #27919254) * If flushing the error log failed due to a file permission error, the flush operation did not complete. (Bug #27891472, Bug #90505) References: This issue is a regression of: Bug #26447825. * 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) * The severity of messages produced by the server about being unable to read key files has been escalated from INFORMATION to WARNING. (Bug #27737195) * Failure to create a temporary table during a MyISAM query could cause a server exit. Thanks to Facebook for the patch. (Bug #27724519, Bug #90145) * parser_max_mem_size was ineffective when parsing stored program definitions. (Bug #27714748) * Host name resolution errors could cause the audit_log plugin to fail. (Bug #27567003) * Unsuccessful connection attempts were not being written to the error log when log_error_verbosity=3. (Bug #27539838) * An earlier code cleanup caused FEDERATED storage engine failures. (Bug #27493633, Bug #89537) References: This issue is a regression of: Bug #25943754. * An attempted read of an uncommitted transaction raised an assertion. (Bug #26876608) * 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) * The audit_log plugin could deadlock the server. (Bug #24353553) * Debug symbol packages are now included for all apt platforms (previously, they were only available on Debian9). (Bug #24008883, Bug #27990381) * Specifying the maximum possible value for a YEAR column failed when expressed as a real constant such as 2155.0E00 or 2.15E3. (Bug #91226, Bug #28172538) * It was possible for a subquery that used a unique key on a column allowing NULL to return multiple rows. (Bug #88670, Bug #27182010) On Behalf of MySQL/ORACLE RE Team Gipson Pulla -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.7.23 has been released
d. (Bug #26643180, Bug #87455) References: This issue is a regression of: Bug #82848, Bug #24590891. * The slave_rows_search_algorithms system variable controls how rows are searched for matches when preparing batches of rows for row-based logging and replication. Specifying INDEX_SCAN as one of the search algorithms performs an index scan if an index is present. In the situation where a different primary key is used on the master and the slave, and a unique key is present on the slave, a bug in the code meant that the index scan was not being performed as it should be, and a slower table scan was being performed instead. The issue has now been corrected so that an index scan is used. (Bug #26450129, Bug #81500) * Certain cases of subquery materialization could cause a server exit. These queries now produce an error suggesting that materialization be disabled. (Bug #26402045) * 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) * The SHOW CREATE USER statement requires the SELECT privilege for the mysql database, except to see information for the current user. In addition, for the current user, the statement requires the SELECT privilege for the mysql.user system table for display of the password hash in the IDENTIFIED AS clause; otherwise, the hash displays as . (Bug #2497) * CREATE FUNCTION produced an error if there was no default database and the function body called another function. (Bug #24357244, Bug #82350) * For debug builds, a SELECT statement executed within a stored program could raise an assertion if derived table resolution failed. (Bug #23221336) * If mysqldump or mysqlpump were used to dump binary data without the --hex-blob option, reloading the dump file could produce spurious warnings (values were inserted correctly regardless of the warnings). Such values are now written preceded by the _binary introducer to silence the warnings. (Bug #22601255, Bug #80150) On Behalf of MySQL/ORACLE RE Team Gipson Pulla -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/C++ 8.0.11 GA has been released
Dear MySQL users, MySQL Connector/C++ 8.0.11 is the first GA release version of the MySQL Connector/C++ 8.0 series. Connector/C++ 8.0 can be used to access MySQL implementing Document Store or in a traditional way, using SQL queries. It allows writing both C++ applications using X DevAPI or plain C applications using XAPI. To learn more about how to write applications using X DevAPI, see "X DevAPI User Guide" https://dev.mysql.com/doc/x-devapi-userguide/en/ and "X DevAPI Reference" at https://dev.mysql.com/doc/dev/connector-cpp/devapi_ref.html For more information about using plain C XAPI see "XAPI Reference" at https://dev.mysql.com/doc/dev/connector-cpp/xapi_ref.html For generic information on using Connector/C++ 8.0, see https://dev.mysql.com/doc/dev/connector-cpp/ Note For X DevAPI or XAPI applications, Connector/C++ 8.0 requires MySQL Server 5.7.12 or higher with X Plugin enabled. For applications that use the legacy JDBC API, Connector/C++ 8.0 can use MySQL Server 5.5 or higher, and X Plugin is not required. https://dev.mysql.com/doc/refman/5.7/en/document-store.html To download MySQL Connector/C++ 8.0.11, see the "Generally Available(GA) Releases" tab at https://dev.mysql.com/downloads/connector/cpp/ Changes in MySQL Connector/C++ 8.0.11 (2018-04-19, General Availability) For MySQL Connector/C++ 8.0.11 and higher, Commercial and Community distributions require the Visual C++ Redistributable for Visual Studio 2015 to work on Windows platforms. The Redistributable is available at the Microsoft Download Center (http://www.microsoft.com/en-us/download/default.aspx); install it before installing Connector/C++. Functionality Added or Changed * Incompatible Change: When documents without an _id attribute are added to a collection, the server now automatically generates IDs for them. The server determines the ID format, which should be considered opaque from the API perspective (they are no longer UUID-based). As before, no _id attribute is generated if a document already contains one. User-provided document IDs must not conflict with IDs of other documents in the collection. This capability requires a MySQL 8.0 GA server. If the server does not support document ID generation, the document-add operation returns an error indicating that document IDs were missing. For X DevAPI, the generated IDs resulting from a document-add operation can be obtained using the new Result.getGeneratedIds() method, which returns a list. For XAPI, the generated IDs can be obtained using the new mysqlx_fetch_generated_id() function, which returns IDs one by one for successive calls, until it returns NULL to indicate no more generated IDs are available. For both X DevAPI and XAPI, document IDs specified explicitly in added documents are not returned. Incompatibility: The getGeneratedIds() method replaces getDocumentId() and getDocumentIds(), which are now removed. The mysqlx_fetch_generated_id() function replaces mysqlx_fetch_doc_id(), which is now removed. * A patch operation has been implemented that enables specifying a JSON-like object that describes the changes to apply to documents in a collection. For X DevAPI, the CollectionModify operation supports a new patch() clause for patching documents. For XAPI, there are two new functions: mysqlx_collection_modify_patch() directly executes patching on documents in a collection that satisfy given criteria. mysqlx_set_modify_patch() adds a patch operation to a modify statement created with the mysql_collection_modify_new() function. * For connections to the server made using the legacy JDBC API (that is, not made using X DevAPI or XAPI), Connector/C++ 8.0 now supports an OPT_GET_SERVER_PUBLIC_KEY connection option that enables requesting the RSA public key from the server. For accounts that use the caching_sha2_password or sha256_password authentication plugin, this key can be used during the connection process for RSA key-pair based password exchange with TLS disabled. This capability requires a MySQL 8.0 GA server, and is supported only for Connector/C++ built using OpenSSL. Bugs Fixed * Single-document methods such as Collection.replaceOne() did not accept expr() as the document specification, but instead treated it as a plain JSON string. (Bug #27677910) * Compiling X DevAPI and XAPI test programs failed with an error. (Bug #27610760) * Connecting with an incorrect SSL_CA value could result in a memory leak. (Bug #27434254) * For debug builds, specifying a document as _id raised an assertion rather than producing an error.
MySQL Community Server 5.6.40 has been released
Dear MySQL users, MySQL Server 5.6.40, a new version of the popular Open Source Database Management System, has been released. MySQL 5.6.40 is recommended for use on production systems. For an overview of what's new in MySQL 5.6, please see http://dev.mysql.com/doc/refman/5.6/en/mysql-nutshell.html Starting with 5.6.11, Microsoft Windows packages for MySQL 5.6 are available both as a "full" installer and as a "web" installer. The full installer is significantly larger and comes bundled with the latest software releases available. This bundle makes it easy to download and configure a full server and development suite. The web installer doesn't come bundled with any actual products and instead relies on download-on-demand to fetch only the products you choose to install. This makes the initial download much smaller but increases install time as the individual products will need to be downloaded. For information on installing MySQL 5.6.40 on new servers or upgrading to MySQL 5.6.40 from previous MySQL releases, please see http://dev.mysql.com/doc/refman/5.6/en/installing.html MySQL Server is available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/ Not all mirror sites may be up to date at this point in time, so if you can't find this version on some mirror, please try again later or choose another download site. We welcome and appreciate your feedback, bug reports, bug fixes, patches, etc: https://wikis.oracle.com/display/mysql/Contributing The following link lists the changes in the MySQL 5.6 since the release of MySQL 5.6.39. It may also be viewed online at http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-40.html Enjoy! Changes in MySQL 5.6.40 (2018-04-19, General Availability) Functionality Added or Changed * If the server PID file is configured to be created in a world-writable location, the server now issues a warning suggesting use of a more secure location. (Bug #26585560) Bugs Fixed * NDB Cluster: MySQL NDB Cluster encountered race conditions compiling lex_hash.h. (Bug #24931655, Bug #83477, Bug #27470071, Bug #89482) * InnoDB: A REPLACE operation on a temporary table raised an assertion. (Bug #27225649) * InnoDB: A tablespace import operation on a server with a default row format of REDUNDANT raised an assertion failure. (Bug #26960215) * InnoDB: Evaluation of a subquery in a resolving function raised an assertion. (Bug #26909960) * InnoDB: An online DDL operation that rebuilds the table raised an assertion when the last insert log record to be applied was split across two pages. (Bug #26696448, Bug #87532) * InnoDB: A RENAME TABLE operation that renamed the schema failed to rename full-text search common auxiliary tables that were left behind when the full-text search index was removed previously, resulting in a assertion failure when attempting to drop the old schema. (Bug #26334149) * Replication: A number of changes were made to the binary log decoding procedure to improve handling of invalid or corrupted binary log entries. (Bug #24365972) * An invalid input polygon for spatial functions could lead to undefined server behavior. Now the server returns NULL. (Bug #27230859, Bug #88801) * Adding a unique index to an InnoDB table on which multiple locks were held could raise an assertion. (Bug #27216817) * For some statements, the FILE privilege was not properly checked. (Bug #27160888) * ST_Touches() could fail due to a missing null pointer check. (Bug #27081349) * A multiple-insert statement on a table containing a FULLTEXT key and a FTS_DOC_ID column caused a server error. (Bug #27041445, Bug #88267) References: This issue is a regression of: Bug #22679185. * An ALTER TABLE operation attempted to set the AUTO_INCREMENT value for table in a discarded tablespace. (Bug #26935001) * Dropping an index from a system table could cause a server exit. (Bug #26881798) * A server exit could result from simultaneous attempts by multiple threads to register and deregister metadata Performance Schema objects. (Bug #26502135) * The thread pool plugin logged too much information for failed connections. (Bug #26368725, Bug #86863) * For debug builds, using KILL to terminate a stored routine could raise an assertion. Thanks to Laurynas Biveinis for the patch. (Bug #26040870, Bug #86260) * 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
MySQL Connector/Net 8.0.10-rc has been released
e=required). Caching SHA-2 pluggable authentication offers faster authentication than basic SHA-256 authentication. A new and related connection option, AllowPublicKeyRetrieval, was also added. * X DevAPI: The MySqlX.XDevAPI.Collection.CreateIndex method implementation was modified to enable the inclusion of a JSON document that defines the index to be created. Index-definition details can include the fields affected, data types, and so on. Bugs Fixed * X DevAPI: When the PLAIN authentication option was used to make a secure connection, the database name was excluded from the authenticating data and the database value was not set. PLAIN authentication is the default option for connections made with TLS or Unix Sockets. (Bug #27098974, Bug #88427) * Boolean values within a JSON document were improperly stored as strings. (Bug #26837112) * Invoking the MySql.Web.Security.MySqlWebSecurity.CreateUserAndAccount method with valid arguments, including additionalUserAttributes as an object with key/value pairs, returned an out-of-range exception. Thanks to Stein Setvik for contributing to the fix. (Bug #25046364) * The default character set and encoding were not set properly when making a connection to MySQL 5.6 and 5.7 servers configured to use the utf8 character set. (Bug #23257011) * SSL connections made to a single MySQL instance could not be disconnected and created repeatedly without restarting the client application to clear the half-open sockets. (Bug #20393654, Bug #75022) Nuget packages are available at: https://www.nuget.org/packages/MySql.Data/8.0.10-rc https://www.nuget.org/packages/MySql.Web/8.0.10-rc https://www.nuget.org/packages/MySql.Data.EntityFramework/8.0.10-rc https://www.nuget.org/packages/MySql.Data.EntityFrameworkCore/8.0.10-rc https://www.nuget.org/packages/MySql.Data.EntityFrameworkCore.Design/8.0.10-rc Enjoy and thanks for the support! On Behalf of the MySQL/ORACLE RE Team Gipson Pulla -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.6.39 has been released
nce assessment. (Bug #22305994, Bug #26734457) * VALUES() was not handled correctly in some cases. (Bug #26881946) References: See also: Bug #19601973, Bug #17458914. * The Performance Schema now stores rewritten rather than raw SQL statement text when available. (Bug #26732229) * Incorrect results or a server exit could result when SHA2() was passed a user-defined variable in some character sets. (Bug #26704451) * Creating a table with excessive index information could cause a server exit. (Bug #26529369) * Some statements could cause a buffer overflow in the digest code. Thanks to Laurynas Biveinis and Roel van de Paar for the patch. (Bug #26021187) * Incorrect results could occur on a table with a unique index when the optimizer 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. * 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) * 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) * Setting the MYSQL_GROUP_SUFFIX environment variable had no effect. (Bug #23072792) * A circular dependency problem involving sql/sql_builtin.cc was resolved. (Bug #16877045) * A prepared statement containing an ORDER BY list that referred to a parameter was not always handled correctly. (Bug #87863, Bug #26867652) * REFERENCES privilege checking could use the incorrect database in some cases. (Bug #26106655) On Behalf of MySQL/ORACLE RE Team Gipson Pulla -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/Net 6.9.10 has been released
Dear MySQL users, MySQL Connector/Net 6.9.10 is a maintenance 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.10 (2017-10-23, General Availability) Bugs Fixed * Executing MySql.Web.Security.CreateUserAndAccount with valid arguments returned an out-of-range exception. Thanks to Stein Setvik for contributing to the fix. (Bug #25046364) * The default character set and encoding were not set properly when making a connection to MySQL 5.6 and 5.7 servers configured to use the utf8 character set. (Bug #23257011) 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.9.10 https://www.nuget.org/packages/MySql.Data.Entity/6.9.10 https://www.nuget.org/packages/MySql.Fabric/6.9.10 https://www.nuget.org/packages/MySql.Web/6.9.10 Enjoy and thanks for the support! On behalf of the MySQL Connector/NET and the MySQL/ORACLE RE Team Gipson Pulla -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.6.38 has been released
111). (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) * 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) * NAME_CONST() can return null if incorrect arguments are given. In some cases, this was not handled and could cause a server exit. (Bug #19143243, Bug #26361149) On Behalf of MySQL/ORACLE RE Team Gipson Pulla -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/Python 2.1.7 GA has been released
Dear MySQL users,
MySQL Connector/Python 2.1.7 GA is a fifth 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.7 GA is compatible with MySQL Server
versions 5.5 and greater. Python 2.6 and greater as well as Python 3.4
and greater are supported. Python 2.4, 2.5, and 3.1, 3.2, 3.3 are not
supported.
MySQL Connector/Python 2.1.7 is available for download from:
http://dev.mysql.com/downloads/connector/python/#downloads
MySQL Connector/Python 2.1.7 (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 ChangeLog file included in the distribution contains a brief summary
of changes in MySQL Connector/Python 2.1.7. 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.7 (2017-08-18, General Availability)
* Functionality Added or Changed
* Bugs Fixed
Functionality Added or Changed
* Connector/Python is now compatible with Django 1.11.
Thanks to Brian Tyndall for the patch for some of the
work. (Bug #25965922, Bug #86105, Bug #26257499, Bug
#86652)
* Connector/Python now attempts to connect using TLS by
default if the server supports secure connections. (Bug
#21947091)
Bugs Fixed
* Prepared statements did not work with a MySQL 8.0 server.
(Bug #26376334)
* With a connection character set of utf8mb4, multiple-row
insert operations failed with an error of LookupError:
unknown encoding: utf8mb4. (Bug #24659561, Bug #82948)
* Creating a Connection instance with use_pure=True could
lead to the underlying socket not being closed if the
user name or password were invalid. Thanks to Vilnis
Termanis for the patch. (Bug #24342757, Bug #82324)
* For cursors created with named_tuple=True,
MySQLCursorNamedTuple objects could leak memory. Thanks
to Piotr Jurkiewicz for the patch on which this fix was
based. (Bug #22880163, Bug #80621)
* The C Extension leaked memory if used to execute INSERT
statements that inserted Unicode strings. (Bug #22825962,
Bug #79887)
* The escape_string() method leaked memory. (Bug #22810810,
Bug #79903)
* With Python 2.x, for a call to encode('utf8') on a
bytestring that was serialized from unicode, Python
attempted to decode the string using the 'ascii' codec
and encode it back using 'utf8'. The result was encoding
failure for bytestrings that contain non-ASCII
characters. (Bug #22564149, Bug #79993)
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/
On Behalf of the MySQL/ORACLE RE Team,
Gipson Pulla
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.5.57 has been released
Dear MySQL users, MySQL Server 5.5.57 is a new version of the 5.5 production release of the world's most popular open source database. MySQL 5.5.57 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.57 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.57 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 5.5 since the release of MySQL 5.5.56 It may also be viewed online at: http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-57.html Enjoy! Changes in MySQL 5.5.57 (2017-07-17) * Packaging Notes * Functionality Added or Changed * Bugs Fixed Packaging Notes * mysqladmin was added to Docker/Minimal packages because it is needed by InnoDB Cluster. (Bug #25998285) Functionality Added or Changed * The mysql client now supports a --binary-as-hex option that causes display of binary data using hexadecimal notation (0xvalue). Thanks to Daniël van Eeden for the patch. (Bug #25340722, Bug #84391) Bugs Fixed * Replication: If a relay log index file named relay log files that did not exist, RESET SLAVE ALL sometimes did not fully clean up properly. (Bug #24901077) * The Perl path in #! lines at the beginning of Perl scripts has been adjusted to /usr/local/bin/perl for FreeBSD 11. (Bug #25719975) * A race condition could occur for CREATE TABLE statements with DATA DIRECTORY or INDEX DIRECTORY clauses. (Bug #25451091) * Full-text code now uses the standard isalnum() function rather than the my_isalnum() macro, for improved handling of default character set structure. (Bug #25447551) * MySQL compilation in different directories produced different builds to leakage of absolute paths into debug information and __FILE__. (Bug #25436469, Bug #84608) * mysqld_failed to start the server if the --datadir option was specified with a relative path name. (Bug #25364806) * With read_only enabled, creation of non-TEMPORARY tables by non-SUPER users was permitted under certain conditions. (Bug #25250768) * mysqlaccess was subject to code injection. (Bug #25043674) * On x86 machines, the uint3korr() macro read 4 bytes of data instead of the intended 3 bytes. (Bug #24807826, Bug #83264) * 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 MySQL/ORACLE RE Team Gipson Pulla -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/Java 8.0.7-dmr has been released
reateaTable() failed with a NullPointerException when there were null inputs to it. This fix adds checks for nulls, and makes Connector/J throw the proper errors for them. (Bug #25575103) * X DevAPI: The connection properties enabledSSLCipherSuites, clientCertificateKeyStoreUrl, clientCertificateKeyStoreType, and clientCertificateKeyStorePassword were ignored for connections using the X Protocol. (Bug #25494338) * X DevAPI: Calling getNodeSession() with an URL string containing SSL parameters caused a CJCommunicationsException. This has been fixed by creating a byte buffer to handle SSL handshake data. (Notice that getNodeSession() has since been consolidated into getSession().) (Bug #23597281) * X DevAPI: Concurrent asynchronous operations resulted in hangs, null pointer exceptions, or other unexpected exceptions. This has been fixed by correcting a number of problems with the SerializingBufferWriter and by limiting the number of buffers sent with a gathering write. (Bug #23510958) * X DevAPI: When a thread failed to make a connection to the server using the X Protocol, the client application hung. A new connection property, xdevapi.asyncResponseTimeout (default value is 300s), now provides a duration beyond which the attempt to connect timeouts, and a proper error is then thrown. See description for the new option in Configuration Properties (http://dev.mysql.com/doc/connector-j/8.0/en/connector-j-reference-configuration-properties.html) for details. (Bug #22972057) * Connector/J failed a number of regression tests in the test suite 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) * Configuration templates named by the connection property useConfigs were not recognized by Connector/J. (Bug #25757019, Bug #8) * 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) * An ArrayIndexOutOfBoundsException was thrown when a server-side prepared statement was used and there was a NULL in a BLOB, TEXT, or JSON type column in the ResultSet. (Bug #25215008, Bug #84084) On Behalf of MySQL/ORACLE RE Team Gipson Pulla -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/J 5.1.42 has been released
e two methods when JDBC 4 is used remain unchanged. (Bug #19531384, Bug #73775) * When an UpdatableResultSet was used, trying to close the result set and its prepared statement simultaneously by different threads might result in a deadlock. This fix updates the synchronization mechanism for UpdatableResultSet to avoid the issue. (Bug #17653733, Bug #70704) * After a connection had already switched catalog with setCatalog(), cached data from the old catalog was returned for a reused server-side prepared statement. With this fix, the cache of a server-side prepared statement cache now includes the catalog in its key to avoid wrong cache hits when the statement is reused on another catalog. (Bug #16714868, Bug #66430) On Behalf of MySQL/ORACLE RE Team Gipson Pulla -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.5.55 has been released
server now checks whether the table has the expected structure and produces an error if not. mysql_upgrade must be run to update the tables to the expected structure. (Bug #23295423, Bug #25095876, Bug #25448037) * The QUOTE() function could allocate excessive memory. A limit of max_allowed_packet bytes is now imposed and returns NULL with a warning for attempts to allocate more. (Bug #23195404) * When attempting to locate the data directory, mysqld_safe incorrectly considered $MY_BASEDIR_VERSION/var as one of the possible locations. (Bug #23013510, Bug #80866) * The main.log_tables-big test case could be unstable on highly loaded hosts. Thanks to Laurynas Biveinis for the patch. (Bug #22874167, Bug #80607) * 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. On Behalf of MySQL/ORACLE RE Team Gipson Pulla -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/Java 6.0.6-m5 has been released
ullPointerException was thrown when a NULL object of any of the classes defined in the java.time package was retried by the ResultSet.getObject() method. (Bug #23188159, Bug #81202) * The getType() method returned errors on columns of YEAR and DATETIME data types. (Bug #22931277) On Behalf of MySQL/ORACLE RE Team Gipson Pulla -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/J 5.1.41 has been released
locations of the Connector/J jar could result in the undesired behaviors, as well as warning messages in the Tomcat error log saying it was unable to stop the thread and a memory leak was likely. The implementation of AbandonedConnectionCleanupThread has now been improved, so that there are now four ways for developers to deal with the situation: + When the default Tomcat configuration is used and the Connector/J jar is put into a local library directory, the new built-in application detector in Connector/J now detects the stopping of the web application within 5 seconds and kills AbandonedConnectionCleanupThread. Any unnecessary warnings about the thread being unstoppable are also avoided. If the Connector/J jar is put into a global library directory, the thread is left running until the JVM is unloaded. + When Tomcat's context is configured with the attribute clearReferencesStopThreads="true", Tomcat is going to stop all spawned threads when the application stops unless Connector/J is being shared with other web applications, in which case Connector/J is now protected against an inappropriate stop by Tomcat; the warning about the non-stoppable thread is still issued into Tomcat's error log. + When a ServletContextListener is implemented within each web application that calls AbandonedConnectionCleanupThread.checkedShutdown() on context destruction, Connector/J now, again, skips this operation if the driver is potentially shared with other applications. No warning about the thread being unstoppable is issued to Tomcat's error log in this case. + When AbandonedConnectionCleanupThread.uncheckedShutdown() is called, the AbandonedConnectionCleanupThread is closed even if Connector/J is shared with other applications. However, it may not be possible to restart the thread afterwards. (Bug #17035755, Bug #69526) References: See also: Bug #14570236, Bug #16443387. On Behalf of MySQL/ORACLE RE Team Gipson Pulla -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Cluster 7.2.27 has been released
Dear MySQL Users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance (with optional checkpointing to disk) - Transparent Auto-Sharding - Read & write scalability - Active-Active/Multi-Master geographic replication - 99.999% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http and Memcached) MySQL Cluster 7.2.27, has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.2/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime and agility. More details can be found at http://www.mysql.com/products/cluster/ Changes in MySQL NDB Cluster 7.2.27 (5.5.54-ndb-7.2.27) (2017-01-17) MySQL NDB Cluster 7.2.27 is a new release of NDB Cluster, incorporating new features in the NDB storage engine, and fixing recently discovered bugs in previous MySQL NDB Cluster 7.2 development releases. Obtaining MySQL NDB Cluster 7.2. MySQL NDB Cluster 7.2 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. This release also incorporates all bugfixes and changes made in previous NDB Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.5 through MySQL 5.5.54 (see Changes in MySQL 5.5.54 (2016-12-12, General availability) (http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-54.html)). Bugs Fixed * A number of potential buffer overflow issues were found and fixed in the NDB codebase. (Bug #25260091) References: See also: Bug #23152979. * ndb_restore did not restore tables having more than 341 columns correctly. This was due to the fact that the buffer used to hold table metadata read from .ctl files was of insufficient size, so that only part of the table descriptor could be read from it in such cases. This issue is fixed by increasing the size of the buffer used by ndb_restore for file reads. (Bug #25182956) On Behalf of MySQL Release Engineering Team, Gipson Pulla -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.5.54 has been released
file, it displayed an error message that did not clearly indicate the error was nonfatal. It now indicates that execution continues. (Bug #24496214) * The data structure used for ZEROFILL columns could experience memory corruption, leading eventually to a server exit. (Bug #24489302) * Use of very long subpartition names could result in a server exit. Now partition or subpartition names larger than 64 characters produce an ER_TOO_LONG_IDENT error. (Bug #24400628, Bug #82429) * On Solaris, gettimeofday() could return an invalid value and cause a server shutdown. (Bug #23499695) * A union query resulting in tuples larger than max_join_size could result in a server exit. (Bug #23303485) * For some deeply nested expressions, the optimizer failed to detect stack overflow, resulting in a server exit. (Bug #23135667) * The --character-set-server option could set connection character set system variables to values such as ucs2 that are not permitted. (Bug #15985752, Bug #23303391) On behalf of Oracle MySQL Release Engineering Team, Gipson Pulla -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Cluster 7.2.25 has been released
Dear MySQL Users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance (with optional checkpointing to disk) - Transparent Auto-Sharding - Read & write scalability - Active-Active/Multi-Master geographic replication - 99.999% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http and Memcached) MySQL Cluster 7.2.25, has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.2/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime and agility. More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! Changes in MySQL Cluster NDB 7.2.25 (5.5.50-ndb-7.2.25) (2016-07-18) MySQL Cluster NDB 7.2.25 is a new release of MySQL Cluster, incorporating new features in the NDB storage engine, and fixing recently discovered bugs in previous MySQL Cluster NDB 7.2 development releases. Obtaining MySQL Cluster NDB 7.2. MySQL Cluster NDB 7.2 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.5 through MySQL 5.5.50 (see Changes in MySQL 5.5.50 (2016-06-02) (http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-50.html)). Bugs Fixed * Incompatible Change: When the data nodes are only partially connected to the API nodes, a node used for a pushdown join may get its request from a transaction coordinator on a different node, without (yet) being connected to the API node itself. In such cases, the NodeInfo object for the requesting API node contained no valid info about the software version of the API node, which caused the DBSPJ block to assume (incorrectly) when aborting to assume that the API node used NDB version 7.2.4 or earlier, requiring the use of a backward compatability mode to be used during query abort which sent a node failure error instead of the real error causing the abort. Now, whenever this situation occurs, it is assumed that, if the NDB software version is not yet available, the API node version is greater than 7.2.4. (Bug #23049170) On behalf of Oracle MySQL RE team Gipson Pulla -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Workbench 6.3.7 GA has been released
rkbench makes one connection at
the start to disable triggers, makes a separate
connection to do the data copy, then returns to the first
connection to re-enable triggers. If the copy takes
longer than the server's wait_timeout, the first
connection timed out. (Bug #22190703, Bug #79242)
* The Driver sends Unicode data as UTF-8 advanced database
migration option that is available when using an ODBC
driver is now disabled by default. Also, connections
could hang when this option was enabled. (Bug #22149342,
Bug #76382)
* Executing Delete Row(s) after selecting more than six
rows from the results grid would not delete all of the
selected rows. (Bug #21909625, Bug #78560)
* Adding a DATETIME with precision (such as DATETIME(3))
from the Table Editor would eventually get reverted to
DATETIME (without precision). (Bug #21666012, Bug #78153)
* The search (magnifying glass) icon in the schema search
field was misplaced after the left sidebar was resized.
(Bug #21329109, Bug #77507)
* Workbench will now prompt to continue the execution of
operations containing loops in stored procedures, instead
of just canceling it after ~200 executions. (Bug
#21310357, Bug #77470)
* The Performance Schema installation procedure in
Workbench failed to check user privileges before
attempting the installation. For example, if the user had
all privileges except "ALTER ROUTINE", it would update
sys.version but fail to complete the installation, and
also fail to back out thereby leaving the sys.version as
current but none of the functions were updated. (Bug
#21261239, Bug #77360)
* On Linux and OS X, the Options File viewer shortened
(cut) long option names in the GUI, although editing
their values changed the correct options. (Bug #21167521,
Bug #77179)
* MySQL connections were leaked when connecting and
disconnecting to MySQL databases. It leaked one
connection per re-connect to a database. (Bug #20996606)
* A large database caused the size reported under the
Schema Inspector to wrap around and display a negative
number. (Bug #20990435)
* From the Options File management feature, clicking
Discard with the Advanced tab open would always revert
the thread_handling option value to
"one-thread-per-connection" even if it was set to "no
threads". (Bug #20956570)
* The print preview icon dialog was missing the Workbench
icon. (Bug #20309812, Bug #75422)
* Changes to the modeling Appearance font preference did
not save properly, or have an effect. (Bug #20196073, Bug
#75173)
* On Windows, the Query Stats graph would not render with
MySQL Server 5.7. (Bug #20141414, Bug #75100)
* The Query Stats information tab was populated even when
the Performance Schema was disabled. (Bug #20141262, Bug
#75101)
* The Toggle whether execution of SQL script should
continue after failed statements button was updated to
better indicate when the option is enabled or disabled.
(Bug #20093801, Bug #74982)
* On Windows, after closing and reopening Workbench with
several SQL Editor tabs open, the tabs names were hash
values (instead of MySQL connection names) if the
connection names contained non-standard text. (Bug
#20086117, Bug #74966)
* In the Table Editor, if a column has NN checked, and NN
is then unchecked, then a default NULL value is
automatically added to the CREATE TABLE statement when
Apply is clicked. The column then shows a default value
of NULL in the Table Editor. (Bug #19890571, Bug #74558)
* If a setting is (incorrectly) defined twice in my.ini,
Workbench separates its values with a newline ("\n"). For
example, if sort_buffer_size is defined twice, Workbench
displays it as "sort_buffer_size=256K\n256K". Workbench
now follows MySQL Server behavior, and uses the last
defined option. (Bug #19769849)
* The cursor could seemingly disappear after executing a
query, as it could remain at its last position when the
query started to execute. (Bug #19703074, Bug #74128)
* The model Page setup... functionality was not always
preserved when choosing a size for printing. (Bug
#11766583, Bug #59724)
On behalf of the MySQL Workbench and the MySQL/ORACLE RE Team
Gipson Pulla
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.5.48 has been released
ems, 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. * When an invalid date was supplied to the UNIX_TIMESTAMP() function using the STR_TO_DATE() function, no check was performed before converting it to a timestamp value. (Bug #21564557) * 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) * Using systemd to start mysqld failed if configuration files contained multiple datadir lines. Now the last datadir line is used. (Bug #79613, Bug #22361702) On behalf of Oracle MySQL Release Engineering Team, Gipson Pulla -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL for Excel 1.3.6 has been released
Dear MySQL users, The MySQL Windows Experience Team is proud to announce the release of MySQL for Excel version 1.3.6. This is a maintenance release for 1.3.x. It can be used for production environments. MySQL for Excel is an application plug-in enabling data analysts to very easily access and manipulate MySQL data within Microsoft Excel. It enables you to directly work with a MySQL database from within Microsoft Excel so you can easily do tasks such as: * Importing MySQL Data into Excel * Exporting Excel data directly into MySQL to a new or existing table * Editing MySQL data directly within Excel MySQL for Excel is installed using the MySQL Installer for Windows. The MySQL Installer comes in 2 versions - Full (150 MB) which includes a complete set of MySQL products with their binaries included in the download. - Web (1.5 MB - a network install) which will just pull the MySQL for Excel over the web and install it when run. You can download MySQL Installer from our official Downloads page at http://dev.mysql.com/downloads/installer/ The MySQL for Excel product can also be downloaded by using the product standalone installer found at this link http://dev.mysql.com/downloads/windows/excel/ Changes in MySQL for Excel 1.3.6 (2016-01-07) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * A new Generate an INSERT statement for each data row option was added to the Advanced Options dialog for Append and Export Data operations. This is disabled by default. A single INSERT statement is generated that inserts all affected rows, unless this option is enabled. When checked, an INSERT statement for each data row being appended or exported is generated in the resulting SQL query sent to the MySQL server. When unchecked, a single INSERT statement is generated as a bulk data operation, which performs better than multiple INSERT statements. While row-by-row inserts are slower, for debugging errors it could help determine which row causes an error, since the MySQL Server will process them row by row. * Added column properties to the Export Data dialog to support the definition of Auto Increment and Default Value for new MySQL tables where the data will be exported. Added a context menu to declare a numeric field to be Unsigned or to have Zero-Fill, accessible by right-clicking the Data Type combo box. Added the TIMESTAMP data type to the full list of valid data types, as it was not being shown before. Added help tool tips to fields in the Export Data dialog that explain in detail how the column properties work in a MySQL database. Bugs Fixed * The Pivot Table feature was updated to work with Excel 2016. (Bug #22387425) * Closing the plugin via the Close button in the panel would not toggle the MySQL for Excel checkbox in the Data ribbon. (Bug #22374026, Bug #79655) * Fixed the content detector for the active Excel cell after importing data and after loading database objects when a database is opened. Now, the data options are not enabled until a table is selected. (Bug #22372915) * Append and Export operations would not append/export boolean data. (Bug #22138966) * The MySQL for Excel Refresh All function would throw an unhandled exception. (Bug #22110627, Bug #78941) * With Office 2007, data would not auto-save after closing Excel. (Bug #22081313, Bug #78910) * Numeric data stored in text columns is now correctly formatted by Excel as text, and not as the "General" format that automatically formats cells as numbers when the data is stored in a text object. This fixes the issue where text columns were formatted as numbers, which stripped leading zeros. (Bug #20905284, Bug #76738) * Changed settings for containers and forms to let all UI components automatically scale on different DPI settings. Also removed the restriction to resize the MySQL for Excel's pane, so in case a different DPI setting is used and the fonts look too big, the pane can be resized to see contents as best as possible. (Bug #18099454, Bug #71389) Quick links: MySQL for Excel documentation: http://dev.mysql.com/doc/en/mysql-for-excel.html. Inside MySQL blog (NEW blog home): http://insidemysql.com/ MySQL on Windows blog (OLD blog home): http://blogs.oracle.com/MySQLOnWindows. MySQL for Excel forum: http://forums.mysql.com/list.php?172. MySQL YouTube channel: http://www.youtube.com/user/MySQLChannel. Enjoy and thanks for the support! The MySQL on Windows team at Oracle. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
