Repository navigation
Conversation
includes the new tables, and support files; but doesn't change any of the existing code: purely additive
This reverts commit f5e4dce.
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.
summary of changes:
./shift mysql)steps to migrate:
running the migration adds new data; it doesn't affect existing data.
./shift compose exec node npm run --silent -w tools mysql-migrate > /tmp/reorg.sqlex. at the bottom of the generated output there will be notes about events it skipped because there were no scheduled days, invalid image types, and rewrites to handle legacy 'E' exception events ( so far as i can tell, these were events which were copies so that the start time could be adjusted. the migration fully clones them and sets their status to 'A' )
./shift mysql-pipe < /tmp/reorg.sqltesting
to test things we could: