Repository navigation
fix(history): keep existing event and template history - #339
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Follow up to #337
The unified history migration dropped the previous
historyrows on the assumption nothing read them, but staff-api writes calendar event changes there and serves them fromGET /events/history.The migration now renames the old table, copies its rows into the new one (
type→resource_type,template→signage_template) and then drops it. Down restores them.Environments that have already run 9.121's migration have lost those rows; this keeps them everywhere else.
Review
historyandgroup_historyrows: event and template rows are kept in both directions, alongside the migrated group history.🤖 Generated with Claude Code