Conversation
Keep prior-event attempts and solves during dual writes so event switches do not erase collected solve history before the RaceSession cutover.
Preserve historical PostgreSQL solves
coder13
marked this pull request as ready for review
July 14, 2026 03:24
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
1 participant
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.
Summary
Promotes the verified dev candidate containing #234 to master.
Included change
The background PostgreSQL dual writer preserves a room's prior attempts and solves when its event changes. This prevents historical solve data from being deleted before the RaceSession migration.
Visibility
No new user-facing feature is enabled. PostgreSQL data collection remains enabled behind the existing backend configuration.
Verification
The dev push is green: