Re:Do We Still Have to Denormalize? Have Your Schema and Sea...
by oulipo on Monday November 16, 2026 @04:47AM
(#50515795)
Not really, as the article mentions: if you simply denormalize everything, each time you need to eg update a user name, you suddenly have to update its whole posts and comments everywhere, making it something quite expensive
[ Parent
| on HN ]
Re:Do We Still Have to Denormalize? Have Your Schema and Sea...
by KellyCriterion on Monday November 16, 2026 @05:10AM
(#50515936)
a) thats the reason why lot of platforms do not allow to change username after signup
b) absolutely manageable with a solid tooling (and honestly, in 99% of cases this event is trivial as most systems just do not hold enough data to make it like a "eeek this change will run for 3 days for that 1 user")
Re:Do We Still Have to Denormalize? Have Your Schema and Sea...
by fauigerzigerk on Monday November 16, 2026 @07:11AM
(#50516736)
>a) thats the reason why lot of platforms do not allow to change username after signup
Nor any of the other user data that is indexed with every single post?
Re:Do We Still Have to Denormalize? Have Your Schema and Sea...
by KellyCriterion on Monday November 16, 2026 @07:43AM
(#50517018)
If I look at my youtube comment notification, Id say propably not? (Timestamp belongs to a post as well as likes etc.?)
Re:Do We Still Have to Denormalize? Have Your Schema and Sea...
by sgarland on Monday November 16, 2026 @08:45AM
(#50517548)
Experience across multiple companies of varying size and maturity has proven to me that devs are incapable of doing the RDBMS’ job for it; there are always orphaned rows and referential integrity issues when FK Constraints get dropped.
Databases are hard. They’re also some of the best-tested code that exists, so maybe let them do their job.