#34701: Add support for NULLS [NOT] DISTINCT to UniqueConstraint
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: Simon
| Charette
Type: New feature | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Sarah Boyce <42296566+sarahboyce@…>):
In [changeset:"0e49a8c3bd9119795525d9f076f73740741479b7" 0e49a8c3]:
{{{#!CommitTicketReference repository=""
revision="0e49a8c3bd9119795525d9f076f73740741479b7"
Refs #34701 -- Moved UniqueConstraint(nulls_distinct) validation tests.
The original tests required the creation of a model that is no longer
necessary
and were exercising Model.full_clean(validate_constraints) which has
nothing
to do with the nulls_distinct feature.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34701#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070190c0526268-ee1ae845-1f71-4ea0-a107-6f6751951fc9-000000%40eu-central-1.amazonses.com.
