#26609: Add system check for field choices using unorderable iterables
-------------------------------------+-------------------------------------
Reporter: Harry Percival | Owner: Karl
Type: | Status: assigned
Cleanup/optimization |
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: migrations | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Karl):
I have not been entirely clear on how check error numbers are created. I
can see where they're documented but it is not self-evident to me whether
there is a pattern to them. Should this be "E013"? Should it just be added
into the existing "E004"?
Also, barring testing against known unstable types, does anyone have any
clever ways to do this test? I'm going to just check specifically against
`sets` (`dicts` are something we want to continue to allow, right?). I'll
use a list so it can be modified in the future if needed, but that's the
only one I'm currently aware of this problem for.
--
Ticket URL: <https://code.djangoproject.com/ticket/26609#comment:10>
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/01070192ba5d4cbd-133b5895-a612-4e05-b1d9-52d83a27fdfc-000000%40eu-central-1.amazonses.com.
