#7582: Sorting by nullable ForeignKey
-----------------------------------------+----------------------------------
Reporter: [EMAIL PROTECTED] | Owner: nobody
Status: new | Milestone: post-1.0
Component: Admin interface | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------------+----------------------------------
Comment (by kmtracey):
Myself I'd call it removing remnants of an old bug (prohibiting something
that wasn't handled correctly before queryset-refactor), not an
enhancement. As jpwatts mentions, there's no documentation explaining why
these fields are not made sortable in the admin. Thus the current
behavior is confusing to the user, since there is no obvious reason for
these fields to be treated differently than all the others that are
automatically sortable. (Which is why it came up on the user's list in
the first place.)
So I'd argue it should be fixed for 1.0, or documented. Fixing it is
easier: there's the patch, which does in fact still apply correctly as of
[8472].
--
Ticket URL: <http://code.djangoproject.com/ticket/7582#comment:7>
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
-~----------~----~----~----~------~----~------~--~---
