Repository navigation
feat: persist match events and idempotency receipts in SQLite - #10
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Match events and successful command receipts persist across process restarts through a SQLx SQLite adapter for
MatchStore. Embedded migrations create the match, ordered event, and receipt tables. WAL connections with full synchronous durability and immediate write transactions serialize concurrent appends; read transactions return consistent snapshots.Production queries are checked at compile time. Committed offline metadata supports builds without a database, while CI recompiles against a fresh migration-derived schema and checks for metadata drift. The lockfile adds storage dependencies without changing existing package versions.
Depends on #8. This PR covers SQLite persistence; PostgreSQL, searchable metadata, snapshots, retention, and server wiring remain separate units.
Validation: all GitHub Actions checks pass at
30a16dbe1dcad0af16365d905c0c3adc3cae5271, including 20 Rust tests, query/schema consistency, fmt, clippy with offline SQLx metadata, dependency boundaries, cargo-deny, core API compatibility, web checks, and game benchmarks. Seven new database tests cover restart recovery, retry ordering and key scope, competing writers through independent pools, rollback after partial writes, and corrupt event sequences.