MySQL Utilities download

v1.5 [Jul 11, 2014]
- Added the missing README and LICENSE text for the commercial packages. (Bug #19675930)
- The failure detector was specifying a set of groups as lockable objects, and a failover operation could potentially run while a group was being updated by another operation which could lead to unpredictable results. (Bug #19594070, Bug #73873)
- For Windows, the Utilities MSI distribution package was setting the wrong permissions for the generated installation directory, which included all permissions granted for the 'Users' group. Now, the only permission set here for the 'Users' group is read-only. (Bug #19611879)
- A debugging message was being sent through the Fabric RPC protocol. (Bug #19588383, Bug #73864)
- Due to licensing conflicts between OpenSSL and GPL, SSL support is not included in the community edition for Windows. (Bug #19487002)
- Fabric behaved inconsistently with respect to sharding and non-existent tables. (Bug #19450843, Bug #73599)
- Separate CHANGES and README files were added to the commercial distribution. (Bug #19380635)
- For Fabric, Connectors inserting large amount of data before the TTL expires, after a resharding metadata update, could cause inconsistencies between the sharding definition and the data on the shard. (Bug #19427027, Bug #73546)
- Fabric could return an incorrect "lower_bound" length, depending on the character set. (Bug #19352961, Bug #73218)
- The mysqlserverclone utility did not check for a low amount of free space before it created a new instance of the server. It now errors out if 120+ MB of free space is unavailable, but this check can be ignored by also passing in the --force option.
- The --disable-binary-logging flag of the mysqldbcompare utility did not function properly. It always required SUPER privileges in cases where the server had binary logging enabled, it was enabled internally even when not in use, and it threw an error when attempting to generate SQL statements for the differences between tables if one of the rows had columns with NULL values.
- When copying views that depended on sub-views that were not yet copied, some utilities such as mysqldbcopy failed. The dependency related code was fixed to solve this problem. (Bug #19302898, Bug #73383)
- The policy command for the mysqlauditadmin utility failed when applied to recent MySQL server versions (such as MySQL 5.6.20 and 5.7.5). This is because audit_log_policy is now a READONLY variable (Bug #19259597)
- The utilities did not parse all types of GRANT statements, such as those with PROXY privileges and stored routines. The utilities could also fail when objects contained backticks. (Bug #19238432)
- Commands accept either a UUID or an address (i.e. host:port) to specify a server. The code was ignoring that a wrong address could be provided, and in consequence the execution could hang. The address is now validated before it is used.