Fix large and real numbers in search
query
#22345
Merged
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.
This is a continuation of #22205 (did some git anti-magic and accidentally auto-closed the PR 🪄 )
Scope
Postgres and MSSQL have trouble when using numbers larger than the targeted column in
where
clauses, as such we need to guard those calls against too large and invalid numbers. Additionally Postgres doesn't play well with floating point numbers used inwhere
clauses of integer type fields.What's changed:
Potential Risks / Drawbacks
None
Review Notes / Questions
Fixes #17946