docs: missing documentation for SHOW_SEQUENCES table function
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- sql
- Domain
- documentation
Research direction
Read the implementation at src/query/service/src/table_functions/show_sequences/show_sequences_table.rs and its registration in src/query/service/src/table_functions/table_function_factory.rs. Create docs/en/sql-reference/20-sql-functions/17-table-functions/show-sequences.md covering the listed output columns and the SELECT * FROM show_sequences() example; done means the missing documentation page is complete.
Written by the indexing model from the issue text.
Description
Missing Documentation: show_sequences Table Function
What is missing
The show_sequences table function is implemented in the Databend source code but has no documentation page in databend-docs.
Source code location
src/query/service/src/table_functions/show_sequences/show_sequences_table.rs
Also registered in the table function factory at:
src/query/service/src/table_functions/table_function_factory.rs
What it does
show_sequences() returns a list of all sequences defined in the current tenant/catalog. It is the table-function equivalent of the SHOW SEQUENCES SQL statement and can be used in queries, CTEs, and subqueries.
Output schema:
name(String) — sequence nameinterval(Int64) — auto-increment step intervalcurrent(UInt64) — current value of the sequencecreated_on(Timestamp) — creation timestampupdated_on(Timestamp) — last updated timestampcomment(String, nullable) — optional comment
Example usage:
SELECT * FROM show_sequences();
Suggested doc location
docs/en/sql-reference/20-sql-functions/17-table-functions/show-sequences.md
- 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