Re:5NF and Database Design
by tadfisher on Tuesday April 14, 2026 @12:44PM
(#47768004)
I love reading about the normal forms, because it makes me sound like I know what I'm talking about in the conversation where the backend folks tell me, "if we normalized that data then the database would go down". This is usually followed by arguments over UUID versions for some reason.
[ Parent
| on HN ]
So which normal form do they argue for and against? And what UUID version wins the argument?
Explaining jokes is poor form.
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.
On the internet it is normal.
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.
Yeah, no NULL is ever equal to any other NULL, so they are basically unique.
You are also guaranteed to be able to retrieve your data, just query for '... is null'. No complicated logic needed!