+++
title = "[TRIAGE] Local dev config: Turso (file SQLite) vs D1 binding selection strategy"
priority = 8
status = "todo"
ticket_type = "task"
dependencies = ["f3dc74"]
+++

<context>
This is a triage decision ticket. It must be resolved before dependent implementation tickets can proceed.
</context>

<question>
Local dev config: should the API use Turso (file-backed SQLite via libsql) or a D1 binding (via wrangler dev) for local development? How is the selection made at runtime?
</question>

<options>
1. **Turso/libsql** — lightweight local SQLite file, no Cloudflare account needed. Connection string via env var. SQLx-compatible.
2. **Wrangler D1 local** — `wrangler dev` spins up a local D1 emulator. Closer to production but requires wrangler and a Cloudflare account even locally.
3. **Plain SQLite via sqlx** — use sqlx's SQLite driver with a local file. No Turso dependency needed for dev.
</options>

<resolution>
1. Research the options above and choose the best approach for this project.
2. Update ticket a5049d (database connection module) and ticket af56a7 (local dev docs) with the chosen strategy.
3. Mark this ticket done with a note on the chosen approach in the body or a comment.
</resolution>

<commit>
`chore(quotesdb): resolve triage — local-dev-config-turso-file-sqlite-vs-d1-binding-selection-s`
</commit>