this post was submitted on 30 Jun 2024
5 points (55.8% liked)

Programming

17489 readers
61 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 1 year ago
MODERATORS
 

This document presents new time-based UUID formats which are suited for use as a database key.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 6 points 4 months ago (1 children)

My understanding is that as long as IDs are roughly the same range of the index instead of literally random, it reduces the thrashing about needed for indexing these. It probably doesn't need to be perfectly exact. They're talking about B-trees, so these would all be modifying the same smaller branches of the tree instead of going in all over the place.

[–] [email protected] 2 points 4 months ago (1 children)

Yeah, that is my understanding, too. Otherwise you'd only want to generate them on the database host, as even with NTP there will be small differences. This would kind of defeat the purpose of UUIDs.

If you're saying that even without NTP, just by manually setting the time, things will be fine. I mean, maybe. But I've seen it far too many times already that some host shows up with 1970-01-01...

[–] [email protected] 2 points 4 months ago

Haha, that's fair, someone absolutely would manage to write 1970s dates if they aren't pulling the current time.