#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: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* has_patch: 0 => 1
Comment:
This involved changing when we `COALESCE` as the approach taken in #33996
was too generic. `nulls_distinct` shouldn't be a factor here as it only
affects the constraint itself (fields / expressions) and not the
`condition`'s handling of `NULL` / `UNKNOWN`.
--
Ticket URL: <https://code.djangoproject.com/ticket/37057#comment:7>
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/0107019db5f03a28-0d82c5b5-39a3-49fa-bc8c-0ec9d749797f-000000%40eu-central-1.amazonses.com.
