{
  "id": 8293315,
  "title": "The rollback that only rolled back half of it",
  "url": "https://urgent.news/2026/09/18/the-rollback-that-only-rolled-back-half-of-it",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-18T19:14:29.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/pauloantunes/the-rollback-that-only-rolled-back-half-of-it-51dg"
  },
  "original_language": "en",
  "account": "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.",
  "summary": "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…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}