(Database Design – products attributes): What is better option for product attribute database design? [closed]

by

You’re making a common mistake of database design, storing name in one column and value in another column. This is not a relational database design.

Each attribute should be named by the column name. Color, pages, shirt size, publish date, should be column names.

If each product type has a distinct set of attributes, there are other solutions. See my answers to:

Also please read this story: Bad CaRMa: Introducing Vision before you implement a database designed around name-value pairs as you are doing.

More Related Contents:

  1. Modeling Product Variants
  2. How to design a product table for many kinds of product where each product has many parameters
  3. How to implement one-to-one, one-to-many and many-to-many relationships while designing tables?
  4. How to pivot a MySQL entity-attribute-value schema
  5. How to create multiple one to one’s
  6. What is the best design for a database table that can be owned by two different resources, and therefore needs two different foreign keys? [closed]
  7. How do you like your primary keys? [closed]
  8. designing database to hold different metadata information
  9. Sql – Indirect Foreign Key
  10. NoSql vs Relational database
  11. Entity-Attribute-Value Table Design
  12. Relational table naming convention [closed]
  13. When I should use one to one relationship?
  14. Relational database design multiple user types
  15. Should I use EAV model?
  16. Why use multiple columns as primary keys (composite primary key)
  17. Database schema which can support specialized properties
  18. Database EAV Pros/Cons and Alternatives
  19. How should international geographical addresses be stored in a relational database?
  20. Still Confused About Identifying vs. Non-Identifying Relationships
  21. Proper database model for a user feedback system (an interesting case)
  22. Which is a good design for a database table that can be owned by two different resources, and therefore needs two different foreign keys? [closed]
  23. Composite Primary Keys : Good or Bad?
  24. Alternatives to Entity-Attribute-Value (EAV)?
  25. Minimum no of tables that exists after decomposing relation R into 1NF?
  26. NULL permitted in Primary Key – why and in which DBMS?
  27. Relational Data Model for Double-Entry Accounting
  28. Best beginner resources for understanding the EAV database model? [closed]
  29. Inventory management with stock options
  30. uncertainty in developing a database model

Leave a Comment