Live data from Hacker News

New UUID Formats

ietf.org

1–10 of 172 posts

Re: New UUID Formats

#3
This had appeared a few times before at earlier stages of the draft process...

https://news.ycombinator.com/item?id=28088213 [244 comments]

Personally, I really like UUIDv7, except I transform the UUID to a 25-character string which has all the same properties except it doesn't look like a UUID. The last thing I want is my index of time-sortable UUIDs getting contaminated with with some UUIDv4 fully random ones. Since UUIDs may be generated and persisted in a distributed manner, it's a simple way to at least spot this.

Re: New UUID Formats

#6

This had appeared a few times before at earlier stages of the draft process... https://news.ycombinator.com/item?id=28088213 [244 comments] Personally, I really like UUIDv7, except I transform the UUID to a 25-character string which has all the same properties except it doesn't look like a UUID. The last thing I want is my index of time-sortable UUIDs getting contaminated with with some UUIDv4 fully random ones. Sinc…

The UUID version is in the actual ID, so you would be able to spot the version as it isn't fully random.

Although you light mean just visually you'd spot the difference much easier!

Re: New UUID Formats

#9

It's a shame they didn't finally drop big endian. Little endian won out and our newer protocols should reflect that for efficiency's sake.

It's necessary to keep them sortable at byte level.

Re: New UUID Formats

#10

It's a shame they didn't finally drop big endian. Little endian won out and our newer protocols should reflect that for efficiency's sake.

But network byte order is big endian, so I can see arguments both ways (as it were)
Post reply on HN