8000 Feedback: SQL FAQs - missing info on unordered_unique_rowid() · Issue #19606 · cockroachdb/docs · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

8000 Feedback: SQL FAQs - missing info on unordered_unique_rowid() #19606

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
hand-crdb opened this issue May 13, 2025 · 0 comments
Open

Feedback: SQL FAQs - missing info on unordered_unique_rowid() #19606

hand-crdb opened this issue May 13, 2025 · 0 comments

Comments

@hand-crdb
Copy link
hand-crdb commented May 13, 2025

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, and unique_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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant
0