The rollback that only rolled back half of it
I was testing a new screen against the production ERP database: a box comes back from the customer, and the screen has to release the material inside it so it can be scanned into a new order. Two writes, one transaction, and a ROLLBACK at the end so the rehearsal wouldn't leave a trace. The rollback ran. No error. And half of it stayed. The item table was back to its old state. The volume table…
A new screen was tested against the production ERP database. The screen had to release material inside a box so it could be scanned into a new order. Two writes and a rollback were involved, with the rollback intended to leave no trace of the rehearsal. However, the rollback only partially succeeded. The item table returned to its original state, but the volume table did not, as the write had persisted in an explicitly undone transaction.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
