mysql - Database approach for different product types -



mysql - Database approach for different product types -

my e-commerce application has different product/service types listed. each product/service type has different properties/attributes. example, mobile phone have different attributes cdma/gsm , tv have different set of attributes usb/hdmi. many product types available in starting , maintain on adding different product/service types.

so question is, should need have different table each product/service type in database because each product/service has different attributes (columns) or there different, improve approach? estimated count of product/service types 50+.

your case instance of class/subclass or type/subtype. buzzphrase in er modeling "generalization/specialization".

here's list of tags pertain questions yours:

single-table-inheritance class-table-inheritance shared-primary-key

if read tag wiki these 3 tags, you'll general pointers on designing case outline. in addition, questions tagged 3 tags contains answers help you.

if you'd little more research on web, recommend martin fowler's web pages outlines single table inheritance , class table inheritance. covers basics well. if still want go deeper, you'll need consult textbook.

all of these techniques arise out of fact neither relational info model nor vanilla sql had mechanism providing inheritance modeler.

mysql database database-design

Comments

Popular posts from this blog

xslt - DocBook 5 to PDF transform failing with error: "fo:flow" is missing child elements. Required content model: marker* -

mediawiki - How do I insert tables inside infoboxes on Wikia pages? -

Local Service User Logged into Windows -