Fix example SQL UDF in SET docs#25071
Merged
mosabua merged 1 commit intotrinodb:masterfrom Feb 18, 2025
Merged
Conversation
wendigo
approved these changes
Feb 18, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Description
Discovered by @wendigo .. looks like coercion is not supported. Not sure how this statement got into the docs in the first place .. I recall testing them all. This removes the coercion since it doesnt add any value to the example anyway. Tested with 468 .. not that it should matter.
Potentially @electrum could add support for coercion as a follow up.
Additional context and related issues
na
Release notes
(x) This is not user-visible or is docs only, and no release notes are required.