Bug #86602 | loss of data | ||
---|---|---|---|
Submitted: | 6 Jun 2017 9:25 | Modified: | 6 Jun 2017 10:25 |
Reporter: | Hannah Fraser | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Workbench | Severity: | S1 (Critical) |
Version: | 6.0.8.11354 | OS: | Ubuntu (LTS 14.04) |
Assigned to: | CPU Architecture: | Any | |
Tags: | data loss |
[6 Jun 2017 9:25]
Hannah Fraser
[6 Jun 2017 10:25]
MySQL Verification Team
Hello Hannah Fraser, Thank you for taking the time to report a problem. Unfortunately you are not using a current version of the product(6.0.8 was released almost 4 years ago and 6.3.9 is the latest WB version) you reported a problem with -- the problem might already be fixed. Please download a new version from http://www.mysql.com/downloads/ If you are able to reproduce the bug with one of the latest versions, please change the version on this bug report to the version you tested and change the status back to "Open". Again, thank you for your continued support of MySQL. From the problem description I suspect that default mode in Preferences: SQL Editor: SQL Execution for "Leave autocommit mode enabled by default" is un checked and thus causing data not to be stored. Please could you confirm if this is the case https://dev.mysql.com/doc/workbench/en/wb-preferences-sql-editor.html Also, if it is enabled by default and still you see data loss then could you please confirm if autocommit settings of your server causing this in your case https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_autocommit regards, Umesh