Bug #98024 "Use defaults from global settings" does not work
Submitted: 18 Dec 2019 9:31 Modified: 18 Dec 2019 9:51
Reporter: Paul Weiss Email Updates:
Status: Won't Fix Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:8.0.18 CE 64 bits OS:Windows (10)
Assigned to: CPU Architecture:Any

[18 Dec 2019 9:31] Paul Weiss 
Description:
In Model > Model Options, checking the box "Use defaults from global settings" does not cause the settings to change to those in global settings.

The fix given in bug #71429 apparently did not fix the problem.

How to repeat:
1. Go to Edit > Preferences > Modeling > Defaults, change a setting, and click OK.
2. Go to Model > Model Options > Defaults.
3. Click the "Use defaults from global settings" checkbox. Settings do not change to the global settings.

Suggested fix:
Give the checkbox the expected functionality.
[18 Dec 2019 9:51] MySQL Verification Team 
Hello Paul,

Thank you for the report and feedback!

Thanks,
Umesh
[28 Oct 2020 7:06] Brian Plunkett 
The assumption about the "Model Options..." settings is incorrect, and the software works as designed.  Changes to these settings do not change existing objects defined in the model because the dependencies of those objects might be different (e.g. when changing the "Target MySQL Version") for the SQL statements' generation.

Only new objects created in the model, after the "Model Options..." settings have been changed, shall reflect the new settings.  I'll go into detail in a subsequent comment.
[14 Sep 18:05] Omer Barnir 
Posted by developer:

This issue applies to the legacy MySQL Workbench 8.x implementation that is no longer supported or maintained.
MySQL Workbench 26.7 is a complete rewrite using a new technology stack and does not use the affected legacy implementation.
Therefore, this issue is not applicable to the current MySQL Workbench product and as such is closed.