Many yes/no attributes: table design study

🔗 Many yes/no attributes: table design study
kb.databasedesignbook.com

I wanted to demonstrate the relationship between the logical model and a physical model. We're going to design a commonly seen use case: many yes/no attributes of a single anchor (in our case, Restaurant). Then we'll discuss how the physical tables would be designed. We'll see that sometimes physical design strategy changes as the system becomes more mature. At the same time, logical design elements never change if the business requirement is still relevant.

We will briefly discuss three different physical table design strategies: a table per anchor, side table, and Entity-Attribute-Value (EAV).

continue reading on kb.databasedesignbook.com

⚠️ This post links to an external website. ⚠️

If this post was enjoyable or useful for you, please share it! If you have comments, questions, or feedback, you can email my personal email. To get new posts, subscribe use the RSS feed.