#30910: Add system check warning on duplicate check constraints.
--------------------------------------+------------------------------------
Reporter: Jon Dufresne | Owner: nobody
Type: New feature | Status: closed
Component: Core (System checks) | Version: master
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => wontfix
Comment:
Reviewing again with Mariusz, we're not convinced the proposed solution is
sufficiently robust to capture more than the most naive cases. (There are
just too many ways of writing equivalent constraints.) As such, we're not
convinced of the value of the check. (Leaning towards a suspicion it would
actually be unhelpful on balance, which we've seen with other proposed
system checks at times.) Will close on that basis.
Possible to revisit if a way of ''reducing'' semantically equivalent
constraints turns up...
(c.f. [https://github.com/django/django/pull/11973 Discussion on PR].)
--
Ticket URL: <https://code.djangoproject.com/ticket/30910#comment:3>
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/067.f9e3ba64e84a8ec7ed23f161d611dd61%40djangoproject.com.
