Frankly I don't think that overcounting is solved by normalizing, because it's easy to write an overcounting SQL query over perfectly normalized data.
I tried to explain the real cause of overcounting in my "Modern Guide to SQL JOINs":
https://kb.databasedesignbook.com/posts/sql-joins/#understan...
Re:5NF and Database Design
by estetlinus on Wednesday April 15, 2026 @03:32AM
(#47775803)
Great read, thank you!
I'll go one further and say that if you're reaching for DISTINCT and you have joins, you may have joined the data the wrong way. It's not a RULE, but it's ALWAYS a 'smell' when I see a query that uses DISTINCT to shove away duplicate matches. I always add a comment for the exceptions.
Re:5NF and Database Design
by hilariously on Tuesday April 14, 2026 @05:08PM
(#47771546)
It depends on if you are doing OLTP (granular, transactional) vs OLAP (fact/date based aggregates) - dates are generally not something you'd consider in a fully normalized flow to uniqify records.
Re:5NF and Database Design
by estetlinus on Wednesday April 15, 2026 @03:32AM
(#47775799)
Makes sense. I’m an OLAP guy.
Re:5NF and Database Design
by hilariously on Wednesday April 15, 2026 @09:52AM
(#47778978)
Well you are in luck, if someone tells your to normalize you can tell them their source system can fuck right off.
I would maybe throw in date as an key too. Bad idea?