#8682: Admin ordering works incorrectly if ModelAdmin.ordering has several
fields,
and one of them is an another Model field
--------------------------------------+-------------------------------------
Reporter: semenov | Owner: nobody
Status: closed | Milestone:
Component: Admin interface | Version: SVN
Resolution: invalid | Keywords: newforms-admin admin
ordering
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------------+-------------------------------------
Comment (by kmtracey):
Replying to [comment:2 semenov]:
>
> Then, however, I don't understand what's the point to have
ModelAdmin.ordering as a '''tuple''', if only the first element is always
used?
Consistency with most of the other !ModelAdmin options? Leaving the door
open to one day implement multi-field ordering in Admin? I don't really
know.
--
Ticket URL: <http://code.djangoproject.com/ticket/8682#comment:3>
Django Code <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
