News for hackers. Stuff that matters.
Re:5NF and Database Design by necovek on Tuesday April 14, 2026 @12:57PM (#47768180)
So which normal form do they argue for and against? And what UUID version wins the argument?
Re:5NF and Database Design by tadfisher on Tuesday April 14, 2026 @01:29PM (#47768550)
Explaining jokes is poor form.
Re:5NF and Database Design by necovek on Tuesday April 14, 2026 @03:26PM (#47770253)
This was an attempt to extend jokes and not ask for explanation: there are a number of normal forms, and people usually talk about "normalization" without being specific thus conflating all of them; out of 7 UUID versions, only 2 generally make sense for use today depending on whether you need time-incrementing version or not.
Re:5NF and Database Design by culi on Tuesday April 14, 2026 @01:39PM (#47768711)
On the internet it is normal.
Re:5NF and Database Design by Tostino on Tuesday April 14, 2026 @01:06PM (#47768298)
Not OP, but UUID v7 is what you want for most database workloads (other than something like Spanner)
Re:5NF and Database Design by tossandthrow on Tuesday April 14, 2026 @03:14PM (#47770059)
I use the null uuid as primary key - never had any DB scaling issues.
Re:5NF and Database Design by petalmind on Tuesday April 14, 2026 @03:23PM (#47770210)
Yeah, no NULL is ever equal to any other NULL, so they are basically unique.
Re:5NF and Database Design by Groxx on Tuesday April 14, 2026 @03:40PM (#47770445)
You are also guaranteed to be able to retrieve your data, just query for '... is null'. No complicated logic needed!
Re:5NF and Database Design by RedShift1 on Tuesday April 14, 2026 @03:47PM (#47770536)
Me still using bigints... Which haven't given me any problems. Wouldn't use it for client generated IDs but that is not what most applications require anyway.