Normalisation: Friend Or Foe
summary
Covers concrete application of 1st–3rd normal forms with dated origin (1970–71), turning a 3–4‑row bus/train example into 12 rows and introducing separate tables for district and district_manager, plus dish → ingredients → relation → preparation tables. Uses relational databases (MySQL examples and discussion of SET fields), shows a real cost: a simple select becomes a query with three left joins, and recommends using views and indexes or denormalization when joins hurt — "normalize till it hurts, denormalize till it works."
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:00What is Normalisation
- 3:43First Normal Form
- 10:21Third Normal Form
- 12:14Third Normal Form Example
- 15:40Normalisation Resources
- 16:25Performance Hit
- 18:22Data Sync
- 19:32Resources
- 21:23Questions
related talks
24m"Normalize until it hurts; denormalize until it works" in Django
39mDatabase Design for Beginners
58mFrom Big to Very Big Data — Why Normalization Is Needed in Big Data
44mDenormalization With Eloquent: How, Why and When
43mNORM: No ORM Framework
01h 07mAnchor Modelling: Sixth Normal Form Databases!
18mGermany's Next Top Data Model
29mHow De-normalizing Your Data with JSON Can Boost Query Performance