#36594: Clarify UniqueConstraint's nulls_distinct system check warning
-------------------------------------+-------------------------------------
Reporter: Russell Owen | Owner: Mridul
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: UniqueConstraint | Triage Stage: Ready for
nulls_distinct | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls <jacobtylerwalls@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"d1a4979fa55071581411b7d62eb1ee20f2380ae3" d1a4979]:
{{{#!CommitTicketReference repository=""
revision="d1a4979fa55071581411b7d62eb1ee20f2380ae3"
Fixed #36594 -- Improved UniqueConstraint's nulls_distinct system check
message.
Clarified that the nulls_distinct argument is not supported, as opposed
to certain values for the argument.
Thanks Russell Owen for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36594#comment:12>
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/0107019b28c54342-fa88a576-73c9-4339-8fac-7e9b7356576e-000000%40eu-central-1.amazonses.com.
