Remove obsolete acount() during apage() evaluation
#55
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The previous implementation performed two database queries to evaluate `apage()`. Now we make use of the pre-fetched element from `_apply_paginator_arguments` to check if there are additional pages without using `acount()`. Added tests for `page()` and `apage()` to verify only one database query is performed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The previous implementation performed two database queries to evaluate
apage().Now we make use of the pre-fetched element that is prepared in
_apply_paginator_argumentsto check if there are additional pages without using
acount().Added tests for
page()andapage()to verify only one database query is performed.Tested against py3.13.2 / django 5.2.8
See #54 for full discussion.