Historial de Versiones de MySQL Workbench 5.2.26

Bugs fixed:

  • On the Home screen, the saved connections previously listed in the Workspace were no longer visible. (Bug#55484)
  • When a model was synchronized with a live database, CHAR(n) columns were always synchronized as CHAR(1). (Bug#55334)
  • Importing a DBDesigner model caused MySQL Workbench to crash. (Bug#55300)
  • In the Synchronize Model with Database wizard, the list of schemata was not drawn correctly on theSelect Schemata page, if Back was clicked from the Fetch Object Info page. (Bug#55174)
  • Complex queries with multiple newlines did not fit well in the Action column of the Output tab of the SQL Editor. This prevented any query error messages from being read. (Bug#55117)
  • In the Reverse Engineer Database wizard, if a pattern mask was used to filter tables being imported, MySQL Workbench subsequently crashed. (Bug#55076)
  • Configuration variables in the my.cnf file that contained an underscore character were not displayed in theConfiguration section of the MySQL Workbench Administrator. (Bug#54933)
  • MySQL Workbench crashed if minimized while loading a model. (Bug#54918)
  • In the Overview tab of the SQL Editor, if there was a large number of schemata, and an attempt was made to use the arrow buttons in the interface to scroll through them, then MySQL Workbench crashed, usually on the last schema in the list. (Bug#54891)
  • When using the SQL Editor and issuing a query containing SQL_CALC_FOUND_ROWS and a subsequentFOUND_ROWS() call, FOUND_ROWS() returned zero instead of the number of matching rows without a LIMITapplied. (Bug#54868)
  • MySQL Workbench would not compile on RHEL 5. This was due to the calls to the function set_opacity inlibrary/form/gtk/src/lf_utilities.cpp (line 661) and library/forms/gtk/src/lf_popup.cpp (line 64). The set_opacity function was not available in GTK 2.10. (Bug#54844)
  • Multi-statement syntax did not work in the SQL Editor. If the delimiter was set to a character other than the default semi-colon, then the semi-colon should still have been recognized as a valid delimiter for multi-statements, but in the SQL Editor it was not. (Bug#54831)
  • In the SQL Editor, if a column's comment contained a Chinese word, then in the Object Browser, if the context-sensitive menu item Send to SQL Editor, Create Statement was selected, incomplete script code was sent to the SQL Query tab. (Bug#54822)
  • When a model was forward engineered to a database, insert statements associated with binary data were not present in the generated code. As a result, binary data was not forwarded to the database. (Bug#54680)
  • In an EER Diagram the circles at each end of a relationship line were drawn in different sizes. (Bug#54663)
  • When forward engineering a SQL ALTER script, the generated code attempted to recreate all foreign keys. (Bug#54363)
  • In forward engineering a model to a database, the PRIMARY index was not reordered correctly when columns were reordered. (Bug#54176)
  • When zooming in and out of the EER Diagram view, MySQL Workbench generated an unknown error. (Bug#52829, Bug#55390)
  • After creating a server instance and double-clicking it on the Home screen, the Administrator took an excessively long time to load (over 10 minutes). (Bug#52530)
  • MySQL Workbench crashed when executing LOAD DATA LOCAL INFILE as a query in the SQL Editor. (Bug#49694)