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.

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!

back

Follow this topic

Rhys Morgan

Last answered:

March 18, 2021

Posted on:

March 18, 2021

Rollback not reverting DB state after using INSERT INTO

in SQL / The UPDATE Statement - Part II

3 answers ( 0 marked as helpful)

Rhys Morgan

Posted on:

March 18, 2021

Martin Ganchev

Posted on:

March 18, 2021

Andrew Cross

Posted on:

March 18, 2021

Submit an answer

Content

Rollback not reverting DB state after using INSERT INTO

Submit an answer

related questions