V9: Fixes issue where PublishedContentQuery executes skip twice. #11549
Conversation
This file contains 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
…e query returns 4 resuls, and you have skip =1 take=5, you only had 2 results. This is fixed in this commit.
|
Duplicate of #11378 |
elit0451
deleted the
v9/bugfix/publiced_content_query_execute_skip_in_search_twice
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes issue where PublishedContentQuery executes skip twice.
So if the query returns 4 results, and you have skip =1 take=5, you only had 2 results. This is fixed in this commit.
This is an issue compared to v8, because Examine now handles skiptake directly, in a few lines above these changes.