This repository was archived by the owner on Nov 24, 2025. It is now read-only.
change server primary key to only id#4994
Merged
ocket8888 merged 2 commits intoapache:masterfrom Sep 15, 2020
Merged
Conversation
Contributor
|
Manual tested (successful) as follows:
Unit tests pass |
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.
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 PR updates the server table so that only the id is the primary key instead of the id, cachegroup, type, status, and profile
Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
verify that all unit and API tests are successful, verify that adding, editing, and deleting a server works as before except that servers cannot have the same id twice
If this is a bug fix, what versions of Traffic Control are affected?
The following criteria are ALL met by this PR
There are no test updates because it is covered by existing tests
There are no CHANGELOG updates since it is not a functionality change
There are no doc updates since it is just a db change
Additional Information