Add LimitOffsetPagination.get_count to allow method override #5846
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR:
pagination._get_count
LimitOffsetPagination.get_count
instance methodLimitOffsetPagination.paginate_queryset
I have a custom pagination class that subclasses
LimitOffsetPagination
. When paginating a large queryset with an.order_by()
clause, the combination of sorting can add a lot of overhead to the pagination calculation, which in turn slows down the entire response. Addingget_count()
as an instance method gives developers the ability to override it's behavior if necessary. In my case, I will override the method to remove any ordering constraints from the queryset.