docs: explain dialect requirement for lambda examples - #26040
Open
Prajwal-k-tech wants to merge 1 commit into
Open
Prajwal-k-tech wants to merge 1 commit into
Prajwal-k-tech wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
Rationale for this change
The SQL reference examples for these higher-order array functions use lambda expressions, but the default SQL dialect does not parse the
->syntax. The examples work when a lambda-capable dialect is selected, and the current descriptions do not explain that requirement.What changes are included in this PR?
any_match,array_filter,array_first, andarray_transformexplaining that lambdas require a supporting dialect and showing how to select DuckDB.#[user_doc]descriptions.This change was prepared with AI assistance. The patch and generated documentation were checked against the issue and repository guidance.
What is the testing strategy for this PR?
This is a documentation-only change, so no runtime tests were added. Verified the generated reference with
./dev/update_function_docs.sh, ran the repository documentation Prettier check,cargo +1.99.0 fmt --all -- --check,cargo clippy --all-targets --all-features -- -D warnings, andgit diff --check.Are there any user-facing changes?
Yes. The SQL function reference now tells users which dialect setting is needed to run the lambda examples.