Paging bug with multiEntry cursor not returning all matches #200
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
added 2 commits
May 12, 2015 13:39
There's no way around doing a full table scan for cursors against multi entry indexes.
|
Sorry for the delay. I've been away on vacation. I'm looking at this now. Creating some unit tests first to demonstrate the problem, then I'll merge your fix. |
JamesMessinger
added a commit
that referenced
this pull request
May 27, 2015
Paging bug with multiEntry cursor not returning all matches
JamesMessinger
added a commit
that referenced
this pull request
May 28, 2015
|
No worries! Thanks for merging this. It's always a nice feeling being on the latest official version. |
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.
Results are limited to matches found within the first 100 rows because of the paging logic. Removed paging logic to do a full table scan when doing a multiEntry cursor prefetch.
There doesn't seem to be a simple way to avoid a full table scan for multiEntry index matches anyhow.