This repository was archived by the owner on Nov 24, 2025. It is now read-only.
Update to DB migration server_id_primary_key.sql#5509
Merged
ocket8888 merged 1 commit intoapache:masterfrom Feb 11, 2021
hbeatty:HB-update-server_id_primary_key.sql
Merged
Update to DB migration server_id_primary_key.sql#5509ocket8888 merged 1 commit intoapache:masterfrom hbeatty:HB-update-server_id_primary_key.sql
ocket8888 merged 1 commit intoapache:masterfrom
hbeatty:HB-update-server_id_primary_key.sql
Conversation
I was unable to run the dbadmin upgrade because this update was trying to add 2 primary keys (one for each schema). I encountered this while trying to upgrade from 4.1.1 to 5.0.0.
hbeatty
added
bug
ocket8888
approved these changes
Feb 11, 2021
Contributor
ocket8888
left a comment
ocket8888
left a comment
There was a problem hiding this comment.
Checked migration up/down, works without breaking, finished database works with TO on master (checked DS content available through CiaB).
ocket8888
pushed a commit
that referenced
this pull request
Feb 16, 2021
I was unable to run the dbadmin upgrade because this update was trying to add 2 primary keys (one for each schema). I encountered this while trying to upgrade from 4.1.1 to 5.0.0. Co-authored-by: Hank Beatty <hbeatty@dev4.atl-priv.kabletown.test> (cherry picked from commit 46b4fd1)
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.
What does this PR (Pull Request) do?
I was unable to run the dbadmin upgrade because this update was trying to add 2 primary keys (one for each schema).
I encountered this while trying to upgrade from 4.1.1 to 5.0.0.
Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
I'm not sure how to test this. My DB has been around since the 1.x days. It has 2 schemas (traffic_ops and public). This SQL statement was trying to create a primary key in both schemas.
If this is a bug fix, what versions of Traffic Control are affected?
The following criteria are ALL met by this PR