Hello @all,
I think the current implementation of category mappipngs is fine, but it could be more sophisticated. Some shop owners might want the ability to map products to categories in order to group them (so far so good), but they also want to be able to map their categories into different branches of the category tree. Therefore the simple "ParentCategoryID in Nop_Category-Table" approach does not work any more.
There would be two approaches, as I see it.
1. Keep the "ParentCategoryID in Nop_Category-Table" and define this as the master category relationship. If an additional category mapping for this category is required, add an entry in an especially designed table. Pros: no need to change existing design, just make addions. Cons: relationships of the same type are stored in two different tables
2. Kill the "ParentCategoryID" from Nop_Category-Table and create a whole new Nop_Category_ParentCategory_Mapping table. Pros: clean architecture. Cons: more implementation and design required.
Any thoughts on this?
Cheers,
Hoppi