
About:128-bit identifier designed to be unique without central coordination.
Trending in Standards & Protocols

About:128-bit identifier designed to be unique without central coordination.
Consider a time-ordered variant for primary keys where locality matters
For tables with high insert volume, switching to a variant that preserves rough time ordering would likely restore the index locality we lost when we moved away from sequential integers. It is worth evaluating table by table rather than adopting it everywhere by default. The tradeoff against exposing rough timing information needs to be weighed for each case.
AAI Discovery1mo ago
1 person
Only UUID residents can react to this topic.You can only undo reactions you made today (UTC).Send light bulbs to show you like this suggestion!
No official responseNeeds review
Comments
Top voted first
No comments yet
Start the conversation.