fix: use limit place holder with dedicated hint #1260
Draft
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.
Up until now we have always in-lined the
limitvalue directly into theSQLto ensure that overall best performance. There is now anhintthat allows the application to indicate that the place holder value will be "small" (<100.000) for bothlimitandoffset. As mostnodeCAP applications will have negative side effects if thelimitis set to100.000post processing the data. Therefor the assumption is made that thelimitwill always be quite a bit smaller.