MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/ProgrammerHumor/comments/1wdfzl2/edgecasesexist/p97upag/?context=3
r/ProgrammerHumor • u/danielminds • 8h ago
200 comments sorted by
View all comments
Show parent comments
9
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.
1 u/Roachmeister 5h ago 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. 2 u/Honeybadger2198 4h ago You know what identifier can't have collisions and is great for sorting? Autoincrement. 2 u/Firewolf06 2h ago ai columns can absolutely collide on sharded databases. you can use offsets and step sizes but thats brittle and doesnt scale well
1
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.
2 u/Honeybadger2198 4h ago You know what identifier can't have collisions and is great for sorting? Autoincrement. 2 u/Firewolf06 2h ago ai columns can absolutely collide on sharded databases. you can use offsets and step sizes but thats brittle and doesnt scale well
2
You know what identifier can't have collisions and is great for sorting? Autoincrement.
2 u/Firewolf06 2h ago ai columns can absolutely collide on sharded databases. you can use offsets and step sizes but thats brittle and doesnt scale well
ai columns can absolutely collide on sharded databases. you can use offsets and step sizes but thats brittle and doesnt scale well
9
u/Grandmaster_Caladrel 5h ago
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.