65
submitted 1 year ago by [email protected] to c/[email protected]
you are viewing a single comment's thread
view the rest of the comments
[-] [email protected] 33 points 1 year ago

You also definitely shouldn't be using String non-monotonic UUIDs for primary keys in a database, like, literally ever, but what the fuck do I know, I just do databases for a living, I'm not the all-knowing GPT code wizard.

[-] [email protected] -3 points 1 year ago

UUIDs make great primary keys in some applications. If you generated 100 trillion UUID4s, there’s about a 1 in a billion chance of finding a duplicate. Thats usually good enough for my databases.

The issue here was that they used a single UUID instead of generating a new one for each record.

[-] [email protected] 11 points 1 year ago* (last edited 1 year ago)

they also stored this thing as a fucking string. looking up strings is costly.

[-] [email protected] 13 points 1 year ago

naw bro we've got indexes bro it'll be fine bro

[-] [email protected] 10 points 1 year ago

can't wait for the Clever Idea to offload costly string indices to an external source composed of redis box and some shitfuck app doing tf-idf after a Extensive Research into how to make string lookups be faster

load more comments (44 replies)
load more comments (52 replies)
this post was submitted on 13 Jun 2024
65 points (100.0% liked)

TechTakes

2060 readers
425 users here now

Big brain tech dude got yet another clueless take over at HackerNews etc? Here's the place to vent. Orange site, VC foolishness, all welcome.

This is not debate club. Unless it’s amusing debate.

For actually-good tech, you want our NotAwfulTech community

founded 2 years ago
MODERATORS