Add support for nullable fields in unique_together #24
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
OskarPersson
force-pushed
the
unique-together-nullable-field
branch
3 times, most recently
from
984bc64
to
d5d4bf4
Compare
OskarPersson
force-pushed
the
unique-together-nullable-field
branch
from
d5d4bf4
to
08c2721
Compare
OskarPersson
force-pushed
the
unique-together-nullable-field
branch
from
53dee7b
to
29a4a7e
Compare
sparrowt
added a commit
to sparrowt/django-mssql-backend
that referenced
this pull request
Jul 6, 2020
Doubtless there are more cases that should be tested, but these are the 3 specific ones that I've found to be broken and reported in issue ESSolutions#58 These tests fail on latest django-mssql-backend (e.g. v2.8.1) but passed on v2.4.2 before ESSolutions#24 went in.
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.
No description provided.