#35594: Add support for non-distinct NULL expressions to
UniqueConstraint.validate()
-------------------------------------+-------------------------------------
Reporter: Mark Gensler | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: unique constraint | Triage Stage: Ready for
nulls_distinct validation | checkin
expressions |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce <42296566+sarahboyce@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"adc0b6aac3f8a5c96e1ca282bc9f46e28d20281c" adc0b6aa]:
{{{#!CommitTicketReference repository=""
revision="adc0b6aac3f8a5c96e1ca282bc9f46e28d20281c"
Fixed #35594 -- Added unique nulls distinct validation for expressions.
Thanks Mark Gensler for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35594#comment:14>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070190c0526246-3a667c83-66b3-4fd2-a7fd-c0b70cd99a9a-000000%40eu-central-1.amazonses.com.
