Transactions & Safe Edits

From SQL Editor, use Transaction Sandbox when you need to test a write flow safely before committing.

QuraMate generates a guided template with:

• BEGIN; (or BEGIN TRANSACTION; on SQL Server)
• A preview block that estimates affected rows for UPDATE ... WHERE ... and DELETE ... WHERE ...
• Your mutation block
• Safe finalize step with ROLLBACK; (or ROLLBACK TRANSACTION;) and optional COMMIT

Use this sequence every time:

1. Run the preview affected rows block first.
2. Verify impacted rows and filter scope (WHERE clause).
3. Run the mutation inside the same transaction.
4. Keep ROLLBACK for dry-run until data checks pass.
5. Switch to COMMIT only when verification is complete.

Transaction keywords are aligned per engine:

• PostgreSQL / MySQL / MariaDB style: BEGIN;, COMMIT;, ROLLBACK;
• SQL Server style: BEGIN TRANSACTION;, COMMIT TRANSACTION;, ROLLBACK TRANSACTION;

• Prefer scoped writes with explicit primary key or narrow predicates.
• If no WHERE exists, stop and validate intent before running.
• Keep read-only during exploration, then escalate to write only for the final execution window.