Feedback: SQL FAQs - missing info on unordered_unique_rowid()
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- documentation
Research direction
Start with the v25.2 SQL FAQs page at sql-faqs.html and review the auto-generated row identifier paragraph and the table under “What are the differences between UUID, sequences, and unique_rowid()?” Add unordered_unique_rowid() where appropriate, then verify both examples accurately describe its use cases and the page renders correctly.
Written by the indexing model from the issue text.
Description
Page: https://cockroachlabs.com/docs/v25.2/sql-faqs.html
What is the reason for your feedback?
[X] Missing the information I need
[ ] Too complicated
[ ] Out of date
[ ] Something is broken
[ ] Other
Additional details
This page is incomplete because it does not mention unordered_unique_rowid()
For example, it omits unordered_unique_rowid() when it says:
To auto-generate unique row identifiers, you can use the gen_random_uuid(), uuid_v4(), or unique_rowid() functions.
Another example further down the page is the table that does not include unordered_unique_rowid() :
What are the differences between
UUID, sequences, andunique_rowid()?
| Property | UUID generated with uuid_v4() | INT generated with unique_rowid() | Sequences |
|---|
The unordered_unique_rowid() function is useful to document because it matches many use cases, especially when modifying the database schema to remove sequences, in the situation when the column needs to remain an integer, and when it is important to use an unordered value to reduce hot spots.
Jira issue: DOC-13671
- Dominant language
- HTML
- Stars
- 212
- Forks
- 477
- Avg merge
- 40m
- Merged PRs (30d)
- 3
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 cockroachdb/docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cockroachdb/docs#23456 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
cockroachdb/docs#23454 ·
-
Difficulty 2/5 1-2 days Newbie friendliness 68/100
cockroachdb/docs#23445 · 1 comment ·
-
sql-diagram-validation
Difficulty 1/5 Under an hour Newbie friendliness 85/100
cockroachdb/docs#23444 · 4 comments ·
-
Feedback: BACKUP Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
cockroachdb/docs#23394 ·
All issues in cockroachdb/docs
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100