MySQL Connector/NET 8.0.16 has been released
ers. (Bug #29249857, Bug #29304767) * An exception was generated when the MySqlDbType enumeration was given an explicit value and then passed as a parameter to the MySqlCommand.Prepare method. (Bug #28834253, Bug #92912) * Validation was added to ensure that when a column is of type TIME and the value is 00:00:00, it takes the value instead of setting NULL. (Bug #28383726, Bug #91752) On Behalf of MySQL Release Engineering Team, Surabhi Bhat
MySQL Community Server 5.7.26 has been released
#29240701) * With the --users option, mysqlpump wrote CREATE USER and GRANT statements to the output, but too late to apply to the other objects created by the dump. Consequently, restoring the dump file created the user accounts too late to apply to other objects created by the file. mysqlpump now writes user accounts to the dump file before other objects. (Bug #29023216) * A damaged mysql.user table could cause a server exit. (Bug #28986737) * The CMake check for tirpc headers now falls back to using pkgconfig, to enable finding the headers on more Linux platforms. This requires that pkgconfig be installed. (Bug #28970313, Bug #93341, Bug #28997093) * An attempt to access a null pointer could occur during prepared statement execution. (Bug #28692136) * The Aborted_connects status variable was not incremented for unsuccessful connection attempts, if connections were managed by the thread_pool plugin. (Bug #28490126) * mysqladmin shutdown did not wait for mysqld to shut down. (Bug #28466137, Bug #91803) References: This issue is a regression of: Bug #25364806. * Repeated invocations of stored procedures which executed queries undergoing short-circuit evaluation were not always handled correctly. (Bug #28379655) * Keyring migration should require only read access to the source keyring, but failed unless the user had write access. (Bug #28339014) * If a user performing a keyring migration did not have write access to the keyring file, the migration failed but reported success in its final error log message. (Bug #28330922) * During FLUSH STATUS execution, the Performance Schema unnecessarily aggregated session status to global status, causing double counts for some status variables. (Bug #28291258, Bug #91541) * Some status variable values could temporarily increase before returning to their original value. (Bug #27839644, Bug #90351) * Executing ALTER INSTANCE ROTATE INNODB MASTER KEY and migrating keys from the keyring_file plugin to the keyring_encrypted_file plugin could make encrypted tables unusable. (Bug #27760952) * The binary file for the udf_example user-defined function was omitted from binary distributions. (Bug #26115002, Bug #29178542) * When the server was started with the --skip-name-resolve option, spurious warnings could be written to the error log about ignoring accounts with a host name part of localhost. (The accounts in fact were used and not ignored.) (Bug #23329861, Bug #81441) * Installing and uninstalling a plugin concurrently with client connection activity could cause a server exit. (Bug #22980441) * Some queries involving complex joins leaked file handles. (Bug #90902, Bug #28039829) On Behalf of MySQL Release Engineering Team, Surabhi Bhat
MySQL Enterprise Backup 3.12.4 has been released
ariable setting
--innodb_checksum_algorithm=0 to mean
--innodb_checksum_algorithm=crc32, a mysqlbackup
operation (except for backup) failed when
--innodb_checksum_algorithm=0 was set as a configuration
option. With this fix, mysqlbackup now accepts
--innodb_checksum_algorithm=0 as valid and interprets it
as --innodb_checksum_algorithm=crc32. (Bug #28295519)
* On macOS, mysqlbackup failed to determine the relay log
file name correctly if the relay log index file name was
not specified. (Bug #25574605)
* The Release number for the RPM packages of MySQL
Enterprise Backup always said "1," instead of giving the
release number of the Linux distribution for which the
package was built. (Bug #25538798)
* When the option --only-innodb-with-frm or --no-locking
was used during a backup operation, the backup sometimes
failed with mysqlbackup complaining that the highest LSN
was larger in a copied page than on the backed-up server.
It was because mysqlbackup did not perform a log flushing
before copying the redo log when either of the mentioned
options was used. With this fix, log flushing was always
performed to prevent the error. (Bug #25412655)
* When creating a full image backup with the --no-locking
option, mysqlbackup failed to write the binary log
information to the backup history table and the
backup_variables.txt file. The result was that when
creating an incremental image backup based on the full
backup, the attempt to copy the binary log files from the
server into the incremental image backup (which is the
default behavior) would fail, causing the incremental
backup to stop. With this fix, the binary log information
is no longer missing after the full backup, so the
incremental image backup no longer fails." (Bug
#25296324)
References: See also: Bug #19915713.
* After restoring an incremental backup of a slave server,
the file ibbackup_slave_info was missing from the meta
folder under the backup directory on the target server.
(Bug #25097753)
* mysqlbackup logged double entries with wrong information
into the backup_history table for optimistic backups.
(Bug #24502876)
* Backups for a slave server in a multi-source replication
setup using the --slave-info option failed. (Bug
#2950)
References: See also: Bug #21830316.
* Attempts to restore an image backup from the cloud using
the --skip-binlog option failed with a "global tail magic
mismatch" error. This was because mysqlbackup failed to
perform a non-sequential read from the cloud with gaps
caused by the skipping of the binary logs. This fix makes
sure mysqlbackup can perform such reads. (Bug #23534700)
* An extract operation for an image backup failed with a
checksum mismatch error in cases when, during the backup,
an InnoDB tablespace file kept growing in size, and
mysqlbackup failed to put the correct file size in its
file header. (Bug #22905984)
References: This issue is a regression of: Bug #22613568.
* After an apply-incremental-backup operation on a full
backup, mysqlbackup printed to the output stream and the
message log file the old instead of the updated binary
log position. (Bug #22085034, Bug #78898)
* When running the backup-and-apply-log command without a
connection to the MySQL server, mysqlbackup could not
know the correct binary log file name and binary log
position for the backup; yet, at the end of the
backup-and-apply-log operation, mysqlbackup still printed
out some values for the binary log file name and
position, which were random in nature. (Bug #21623089)
* Occasionally, some files were missing from an image
backup created by the --backup-to-image command. It was
due to an internal race condition, which this fix
eliminates. (Bug #19600687)
On Behalf of MySQL Release Engineering Team,
Surabhi Bhat
MySQL Connector/NET 8.0.15 has been released
Dear MySQL users, MySQL Connector/NET 8.0.15 is the third version to support Entity Framework Core 2.1 and the fifth general availability release of MySQL Connector/NET to add support for the new X DevAPI, which enables application developers to write code that combines the strengths of the relational and document models using a modern, NoSQL-like syntax that does not assume previous experience writing traditional SQL. To learn more about how to write applications using the X DevAPI, see http://dev.mysql.com/doc/x-devapi-userguide/en/index.html. For more information about how the X DevAPI is implemented in Connector/NET, see http://dev.mysql.com/doc/dev/connector-net. NuGet packages provide functionality at a project level. To get the full set of features available in Connector/NET such as availability in the GAC, integration with Visual Studio's Entity Framework Designer and integration with MySQL for Visual Studio, installation through the MySQL Installer or the stand-alone MSI is required. Please note that the X DevAPI requires at least MySQL Server version 8.0 or higher with the X Plugin enabled. For general documentation about how to get started using MySQL as a document store, see http://dev.mysql.com/doc/refman/8.0/en/document-store.html. To download MySQL Connector/NET 8.0.15, see http://dev.mysql.com/downloads/connector/net/ Installation instructions can be found at https://dev.mysql.com/doc/connector-net/en/connector-net-installation.html Changes in MySQL Connector/NET 8.0.15 (2019-02-01) Bugs Fixed * The client library has been modified to initialize the MySqlBulkLoader class with the local-infile capability disabled by default (see Using the BulkLoader Class (http://dev.mysql.com/doc/connector-net/en/connector-net-programming-bulk-loader.html)). (Bug #29259767) On Behalf of MySQL Release Engineering Team, Surabhi Bhat
MySQL Community Server 5.7.25 has been released
efinitions that could result in a server exit. (Bug #27595603) * The server failed to start if the keyring_encrypted_file plugin keyring file was invalid. (Bug #27588064) * Keyring migration failed with source and destination keyring plugins of keyring_okv and keyring_encrypted_file, respectively. (Bug #27493970) * When executing a prepared statement with a procedure call with the CURSOR_TYPE_READ_ONLY flag set, the client library hung if the procedure performed a SELECT that returned an empty result set. (Bug #27443252, Bug #89214) * The parser performed some out-of-memory checks incorrectly. (Bug #25633994) * When a subquery contained a UNION, the count of the number of subquery columns was calculated incorrectly. (Bug #24899924) * When binlog_format is ROW or MIXED, operations on temporary tables are not logged. Previously, the exception to this rule was that when the connection was terminated at the end of the session, the statement DROP TEMPORARY TABLE IF EXISTS was logged for any temporary tables that had been opened in the session. For row-based replication, this behavior caused an unnecessary write to the binary log, and added a transaction sequence number for the GTID where these were enabled. Now, when a temporary table is created in a session, the binary logging format is tracked. The DROP TEMPORARY TABLE IF EXISTS statement is only logged at the end of the session if statement-based format was in effect when the temporary table was created, so the CREATE TEMPORARY TABLE statement was logged. If row-based or mixed-format binary logging was in use when the table was created, the DROP TEMPORARY TABLE IF EXISTS statement is not logged. Thanks to Laurynas Biveinis for the patch. (Bug #24670909, Bug #83003, Bug #28606948) * DML statements using IGNORE were not always handled correctly on tables having generated columns. (Bug #22990029) * A query employing a dynamic range and an index merge could use more memory than expected. (Bug #89953, Bug #27659490) On Behalf of MySQL Release Engineering Team, Surabhi Bhat -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/NET 8.0.14 has been released
Dear MySQL users, MySQL Connector/NET 8.0.14 is the second version to support Entity Framework Core 2.1 and the fourth general availability release of MySQL Connector/NET to add support for the new XDevAPI, which enables application developers to write code that combines the strengths of the relational and document models using a modern, NoSQL-like syntax that does not assume previous experience writing traditional SQL. To learn more about how to write applications using the XDevAPI, see http://dev.mysql.com/doc/x-devapi-userguide/en/index.html. For more information about how the XDevAPI is implemented in Connector/NET, see http://dev.mysql.com/doc/dev/connector-net. NuGet packages provide functionality at a project level. To get the full set of features available in Connector/NET such as availability in the GAC, integration with Visual Studio's Entity Framework Designer and integration with MySQL for Visual Studio, installation through the MySQL Installer or the stand-alone MSI is required. Please note that the XDevAPI requires at least MySQL Server version 8.0 or higher with the X Plugin enabled. For general documentation about how to get started using MySQL as a document store, see http://dev.mysql.com/doc/refman/8.0/en/document-store.html. To download MySQL Connector/NET 8.0.14, see http://dev.mysql.com/downloads/connector/net/ Installation instructions can be found at https://dev.mysql.com/doc/connector-net/en/connector-net-installation.html Changes in MySQL Connector/NET 8.0.14 (2019-01-21) *Functionality Added or Changed* * The internal method called by the MySqlX.XDevAPI.Relational.Table.Count, MySqlX.XDevAPI.Collection.Count, and MySqlX.XDevAPI.Collection.Count methods were moved to a standardized location within the library. * The auth connection option (along with aliases authentication and authentication mode) was removed from the MySqlBaseConnectionStringBuilder class. This option now is available for X Protocol connections only. * The following obsolete (deprecated) members of Connector/NET 8.0 API classes were removed: + Collection.Remove(Object) method + Collection.Remove(DbDoc) method + FindStatement.Limit(Int64, Int64) method + MySqlParameterCollection.Add(String, Object) method + TableSelectStatement.Limit(Int64, Int64) method + BaseResult.WarningCount property + MySqlBaseConnectionStringBuilder.Auth property + Result.RecordsAffected property + SqlResult.AutoIncrementValue property + SqlResult.RecordsAffected property On Behalf of MySQL Release Engineering Team, Surabhi Bhat
MySQL Cluster Manager 1.4.7 has been released
configuration is only received once. (Bug #25517245) * Agent: The create site command failed with a timeout when the site to be created had a large number of hosts (more than 45), and the hosts were not uniform in their machine configurations. (Bug #25075284) * Client: In a number of instances where an ndb_mgmd command or a mysqld query failed, the wrong error (Error 1006 or Error 7006) was thrown. With this fix, the appropriate Error 7030 is thrown instead. (Bug #28829732) On Behalf of MySQL Release Engineering team, Surabhi Bhat
MySQL Connector/NET 8.0.13 has been released
assic
MySQL operations.
* Connector/NET now provides connection pooling for
applications using the X Protocol. The implementation
includes the new static MySQLX.GetClient method that
takes two parameters: connectionData (connection string
or URI) and connectionOptions (JSON-formatted string or
anonymous object containing the pooling options).
Methodoverloading enables the following type combinations:
MySQLX.GetClient(Object, Object)
MySQLX.GetClient(Object, String)
MySQLX.GetClient(String, Object)
MySQLX.GetClient(String, String)
GetClient returns the new Client object, which retrieves
an existing and currently unused network connection from
the pool, resets it, and uses it. Closing a session marks
the underlying connection as unused and returns it to the
pool.
Connection options are configured as follows:
// Connection options of type String
Client client = MySQLX.GetClient(ConnectionData, "{
\"pooling\": { \"maxSize\": 5, \"queueTimeout\": 5000 } }");
// Connection options of type Object (anonymous object)
Client client = MySQLX.GetClient(ConnectionData, new { pooling =
new {maxSize = 5, queueTimeout = 5000 } });
The new keyword must be used twice when the connection
options are configured using an anonymous object.
Connection options are: enabled, maxSize, maxIdleTime,
and queueTimeout. For more information, see Connection
and Session Concepts
(http://dev.mysql.com/doc/x-devapi-userguide/en/devapi-connection-concepts.html).
*Bugs Fixed*
* Document Store: Connector-side validation performed when
the Collection.CreateIndex method was called duplicated
some of the checks already made by the server. The
connector now only validates that the indexDefinition
value passed to the method is a valid JSON document with
the correct structure. (Bug #28343828)
* 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)
* Document Store: A mixed alphanumeric value such as
"1address" when used with the Set and Unset methods
caused the operations to throw an exception. This fix
resolves the way mixed values are converted into tokens
to generate only one token as an identifier. (Bug
#28094094)
* EF Core: The implementation of some methods required to
scaffold an existing database were incomplete. (Bug
#27898343, Bug #90368)
* 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 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)
On Behalf of MySQL Release Engineering team,
Surabhi Bhat
MySQL Community Server 5.6.42 has been released
spurious popup window. (Bug #27463864) * Concurrent INSERT and SELECT statements on a MERGE table could result in a server exit. (Bug #28379285) * 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) * Very long table keys were handled incorrectly on replication slaves. (Bug #27930505) * 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) * 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) * 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) * yum update did not properly update from RHEL5 RPM packages to current packages. (Bug #20560761) * 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 Release Engineering Team, Surabhi Bhat -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Connector/J 5.1.47 GA has been released
ates before the Julian-Gregorian cutover (October 15, 1582) were stored wrongly. With this fix, a proleptic calendar is properly used if supplied to the setDate() method. Note that when trying to set or retrieve dates before the Julian-Gregorian cutover with PreparedSatement methods, a proleptic GregorianCalendar should always be explicitly supplied to the setDate() and getDate() method.For details, see Known Issues and Limitations (http://dev.mysql.com/doc/connector-j/5.1/en/connector-j-usagenotes-known-issues-limitations.html). (Bug#18749544, Bug #72609) On Behalf of MySQL Release Engineering Team, Surabhi Bhat
MySQL Connector/NET 8.0.12 has been released
were not parsed properly when the values included a decimal separator other than a period (.) character. (Bug #28112229) * X DevAPI: The list of members shown with IntelliSense did not match the members provided in the reference documentation. (Bug #27918879, Bug #90615) * 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 TreatTinyAsBoolean connection option was ignored when the MySqlCommand.Prepare() method was called. (Bug #27113566, Bug #88472) * 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) On Behalf of MySQL Release Engineering team, Surabhi Bhat -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Cluster 7.4.21 has been released
Dear MySQL Users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance - Transparent Auto-Sharding - Read & write scalability - Active-Active/Multi-Master geographic replication - 99.999% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http, Memcached and JavaScript/Node.js) MySQL Cluster 7.4 makes significant advances in performance; operational efficiency (such as enhanced reporting and faster restarts and upgrades) and conflict detection and resolution for active-active replication between MySQL Clusters. MySQL Cluster 7.4.21, has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.4/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime and agility. More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! Changes in MySQL NDB Cluster 7.4.21 (5.6.41-ndb-7.4.21) (2018-07-27, General Availability) MySQL NDB Cluster 7.4.21 is a new release of MySQL NDB Cluster 7.4, based on MySQL Server 5.6 and including features in version 7.4 of the NDB storage engine, as well as fixing recently discovered bugs in previous NDB Cluster releases. Obtaining MySQL NDB Cluster 7.4. MySQL NDB Cluster 7.4 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL NDB Cluster 7.4, see What is New in NDB Cluster 7.4 (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is <http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is-new-7-4.html>-new-7-4.html <http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is-new-7-4.html>). This release also incorporates all bug fixes and changes made in previous NDB Cluster releases, as well as all bug fixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.41 (see Changes in MySQL 5.6.41 (Not yet released, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-41.html)). Bugs Fixed * NDB Cluster APIs: When Ndb::dropEventOperation() tried to clean up a pending event, it failed to clear a pointer to the list of GCI operations being deleted and discarded (Gci_ops object), so that this pointer referred to a deleted object. GCI operations arriving after this could then be inserted as part of the next such list belonging to the now-deleted object, leading to memory corruption and other issues. (Bug #90011, Bug #27675005) * NDB attempted to drop subscriptions which had already been dropped, leading to a data node shutdown with Error 2341. (Bug #27622643) * An NDB online backup consists of data, which is fuzzy, and a redo and undo log. To restore to a consistent state it is necessary to ensure that the log contains all of the changes spanning the capture of the fuzzy data portion and beyond to a consistent snapshot point. This is achieved by waiting for a GCI boundary to be passed after the capture of data is complete, but before stopping change logging and recording the stop GCI in the backup's metadata. At restore time, the log is replayed up to the stop GCI, restoring the system to the state it had at the consistent stop GCI. A problem arose when, under load, it was possible to select a GCI boundary which occurred too early and did not span all the data captured. This could lead to inconsistencies when restoring the backup; these could be be noticed as broken constraints or corrupted BLOB entries. Now the stop GCI is chosen is so that it spans the entire duration of the fuzzy data capture process, so that the backup log always contains all data within a given stop GCI. (Bug #27497461) References: See also: Bug #27566346. On Behalf of MySQL Release Engineering team, Surabhi Bhat
MySQL Community Server 5.6.41 has been released
the slave reconnects to the master. Previously, this process was not done for CREATE DATABASE, ALTER DATABASE, and DROP DATABASE statements, but it is now carried out for those statements as well as for others. (Bug #27308751, Bug #88891) * Replication: On a multithreaded slave, when a STOP SLAVE statement is executed on the slave, followed by a START SLAVE statement, the error log can report a different position in the binary log for the slave SQL thread when exiting, compared to the position reported for the slave SQL thread at the subsequent initialization. For a multithreaded slave, the position reported for the SQL thread on exit is a low water mark, up to which the replication stream is consistent and has no gaps. Transactions appearing before the position are guaranteed to have committed, but transactions after the position may have committed or not. However, this low water mark was being reported before the process to stop the worker threads was actually carried out, and the low water mark was subsequently updated by a checkpoint routine during that process. The timing of the log message has now been changed so that the final low water mark is reported as the position for the SQL thread on exit. (Bug #27300658) * 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) * On Windows, if the Visual C++ Redistributable for Visual Studio had been removed, MySQL uninstallation using the MSI installer failed. (Bug #27621546) * A memory leak in the pfs-t unit test was fixed. Thanks to Yura Sorokin for the patch. (Bug #27440735, Bug #89384) * 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) * FORCE INDEX had no effect on a query that used GROUP BY, ORDER BY, and LIMIT together. (Bug #90817, Bug #27998526) On Behalf of MySQL Release Engineering Team, Surabhi Bhat -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Cluster Manager 1.4.6 has been released
Dear MySQL Users, MySQL Cluster Manager 1.4.6 can be downloaded from the My Oracle Support (MOS) website. It will also be available on Oracle Software Delivery Cloud at http://edelivery.oracle.com with the next monthly update MySQL Cluster Manager is an optional component of the MySQL Cluster Carrier Grade Edition, providing a command-line interface that automates common management tasks, including the following online operations: - Configuring and starting MySQL Cluster - Upgrades - Adding and removing cluster nodes - Adding and removing site hosts - Configuration changes - Backup and restore MySQL Cluster Manager is a commercial extension to the MySQL family of products. More details can be found at http://www.mysql.com/products/cluster/mcm/. A brief summary of changes in MySQL Cluster Manager version 1.4.6 is listed below: Changes in MySQL Cluster Manager 1.4.6 (2018-05-09) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * Agent: The list backups command has been extended with a new --agent option for listing agent backups created with the backup agents command. See the option description for details. (Bug #27168819, Bug #27850905) Bugs Fixed * Agent: The collect logs command failed to include logs that had been rotated with the rotate log command. (Bug #27918231) * Agent: A list backups command failed with an Error: 1159 (timeout reading communication packets) from one of the mcmd agents when it had a huge number of backups to list. With this fix, mcmd has been optimized to enumerate a larger number of backups. (Bug #27868499) * Agent: The mcmd agent quit unexpectedly if the cluster's global configuration file (config.ini usually) contained a [system] section. It was because in MySQL Cluster Manager, the handling for the [system] section was missing, which has now been added by this fix. The addition also allows mcmd to set the name attribute in the [system] section, which is required for MySQL Enterprise Monitor 4.0 to monitor the cluster. (Bug #27638138, Bug #27519205) * Agent: The collect logs command hung if a host was referenced earlier with the localhost IP address 127.0.0.1 in the create site or create cluster command. (Bug #27551932) * Agent: The create cluster command was successful even if the format of an IP address submitted with it as a hostname was inconsistent with the format used earlier with the add hosts command (for example, a host was added to a site as 127.0.0.1, and then added to a cluster as 127.0.01). A subsequent attempt to start the cluster failed. This fix added consistency check for the host names, so that inconsistent IP addresses are now rejected. (Bug #27551776) * Agent: When a maintenance restart occurred for a cluster node while mcmd was shutting down, the node remained in the starting stage indefinitely. With this fix, a node restart will not be attempted when mcmd is shutting down. (Bug #27513481) * Agent: An Internal error occurred when mcmd tried to set the MySQL Server system variable audit_log_read_buffer_size with a set command. It was because of the wrong data type used internally for the variable, which has now been fixed. (Bug #27413635) * Agent: mcmd quit unexpectedly sometimes when running a restore cluster command. It was due to a race condition in which mcmd started executing the restore before the required ndbapi node was ready for the task. This fix added checks to eliminate the race condition. (Bug #27342271) On behalf of MySQL Release Engineering Team, Surabhi Bhat
MySQL for Visual Studio 1.2.8 has been released
Dear MySQL users, The MySQL Windows Experience Team is proud to announce the release of MySQL for Visual Studio 1.2.8. This is a maintenance release for 1.2.x. It can be used for production environments. MySQL for Visual Studio is a product that includes all of the Visual Studio integration functionality to create and manage MySQL databases when developing .NET applications. MySQL for Visual Studio is installed using the MySQL Installer for Windows which comes in 2 versions: * Full (386.6 MB) which includes a complete set of MySQL products with their binaries included in the downloaded bundle. * Web (1.7 MB - a network install) which will just pull MySQL for Visual Studio over the web and install it when run. You can download MySQL Installer from our official Downloads page at http://dev.mysql.com/downloads/installer/. MySQL for Visual Studio can also be downloaded by using the product standalone installer found at http://dev.mysql.com/downloads/windows/visualstudio/. Changes in MySQL for Visual Studio 1.2.8 (2018-05-04, General Availability) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * When Microsoft Visual Studio receives a request to register (or unregister) MySQL for Visual Studio within the IDE during the installation, Visual Studio might not execute the command properly if the host is running Windows 7. This fix identifies when Visual Studio does not register MySQL for Visual Studio as requested and then provides an alert to perform the registration manually from the Developer Command Prompt for Visual Studio using the following command: devenv /updateconfiguration /log (Bug #27365261, Bug #87902) * MySQL for Visual Studio now supports the MySQL 8.0 release series (requires Connector/Net 6.9.12, 6.10.7, or 8.0.11) including: + MySQL data dictionary, which uses INFORMATION_SCHEMA tables rather than tables in the mysql database (see MySQL Data Dictionary (http://dev.mysql.com/doc/refman/8.0/en/data-dictionary.html)). + The caching_sha2_password authentication plugin introduced in MySQL 8.0 (see Caching SHA-2 Pluggable Authentication (http://dev.mysql.com/doc/refman/8.0/en/caching-sha2-pluggable-authentication.html)). In addition, MySQL for Visual Studio now requires that .NET Framework 4.5.2 (or later) be installed for use within Visual Studio 2012 and Visual Studio 2013. Bugs Fixed * The Website Configuration Tool was unable to add an ADO.NET entity data model to an ADO.NET web application successfully. In addition to aligning the web.config file with the installed version of Connector/Net, this fix also disables the Entity Framework 5 selection when the installed connector no longer includes a provider for EF5 (Connector/Net 6.10 and higher). (Bug #27593219) * Queries made with a valid MySQL connection received no response from the server. (Bug #27584991) * When the MySQL for Visual Studio parser was unable to parse an SQL statement, it generated an unhandled exception that caused Visual Studio to exit unexpectedly. This fix enables the parser to handle exceptions properly and updates the parser to include support for CREATE USER syntax in the MySQL 8.0 release series. (Bug #27580303) * The version for the MySql.Web assembly was incorrectly extracted, which prevented the assembly from loading properly and the MySQL Website Configuration Tool from launching. (Bug #27450530) * Attempting to open the MySQL Web Configuration Tool, with MySQL Connector/Net and MySQL for Visual Studio prerequisites installed properly, displayed an error message instead of opening the tool. (Bug #27365141, Bug #88570) On Behalf of MySQL Release Engineering Team, Surabhi Bhat -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
