contrib.auth.models Group should have a default ordering to prevent UnorderedObjectListWarning

[Denise Mauldin]

Since contrib.auth.models Group doesn't have an ordering default, any selection using Group and filter causes an UnorderedObjectListWarning in Django 1.11.

Group.objects.filter(user=user.id)

Can a default ordering be set somehow to prevent this warning?

Thanks,
Denise

[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 ​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()?

[Denise Mauldin]

Will do. Just was hoping there was a faster way than updating all of our code. Thanks.

Replying to 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 ​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()?