News for hackers. Stuff that matters.
Re:Do We Still Have to Denormalize? Have Your Schema and Sea... by weego on Monday November 16, 2026 @06:11AM (#50516287)
Your assumption that increased resource usage is single concept with one outcome and no nuance is entirely false (where do the problems of engineering a desktop app even overlap with row level schema planning in a database?)

The claim that is somehow causes data consistency issues also seems kind of unsubstantiated.

The upside is that when you model it correctly your data conforms to your domain and business in a way that makes every aspect of its use easier.

Re:Do We Still Have to Denormalize? Have Your Schema and Sea... by lompad on Monday November 16, 2026 @09:55AM (#50518237)
> The claim that is somehow causes data consistency issues also seems kind of unsubstantiated.

Let me explain that part a bit more. If you have one application, developed by at most a handful of devs, there will not be any consistency issues. But add a few more applications and even a dozen devs (or just simply a decade of time and some staff changes), and there _will_ be misunderstandings/issues identifying the correct rows to update, with exact interpretation differing per application.

Congratulations, you now own a mess. Correcting this after the fact is a major effort.

If you're in 3NF this can't really happen - the exist once and only once. It's always clear which to update and nothing can be forgotten.

Re:Do We Still Have to Denormalize? Have Your Schema and Sea... by williamdclt on Monday November 16, 2026 @11:22AM (#50519343)
while I mostly agree with you, you're opposing "teams who made mistakes while denormalising" with "teams who made no mistake while normalising". The biggest difference between these two scenarios isn't that one is using denormalisation and the other normalisation, it's that one made mistakes and the other didn't.

In real life, the teams working on a supposedly-normalised data schema will also make mistakes: they will model their domain incorrectly, have information duplication without realising it at first, different interpretation of the same data (accessing the same data doesn't mean they'll interpret it the same way... or that it even _can_ be interpreted in a consistent way if not modelled correctly).

I do agree that denormalisation increases the chances of that happening. But IMO, there's much more issues on data modelling than there is in denormalisation. If you have a solid model that is shared by everyone, you'll have much fewer issues even with denormalisation than if you have a not-solid model that is not-shared by everyone even with normalisation.