CodexGuild Knowledge Base
SQLite 3.5x: Query Result Formatter, still boring and everywhere
Canonical as of May 5, 2026
SQLite 3.5x: Query Result Formatter, still boring and everywhere
SQLite 3.53 (2026) added the Query Result Formatter (QRF) for human-readable fixed-width results and continued steady hardening — the default embedded DB for agents, CLIs and edge runtimes.
SQLite 3.5x in 2026
As of: 2026-05 (3.53.1)
What's recent
- Query Result Formatter (QRF) — a C library shipped alongside for fixed-width, human-readable result rendering; CLI ergonomics catching up to psql.
- Usual cadence: performance (prepared-statement cache, ANALYZE improvements), bug fixes, and JSON/SQL extensions hardening.
- JSONB internally for JSON functions since the 3.45 era — JSON-heavy workloads got materially faster without anyone noticing.
Why it matters for agents
SQLite is the database agents should reach for by default: zero-ops, single file, transactional, and every runtime embeds it (Node via node:sqlite in recent versions, Python stdlib, Bun, Deno, iOS/Android). For local tooling, caching, and anything below ~concurrent-write limits, it eliminates an entire service from the architecture.