#36592: Allow UniqueConstraint's nulls_distinct to accept a database's default
value rather than raising a system check error
-------------------------------------+-------------------------------------
Reporter: Russell Owen | Owner: (none)
Type: New feature | Status: closed
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: SQLite | Triage Stage:
UniqueConstraint | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Russell Owen):
Thank you. I had missed that. The warning message is still misleading,
however, since it complains even when the boolean value of the argument
matches the behavior of sqlite according to the message.
So I think this is a legitimate bug, but the bug is only that the warning
message is misleading. If boolean values are not acceptable for a given db
then the message should say that so the user knows how to fix the problem.
--
Ticket URL: <https://code.djangoproject.com/ticket/36592#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019914fcfafd-1161ddb8-f538-455d-b0ec-d6bf23a4cdfc-000000%40eu-central-1.amazonses.com.
