DB Schema Migration: Ignore duplicate column errors#2514
Merged
Conversation
Member
|
Makes sense. Thank you. LGTM. |
Contributor
Author
|
This will allow me to add a new column |
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
2 participants
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.
During development new columns may be added in advance before the final version number for the schema migration is known. IMO we can safely ignore this class of errors during schema migration.
It helps testing PRs that involve a schema migration. The only manual intervention that still might be needed is lowering
mixxx.schema.versionfrom time to time to apply all migrations that have been merged into master in the mean time.