Refactor substr signature #18653
Merged
Refactor substr signature #18653
+50
−81
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
sqllogictest
comphead
reviewed
Nov 13, 2025
| signature: Signature::one_of( | ||
| vec![ | ||
| TypeSignature::Coercible(vec![string.clone(), int64.clone()]), | ||
| TypeSignature::Coercible(vec
comphead
reviewed
Nov 13, 2025
| ], | ||
| Volatility::Immutable, | ||
| ) | ||
| .with_parameter_names(vec
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Which issue does this PR close?
Part of #12725
Rationale for this change
Prefer to avoid user_defined for consistency in function definitions.
What changes are included in this PR?
Refactor signature of substr to use coercion API instead of being user defined.
Are these changes tested?
Existing tests.
Are there any user-facing changes?
No