SQLite best practices for Go — WAL mode, foreign_keys, busy_timeout, SetMaxOpenConns, context-aware queries, transactions, migrations
98
99%
Does it follow best practices?
Impact
97%
2.36xAverage score across 5 eval scenarios
Passed
No known issues
A freelancer wants a command-line expense tracker written in Go that uses SQLite to store financial records locally. The tool should work entirely offline.
The tool needs to support:
Each expense has: id, amount_cents (integer), category, description, date, created_at.
Each income has: id, amount_cents (integer), source, date, created_at.
The amount should be stored as integer cents internally but accepted as decimal dollars from the user (e.g., "42.50" becomes 4250 cents).
Produce:
main.go -- CLI entry point with subcommandsdb.go -- Database setup and migrationsexpenses.go -- Expense CRUD operationsincome.go -- Income CRUD operationsgo.mod -- Module fileThe code should be complete Go with no placeholders or TODO comments.
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
skills
sqlite-go-best-practices
verifiers