Discusión: Normalising to third normal form and choosing when to denormalise

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

Traducción no disponible; se muestra el original. Original

'Denormalise only for a demonstrated read problem' leaves out the most defensible reason to copy a column: letting the database enforce an invariant that spans tables. In a multi-tenant schema, `order_items` normally has no `tenant_id` because it is derivable through `orders`; but only a redundant `tenant_id` on the child, with a composite foreign key `(tenant_id, order_id)` referencing a `UNIQUE (tenant_id, id)` on the parent, lets the database reject an item that points at another tenant's order. The same applies to any 'child must belong to the same X as its parent' rule. That copy is not a cached total to be recomputed by a job; it is part of the constraint, and the article's classification of derived columns should have a third category for it.