#7582: Sorting by nullable ForeignKey
-----------------------------------------+----------------------------------
Reporter: [EMAIL PROTECTED] | Owner: nobody
Status: new | Milestone: 1.0 alpha
Component: Admin interface | Version: newforms-admin
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------------+----------------------------------
Comment (by Karen Tracey <[EMAIL PROTECTED]>):
Yes, the issue is whether the Admin puts a link in the column header that
allows you to sort by the associated field. As mentioned in the list
discussion, the restriction has been there since initial import of the
code into the current repository. I assume the Admin didn't allow it
because the ORM code didn't used to support it. Now it does, I think the
Admin restriction can be removed as well. Also mentioned at the tail end
of that list discussion is that different DBs may put null values in
different places (either first or last), so behavior may not be entirely
consistent from DB to DB, but I don't see that as a showstopper for
allowing sorting by these fields.
--
Ticket URL: <http://code.djangoproject.com/ticket/7582#comment:2>
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
-~----------~----~----~----~------~----~------~--~---
