Bug #66340 "Rename" functionality does not differ from "Ignore" in "Fix Index Names" dialog

Submitted: 12 Aug 2012 21:41 Modified: 27 Sep 2013 3:26
Reporter: Brant Gurganus Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:5.2.41 CE OS:Windows (8 Consumer Preview)
Assigned to: CPU Architecture:Any

[12 Aug 2012 21:41] Brant Gurganus 
Description:
The "Rename" functionality does not appear to do anything different from "Ignore" in the "Fix Index Names" dialog.

How to repeat:
1. Open a workbench file with index names same as foreign key names.
2. Choose "Rename" in "Fix Index Names" dialog.
3. Observe you are just shown the main tab as if you opened any other workbench file. You aren't even on a screen where you can rename.
4. Close the workbench file.
5. Observe that you are not prompted to save any behind the scenes automatic renaming.
6. Open the workbench file. Observe that you are still prompted to fix index names so no silent behind the scenes renaming was done and saved.
7. Choose the "Ignore" option in "Fix Index Names" dialog.
8. Observe no difference in behavior compared to "Rename" earlier.

Suggested fix:
When the "Rename" option is selected, bring up a user interface where the conflicting names are shown and the user can rename them as necessary.
[12 Aug 2012 21:45] Brant Gurganus 
It appears that automatic renaming does occur, but it is not setting the save-prompt-on-close functionality to be enabled.
[17 Aug 2012 13:03] Alfredo Kojima 
Thank you for the bug report, the not marking of the model as dirty is indeed an issue.
[27 Sep 2013 3:26] Philip Olson 
Fixed as of MySQL Workbench 6.0.5, and here's the changelog entry:

The "Rename" functionality, from within the "Fix Index Names" dialog, did
not report that the rename operation was successful.

Thank you for the bug report.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.039 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.