#17198: In admin results can be omitted due to pagination and inadequate
ordering
clauses
-------------------------------+------------------------------------
Reporter: lukeplant | Owner: julien
Type: Bug | Status: new
Component: contrib.admin | Version:
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by lukeplant):
> "if you don't have a total ordering on your models then you need to
understand the consequences".
I agree with that, but put that like it kind of implies that the developer
is choosing not to have a total ordering, which isn't quite fair when it
is the Django default. It's especially unfair since before 1.4 if you
specified an ordering for the admin which was a total ordering, everything
but the first item was silently ignored. (I understand I'm reading
something into the 'tone' of that comment which might not have been there,
but you get my point).
I'm happy with this being a wontfix, but if so I think at the very least
we need some doc fixes. Is there perhaps some way to do a warning as well?
--
Ticket URL: <https://code.djangoproject.com/ticket/17198#comment:12>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
