Database: Add primary key to settings table #108569
Closed
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 is this feature?
Several tables are missing primary keys, with
setting
being one of those. This PR adds a primary key to that table based on an already existing unique constraint on(section, key)
.Why do we need this feature?
Having primary keys is a good idea, but a customer is blocked from upgrading to newer versions of Grafana due to a new internal policy that mandates SQL tables have primary keys.
Who is this feature for?
Database Administrators
Which issue(s) does this PR fix?:
Part of https://github.com/grafana/search-and-storage-team/issues/393
Special notes for your reviewer:
Please check that: