-
Notifications
You must be signed in to change notification settings - Fork 327
/
ChangeLog
6382 lines (6015 loc) · 347 KB
/
ChangeLog
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
Version 5.2.46 :
================
Functionality Added or Changed:
* New role functionality was added. It is now is possible to add
schemas.*, tables.*, and *.*, and to assign privileges to each
object. Before it was only possible to add individual tables when
defining roles. (Bug #11761640, Bug #54153)
* The auto-completion feature was improved. For example, it now
includes the parsing of aliases and subqueries for SELECT
statements.
Bugs Fixed:
* Microsoft Windows: In an EER Diagram, the circles at each end of a
relationship line were rendered as different sizes. (Bug #12628088,
Bug #54663)
* Closing a table's properties window from within the EER Model
diagram window would crash MySQL Workbench. (Bug #16185134, Bug
#68101)
* An SQL syntax error would be reported when a comment was added to
an INDEX. (Bug #15991038, Bug #67835)
* Functionality (such as Copy to Clipboard) was missing from the
right-click context-menu of the Schema browser when multiple
columns were selected. (Bug #14834245, Bug #67417)
* The Show Filter table listing for Export MySQL Table Objects is now
sorted alphabetically. (Bug #14706782, Bug #66712)
* The Bulk Data Transfer migration step would fail if too many tables
were being migrated, because too many arguments were being passed
to the command-line. This table listing is now saved to a new file
named wb_tables_to_migrate.txt, which is now read during the
migration process. (Bug #14588167, Bug #66611)
* MySQL Workbench could crash (segmentation fault) at startup if a
configuration file was corrupt. (Bug #14622471, Bug #66776)
* Creating a table in a schema that had a "-" in the schema name
would emit an error about an "unknown column", and fail to create
the table. (Bug #14632271, Bug #66815)
* Sometimes the Create Table... dialog in the Object Browser would
emit an error instead of creating the table, after pressing Apply.
(Bug #14520406, Bug #66169)
* On Linux, the right-click context menu would differentiate between
unselected and selected rows, when called from within the SQL
editor results view panel. This menu is now consistent. (Bug
#14539036, Bug #66308)
* Changes to a table that a view referenced would cause an error
while attempting to edit the view. This fix allows MySQL Workbench
to work around the underlying bug, which is MySQL bug #61718. (Bug
#14526308, Bug #66502)
* On Mac OS X, and in the table editor, the schema name was changed
from a dropdown-box to a simple label. (Bug #14456213)
* Right-clicking on a tab name did not show the New Tab, Save tab,
Close other tabs, and Copy path to clipboard options. (Bug
#14171956, Bug #65455)
* Selecting the server engine default within the Alter Table window
would generate an error. (Bug #14076198, Bug #65101)
* On Linux, the Edit, Preferences menu did not wrap properly, and was
too narrow so it would hide (cut) text. (Bug #14070969, Bug #64917)
* On Microsoft Windows, holding down Shift with the Spacebar would
not enter a space. (Bug #13919870, Bug #64820)
* Changes to File, Document Properties for a Model were not detected
or saved by MySQL Workbench. A Save prompt is now generated. (Bug
#13040173)
* On Linux, clicking Apply Changes when the cursor focus was in a
data cell, the data content was not saved. (Bug #12922070, Bug
#62232)
* The EER diagram Arrange, Center Diagram Content option would hide
objects from the diagram. (Bug #12898144)
* If MySQL Workbench crashed when an EER diagram was being created,
after restarting MySQL Workbench the EER diagram would be listed as
"unsaved" but would not open. And it could not be deleted from the
diagram list. (Bug #12642422, Bug #61444)
* After selecting multiple objects and choosing delete, then choosing
keep when prompted to delete or keep the selected objects, the
relationship lines were still deleted. MySQL Workbench now asks if
the relationship columns should be deleted or kept. (Bug #12565850,
Bug #61113)
* Under certain circumstances, synchronizing a database to a model
would remove the mandatory relationships. (Bug #11834230, Bug
#60312)
* Changes made to a database schema while the Database, Synchronize
Model wizard was active, would throw an exception. (Bug #11765036,
Bug #57948)
* On Linux, a warning will now warn you after attempting to close the
SQL Editor when unsaved INSERT changes still exist.
Also, all platforms (Linux, Mac OS X, Windows) are now consistent,
and will also warn you after attempting to close MySQL Workbench
with any unsaved changes. (Bug #11758193, Bug #50363)
* The Default Schema setting was ignored by the Reverse Engineer
Database wizard. (Bug #11757887, Bug #50002)
Version 5.2.45 (2012-12-27):
============================
Functionality Added or Changed:
* Models: Copy, Cut, and Paste options were added to the context menu
(right-click) of the Columns list in the models table editor. These
options can be used between models. (Bug #13029519, Bug #62503)
* A Copy Selected button was added to the Server Status panel of the
Server Administration window. It copies the query of the selected
connection to the clipboard. (Bug #14799336, Bug #66728)
* The Control + / keyboard shortcut was added to comment/uncomment
lines while editing SQL queries. (Bug #14803414, Bug #67002)
* An Import Recordset from CSV File option was added to the SQL
Editor and model insert tabs. This import functionality parses a
file with comma-separated values. (Bug #14079606, Bug #65252)
Bugs Fixed:
* Linux: Right-dragging saved connections, models, and MySQL Server
instances on the home screen could crash MySQL Workbench. (Bug
#14812457)
* Linux: Executing MySQL Workbench from the command-line would print
stdout twice. (Bug #14565095, Bug #66590)
* Mac OS X: The results window from executing an SQL query could be
empty. A workaround was to resize the results window. (Bug
#14520361, Bug #66446)
* Mac OS X: Closing MySQL Workbench after executing and making
changes with the Alter Table tool would not prompt the user with
the save dialog. (Bug #14456136)
* Mac OS X: On Mac OS X, the default column name and column type
model preferences did not function. Note that this feature does not
function on Linux. (Bug #14399236, Bug #66090)
* Mac OS X: The ability to select multiple columns in the models
table editor did not function on Mac OS X. It is now possible to
use Shift, Command, and mouse dragging. (Bug #11766291, Bug #59372)
* Microsoft Windows; Models: After opening and then closing a model
file from the file manager, attempts to open a different model file
would fail to load the model. (Bug #14791573, Bug #67312)
* Microsoft Windows; Models: Model files (*.mwb) would not load MySQL
Workbench after being double-clicked in Windows Explorer. (Bug
#14521111)
* Microsoft Windows: Pressing Control + A in the table editor on a
table field would select all table entities instead of the text in
the field. (Bug #15884658, Bug #67610)
* Microsoft Windows: Clicking on the Schema and Schema Objects column
headers within Server Administration, Data Export would properly
sort in descending order, but would not sort in ascending order
when clicked again. (Bug #15849616, Bug #67518)
* Microsoft Windows: Renaming an EER Diagram would crash MySQL
Workbench. (Bug #14799722, Bug #66818)
* Microsoft Windows: The Enter key would not create newlines within
the table column comment dialogue. (Bug #14829617, Bug #67320)
* Microsoft Windows: Queries surrounded by parenthesis would not
display results in the view tab. (Bug #14651969, Bug #66887)
* Microsoft Windows: Right-clicking on a database name in the schema
browser and choosing Set as Default Schema would add a
strikethrough to the chosen database name. (Bug #14663690, Bug
#66930)
* Microsoft Windows: The Explain button would not display the results
in the Explain tab. (Bug #14702591, Bug #67059)
* Microsoft Windows: The Id and Time columns within the Server
Administration, Server Status, Connections panel would not sort
properly, as they were sorted as ASCII values instead of
numerically.
Additionally, miscellaneous sorting improvements were implemented.
(Bug #14612413, Bug #15953190, Bug #66768, Bug #67786)
* Microsoft Windows: A model would fail to load when opened from the
Microsoft Windows 7 taskbar if a different model was already open.
(Bug #14621880, Bug #66799)
* Microsoft Windows: Control + H did not invoke the replacement
function. (Bug #14520920, Bug #66422)
* Microsoft Windows: After using the schema search filter in the
object browser, right-clicking on a filtered schema would generate
a context menu with invalid options. (Bug #14521006, Bug #66346)
* Microsoft Windows: Find and Replace would not function properly
while using '_' as a replacement character. (Bug #14499088, Bug
#66390)
* Microsoft Windows: The Explain Current Statement option would not
function. A workaround is to manually prepend EXPLAIN to your
query. (Bug #14483518, Bug #66157)
* Microsoft Windows: Control + A would not always select data from
cells in the query results tab. (Bug #13891109, Bug #64723)
* Microsoft Windows: The default plugin directory in the
configuration tab was set as a Linux style path such as "/usr/",
but it is now based on the OS aware BASEDIR value. (Bug #11764440,
Bug #57271)
* MySQL Server 5.6: The SHA-256 Authentication Plugin is now
supported. (Bug #14786561, Bug #67155)
* MySQL Server 5.6: MySQL Workbench would alter the mysql.* system
tables for tasks such as account management, instead of using the
corresponding account manipulation statements. This would conflict
with GTID usage as of MySQL Server 5.6. (Bug #14786531, Bug #67150)
* MySQL Server 5.6: The MySQL 5.6 ALTER USER ... PASSWORD EXPIRE
option is now supported. An expired password indicator, and an
Expire Password button to expire the current password, were added.
(Bug #14786564, Bug #67157)
* MySQL Server 5.6: MySQL Workbench now supports MySQL Server 5.6
configuration options. (Bug #14786556, Bug #67153)
* MySQL Server 5.6: The SQL Editor would emit invalid syntax errors
with MySQL 5.6 queries. For example, GET DIAGNOSTICS queries would
return "syntax error, unexpected IDENT_QUOTED, expecting ':'". (Bug
#14786599, Bug #14786604, Bug #14786615, Bug #67163, Bug #67164,
Bug #67168)
* MySQL Server 5.6: MySQL Workbench would not allow passwords to be
created or changed for user accounts that utilize the SHA-256
Authentication Plugin, which exists as of MySQL Server 5.6.6. (Bug
#14786567, Bug #14786558, Bug #67158, Bug #67154)
* MySQL Server 5.6: The partition count definition was limited to
1-10 as a drop-down selector in MySQL Workbench. This option is now
a text field, which accommodates the 8192 partition limit in MySQL
Server 5.6. (Bug #14786614, Bug #67166)
* MySQL Server 5.6: A DDL related parsing error would be generated
while attempting to update an existing routine that contained a
DateTime variable type with precision. This feature is specific to
MySQL Server 5.6. (Bug #14684874, Bug #14545075)
* MySQL Server 5.6: Creating a standard user with MySQL Server 5.6
would sometimes fail, and emit an error that referred to an unknown
mysql_native_password plugin. (Bug #14574998, Bug #66638)
* MySQL Server 5.6: The MySQL Workbench UI now supports the extended
TIMESTAMP and DATETIME features that MySQL Server 5.6 offers. Both
the initial and on-update values can now be defined for these
types, and the fractional-second granularity is also now supported.
(Bug #67165, Bug #67169, Bug #14786605, Bug #14786616)
* MySQL Server 5.6: All MySQL Server 5.6 system variables were listed
under the Other tab instead of their proper location. For example,
gtid_done is now listed under the Replication tab. (Bug #67170, Bug
#14786569)
* MySQL Server 5.6: Creating a standard MySQL Server 5.6 user account
in MySQL Workbench would fail, and emit an error related to the
msyql_native_auth plugin. (Bug #67151, Bug #14786542)
* MySQL Server 5.6: The creation of a username and password will now
utilize the Password Validation Plugin in MySQL 5.6. This option is
available within the Server Administration section, under the
Security Options tab. (Bug #67152, Bug #67161, Bug #14786551, Bug
#14786626)
* Migration: Migrating a Microsoft SQL Server database would fail if
nvarchar(max) was used. These are now converted to LONGTEXT. (Bug
#14780416, Bug #67289)
* Migration: From within the Manual Editing section of the database
migration procedure, viewing Migration Problems after All Objects
would continue to display information from All Objects. (Bug
#14761792, Bug #67229)
* Migration: Migrating from MySQL Server 5.0 to MySQL Server 5.6
could fail. The migration tool now supports MySQL Server 4.1 and
above as the source database. MySQL Server 5.1 and above are
supported as the target database. (Bug #14647426, Bug #66861)
* Models: Switching from a table column tab to a different tab, and
then back to the column tab, would add an empty column named
"tablenamecol". This empty column would be added to the table
unless Escape was pressed. (Bug #14768685, Bug #67235)
* Models: Model notes could not be saved. The Apply Changes button is
available again. (Bug #14813462, Bug #67211)
* Models: Synchronizing a model with a database could crash MySQL
Workbench by causing a segmentation fault. (Bug #14588524, Bug
#66707)
* Models: While executing the Synchronize Model with Database wizard,
invalid trigger related errors could be emitted even though the
definitions were correct. (Bug #14498358, Bug #65982)
* Models: Forward Engineering a model with users and roles could
generate invalid SQL, because the username was not escaped within
the generated GRANT statements. (Bug #14396930, Bug #66070)
* Models: The File, Import, Import DBDesigner4 Model feature would
fail to function. (Bug #13548113, Bug #63878)
* Models: Sometimes a modified stored procedure would not be flagged
as modified while synchronizing a model. (Bug #13364922, Bug
#62595)
* Models: The ability to open model files from older versions of
MySQL Workbench has been improved. (Bug #12747012, Bug #61703)
* Models: Pressing Cancel in either the Create EER Model from
Existing Database or Create EER Model from SQL Script dialogs would
still open a Model tab. (Bug #11757140, Bug #49145)
* Models: When editing an EER diagram, the Cut context menu option
follows Delete behavior by also deleting the schema object. It will
now only remove it from the EER canvas. And a new Remove option was
added that also only removes an object from the EER canvas. (Bug
#11761492, Bug #53994)
* Under certain circumstances, comments could interfere with the
execution of SQL statements. (Bug #15960066, Bug #67747)
* Saving script files did not function properly with the clipboard.
Content pasted from the clipboard was not saved. (Bug #15837775,
Bug #67462)
* Clearing the output window while a query was running could cause
MySQL Workbench to crash after the query finished. (Bug #15891884,
Bug #67618)
* Having sql_mode set to PAD_CHAR_TO_FULL_LENGTH causes the routine
functionality to fail, as MySQL Workbench is not designed for this
setting. A connection specific sql_mode option was added, and it
can be set from the Advanced tab in the Connection Editor. It
defaults to "". (Bug #14845656)
* The following scenario would crash workbench: open a table, insert
a new row of data, close the table, open a different table via
double-click, then press Save Changes. (Bug #14829570, Bug #67237)
* Added DbMySQLQuery->affectedRows, fixed MySQLResult->firstRow, and
added a Splitter control to the Python binding for mforms. (Bug
#14799403, Bug #66804)
* MySQL Workbench would fail to interpret C-style comments, such as
/*! MySQL-specific code */. For more information about comment
usage in MySQL, see Comment Syntax. (Bug #14807602, Bug #67203)
* Opening a connection using Open connection to Start Querying from
the MySQL Workbench home screen could crash MySQL Workbench. (Bug
#14803527, Bug #67074)
* Procedures were always included in the exported SQL, even if
excluded via a filter or configuration setting. (Bug #14758896, Bug
#66790)
* An error tooltip would sometimes fail to be displayed while
hovering the mouse pointer over an error marker in the SQL editor.
(Bug #14705012, Bug #67067)
* The Select Objects to Forward Engineer filter was ignored while
executing Forward Engineer to Database. All tables were exported.
(Bug #14696609, Bug #67031)
* A model could not be synchronized if a field contained a comment
with a single quote. (Bug #14582241, Bug #66680)
* A crash could occur after switching tables in the EER Diagram tab
while the Privileges was open, or while adding roles to the active
table. (Bug #14645542, Bug #66869)
* The bundled ChangeLog listing was outdated. (Bug #14547966, Bug
#66528)
* In the MySQL Workbench Scripting Shell, an exception is now thrown
while attempting to use input() or read from stdin. (Bug #14520741,
Bug #66452)
* The non-functional comments box was removed from the schema editor.
(Bug #14548126, Bug #66553)
* An exception would be generated when executing Forward Engineer
without a MySQL Server connection. (Bug #14574987, Bug #66648)
* Lower level changes, such as a newly created TRIGGER, would not be
visible after the object browser was refreshed. (Bug #14551801, Bug
#66549)
* The mouse scroll would not function while viewing the Options File
in the Server Administration panel. (Bug #14388344)
* Unlike the Server Administration panel (since 5.2.35), the SQL
Editor did not support syntax that utilized the authentication
plugins. (Bug #14356470)
* The Server Access Management interface would not allow a password
to be set as an empty string. (Bug #14278189, Bug #65739)
* The Limit Connectivity to Hosts Matching option did not allow an IP
with a Subnet Mask because "/" was considered an invalid character.
(Bug #14207793, Bug #65583)
* Having multiple connections with TCP/IP over SSH could cause MySQL
Workbench to not connect when exceeding MaxAuthTries. This may
happen if an encryption type is unknown. The bundled paramiko
library (on Mac OS X, and Windows) was updated to version 1.7.7.1,
which helps solve this problem, as it adds known support for
OpenSSL keys. (Bug #13919914, Bug #64802)
* Multiple instances of MySQL Workbench will no longer open the same
database model file. Doing so caused problems with features such as
auto save and file locking. (Bug #13864687, Bug #64639)
* An SSL connection required a client certificate. (Bug #13851229,
Bug #61266)
* A new General, SQL Editor option was added. Enabling Create new
tabs as Query tabs instead of File (disabled by default) causes new
SQL Editor tabs to default as Query tabs instead of SQL File tabs.
File tabs include additional options, and prompt to be saved when
the tab closed. (Bug #13492434, Bug #14541178, Bug #62929, Bug
#66541)
* Changing a foreign key column to be nullable now deselects the
mandatory checkbox. If all foreign key columns are set to NOT NULL,
then the mandatory checkbox value will be selected. (Bug #13252655,
Bug #62737)
* The Start Command Line Client feature would fail to connect with
SSH connections. (Bug #12612343, Bug #61325)
* A Refresh Rate option was added to the Server Administration,
Server Status window. The refresh rate defaults to "Don't Refresh"
and includes options ranging from 0.5 to 30 seconds. (Bug
#11926869, Bug #60546)
* It was not possible to sort schemas for exporting. (Bug #11926862,
Bug #60566)
* Changes to the DEFINER clause were not detected by the Alter Table
wizard when altering this clause was the only change. (Bug
#11829867, Bug #60164)
* Importing a saved connection that used an SSH tunnel would throw an
exception, and fail to import the connection. (Bug #11765909, Bug
#58922)
* When foreign keys are added, existing indexes are now used instead
of always creating new indexes. (Bug #11760834, Bug #53277)
* Attempting to open MySQL Doc Library while it was already opened
would generate an error. (Bug #11763691, Bug #56432)
* The ALTER ROUTINE functionality would not detect stored procedure
changes when only the case changed. This check was
case-insensitive. (Bug #65277, Bug #14136994)
Version 5.2.44 (2012-09-27):
============================
Functionality Added or Changed:
* Updated the bundled MySQL Utilities to version 1.1.0, which
includes the new mysqluc console.
* Added native migration support for PostgreSQL and Sybase ASE.
Bugs Fixed:
* After right-clicking on a non-empty field in the SQL editor, and
choosing Copy Row Content, pasting the row into an empty row (by
right-clicking and choosing Paste Row) would not increment the row
id when it was appropriate to do so. (Bug #14587186, Bug #66668)
* When a table from Microsoft SQL Server was migrated to MySQL, TEXT
columns were mapped to VARCHAR(16). They are now mapped to LONGTEXT
because Microsoft SQL Server TEXT columns have a maximum length of
2^31 - 1. (Bug #14556732, Bug #66584)
* The MySQL Workbench Data Export feature would fail to recognize
tables that contained accented characters in the table's name. (Bug
#14504342, Bug #66421)
* The object browser would not update the column order after a table
was altered. (Bug #14495629, Bug #66232)
* On Mac OS X systems with the Retina display, the mouse cursor would
register incorrect mouse coordinates. (Bug #14396939, Bug #65607)
* Entering the caret ("^") character inside the SQL editor, followed
by any other character, could cause MySQL Workbench to hang. This
was a Scintilla bug that is now fixed. (Bug #13930994, Bug #64848)
* After choosing Alter Table, pressing Apply would cause MySQL
Workbench to display "Preparing..." in the output panel, but it now
displays "No changes detected." (Bug #13497239, Bug #63604)
* When synchronizing a model to a database after changing a field
definition from NOT NULL DEFAULT x to NULL DEFAULT NULL, the model
synchronization would correctly generate the SQL. But after
executing this SQL and resynchronizing, MySQL Workbench would
report that the table needed to be updated. (Bug #12756728, Bug
#61720)
Version 5.2.43 (2012-09-12):
============================
Functionality Added or Changed:
* The default object/relationship notation for new models will now be
taken from the last notation selected by the user. This is chosen
via Model, Relationship Notation. (Bug #49997, Bug #11757883)
Bugs Fixed:
* It was possible for a custom plugin to cause MySQL Workbench to
crash. (Bug #14595613, Bug #65817)
* After editing and closing an EER diagram, double-clicking on one of
the diagram tables could generate an exception. (Bug #14587490, Bug
#66699)
* MySQL Workbench would sometimes crash at startup due to a race
condition. The logged error included "Invoke or BeginInvoke cannot
be called on a control until the window handle has been created."
(Bug #14526134, Bug #66130)
* Clicking Browse after the Target Creation Options stage of the
database migration wizard would generate an error. (Bug #14520838,
Bug #66271)
* Passing in the -nologo argument while starting MySQL Workbench
would cause a crash. (Bug #14527014)
* Right-clicking and choosing Edit Table Data while multiple schemas
are selected could cause the activity animation icon to remain
active and/or crash MySQL Workbench. (Bug #14524139, Bug #66022)
* A semicolon at the end of a single lined SQL comment would be
treated as a delimiter, and cause the SQL query to not execute.
(Bug #14529811, Bug #66505)
* Dropping multiple objects at the same time was not possible.
Selecting multiple objects, right-clicking on one of the selected
objects, and then choosing the Drop n Object option would generate
SQL that deleted only one of the selected objects. (Bug #14538863)
* Migrating a Microsoft SQL Server table that contained both NULL and
non-null values in a DATETIME column would fail to import properly.
(Bug #14509484, Bug #66359)
* Migrating from a remote SQL Server 2008 database to a local MySQL
database would fail at the Fetch Schemata List stage of the
database migration wizard, as it was unable to connect to the
source database. (Bug #14498549, Bug #66030)
* On Mac OS X, code signing was added to MySQL Workbench so it will
now load when this condition is required. (Bug #14457847, Bug
#66052)
* The object browser did not display foreign keys. A workaround was
to view them via the Alter Table interface. (Bug #14483668, Bug
#66226)
* Objects in the schema tree, such as tables, were not listed
alphabetically after edits were made. (Bug #14483610, Bug #66209)
* Selecting a view in the object browser would sometimes insert the
view into the table listing. (Bug #14483526, Bug #66158)
* On Linux, the mysql-workbench-bin executable is no longer installed
under /usr/bin/ because it cannot be executed directly. It was
moved to /usr/lib*/mysql-workbench/. (Bug #14485725, Bug #66322)
* On Microsoft Windows, MySQL Workbench would crash after attempting
to export a model as a PNG, SVN, or PDF. (Bug #14483735, Bug
#66298)
* On Fedora 17, autoconf would not detect the altlr which is antlr3-C
version 3.4. (Bug #14495924, Bug #66325)
* The database export feature would not always export the correct
databases if some database names were clicked while others checked
the selection checkbox. This feature now only takes into account
the checkboxes. (Bug #14495660, Bug #66376)
* Under certain conditions, synchronizing a model would generate SQL
statements that dropped a schema before altering it. (Bug
#14495165, Bug #66083)
* Right-clicking on a table and selecting Copy Insert Statement would
generate SQL with the columns sorted in alphabetical order. The SQL
is now generated in the order listed in the database. (Bug
#14508845, Bug #66419)
* With the Slovenian keyboard layout chosen, pressing Control + /
would not toggle commenting. (Bug #14504877, Bug #66131)
* Synchronizing a model could crash if the model had an invalid
foreign key. (Bug #14498436, Bug #66020)
* Synchronizing a restored EER model with the Model and Database
Differences, Update Model Only configuration option enabled for all
tables would cause MySQL Workbench to crash. (Bug #14510962, Bug
#66436)
* The Select Schemata step of the Reverse Engineer Database wizard
would not display the underscore character correctly. Instead it
would appear as an underline to the next character. (Bug #14467930,
Bug #66248)
* On Microsoft Windows, the behavior of Control + Enter was changed
back to the previous behavior, which is to execute the statement
that contains the cursor, instead of the last statement in the SQL
editor, or the current statement if the cursor is at the beginning.
(Bug #14396992, Bug #66025)
* After exporting a schema, and unselecting the schema, exporting a
new schema would export both the current and previously exported
schema. (Bug #14388355)
* On a table with a multiple field foreign key, attempts to remove
one of these fields would fail. The associated checkboxes can now
be used with success. (Bug #14415483, Bug #66171)
* Expanding a view object from within the schema viewer would
immediately collapse, and it would only expand with subsequent
attempts. (Bug #14404189)
* A warning message was added when a user attempts to delete an index
that belongs to a foreign key. (Bug #14359329, Bug #65972)
* The default database while applying changes to users and privileges
is now set to mysql. (Bug #14359266, Bug #65959)
* Exporting a table that contained views could fail to export. (Bug
#14359349, Bug #65780)
* The --enable-maintainer-mode autoconf option was not available.
(Bug #14329365, Bug #65900)
* MySQL Workbench could execute queries from the wrong tab after tabs
were moved (reordered). (Bug #14221754, Bug #65557)
* The vertical scrollbar in the table definition window would appear
incorrect after clicking a NN (Not Null) checkbox on one of the
column definitions. (Bug #14221022, Bug #65500)
* Choosing the Edit in New Window context menu on a routine would not
open a new window. (Bug #14171776, Bug #65520)
* On Linux, pressing the Enter key after typing a file name would not
save the file while doing so in the SQL editor file save dialogue.
(Bug #14124900, Bug #64945)
* On Mac OS X, new tabs could not be closed (via the [x]) if ten or
more tabs were already open, and if the total MySQL Workbench
window width exceeded around 1200px. (Bug #14127281, Bug #65186)
* Executing from mysql.utilities.parser import GeneralQueryLog from
within the MySQL Workbench scripting shell would result in an
error. (Bug #14128312)
* The MySQL Export wizard would not escape hardcoded newlines in the
generated SQL, but they are now escaped. For example, a \n now
remains as \n in the exported query, when before it was expanded.
(Bug #14124914, Bug #65222)
* On Linux, tables that are present are now marked with a black point
in the diagram editor. (Bug #14107656, Bug #65210)
* On Mac OS X, hiding a window pane (such as the snippets) would
cause the window pane to remain hidden, even after restarting MySQL
Workbench. (Bug #14017268, Bug #65138)
* The Plugins, Objects, Create Multiple Tables feature did not
function on Microsoft Windows, and only created one table on Linux.
(Bug #14026694, Bug #14026709)
* Exported "Excel Spreadsheet" files were exported with the ".xls"
extension, instead of the ".xml" extension. (Bug #13970552, Bug
#64955)
* MySQL Workbench was unable to edit the lc_time_names variable. (Bug
#13939985, Bug #64880)
* Under certain conditions, MySQL Workbench would generate invalid
SQL when dealing with foreign keys. (Bug #13865784, Bug #14486006,
Bug #64601, Bug #66285)
* While editing a model, right-clicking on a user and choosing Copy
SQL to Clipboard would not function. (Bug #13742855)
* After setting an EER diagram marker, modifying the zoom, and then
setting a marker, the markers would not be created. (Bug #13742896)
* On Linux, the WB_FORCE_SYSTEM_COLORS environment variable was
added. Enabling this variable (with a value of 1) will disable
MySQL Workbench from using its own color scheme. Example usage:
export WB_FORCE_SYSTEM_COLORS=1. This is useful for certain
conditions, like when using the HighContrastInverse or GnomishDark
system themes. (Bug #13608244, Bug #64013)
* MySQL Workbench would yield incorrect results while displaying
results from the MAX function on a bit field. (Bug #13496747, Bug
#63457)
* Table data could not be edited if the primary key was a binary
field. (Bug #13418610, Bug #63198)
* Multiple objects would remain selected after adding a new table
within the Create new EER Model wizard. (Bug #12933282)
* The Forward Engineering wizard did not utilize the Use Default
Schema setting that is set in the Manage Connections configuration
table. (Bug #12757331, Bug #61786)
* Passwords are now removed if they are no longer used by other
connections when a particular connection is deleted. (Bug
#12627613, Bug #61322)
* Deleting a connection would not immediately delete the connection
from MySQL Workbench. (Bug #12642474, Bug #61445)
* The Treat BINARY/VARBINARY as nonbinary character string preference
for SQL Queries did not function. (Bug #12612409)
* When a routine contained CONCAT with a number as an argument, MySQL
Workbench would return it as a BLOB. (Bug #11763872, Bug #56642)
* On Mac OS X, the Server Status tool would fail to find the server.
(Bug #11766286, Bug #59365)
* MySQL Workbench would not export data when using a remote server
connection through SSL with certificates. (Bug #11766196, Bug
#59249)
* On Mac OS X, the window to set up a Standard TCP/IP over SSH
connection contained incorrect descriptions. And the dialogue now
behaves more intelligently. (Bug #11761555, Bug #54061)
* The error icon would continue to be displayed in the SQL editor
after deleting a character to create the error, and then adding it
back. This only affected multiline SQL statements. (Bug #11763319,
Bug #56015)
* The Tab key would not navigate field values in the Set remote
configuration parameters dialogue of the Server Administration
panel. (Bug #11757375, Bug #49413)
* Closing MySQL Workbench while an unsaved model was open would
prompt the user with a "MySQL Workbench has stopped working" error,
with a Close button. MySQL Workbench now prompts to either save or
close. (Bug #61802, Bug #12912241)
* While using the Forward Engineer wizard, any change detected in a
connection option now clears the "Stored connection" field. (Bug
#49921, Bug #11757818)
Version 5.2.42 (2012-08-13):
============================
Bugs Fixed:
* The Reformat DDL for Views configuration option would generate
invalid SQL syntax if the expression contained an even number of
parts that were very long. (Bug #14396953, Bug #66068)
* There was a typographical error in the "Rename" dialogue that
prompts a user to rename unsupported foreign key names that
originate from old model files. (Bug #14399185, Bug #66113)
* The Search on server button would create an additional Search on
server button each time it was pressed. (Bug #14395153)
* Data modeling would not allow table edits, and repeated attempts to
do so would crash MySQL Workbench. (Bug #14374169, Bug #66013)
* After upgrading to MySQL Workbench 5.2.41, MySQL Workbench would
freeze if the initial load involved a connection without a saved
password. (Bug #14383570, Bug #66016)
* MySQL Workbench would sometimes crash after populating a model.
(Bug #14211444, Bug #65423)
* On Microsoft Windows XP, the width of the line number column would
display a maximum of four characters. It now displays additional
characters, such as the number "10000". (Bug #14079497, Bug #65259)
* Undoing the last four changes via the history tab would only undo
the last three changes. (Bug #14026666)
* Entering the caret ("^") character inside the SQL editor, followed
by any other character, could cause MySQL Workbench to hang. This
was a Scintilla bug that is now fixed. (Bug #13930994, Bug #64848)
* On Microsoft Windows, the Enter key would not create newlines
within the table column comment dialogue. This was a Scintilla bug
that is now fixed. (Bug #13891121, Bug #64714)
* On Microsoft Windows, certain conditions would allow the model
overview pane to shrink, and only display a small portion of the
diagram information. (Bug #13877323, Bug #64640)
* Synchronizing a model after adding a column to the model would not
add the new column to the syncronized database. (Bug #13891063, Bug
#63938)
* Models that were temporarily saved as "Unsaved models" could not be
deleted. (Bug #13742833)
* On Mac OS X, attempts to store a password into the keychain could
result in an error. (Bug #13387025, Bug #62279)
* A signal statement in a stored procedure was not supported, and
would report a syntax error. (Bug #11763874, Bug #56644)
* Using \func would prevent the Apply changes to data option to
function, and instead "Pending changes" error message windows would
be displayed. (Bug #62061, Bug #12844298)
* On Ubuntu 12.04 64-bit, MySQL Workbench could freeze. (Bug #65331,
Bug #14120708)
* Expanding the tree view for a database with a large number of
tables (tested 30,000) would crash MySQL Workbench. (Bug #66036,
Bug #14383521)
* In the SQL Editor, the cursor would inappropriately flash. This was
fixed while moving to the native Scintilla control. (Bug #61752,
Bug #12757202)
Version 5.2.41 (2012-07-25):
============================
Functionality Added or Changed:
* Added a new Data Import/Restore option to select the default schema
to import to, and a button to create a new schema in case a dump is
being imported from a single file. (Bug #13539030, Bug #63853)
* A word wrapping option was added to the SQL Editor. (Bug #11765583,
Bug #58566)
* The Diagram object tooltip now displays the column comments. (Bug
#11765060, Bug #57977)
* A Global Privileges tab was added to the Server Administration
interface. It allows adding and editing individual global user
privileges. (Bug #11761628, Bug #54141)
* Basic code completion functionality has been implemented. (Bug
#11760500, Bug #13813099, Bug #52917, Bug #64525)
* The model wizards now remember the last connection that was added.
(Bug #56515, Bug #11763761)
* MySQL Workbench added a migration wizard, which will migrate ODBC
compliant databases to MySQL. (Bug #54731, Bug #11762168)
Bugs Fixed:
* The Search on Server option would not function, and instead it
generated errors when searching MySQL Server 5.1. This option is
now only available when connecting to MySQL Server 5.5 or greater.
(Bug #14404138)
* MySQL Workbench was not compatable with alocal versions greater
than 1.11.1. Compiling would generate errors related to
AC_RUN_IFELSE usage, as opposed to the preferred AC_LANG_SOURCE.
(Bug #14329354, Bug #65898)
* A snippets file could not be created. (Bug #14278287, Bug #65734)
* On Microsoft Windows 64-bit, closing MySQL Workbench from within
the SQL editor could cause a crash. (Bug #14307316)
* The option to control specific user privileges is now available
with MySQL Workbench. Before it was only possible to edit the roles
(e.g., DBManager) but now the specific privileges (e.g., RELOAD)
can also be modified. (Bug #14226955, Bug #65677)
* It is now possible to select a range of rows using the shift key.
And on Mac OS X, the command key will now allow the selection of
individual rows (Bug #14177386, Bug #65569)
* Comments and collation controls are now disabled until a column in
the column editor is selected. Before it was always available, so
invalid entries would attempt to be created, which would result in
an error. (Bug #14177412, Bug #65574)
* MySQL Workbench would not load with Ubuntu 11.10. (Bug #14058886,
Bug #63626)
* An orphaned privileges tab would be shown in the table editor when
switching tables. Now only the current privilege tab is displayed.
(Bug #14102537, Bug #65182)
* The Edit, Find, Find and Replace operation was slow. (Bug
#14079480, Bug #65262)
* Having a schema without a name in a model would cause MySQL
Workbench to crash. (Bug #14017357, Bug #65119)
* Several exposed DbMySQL methods (such as makeSQLExportScript) were
problematic, and have been replaced by the DbMySQLRE and DbMySQLFE
modules. (Bug #13971951, Bug #62596)
* MySQL Workbench would fail to compile with automake 1.11.2 or
greater, due to the pkglib_DATA reference. (Bug #13972001, Bug
#63898)
* Using the '%' character within environment variables could cause
MySQL Workbench to crash. (Bug #13989371, Bug #65056)
* The SQL Beautifier feature would remove DISTINCT from inner
queries. (Bug #13970596, Bug #64932)
* Creating and then synchronizing a table in a model with a DOUBLE
typed column would generate invalid SQL, thus generating an
"Invalid SQL syntax" error. (Bug #13970484, Bug #64990)
* MySQL Workbench would crash while multiple model routines were
opened. (Bug #13970497)
* The SQL Beautifier would delete WITH ROLLUP if it was contained
within a subquery. (Bug #13919924, Bug #64796)
* The Replace All option would not function when the replacement
string was empty. (Bug #13919875, Bug #64818)
* A new Copy Row (tab separated) option was added to the result set
context menu within the SQL editor. A comma separated variant of
this option already existed. (Bug #13884753, Bug #64724)
* Certain conditions would cause privilege related problems and emit
errors such as "Incorrect Value Entered" when creating a table in
one tab, altering it in another, then going back to the original
tab. (Bug #13877873, Bug #64591)
* Passing a grt.classes.db_query_EditableResultset object to
getattr() could cause a crash. (Bug #13893388, Bug #64777)
* On Linux and Mac OS X, it was not possible to select/copy multiple
rows from within the result set grid. (Bug #13895191)
* Input elements are now correctly disabled until an editable row in
the column editor is selected. Therefore, invalid values are no
longer set in the model. (Bug #13812811, Bug #64550)
* Inputting invalid SQL would remain designated as such, even after
the SQL was corrected. (Bug #13820997, Bug #64481)
* Internal log tables are now excluded while exporting a the MySQL
database. The excluded tables are mysql.schema, mysql.apply_status,
mysql.general_log, and mysql.slow_log. (Bug #13837725)
* Using Paste Row after Copy Row Data within the SQL editor would
insert rows with extra apostrophes. For example, 'hello' would
become ''hello''. (Bug #13840070, Bug #64630)
* Closing an SQL Editor tab that had a Find/Replace dialog box open,
then subsequently closing the Find/Replace dialog box would crash
MySQL Workbench. (Bug #13816167, Bug #64569)
* Changing the Default Collation of a schema after changing its name
would reset the schema name to "new_schema". (Bug #13799456, Bug
#64259)
* The Edit table data SQL editor option would not properly display or
save Unicode characters. (Bug #13790645, Bug #64447)
* On Mac OS X, the color dropdown in the object tool would not
display the color properly. It instead showed the color code, and
would not apply the color to the object. (Bug #13742905)
* All editor tabs now prompt to save data when these tabs are closed.
Before, only the main tabs (like the SQL Editor) would prompt for
to save. (Bug #13788071, Bug #64462)
* Opening the Scripting Shell window, followed by selecting then
closing the snippet tab, would cause MySQL Workbench to crash. (Bug
#13744364)
* If Plugins, Utilities, Indent Selected Lines is used while a row is
selected, then MySQL Workbench would delete the selected row. (Bug
#13744346)
* The Match Case search option did not function. (Bug #13790397)
* On Mac OS X, the Option key did not behave like a standard Mac OX
application. For example, Option + Delete would delete one
character instead of one word. (Bug #13702376, Bug #64217)
* Added version dependent keyword list support for syntax
highlighting. Supports MySQL Server 5.0, 5.1, 5.5, and 5.6 (Bug
#13699804)
* On Mac OS X, and while working with mixed-case table names, a
foreign key could not be assigned to link two InnoDB tables
together. (Bug #13639162, Bug #64109)
* Quickly executing the same query multiple times would cause MySQL
Workbench to use an excessive amount of memory and CPU. (Bug
#13642999, Bug #64077)
* After right-clicking on a value in the SQL editor and choosing Open
Value in Viewer, selecting the text would insert extra new lines
into the clipboard. (Bug #13538942, Bug #63753)
* The Model, Model Options, Diagram, Hide Captions option could not
be altered (disabled) and would remain checked (enabled). (Bug
#13571857, Bug #63937)
* MySQL Workbench would allow the creation of multiple foreign keys
across multiple tables but with the same foreign key name.
Synchronization would then emit a "Can't create table" error. (Bug
#13548236, Bug #13500447, Bug #63642, Bug #62960)
* The Object Browser now manages procedures and functions separately,
when before they could not co-exist with the same name. They remain
under the routines group but have separate icons and menu options.
(Bug #13548213, Bug #13730415, Bug #63849)
* Plugins, Utilities, Execute query would freeze MySQL Workbench if
the query resulted in 1000 or more rows. (Bug #13470781)
* The Server Administration, Server logs, General Log Table option
would not function, and only show a Try again button. (Bug
#13530413)
* While editing in the Edit Table tab, Control + A would also select
diagram objects. (Bug #13519852, Bug #63758)
* A "Removed corrupt column definition for Foreign key" error would
sometimes be emitted while editing a table with foreign keys. (Bug
#13519797, Bug #63772)
* OpenGL determination at startup has been disabled, and instead this
check is performed while creating diagrams. The system could fail
at startup, so now MySQL Workbench avoids this startup trouble and
can better fall back to software rendering if necessary.
MySQL Workbench would also silently fail to load if "Microsoft
Visual C++ 2010 Redistributable Package" was not available. This is
now checked and reported to the user. (Bug #13512714, Bug #61969)
* The Open Value in Editor SQL editor option did not work with INT or
NULL values. (Bug #13492493, Bug #62934)
* The Move to a group context option for database connections would
cause saved connections below the target connection (that is being
added to a group) to disappear. (Bug #13470318)
* After synchronizing a database, refreshing a model would not
refresh the stored procedure information. (Bug #13418563, Bug
#62879)
* The info and session tabs within the MySQL connection interface
would not display any information. (Bug #13466537)
* The Options tab within the SQL Editor would always display an empty
AUTO_INCREMENT value for tables using InnoDB. (Bug #13463458, Bug
#63464)
* After making changes to a model, then closing the window, clicking
Cancel on the unsaved changes warning/dialogue would close MySQL
Workbench. Now the model window remains open. (Bug #13463465, Bug
#63460)
* On Mac OS X, Command + A would not select all results from the
result set. (Bug #13463374, Bug #63461)
* A query such as "SELECT * FROM SomeTable PROCEDURE analyse()" would
only work if "limit rows" was disabled in the preferences. The
MySQL Workbench query parsing has been extended to support this
type of query. (Bug #13344686, Bug #62964)
* The MySQL Workbench bug reporting form (MySQL Bugs: Report) did not
allow pasting content into the form. (Bug #13344751, Bug #62928)
* "MariaDB" has been change to "Aria" within MySQL Workbench. (Bug
#13252479, Bug #62903)
* On Microsoft Windows, Server Administration, Server logs, Slow Log
File would display an error instead of showing the slow query log.
(Bug #13026572)
* Routine groups on the diagram was not updated after adding new
routines to the group. (Bug #13029520, Bug #62496)
* Right-clicking on Catalog tree within the Model, Diagram context
would display an empty line. (Bug #13025389)
* MySQL Workbench would crash after clicking EER links and options
multiple times. (Bug #13024949)
* Clicking between routines with different comments would not update
the description editor with information from the selected object.
(Bug #13025359)
* The Connection Method option within the Edit Table Data window was
partially hidden. (Bug #13025670)
* Detection of a connection to the local machine based on the IP
address has been removed. There is now a selection between
localhost, remote host, and db host on the initial New Server
Instance page. Selecting localhost will let the wizard know that it
is local, as otherwise the full path is now required, which for
example allows 127.0.0.1 to be used as a remote host to support
port forwarding. (Bug #12890503, Bug #62119)
* The View, Home option did not function. (Bug #12879850)
* The sorting options within the Inserts Editor window did not
function. (Bug #12884134)
* The MySQL Workbench window can now be resized to 1024x710. (Bug
#12632406, Bug #60762)
* A confirmation dialog was added that warns users about attempts to
edit stub tables, and it describes why these will be ignored by
both synchronization and forward engineering. The dialog includes
an option to either keep editing it as stub object, or to clear the
stub flag and make the table appear in generated SQL. (Bug
#12616360, Bug #61309)
* User Defined Types (UDT) could not be deleted when they were not
referenced elsewhere. (Bug #12671629, Bug #61530)
* The synchronization wizard now allows the possibility to force
synchronization of schemas that are thought to have been renamed.
Otherwise, MySQL Workbench will recreate the schema from scratch.
(Bug #12565644, Bug #61211)
* The EER Diagram zoom feature would not function. (Bug #12346981,
Bug #60807)
* The Partitions tab within the Alter table context menu would not
show all of the available partitions. (Bug #11933015, Bug #60235)
* On Mac OS X, having a large number of databases (1,000+) could
cause performance issues where MySQL Workbench would load in
several minutes, as opposed to a few seconds. (Bug #11869432, Bug
#60420)
* MySQL Workbench would not allow a user to delete a saved server
instance that contained an incorrect password. This incorrect
password can now be deleted. (Bug #11765337, Bug #58295)
* The Synchronize Model operation would use an excessive amount of
memory. (Bug #11762726, Bug #55355)
* MySQL Workbench would freeze while attempting to search and replace
with a large number of strings, such as over 100,000. (Bug
#11762890, Bug #55539)
* A new Model: MySQL preference was added for Forward Engineering and
Synchronization to configure SQL_MODE. (Bug #11761659, Bug #54173)
* The Synchronization wizard has been changed to allow forcing
synchronization of schemas that have the same name but an
unexpected "last known name", which would cause a confusing
scenario of the target database being recreated from scratch. (Bug
#11756969, Bug #48962)
* Under certain conditions, adding a foreign key could generate
invalid SQL code. (Bug #64539, Bug #13872284)
* A crash would occur if trigger code referred to tables in a schema
different from the one where it is contained. (Bug #60041, Bug
#13611382)
* On Mac OS X, MySQL Workbench would crash when changing database
engines if a database included a table with uppercase characters.
(Bug #65376, Bug #14117038)
* The Copy Column Names to Clipboard option could crash MySQL
Workbench. (Bug #64881, Bug #13970600)
* MySQL Workbench now respects case-sensitivity when
lower_case_table_names = 2. (Bug #60618, Bug #11926851)
* Closing MySQL Workbench while editing SQL Scripts will now prompt
the user to save the edits. (Bug #61037, Bug #62959, Bug #12546710,
Bug #13344705)
* The zoom feature (in or out) could cause a fatal error. (Bug
#65247, Bug #14136870)
* On Microsoft Windows, MySQL Workbench would ignore the system's
font setting, but now uses it when MySQL Workbench is initialized.
(Bug #62105, Bug #12872840)
* On Ubuntu 12.04, MySQL Workbench would not load. (Bug #64956, Bug
#14180754)
* MySQL Workbench would sometimes repeat a warning during a
successful action that followed the action with the warning. (Bug
#62454, Bug #13014873)
* Deleting an EER diagram would cause MySQL Workbench to hang. (Bug
#65174, Bug #14102990)
* While editing an EER diagram, and click-dragging the mouse cursor,
the cursor now remains in the same place it was originally clicked.
(Bug #64487, Bug #13813199)
* New or updated trigger content would disappear from the SQL Editor
GUI, as it was required to reopen the table editor to see the
changes. (Bug #65411, Bug #14137775)
* Loading large files (over 100MB) using File, Open SQL Script...
would fail to load the script, and throw an out of memory exception
while halting operation.
Now, MySQL Workbench warns users if a file exceeding 100MB is
attempted to be loaded, and no longer crashes when running out of
memory but instead reports that the file was unable to be loaded.
(Bug #55312, Bug #60780, Bug #61363, Bug #64186, Bug #11762687, Bug
#12339717, Bug #12627645, Bug #13790375)
* If a view contains a row that is too long to be represented as a
table column, it will now be substituted with an alias column in a
placeholder table, similar to how mysqldump behaves. Before it
could generate invalid SQL, and fail to synchronize the model. (Bug
#63807, Bug #13538955)
* Using File, Export, Forward Engineer SQL CREATE Script would remove
delimiters statements if the Omit Schema Qualifier in Object Names
option was selected. (Bug #63742, Bug #13520528)
* MySQL Workbench now uses the MySQL Server limit for maximum comment
lengths while using the forward engineering wizard. Before it would
truncate comments to 60 characters, which was a MySQL Server limit
before version 5.5.3.
From the MySQL Server 5.5.3 changelog: the maximum length of table
comments was extended from 60 to 2048 characters. The maximum
length of column comments was extended from 255 to 1024 characters.
Index definitions now can include a comment of up to 1024
characters. (Bug #62207, Bug #12904170)
* Adding a trigger with the Alter Table, Trigger interface now warns
the user if the inputted trigger statement was invalid. Before,
MySQL Workbench would output "No changes to object were detected."
if the SQL was valid, but without a CREATE TRIGGER statement. (Bug
#61712, Bug #12908810)
* Synchronizing a model would drop, and then re-add, indexes and
foreign keys if the order of these indexes and foreign keys were
different. This could happen because MySQL Workbench would add
UNIQUE indexes in the order added by the user, whereas the MySQL
Server puts them first. (Bug #60230, Bug #11829807)
* When altering a table with uppercase letters in the table name,
MySQL Workbench would automatically convert the table name to
lowercase. (Bug #64072, Bug #13639292)
Version 5.2.40 (2012-05-16):
============================
Functionality Added or Changed:
* The File, Export, Forward Engineer SQL ... wizards now have the
option to use the same configuration settings from the last time
Forward Engineer SQL ... was used. (Bug #34977, Bug #11748058)
* The SQL editor tab now displays the selected database in the
header. (Bug #50932, Bug #11758694)