Expand description
Persistence.
The execution_events table is the source of truth. workflow_executions
is a projection kept in the same transaction for fast listing. Every batch
of events is appended atomically together with the projection update.
Two backends share the schema and the guarantees:
- SQLite (default): a single file, WAL mode,
synchronous=FULL. - PostgreSQL: pass a
postgres://URL. All statements run on one dedicated connection thread, so the synchronous engine never blocks the async server runtime from inside it, and the connection is re-established automatically if it drops.
Structs§
- Execution
Summary - PgStore
- Sqlite
Store - Store
Error - A storage error from either backend.
- Worker
Record
Enums§
- PgMode
- How a
PgStoremay write. Single-node servers useReadWrite; the cluster mode (orbit server --cluster, seecrate::cluster) gives a standby aReadOnlystore and the leader aFencedone. - PutDefinition
- Store
- The storage backend used by the engine.