this post was submitted on 30 Jun 2024
18 points (100.0% liked)

Programming

423 readers
6 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 !webdev@programming.dev



founded 1 year ago
MODERATORS
 

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

top 2 comments
sorted by: hot top controversial new old
[โ€“] unmagical@lemmy.ml 17 points 4 months ago

Why did you post a 3 year old expired draft whose proposed implementation has been obsoleted?

[โ€“] Ephera@lemmy.ml 4 points 4 months ago

For others wondering what's wrong with UUIDv4:

UUID versions that are not time ordered, such as UUIDv4, have poor database-index locality. This means that new values created in succession are not close to each other in the index; thus, they require inserts to be performed at random locations. The resulting negative performance effects on the common structures used for this (B-tree and its variants) can be dramatic.

I guess, this means with these new UUIDs, ideally you only create UUIDs on systems that are hooked up to NTP, though I guess, it won't really be worse than UUIDv4 either way.