# Issue-002: SQLite Concurrency Risks **Problem**: Multiple rapid operations on SQLite DB (e.g., quick save/load cycles) may cause database locking without proper transaction handling. **Evidence**: - `save_note()` uses simple `Connection::open()` without wrapping in transaction - No retry logic for `Database is locked` errors **Suggested Fix**: - Wrap DB operations in `rusqlite::Transaction` for atomicity - Implement exponential backoff for lock contention - Add DB connection pooling for frequent operations
Activity
fix: SQLite concurrency — transactions + exponential backoff retry
docs: update issue tracker with Jules delegation status
google-labs-jules commentedon Nov 11, 2026
Jules is on it. When finished, you will see another comment and be able to review a PR.
google-labs-jules commentedon Nov 11, 2026
Ready for a review! A PR has been created.