This repository was archived by the owner on Nov 24, 2025. It is now read-only.
db/admin migrate: Migrate first migration explicitly if DB version's migration is squashed#6096
Merged
mitchell852 merged 8 commits intoapache:masterfrom Aug 16, 2021
Merged
Conversation
temporarily set the migration version to 0
zrhoffman
added
bug
rimashah25
reviewed
Aug 13, 2021
rimashah25
reviewed
Aug 13, 2021
zrhoffman
changed the title
db/admin: Set migration version to 0 before migrating if DB version's migration is squasheddb/admin migrate: Migrate first migration explicitly if DB version's migration is squashed
Contributor
|
LGTM. Ready for merge. |
rimashah25
approved these changes
Aug 16, 2021
4 tasks
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 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.
This PR fixes an issue encountered migrating the database if a migration for the current DB migration version does not exist, typically because a migration at that version has been squashed into
create_table.sql:Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
d96c13c~traffic_ops_db/test/docker/initdb.dIf this is a bugfix, which Traffic Control versions contained the bug?
PR submission checklist