uuid7
uuid7-csharp
| uuid7 | uuid7-csharp | |
|---|---|---|
| 3 | 2 | |
| 68 | 35 | |
| - | - | |
| 0.0 | 0.0 | |
| 4 months ago | 10 months ago | |
| Python | C# | |
| MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
uuid7
-
Sequential UUID in snowflake
Snowflake does not support UUID 7. What you could do is import UUID7 Python module and implement a Python UDF.
- New UUID Formats from IETF
-
Understanding UUIDs, ULIDs and String Representations
To summarise the differences:
* UUIDv6 - sortable, with a layout matching UUIDv1 for backward compatibility, except the time chunks have been reordered so the uuid sorts chronologically
* UUIDv7 - sortable, based on nanoseconds since the Unix epoch. Simpler layout than UUIDv6 and more flexibility about the number of bits allocated to the time part versus sequence and randomness. The nice aspect here is the uuids sort chronologically even when created by systems using different numbers of time bits.
* UUIDv8 - more flexibility for layout. Should only be used if UUIDv6/7 aren't suitable. Which of course makes them specific to that one application which knows how to encode/decode them.
UUIDv7 is thus the better choice in general.
(I recently wrote Python and C# implementations - https://github.com/stevesimmons/uuid7 and https://github.com/stevesimmons/uuid7-csharp)
uuid7-csharp
-
Understanding and avoiding visually ambiguous characters in IDs
3. IDs don't use L and O because those can be confused for other characters
I've found it very handy in my travels.
[1] https://github.com/stevesimmons/uuid7-csharp?tab=readme-ov-f...
-
Understanding UUIDs, ULIDs and String Representations
To summarise the differences:
* UUIDv6 - sortable, with a layout matching UUIDv1 for backward compatibility, except the time chunks have been reordered so the uuid sorts chronologically
* UUIDv7 - sortable, based on nanoseconds since the Unix epoch. Simpler layout than UUIDv6 and more flexibility about the number of bits allocated to the time part versus sequence and randomness. The nice aspect here is the uuids sort chronologically even when created by systems using different numbers of time bits.
* UUIDv8 - more flexibility for layout. Should only be used if UUIDv6/7 aren't suitable. Which of course makes them specific to that one application which knows how to encode/decode them.
UUIDv7 is thus the better choice in general.
(I recently wrote Python and C# implementations - https://github.com/stevesimmons/uuid7 and https://github.com/stevesimmons/uuid7-csharp)
What are some alternatives?
ksuid - K-Sortable Globally Unique IDs
Hashids.java - Hashids algorithm v1.0.0 implementation in Java
tiny_id - Rust library for generating non-sequential, tightly-packed short IDs.
uuid6-ietf-draft - Next Generation UUID Formats
dart-uuid - Generate RFC4122(v1,v4,v5,v6,v7,v8) UUIDs
ulid - Universally Unique Lexicographically Sortable Identifier (ULID) in Python 3
prototypes - Draft Prototypes and Tests for UUIDv6 and beyond
uuid6-python - New time-based UUID formats which are suited for use as a database key
vanity-uuid - Create "readable" UUIDs such as "5eedbed5-f05e-b055-ada0-d15ab11171e5" for all your UUID needs!
presents - Like hashids, but based on block ciphers