fix: read WAL-mode SQLite databases (0.4.1)

[copyleftdev]

Bug

The SQLite parser failed on WAL-mode databases with failed to parse sqlite input: ... unable to open database file. Found by dogfooding real on-disk .db files (yfinance, GNOME tracker, webkit) — most production databases default to WAL.

Root cause

The parser loads a DB from its main-file byte image via SQLite's read-only deserialize. A WAL-mode database carries read-version 2 in its file header (byte 19); SQLite refuses to open such an image read-only without the -wal companion — which never travels in a byte stream — returning SQLITE_CANTOPEN. Empirically isolated to byte 19: write=2,read=1 reads fine, read=2 fails.

Fix

The main image of a checkpointed WAL database is itself a complete, valid database. The parser now reinterprets it as legacy (read-version 1) on a private copy and reads its checkpointed state. Read-only — the bytes are never written back, and only byte 19 (which gates reads) is touched.

Verification

Four real WAL databases that returned CANTOPEN now read (tkr-tz 34 rows, cookies 1 row, tracker meta.db 7 rows, …); a non-WAL .sqlite still reads; a genuinely non-SQLite .db (GNU dbm) is still honestly rejected (file is not a database).

Gate

proptest + cargo-mutants 0 missed on sqlite.rs (12 mutants, 9 caught, 3 unviable). New test flips a valid fixture's read-version to 2 (simulating WAL) and asserts the parser still reads it.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@copyleftdev, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 37 minutes and 34 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: d3801340-f54e-4104-9f32-4ed383861c46

📥 Commits

Reviewing files that changed from the base of the PR and between 5c489d8 and 3bd8184.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (3)

• CHANGELOG.md
• Cargo.toml
• crates/ax-normalize/src/parsers/sqlite.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/sqlite-wal

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}