SQL: Design - Entity Attribute Value Tables (Part 1) - Why?
If you’ve been working with databases for any length of time, you will have come across implementations of Entity-Attribute-Value (EAV) data models (or non-models as some of my friends would call them).
Instead of storing details of an entity as a standard relational table, rows are stored for each attribute.
For example, let’s create a table of people:

When we query it, all is as expected:

And for a long time, this has been how we expect to create tables.
2018-02-12
