Hi, I'm having an issue with Rollback statement - I have double checked that the Safe Update setting is de-selected, and I've restarted the Workbench several times, but Rollback still doesn't seem to revert the state of the DB after I run an 'insert into' statement. The order I run the statements is: 1. Commit 2. Insert into 3. rollback I expect rollback to revert to the state of db before I ran the Insert command, but my changes remain. Is there another setting aside from Safe Updates that is causing this? I read online that Insert statement may auto-commit, but I'm not sure if this is what Safe Updates is supposed to prevent? thanks for your help.

Hi Rhys! Thanks for reaching out. Thank you for sharing this with the Community! An alternative solution may be to make sure you have not clicked the following buttons in Workbench and that they appear like this: Good luck and please feel free to post another question should you encounter any difficulties. Thank you. Hope this helps. Best, Martin

UPDATE: I just found the solution - in Edit > Preferences > SQL Execution, un-check the 'New connections use auto commit mode' option. This seems to force a commit after every executed query.

Yeah I found that I had to execute something like SET autocommit=0; Valuable lesson, and luckily it was only with a toy dataset and on a duplicate table!

Hi Andrew! Thanks for reaching out. This is indeed an alternative solution, thank you very much for sharing it with the Community. Also, yes, it is very important to gain a significant amount of practice on fabricated or test datasets prior to start working with real datasets. Particularly when this regards database administrative tasks. Nevertheless, you may encounter similar autocommit issues in future coding in SQL, so it is great to have learnt how things work in this matter. Hope this helps. Kind regards, Martin