docs: missing documentation for LIKE ANY pattern-matching function
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Domain
- documentation
Research direction
Read the like_any implementation in src/query/functions/src/scalars/comparison.rs lines 875–913, then use the existing like.md page as a style reference. Add docs/en/sql-reference/20-sql-functions/06-string-functions/like-any.md with the function behavior and examples, and cross-reference it from the conditional/comparison index and like.md. Done means the page builds and all requested links are present.
Written by the indexing model from the issue text.
Description
Missing Documentation
The like_any function is implemented in Databend but has no documentation page in the docs site.
Source File
/workspace/databend/src/query/functions/src/scalars/comparison.rs (lines 875–913):
"like_any",
// ...
name: "like_any".to_string(),
// ...
like_any_fn,
What It Does
LIKE_ANY(expr, patterns) tests whether a string matches any of a set of LIKE patterns. The second argument can be a tuple of string literals or a single string. It is the multi-pattern variant of the standard LIKE operator — equivalent to writing expr LIKE p1 OR expr LIKE p2 OR ... but more concise.
Example usage:
SELECT * FROM t WHERE name LIKE ANY ('Alice%', 'Bob%');
SELECT like_any(name, ('Alice%', 'Bob%')) FROM t;
Note: issue #2420 in this repo requests this documentation; this issue is filed to formally track it as a missing-docs item.
Suggested Doc Location
/docs/en/sql-reference/20-sql-functions/06-string-functions/like-any.md
It should also be cross-referenced from the conditional/comparison functions index and the existing like.md page.
- Dominant language
- TypeScript
- Stars
- 17
- Forks
- 44
- Avg merge
- 2d 7m
- Merged PRs (30d)
- 4
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from databendlabs/databend-docs
-
Link Checker Report Openautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
databendlabs/databend-docs#3504 ·
-
Link Checker Report Openautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
databendlabs/databend-docs#3503 ·
-
auto-fix-done documentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
databendlabs/databend-docs#3359 ·
-
auto-fix-done documentation
Difficulty 2/5 1-2 days Newbie friendliness 72/100
databendlabs/databend-docs#3356 ·
-
auto-fix documentation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
databendlabs/databend-docs#3302 ·
All issues in databendlabs/databend-docs
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100