sql: make builtin generators with GeneratorWithExprs safer #70699
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.
The
Overload.GeneratorWithExprs
field was added in #70115. This commitmakes usage of this field safer by introducing the
IsGenerator
methodwhich can be used to determine if an overload is an SRF. This commit
also adds guardrails to prevent future issues with
GeneratorWithExprs
in theConvertZipArraysToValues
normalization rule.Release note: None