my question is very similar to question ,But i don't want to use EAV design
Rigth now ,we have these products in our store
Harddisk ->size(GB) ,speed ,price
Shirt -> size(M-L-S) ,color ,price
Book -> nummber of page , writer , price
To design database ,I am trying use Inheritance approach
Product (SN,Odrer ,price ,Date )
→ Harddisk ->size(GB) ,speed
→Shirt -> size(M-L-S) ,color
→Book -> nummber of page , writer
Product and Sub table have one to one relationship
But If in future new product comes with different attribute , i will create new table .
,Is it correct approch or is there any better approch ?
Should i use Entity–attribute–value model ?
->Even if i will use EAV design and still i have update code with new entity and attribute?
Please help/suggest me make a better design ?