#37057: UniqueConstraint incorrectly raises ValidationError on nullable fields
in
condition
-------------------------------------+-------------------------------------
Reporter: Drews | Owner: Simon
| Charette
Type: Bug | Status: assigned
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: UniqueConstraint | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* owner: (none) => Simon Charette
* status: new => assigned
Comment:
I suspect we'll want to adjust the `nulls_distinct` check to ''resolve''
to what the backend actually defaults to if unspecified.
--
Ticket URL: <https://code.djangoproject.com/ticket/37057#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019db57f1a88-e041b521-dc76-49e7-9355-15eac8292c24-000000%40eu-central-1.amazonses.com.
