Bug #56159 safe mode toggle requires restart
Submitted: 20 Aug 2010 21:11 Modified: 10 Nov 2010 14:40
Reporter: [ name withheld ] Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.2.26 OS:Any
Assigned to: Alfredo Kojima CPU Architecture:Any

[20 Aug 2010 21:11] [ name withheld ]
Description:
The safe updates preference (forbid update and delete...) does not toggle to off unless WB is restarted.

How to repeat:
1. Execute a truncate query
2. it fails in safe mode
3. disable safe mode
4. execute a truncate query
5. it fails again
6. restart workbench
7. truncate query succeeds

Suggested fix:
Either change the UI to suggest a restart following the preference change, or make the pref change not require a restart.
[23 Aug 2010 16:52] Johannes Taxacher
actually restarting the current query instance should suffice for the change to take effect, but still this should be announced by the app.
[26 Oct 2010 22:24] Alfredo Kojima
A note about the reconnection requirement has been added to the option and its tooltip
[9 Nov 2010 13:37] Johannes Taxacher
fix confirmed in repository
[10 Nov 2010 14:40] Tony Bedford
An entry has been added to the 5.2.30 changelog:

The safe updates option on the SQL Editor tab of the Preferences dialog required MySQL Workbench to be restarted to come into effect.