---
source: https://iinventedlight.com/library/notes/sqlite-transactions.md
title: "SQLite transactions, savepoints and isolation"
license: CC-BY-4.0
license_url: https://creativecommons.org/licenses/by/4.0/
source_license: "Public domain (sqlite.org); prose restates cited source lines"
attribution: "Summary by iinventedlight (AI-assisted). Sources: SQLite (sqlite.org), Transaction, Public domain (sqlite.org); SQLite (sqlite.org), Isolation In SQLite, Public domain (sqlite.org)."
author: "iinventedlight (synthesis of cited sources); text drafted with AI assistance"
date: 2026-11-04
status: published
checked_on: 2026-11-04
as_of: 2026-11-04
confidence: medium
untested: "No code was run for this note; only the fetched documentation pages were read."
category: coding-references
topic_area: "code-ai-eng: SQLite"
tags: sqlite, transactions, isolation, wal
sources:
  - id: S1
    title: "Transaction"
    publisher: SQLite (sqlite.org)
    url: https://www.sqlite.org/lang_transaction.html
    accessed: 2026-11-04
    license: "Public domain (sqlite.org)"
  - id: S2
    title: "Isolation In SQLite"
    publisher: SQLite (sqlite.org)
    url: https://www.sqlite.org/isolation.html
    accessed: 2026-11-04
    license: "Public domain (sqlite.org)"
---
# SQLite transactions, savepoints and isolation

## Short answer
Every SQLite read or write happens in a transaction. Without `BEGIN`, each statement gets its own automatic transaction, committed when it finishes. COMMIT` (or ROLLBACK); use `SAVEPOINT` for nesting. Transactions are serializable. [S1][S2]

## Key points
- Readers on other connections see only committed work, never partial changes. [S2]
- WAL mode allows readers and a writer at the same time. [S2]

## Claims
- id: C1
  claim: No reads or writes occur except within a transaction.
  source: S1
  evidence: "No reads or writes occur except within a transaction."
- id: C2
  claim: Use SAVEPOINT and RELEASE for nested transactions.
  source: S1
  evidence: "For nested transactions, use the SAVEPOINT and RELEASE commands."
- id: C3
  claim: Uncommitted changes by the writer are invisible to readers.
  source: S2
  evidence: "by the writer that have not been committed are invisible to the reader."
- id: C4
  claim: WAL mode permits simultaneous readers and writers.
  source: S2
  evidence: "WAL mode permits simultaneous readers and writers."

## Sources
- [S1] Transaction. SQLite (sqlite.org). https://www.sqlite.org/lang_transaction.html . License: Public domain (sqlite.org). Accessed 2026-11-04.
- [S2] Isolation In SQLite. SQLite (sqlite.org). https://www.sqlite.org/isolation.html . License: Public domain (sqlite.org). Accessed 2026-11-04.

License: this note is CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Summary by iinventedlight (AI-assisted).
