Skip redundant fetch query for empty query keys results #508
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.
Skip executing redundant paged fetch query that does not have any results, i.e.
The first generated SQL query fetches task keys with the empty result, i.e.
After that, the second fetch query does not apply in search criteria is when the list of ids from the id query is empty, which fetch all data without keys restrictions, i.e.
This is a bug because, the second query should not need to execute at all if there are no ids found for the provided selection criteria. We also can skip
total
count if the select page result is empty to further improve query performance