CODEWITHSUNDEEP
sqldatabase-designrelational-databaseparent-childhierarchical-data
user7918630
user7918630

Reputation:

store product and category in one table is good or else we can use seperate table for category and product?

I am totally confused to store category and product data stored in the same table in hierarchical relation/Parent-child relation use in a table or if we create two separate table for category and product table?

enter image description here

in above table, i used the same table for storing category and product with parentId and childId, If we use like this then what benefits? Or we use a separate table for category and product and why? Please anyone help me

Upvotes: 0

Views: 2118

Answers (1)

Thom A
Thom A

Reputation: 95830

This really depends on if the relationship between store and product categories are one to many or many to many and if a single category can only belong to one category tree.

If the relationship is one to many, and a category can only belong to one tree, then you'll be able to use a single table, with a foreign key referencing the same table.

Otherwise, you'll likely be looking 2 or 3 tables. At a minimum you'll need one table for your categories, and then another for you relationship (what's known as a composite key table).

Also, if Product categories and Store Categories are inherently different (hold different data) then you should be using separate tables for them anyway.

Upvotes: 2

Related Questions