Allow NULL on unique fields to be non-unique in forms #15
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
|
I had a hard time coming up with a somewhat sensible test model, so feel free to change the testapp. |
The database will allow it, but the validator incorrectly rejects NULL values on nullable fields which are part of the unique index.
sjamaan
force-pushed
the
null-uniqueness-validation
branch
4 times, most recently
from
196fb22
to
666bd58
Compare
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.
The database will allow it, but the validator incorrectly rejects NULL
values on nullable fields which are part of the unique index.
This patch fixes that so the form validations correspond to how the database index is checked.