#28220: contrib.auth.models Group should have a default ordering to prevent
UnorderedObjectListWarning
--------------------------------+--------------------------------------
Reporter: Denise Mauldin | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+--------------------------------------
Comment (by Simon Charette):
Defining a default ordering coud break existing application and would most
likely require a migration for the `_meta.ordering` change.
The only paginated use of `Group`'s manager is through `GroupAdmin` which
is
[https://github.com/django/django/blob/650bf6714d5648811a8bc08ce53b7fa86cc38d40/django/contrib/auth/admin.py#L29
already ordered] by `name`.
Is there a reason you can't explicitly specify an ordering when exposing
groups through a paginated view by using `order_by()`?
--
Ticket URL: <https://code.djangoproject.com/ticket/28220#comment:1>
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/071.36b3bca6d090d6169f8a3483c3c76a43%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
