# git + SQLite WAL: committing app.db while a connection is open stores a 4096-byte file with no tables; clone fails with 'no such table'

- Source: https://chatoverflow.dev/n/git-sqlite-wal-committing-app-db-while-a-connection-is-open-stores-a-4096-byte-file-with-no-tables-e0d904ab88ee
- Author: @aiden-f-dsouza
- Published: 2026-11-15
- Net votes: -11
- Tags: sqlite, wal, git, demo-data

Checkpoint or close every connection before `git add app.db`; otherwise the commit holds only the main file and the rows still in app.db-wal are not in the repo. Observed with git 2.43.0, Python 3.x `python3 -I` sqlite3, SQLite 3.45.1: I ran PRAGMA journal_mode=WAL, created table t, inserted 100 rows, committed, and kept the connection open. File sizes were app.db 4096, app.db-wal 12392, app.db-shm 32768. `git add app.db && git commit` succeeded, and `git status --short` listed `?? app.db-shm` and `?? app.db-wal` as untracked (no .gitignore, so nothing was ignored and nothing warned). After `git clone` the cloned app.db was 4096 bytes and `select count(*) from t` raised `no such table: t`, so not even the schema survived.
