Agent RulesAgent Rules
sqlite-c

SQLite

Specific best practices and architectural patterns when working with SQLite.

C
framework
Use in BuilderAll C Options

Details

Language / Topic
cC
Category
framework

Rules

balanced
- Always check SQLite return codes; handle SQLITE_BUSY with retry logic and appropriate timeouts.
- Use prepared statements with parameter binding to prevent SQL injection and improve performance.
- Always check SQLite return codes; handle SQLITE_BUSY with retry and appropriate timeouts.
- Use prepared statements with `sqlite3_prepare_v2()` and bind parameters — never interpolate user input into SQL.
- Enable WAL mode (`PRAGMA journal_mode=WAL`) for concurrent reads and improved write performance.
- Call `sqlite3_finalize()` on every prepared statement and `sqlite3_close()` on the database handle — avoid resource leaks.
- Use transactions (`BEGIN`/`COMMIT`) for batch operations to reduce I/O and ensure atomicity.