Fix two more uniqueness constraints in SQLAlchemy data model #56
Conversation
This file contains 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
Codecov ReportAll modified and coverable lines are covered by tests ✅
📢 Thoughts on this report? Let us know!. |
- SqlExperimentPermission: "experiment_id", "user_id" - SqlRegisteredModelPermission: "name", "user_id"
amotl
force-pushed
the
amo/fix-uniqueness-composite
branch
from
07237aa
to
c2334a1
Compare
matriv
approved these changes
Nov 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
About
GH-46 and GH-52 reported and fixed missing uniqueness constraints on the SQLAlchemy data model. This patch adds two more, based on recent improvements from crate/cratedb-toolkit#70.
/cc @hlcianfagna