Documentation Home
MySQL Workbench Release Notes
Related Documentation
MySQL Workbench Manual
Download these Release Notes
PDF (US Ltr) - 1.0Mb
PDF (A4) - 1.0Mb
MySQL Workbench Release Notes  /  Changes in MySQL Workbench 5.2  /  Changes in MySQL Workbench 5.2.23 (Not released)

Changes in MySQL Workbench 5.2.23 (Not released)

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

Functionality Added or Changed

  • In the SQL Editor, when more result tabs were generated than could fit into the current panel, it was not obvious how to navigate to those result sets that could not currently be displayed. This could be achieved using the left and right arrow keys, but MySQL Workbench now also includes a spin control to navigate the available tabs. (Bug #52998)

  • The Overview tab in the SQL Editor now supports scrolling of content using the mouse wheel. (Bug #50782)

Bugs Fixed

  • In the SQL Editor, attempting to execute a selection in the SQL Query tab caused all text to be executed, not just the selected text. (Bug #54536)

  • Clicking a table caused MySQL Workbench to produce this error message: 

    MySQL Workbench has encountered a problem
Cannot access a disposed object
Object name: 'DockedWindowPlugin'.

    (Bug #54498)

  • In the SQL Editor, exporting a record set failed if the target path contained an international character. (Bug #54479)

  • In the Inserts tab of the Table Editor, adding a new row and applying changes had no effect. (Bug #54456)

  • In the General tab of Configuration in the Administrator, when the Temp directory option was selected, and a directory was selected using the file browser, MySQL Workbench inserted backslashes rather than forward slashes. If backslashes were used in this location in the configuration file, the server crashed at startup. (Bug #54445)

  • In the SQL Editor, if a table in the Overview tab was double-clicked, the query generated replaced code already entered into the SQL Query tab, resulting in the loss of that code. (Bug #54362)

  • Synchronizing a model with a live database produced incorrect SQL code: 

    ALTER TABLE `mydb`.`table1` AUTO_INCREMENT =  ;

    (Bug #54319)

  • In the SQL Editor, for result set exports to a tab-delimited file, MySQL Workbench added a .CSV file name extension. (Bug #54302)

  • In the SQL Editor, selecting Alter Table from the context-sensitive menu had no effect. (Bug #54283)

  • In the SQL Editor, editing a table with a row highlighted, right-clicking a BLOB column and loading a value from a file resulted in this error: 

    An external component has triggered an exception

    (Bug #54266)

  • Changing the name of a stored procedure in the modeler and saving changes caused an erroneous ';' character to be added to the SQL code sent to the database. That resulted in this error: 

    ERROR 1064: You have an error in your SQL syntax; check the manual that
corresponds to your MySQL server version for the right syntax to use
near ';

USE `911datashop`' at line 1
SQL Statement:
;
USE `911datashop`

    (Bug #54258, Bug #11761738)

  • Clicking the Edit Table Data action item from the Home screen caused MySQL Workbench to crash. (Bug #54230)

  • The forward engineering Omit Schema Qualifier in Object Names option was not correctly applied to some statements in Trigger code. In these cases, the schema name remained in place. (Bug #54222)

  • Clicking external links in the embedded browser launched Internet Explorer rather than the default browser. (Bug #54192)

  • When entering binary data into the Inserts tab for a table, the data was truncated at the first null byte (\0). (Bug #54156)

  • Select All (Control+A) did not work when editing comments for a table or column. (Bug #54154)

  • After a foreign key was created, and the referenced table or column was changed, the change was not reflected in the foreign key, resulting in errors. (Bug #54134)

  • MySQL Workbench crashed if a pinned result tab was refreshed in the SQL Editor. (Bug #54114)

  • The integrated docs web server listened on a fixed port (8811), and was not able to handle the situation where this port may be used by another service, such as another MySQL Workbench instance. (Bug #54104)

  • In the SQL Editor, attempting to create a new schema using Create Schema with a server collation of utf8 - default collation produced SQL that resulted in an error when applied. (Bug #54097)

  • Performing an undo operation in SQL Editor actually resulted in an undo operation in the Modeler. (Bug #54091)

  • The HTTP server thread started by MySQL Workbench to provide documentation to the local web browser listened on all IP interfaces, even though it is intended only for local use. (Bug #54083)

  • MySQL Workbench suffered user interface issues when used on a KDE-based system using a dark theme. (Bug #54083)

  • Database export failed due to a faulty path in the command line: 

    15:42:52 Dumping rma3 (etat_produit)

Running: "mysqldump.exe" --defaults-extra-file=c:\docume~1\user\local
settings\temp\tmp9ypdhd  --no-create-info=FALSE --order-by-primary=FALSE --force=FALSE
--no-data=FALSE --tz-utc=TRUE --flush-privileges=FALSE --compress=FALSE --replace=FALSE
--host=127.0.0.1 --insert-ignore=FALSE --extended-insert=TRUE --user=root
--quote-names=TRUE --hex-blob=FALSE --complete-insert=FALSE --add-locks=TRUE --port=3306
--disable-keys=TRUE --delayed-insert=FALSE --delete-master-logs=FALSE --comments=TRUE
--default-character-set=utf8 --flush-logs=FALSE --dump-date=TRUE --allow-keywords=FALSE
--create-options=TRUE --events=FALSE "rma3" "etat_produit"

Could not open required defaults file: c:\docume~1\user\local

Fatal error in defaults handling. Program aborted

mysqldump: Got error: 1045: Access denied for user 'root'@'localhost' (using password:
NO) when trying to connect

Operation failed with exitcode 2

    (Bug #54067)

  • In the Alter Table dialog of the SQL Editor, if an attempt was made to set the NN flag for a column that did not have it set, an error was generated when the changes are applied. (Bug #53918)

  • When carrying out an Alter Routine operation in the SQL Editor, if a routine was modified, and a statement used that, although syntactically correct, was not permitted in a routine, all modifications were lost when changes were applied. (Bug #53887)

  • An EER Diagram appeared to contain hidden tables. Although the diagram contained 12 tables, when a 'select all' was performed the user was informed that 14 tables were selected. It seemed that certain tables had been resized to be so small as to no longer be visible in the diagram. (Bug #53885)

  • In the Layer Tree panel, if a layer was given a blank name, MySQL Workbench subsequently crashed, rather than warning about the of a blank name. (Bug #53807)

  • Keyboard shortcuts such as Command+C, Command+V, and Command+Z were not useable consistently in all parts of MySQL Workbench. (Bug #53790)

  • Columns defined as BIT appeared as requiring synchronization, even if no changes had been made. (Bug #53747)

  • In the Alter Routine dialog of the SQL Editor, if the Find and Replace dialog was invoked with Control+F, and Control+V was used to paste in some search text, the text was actually pasted into the routine code area. (Bug #53735)

  • MySQL Workbench failed to build from source on Debian Linux. This error was generated: 

    libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I./src -I./src -pthread -DNDEBUG -Wall
-Wwrite-strings -Woverloaded-virtual -Wno-sign-compare -g -O2 -Wextra -Wall -Wno-unused
-Wno-deprecated -c src/template.cc  -fPIC -DPIC -o .libs/libctemplate_wb_la-template.o
In file included from ./src/ctemplate/per_expand_data.h:48,
                 from ./src/ctemplate/template_modifiers.h:69,
                 from src/template_modifiers_internal.h:53,
                 from src/template.cc:61:
./src/ctemplate/template_string.h:88: error: ISO C++ forbids declaration of 'TemplateId'
with no type
./src/ctemplate/template_string.h: In member function 'size_t
ctemplate::TemplateIdHasher::operator()(ctemplate::TemplateId) const':
./src/ctemplate/template_string.h:234: warning: right shift count >= width of type
./src/ctemplate/template_string.h: At global scope:
./src/ctemplate/template_string.h:344: warning: overflow in implicit constant conversion
src/template.cc: In static member function 'static void
ctemplate::Template::AssureGlobalsInitialized()':
src/template.cc:2365: warning: comparison between signed and unsigned integer
expressions
make[5]: *** [libctemplate_wb_la-template.lo] Error 1

    (Bug #53668)

  • In the EER Diagram view, it was not possible to delete a relationship by right-clicking the relationship, then selecting Delete from the context-sensitive menu. (Bug #53659)

  • In the SQL Query tab of SQL Editor, tooltip error messages were still displayed, even after switching to another tab. (Bug #53634)

  • In the Diagram Size dialog, displayed using Model, Diagram Properties and Size, it was possible to set the size to 100 pages by 100 pages, but then click outside this area. This caused a MySQL Workbench Unexpected Error. (Bug #53559)

  • The Document Properties dialog was displayed across two screens in a multiple-screen setup. (Bug #53262)

  • After a default primary key name was set in the Workbench Preferences dialog, the PK flag was not selected as expected in the Table Editor and the column flags could not be selected. (Bug #52578)

  • When synchronizing with a live database, MySQL Workbench did not interpret whitespace in ENUMs correctly. For example, ENUM('image', 'video', 'swf') was seen as different from ENUM('image','video','swf'), causing the live server and model to appear unsynchronized. (Bug #49182)

  • When editing a column in the table editor, pressing Control+Z to undo the edit resulted in a previous operation being undone instead. (Bug #46286)


PREV   HOME   UP   NEXT
Related Documentation
MySQL Workbench Manual
Download these Release Notes
PDF (US Ltr) - 1.0Mb
PDF (A4) - 1.0Mb