Group related write operations in a single transaction so they commit or roll back atomically.
A partial failure mid-sequence leaves the database in an inconsistent state that is hard to detect and recover from.
BeforeMerge scans your pull requests against this rule and dozens more. Get actionable feedback before code ships.
When a single logical operation spans multiple statements (debit one row, credit another), a crash or error between them leaves data half-written and inconsistent. A transaction makes the group atomic: all changes commit together or none do.
-- Bad: a failure after the first UPDATE leaves balances wrong
UPDATE account SET balance = balance - 100 WHERE id = 1;
UPDATE account SET balance = balance + 100 WHERE id = 2;-- Good: atomic — both succeed or both roll back
BEGIN;
UPDATE account SET balance = balance - 100 WHERE id = 1;
UPDATE account SET balance = balance + 100 WHERE id = 2;
COMMIT;