feat: Raise on invalid 'is_between' and improve error message quality #18147
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.
Set up architecture to catch non-sensical/ambiguous queries and raise an error asking for explicit casts.
In direct comparisons
<, >, ==, >=
and the likes, we already raised. For functions we didn't have the logic implemented yet. This will prevent a lot of trip ups where people think they compare dates, but instead are comparing string ascii values on order, which is never what you want to happen implicitly.closes #18144