Write Database (SQLite)

How it fits

Typical backends

Caveats

• State lifetimedb_path and table are locked at deploy time (non-mutable). Changing them requires a restart.
• Hard constraintColumn names follow the record's field names. Invalid SQL identifiers fail at startup.
• Hard constraintcreate_table false requires the destination table to already exist with a compatible schema. Missing columns or type mismatches raise on INSERT.
• Fallbackstore_non_atomic_as_json false drops any row that contains a non-atomic field. The dropped row is logged but not retried.
• Parameter interactionbusy_timeout_ms is hot-swappable and re-applied per call. Concurrent readers need a tolerant value to avoid SQLITE_BUSY.
• Hard constraintSQLite is single-writer. Two write_database_sqlite components on the same db_path contend on the writer lock.