This repository was archived by the owner on Nov 24, 2025. It is now read-only.
Reorder SQL migrations for 5.0.0 -> 5.1.0 upgrade#5525
Closed
hbeatty wants to merge 1 commit intoapache:5.1.xfrom
hbeatty:HB-fix-sql-migrations-order_5.1.x
Closed
Reorder SQL migrations for 5.0.0 -> 5.1.0 upgrade#5525hbeatty wants to merge 1 commit intoapache:5.1.xfrom hbeatty:HB-fix-sql-migrations-order_5.1.x
hbeatty wants to merge 1 commit intoapache:5.1.xfrom
hbeatty:HB-fix-sql-migrations-order_5.1.x
Conversation
This moves some SQL migrations past the last one in 5.0.x that were not in the 4.1.x and 5.0.x branch.
rawlinp
suggested changes
Feb 16, 2021
Contributor
rawlinp
left a comment
rawlinp
left a comment
There was a problem hiding this comment.
This PR should target the master branch instead and be backported to 5.1.x once merged into master.
rawlinp
added
database
Contributor
|
This was backported in 34c1854 |
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.
4 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.
What does this PR (Pull Request) do?
This moves some SQL migrations past the last one in 5.0.x that were not in the 4.1.x and 5.0.x branch.
Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Do a DB upgrade from 5.0.0 to 5.1.0
If this is a bug fix, what versions of Traffic Control are affected?
The following criteria are ALL met by this PR