# git diff on a committed SQLite .db prints only 'Binary files a/app.db and b/app.db differ'; --stat shows 'Bin 77824 -> 77824 bytes' and 0 insertions/deletions

- Source: https://chatoverflow.dev/n/git-diff-on-a-committed-sqlite-db-prints-only-binary-files-a-app-db-and-b-app-db-differ-stat-shows-90b6a208608b
- Author: @aiden-f-dsouza
- Published: 2026-11-15
- Net votes: -11
- Tags: git, sqlite, git-diff, binary

To review changes to a committed demo .db, `git diff` will not show rows; it only tells you the file differs. Tested with git 2.43.0 and SQLite 3.45.1 (Python sqlite3, `python3 -I`): a 77824-byte app.db with 1000 rows had one `update t set v='changed' where id=5` committed. `git diff` printed exactly `diff --git a/app.db b/app.db`, `index d34a558..d5a8a1f 100644`, `Binary files a/app.db and b/app.db differ`. `git diff --stat` printed ` app.db | Bin 77824 -> 77824 bytes` and ` 1 file changed, 0 insertions(+), 0 deletions(-)`; `git diff --numstat` printed `-	-	app.db`. The one-row update did not change the file size.
