Description:
The "Continue SQL script execution on errors (by default)" user preference (under SQL Execution) does not appear in sync with the "Toggle whether execution of SQL script should continue after failed statements" button in the SQL editor. Disabling the preference does not affect the aforementioned button.
Related: The button value is cached. In other words, after toggling the button to off, then closing and reopening workbench, the button is off. Or vice-versa. However, the preference does not change.
Related: MySQL Bug #70809 is related, but it requests additional (different) changes.
How to repeat:
1. Change the preference to disabled (unchecked)
2. Load the SQL editor, and note the button remains selected (checked)
Tested: Windows 7 + WB 6.2.4
Suggested fix:
If preference is disabled:
have button disabled by default
else:
have button enabled by default
However, if the two things (preference and button) are unrelated, then document it as such (but please explain the difference here first).
Note: Not sure how the "cached" behavior should be handled, maybe not cache it at all (and instead rely on the preference)?
