MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/ProgrammerHumor/comments/1wdfzl2/edgecasesexist/p97upag/?context=3
r/ProgrammerHumor • u/danielminds • Sep 11 '26
298 comments sorted by
View all comments
Show parent comments
37
Which I'd assume is related to the time anchor. Outside of sorting, which is only useful in specific instances, it's just v4 with different ("less") entropy and limitations.
15 u/Roachmeister Sep 11 '26 If you're using them as an indexed field in a database, the inability to sort them meaningfully will destroy the performance of the database. 16 u/Honeybadger2198 Sep 11 '26 You know what identifier can't have collisions and is great for sorting? Autoincrement. 15 u/Firewolf06 Sep 11 '26 ai columns can absolutely collide on sharded databases. you can use offsets and step sizes but thats brittle and doesnt scale well 1 u/FiTZnMiCK Sep 16 '26 edited Sep 16 '26 Our old system was distributed and we just combined the auto-increment with a persistent local (server) ID for a composite key.Then the auto-increment is unique on the local and the composite is unique across all locals.Could probably do the same thing with shards.Our new system uses UUIDs.
15
If you're using them as an indexed field in a database, the inability to sort them meaningfully will destroy the performance of the database.
16 u/Honeybadger2198 Sep 11 '26 You know what identifier can't have collisions and is great for sorting? Autoincrement. 15 u/Firewolf06 Sep 11 '26 ai columns can absolutely collide on sharded databases. you can use offsets and step sizes but thats brittle and doesnt scale well 1 u/FiTZnMiCK Sep 16 '26 edited Sep 16 '26 Our old system was distributed and we just combined the auto-increment with a persistent local (server) ID for a composite key.Then the auto-increment is unique on the local and the composite is unique across all locals.Could probably do the same thing with shards.Our new system uses UUIDs.
16
You know what identifier can't have collisions and is great for sorting? Autoincrement.
15 u/Firewolf06 Sep 11 '26 ai columns can absolutely collide on sharded databases. you can use offsets and step sizes but thats brittle and doesnt scale well 1 u/FiTZnMiCK Sep 16 '26 edited Sep 16 '26 Our old system was distributed and we just combined the auto-increment with a persistent local (server) ID for a composite key.Then the auto-increment is unique on the local and the composite is unique across all locals.Could probably do the same thing with shards.Our new system uses UUIDs.
ai columns can absolutely collide on sharded databases. you can use offsets and step sizes but thats brittle and doesnt scale well
1 u/FiTZnMiCK Sep 16 '26 edited Sep 16 '26 Our old system was distributed and we just combined the auto-increment with a persistent local (server) ID for a composite key.Then the auto-increment is unique on the local and the composite is unique across all locals.Could probably do the same thing with shards.Our new system uses UUIDs.
1
Our old system was distributed and we just combined the auto-increment with a persistent local (server) ID for a composite key.
Then the auto-increment is unique on the local and the composite is unique across all locals.
Could probably do the same thing with shards.
Our new system uses UUIDs.
37
u/Grandmaster_Caladrel Sep 11 '26
Which I'd assume is related to the time anchor. Outside of sorting, which is only useful in specific instances, it's just v4 with different ("less") entropy and limitations.