third normal form
The rule that every non-key column depends directly on the key, not on another non-key column.
In more detail
If a product row stored both category_id and category_name, the name would depend on the category, not the product, so it moves to a categories table. Ask what identifies the row, then what each column really depends on.
Related terms
- normalisation — Designing tables so each fact is stored in exactly one place, by splitting repeated data into related tables.
- second normal form — The rule that, in a table with a composite key, every other column depends on the whole key and not on just part of it.
- denormalisation — Deliberately storing a copy of data in a second place, usually to make reads faster by avoiding a join.
Taught in
- Normalisation To Third Normal Form — PostgreSQL, Indexing & Relational Data Modeling