#35594: Add support for non-distinct NULL expressions to
UniqueConstraint.validate()
-------------------------------------+-------------------------------------
Reporter: Mark Gensler | Owner: (none)
Type: New feature | Status: new
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: unique constraint | Triage Stage: Accepted
nulls_distinct validation |
expressions |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
No worries and no harm done, I just wanted to make sure you wouldn't waste
time on this problem since both Mark and I had a pretty good idea of where
to take the patch.
I guess a possible rule of thumb would be to at least wait a few days
after the creation of a ticket if there seems to be active discussions and
no call for someone to take the implementation work. In doubt, asking if
help is required is also always welcome.
--
Ticket URL: <https://code.djangoproject.com/ticket/35594#comment:9>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/01070190a2d19e0c-aa826bf3-b81e-41d0-8bf5-320750ca0cfe-000000%40eu-central-1.amazonses.com.
