Bug #71429 Use Defaults Settings in Model Options is Ignored
Submitted: 20 Jan 2014 16:32 Modified: 18 Jun 2018 17:16
Reporter: Ramunas Geciauskas Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:6.0.8 OS:Windows
Assigned to: CPU Architecture:Any
Tags: default settings, fulltext, INDEX

[20 Jan 2014 16:32] Ramunas Geciauskas
Description:
When adding a new index, if "Model -> Model Options" Target MySQL version setting is different from the global settings, but "Use defaults from global settings" is selected, MySQL Workbench is still not using the default one, and will not provide all the MySQL features for the appropriate MySQL version (e.g. FULLTEXT index will not be available).

For example, Model Options -> Target MySQL Version is set to 5.5, but the "Use defaults from global settings" is selected; the global settings won't be used, and you cannot set FULLTEXT index of any of your tables.

How to repeat:
* Create a new Model.
* Make sure that in "Edit -> Preferences -> Model: MySQL", the "Default Target MySQL Version is set to 5.6
* Go to "Model -> Model Options". Uncheck "Use defaults from global settings" box. In "Model: MySQL" tab, enter 5.5 for the "Target MySQL Version".
* Click OK.
* Open "Model Options" again, and check "Use defaults from global settings". Click OK, without changing anything else (Target MySQL Version will stay at 5.5)
* Create a new table, and add an index.
* Type drop-box will not show the FULLTEXT option (since it will assume it's MySQL 5.5, and not 5.6 as dictated in our global settings)

Suggested fix:
When selecting "Use defaults from global settings" in Model Options window, regardless what is entered in this window should be ignored and the Workbench should use the default (global) settings.
[24 Jan 2014 12:11] Marcin Szalowicz
Thank you for the bug report.
[1 Aug 2016 3:32] John Doe
This defect persists into version 6.3.
[18 Jun 2018 17:16] Christine Cole
Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 8.0.12 release, and here's the changelog entry:

The Use defaults from global settings model option (Model, Model Options
from the menu in the MySQL Model tab) when selected did not override the
target MySQL version (set in Model Options) with the default target
version (set in Workbench Preferences).

Thank you for the bug report.