workbench-en.a4
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
MySQL Workb<strong>en</strong>ch Change History<br />
This section docum<strong>en</strong>ts all changes and bug fixes that have be<strong>en</strong> applied since the release of 5.0.24.<br />
Bugs fixed:<br />
• If the user closed all tabs and th<strong>en</strong> quit, Workb<strong>en</strong>ch crashed. (Bug#39346)<br />
• Foreign keys refer<strong>en</strong>cing a deleted table were not removed. (Bug#39150)<br />
• FORWARD ENGINEER SQL CREATE SCRIPT and FORWARD ENGINEER SQL ALTER SCRIPT g<strong>en</strong>erated scripts that did not put<br />
index names in quotes. (Bug#39140)<br />
• Wh<strong>en</strong> Workb<strong>en</strong>ch was started with the GRT Shell tab op<strong>en</strong>ed, the object tree in the GRT TREE pane was not displayed.<br />
(Bug#39122)<br />
• Wh<strong>en</strong> triggers were exported with the GENERATE DROP TABLES STATEMENTS option checked, DROP TRIGGER IF EX-<br />
ISTS did not appear in the exported SQL. (Bug#39119)<br />
• The TRIGGERS tab would always <strong>en</strong>able Insert mode wh<strong>en</strong> op<strong>en</strong>ed. (Bug#39118)<br />
• In the FOREIGN KEY tab of the TABLE EDITOR, the dropdown m<strong>en</strong>u that is displayed on clicking in the REFERENCED TABLE<br />
column, listed table names by creation date, rather than by sorted name. (Bug#38944)<br />
• If any DEFAULT properties were defined for a model, they appeared to be lost after saving the model and restarting Workb<strong>en</strong>ch.<br />
(Bug#38825)<br />
• Wh<strong>en</strong> you loaded a UTF-8 <strong>en</strong>coded script file into Workb<strong>en</strong>ch, the embedded SQL editor replaced international characters with<br />
the ? symbol. (Bug#38783)<br />
• Wh<strong>en</strong> creating Views and Routines, the <strong>en</strong>try in the UNDO HISTORY window showed “Parse MySQL View” instead of “View<br />
Created”, and “Parse MySQL Routine” instead of “Routine Created”.<br />
Wh<strong>en</strong> subsequ<strong>en</strong>tly undoing this operation the correct text was displayed. Performing a redo th<strong>en</strong> resulted in the incorrect text<br />
being displayed again.<br />
Additionally, wh<strong>en</strong> undoing a Routine Group, the previous undo action in the history was incorrectly r<strong>en</strong>amed and the last <strong>en</strong>try<br />
in the history was deleted. (Bug#36047)<br />
• In the TABLE EDITOR tab, wherever data could be <strong>en</strong>tered, such as in the FOREIGN KEY NAME <strong>en</strong>try field, the default wrap<br />
protocol was to go to a new line. This resulted in text that was only partially visible. (Bug#34510)<br />
• The synchronization wizard could show a diff tree for schemata differ<strong>en</strong>t from those that had be<strong>en</strong> selected. (Bug#32365)<br />
A.2.7. Changes in MySQL Workb<strong>en</strong>ch 5.0.24 (12th August 2008)<br />
This section docum<strong>en</strong>ts all changes and bug fixes that have be<strong>en</strong> applied since the release of 5.0.23.<br />
Functionality added or changed:<br />
• In the MySQLGrtShell.exe program the VALUES tab has be<strong>en</strong> r<strong>en</strong>amed to GRT TREE. However, the GRT TREE tab only<br />
shows a root node because there is no GRT Tree loaded wh<strong>en</strong> the Shell is started in standalone mode. (Bug#35052)<br />
Bugs fixed:<br />
• Indexes listed wh<strong>en</strong> the INDEX tab was selected could not be deleted if the index type was FOREIGN. (Bug#38639)<br />
• Wh<strong>en</strong> the m<strong>en</strong>u item MODEL, VALIDATION, VALIDATE ALL was selected, and an error dialog subsequ<strong>en</strong>tly displayed, the dialog<br />
error message had a missing dot separator betwe<strong>en</strong> the database name and table name. (Bug#38632)<br />
• Wh<strong>en</strong> a DBDesigner 4 model that contained duplicate relationships was imported into Workb<strong>en</strong>ch, and th<strong>en</strong> exported, the resultant<br />
script would fail wh<strong>en</strong> executed on MySQL server. (Bug#38488)<br />
• It was not possible to synchronize a model to an external database, if the model contained triggers. (Bug#38436)<br />
• Wh<strong>en</strong> resizing the comm<strong>en</strong>t column under PHYSICAL SCHEMATA view in column format, the column resize was reverted wh<strong>en</strong><br />
switching betwe<strong>en</strong> schemas. (Bug#38431)<br />
87