Answer the question
In order to leave comments, you need to log in
Proper DB design for EAV?
There is a working online store. Works on a "self-made" PHP framework. MySQL database.
At the moment, no more than 100 positions.
No more than 6,000 positions are planned for the next year.
Product data (size, color, brand) is stored in one table. The products are basically the same.
In the near future, goods of various categories will be added and, accordingly, the fields (attributes) will vary greatly. I don't see any reason to add fields to the table as new types of goods arrive.
I am reading about EAV and this model seems to fit me. But as I understand it, it can cause a lot of problems, and most of these problems are caused initially by incorrect base structure.
I could not find specific examples for online stores.
For example, I created a hypothetical structure in Excel. I need your advice.
Example:
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question