Core Concept Mastery • DBMS Module
Imagine a profile page. You want to list your Hobbies (Chess, Cycling) and your Favorite Foods (Pizza, Burger).
The Violation: You try to put them in one table.
Row 1: Jon, Chess, Pizza
Row 2: Jon, Cycling, Burger
Wait... does Jon ONLY eat Pizza when playing Chess? No! They are unrelated.
To be accurate, you'd need:
Row 1: Jon, Chess, Pizza
Row 2: Jon, Chess, Burger
Row 3: Jon, Cycling, Pizza
Row 4: Jon, Cycling, Burger
You have 4 rows for 2 items each! This is the Cartesian Product explosion.
The Fix: Separate tables. One for Hobbies, one for Foods.
It creates a huge multiplication mess. If you have 3 hobbies and 3 children, the database has to create 9 rows just to list them all. It's wasteful.
Jon plays Cricket & Chess. Jon has kids Tom & Jerry. Don't mix them. Create a "Hobbies Table" and a "Children Table".
"4NF deals with which type of dependency?"
Multi-valued Dependency (MVD).