#27752: Fix and test admin_order_field set for the __str__ of a model
-------------------------------+-------------------------------------------
Reporter: Claude Paroz | Owner: Renato Oliveira
Type: Bug | Status: assigned
Component: contrib.admin | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+-------------------------------------------
Comment (by Renato Oliveira):
I'm trying to write something here but nothing seems to fit. Maybe because
I'm not fluent on English
{{{
* The ``__str__()`` method is just as valid in ``list_display`` as any
other model method, so it's perfectly OK to do this::
list_display = ('__str__', 'some_other_field')
* Usually, elements of ``list_display`` that aren't actual database
fields can't be used in sorting (because Django does all the sorting
at the database level).
However, if an element of ``list_display`` represents a certain
database field, you can indicate this fact by setting the
``admin_order_field`` attribute of the item.
This rule doesn't apply to ``__str__`` method.
}}}
It's missing why it's not applicable, but It's not clear to me how to say
that
--
Ticket URL: <https://code.djangoproject.com/ticket/27752#comment:8>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.1e7bc266a1120294b707a06e19481edc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
