|
|
|
|
|
by WorldMaker
1015 days ago
|
|
Sort orders are complicated for UUIDs because of the interesting defined structure to them, and of course endian issues. One fun and useful reference: https://devblogs.microsoft.com/oldnewthing/20190426-00/?p=10... It's particularly interesting that Microsoft SQL Server was designed to optimize indexing for UUIDv1 machine IDs. That makes a certain amount of sense for a database cluster if IDs are sorted by machine. Of course, developers don't let developers use UUIDv1 in 2023 because those machine IDs are not secure in a general sense and can be a privacy/data leak in the worst cases. Other databases sort/index UUIDs differently. There's no real "standard" and optimizing the storage of a UUID key is a game of playing to the strengths of your specific database. (On one project I put some work into matching the much-better-defined ULID sort order to MS SQL Server uniqueidentifier columns for better database locality.) |
|