Opened 7 years ago

Last modified 6 years ago

#28917 closed Cleanup/optimization

Paginator shows ordering warning on an empty .none() queryset — at Initial Version

Reported by: Jeremy Lainé Owned by: nobody
Component: Core (Other) Version: 2.0
Severity: Normal Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Paginator (sanely!) does a check to verify that the queryset it is passed is ordered, and if it isn't, shows a warning.

However, if also emits this warning if passed a queryset which is guaranteed to be empty, for instance Article.objects.none()

Working around this warning involves doing a bizarre Article.objects.none().order_by('id')

I believe there can be legitimate usecases for passing a .none() queryset to a paginator, for instance if a user's permissions are such that we restrict the objects they can view to the empty queryset.

Change History (0)

Note: See TracTickets for help on using tickets.
Back to Top