#26609: Add system check for field choices using unorderable iterables
-------------------------------------+-------------------------------------
     Reporter:  Harry Percival       |                    Owner:  Mariusz
         Type:                       |  Felisiak
  Cleanup/optimization               |                   Status:  closed
    Component:  Database layer       |                  Version:  dev
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  fixed
     Keywords:  migrations           |             Triage Stage:  Accepted
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by GitHub <noreply@…>):

 * resolution:   => fixed
 * status:  assigned => closed

Comment:

 In [changeset:"97acd4d2f92eef8c285bac070d437bf0fd52e071" 97acd4d2]:
 {{{#!CommitTicketReference repository=""
 revision="97acd4d2f92eef8c285bac070d437bf0fd52e071"
 Fixed #26609 -- Extended fields.E004 system check for unordered iterables.

 Co-authored-by: Karl Wooster <[email protected]>
 }}}
-- 
Ticket URL: <https://code.djangoproject.com/ticket/26609#comment:17>
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/0107019a9afe9d89-33c201de-369b-4cc7-8971-9fffc535ace4-000000%40eu-central-1.amazonses.com.

Reply via email to