Changes in MySQL Workbench 5.2.13 (Not released)

This section documents all changes and bug fixes applied since the release of MySQL Workbench 5.2.12.

Bugs Fixed

• Selecting the Help, Check for Updates menu item opened the web browser and displayed an error:

  Not Found
  
  The requested URL /version-check.php was not found on this server.
  Apache Server at wb.mysql.com Port 80

  (Bug #50415)

• When building MySQL Workbench 5.2.11 from source on CentOS 5.4, this error occurred:

  python_context.cpp:388: error: invalid conversion from 'const char*' to 'char*'
  python_context.cpp:388: error:   initializing argument 1 of 'PyObject*
  PyImport_ImportModule(char*)'
  make[4]: *** [python_context.lo] Error 1
  make[4]: Leaving directory `/home/install/mysql-workbench-oss-5.2.11/library/grt/src'
  make[3]: *** [all-recursive] Error 1
  make[3]: Leaving directory `/home/install/mysql-workbench-oss-5.2.11/library/grt'
  make[2]: *** [all-recursive] Error 1
  make[2]: Leaving directory `/home/install/mysql-workbench-oss-5.2.11/library'
  make[1]: *** [all-recursive] Error 1
  make[1]: Leaving directory `/home/install/mysql-workbench-oss-5.2.11'
  make: *** [all] Error 2

  Note, from MySQL Workbench 5.2.13, binary and source packages for CentOS 5.4 will be available. Due to the dependence of MySQL Workbench on certain packages that are older in CentOS 5.4 than in other operating systems, MySQL Workbench has some minor features, such as tooltips, disabled. (Bug #50360)

• In the SQL Editor, if a routine was edited, and the changes applied, the changes were automatically reverted if the apply failed. This meant that any changes the user had made had to be entered again. (Bug #49790)

• In the SQL Editor, if an object was created or renamed, that change was not reflected in the user interface. This change fixes the problem for Linux and OS X. (Bug #49454)

  References: See also: Bug #50424.

• Invalid values were written to the MySQL server configuration file by the configuration editor. MySQL Workbench also added new entries to the configuration file, rather than update the existing entries. As a result of the this the server failed to start. (Bug #49420)

• If the server configuration file contained more than one entry for replicate-do-db, the configuration editor on the Admin tab displayed only the second entry, rather than both. (Bug #49299)

• In the configuration editor in the Admin tab, the lists for displaying units, such as for the Sort buffer size option, did not show 'G', which represents Gigabytes. This bug was fixed in 5.2.10.

  It was subsequently decided to standardize all units around uppercase characters. In particular the 'k' was changed to 'K'. This change was made in version 5.2.13. (Bug #49013)