Documentation Home
MySQL Utilities Release Notes
Download these Release Notes
PDF (US Ltr) - 224.3Kb
PDF (A4) - 225.9Kb

MySQL Utilities Release Notes  /  Changes in Release 1.0  /  Changes in MySQL Utilities 1.0.4 (2011-12-22)

Changes in MySQL Utilities 1.0.4 (2011-12-22)

This section documents all changes and bug fixes applied since the release of 1.0.3.

Functionality Added or Changed

  • Added the --write-command option to the mysqlserverclone utility, which saves the command used to launch the new server instance. This command may also be shown while generated, depending on the -verbose level. (Bug #13082771)

  • Added a parser for the slow and general logs, within the new mysql.utilities.parser module that contains the SlowLog, SlowLogEntry, GeneralLog, and GeneralLogEntry classes.

  • The mysqldbcompare utility can now generate SQL statements for synchronizing the objects and data for the compared databases. This adds the --difftype, --changes-for, and --show-reverse options.

    Also, enabling the --quiet option will now only generate the diff output for runs when the --difftype option is set, but not as =sql. And only output the SQL statements when --difftype is set to =sql.

  • Added the --regexp option, which changes the --exclude option behavior to use REGEXP instead of LIKE for its matching. This change affects the mysqldbcopy and mysqldbexport utilities.

  • Added the --locking option to the mysqldbcopy and mysqldbexport utilities, which now allows for table locking.

Bugs Fixed

  • Installation would alter the permissions of /etc/profile.d/ before creating the file. The order of operations has been corrected. (Bug #13115052)

  • Optimized the mysqldbexport utility performance, namely for the _table.get_column_metadata() and table.get_column_string() methods. (Bug #13082780)

  • The command would not generate all manual pages. (Bug #12988064)

  • Refactored conditions to use list within the mysqldbexport and mysqldbimport utilities. (Bug #12945167)

  • The mysqldbcopy utility would crash when any of the data contained an apostrophe. (Bug #63145, Bug #13418634)