Expand description
Shared SQLite execution types for local and remote depot client backends.
Structs§
- Exec
Result - Execute
Result - Page
Bytes - Shared immutable bytes for one SQLite page version.
- Query
Result
Enums§
Constants§
- COMMIT_
SEGMENT_ MAX_ SHARDS - Shards one staged commit segment may span.
- HEAD_
FENCE_ MISMATCH_ CODE - HEAD_
FENCE_ MISMATCH_ GROUP - MAX_
COMMIT_ DIRTY_ PAGES - Actor-side ceiling: 128 MiB of 4 KiB pages. The server additionally enforces its configured filesystem transaction byte cap before admitting each segment. Large commits stream as bounded segments and publish at one commit sequence.
- SHARD_
SIZE - Pages per storage shard. Shared rather than each side keeping its own copy: the client cuts staged commit segments on these boundaries and the engine rejects segments that are not cut on them, so two definitions could disagree and make every large commit fail.
- TRANSACTION_
TOO_ LARGE_ CODE - TRANSACTION_
TOO_ LARGE_ GROUP - The error a remote SQLite request reports when its transaction changed more pages than one commit may carry.
Functions§
- cut_
page_ segments - Cuts pages into shard-aligned segments, each spanning at most
COMMIT_SEGMENT_MAX_SHARDS. - is_
head_ fence_ mismatch - is_
transaction_ too_ large - segment_
start_ for_ page - Where a staged commit segment carrying
pgnomust start.