Feature: owner-aware unique model name constraint #2827
Merged
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.
Proposed change
As was pointed out in the linked discussion, with permissions added, uniqueness by model name should be owner-aware ie two different owners can have the same tag name. The second
UniqueConstraint
is to handlenull
owner. Also this is enforced via the API when owner is changed using serializer. Hopefully the test coverage is up-to-snuff.Please let me know if I've missed anything as I dabble in the backend world.
Fixes #2802
Type of change
Checklist:
pre-commit
hooks, see documentation.