Polymorphic relationships vs separate tables per type?
❔Advice
Hello,
I want to build "Variant Manager" where user can define through folders, variantSets and variants nested structures that must support ordering, drag and drop, pagination.
I could create simly 2 tables variantManagers and variantManagerNodes where by using a "kind" field i can support different types and of course i can add a parentID to handle nesting easilly. The only thing that bothers me are that some fields would be optional. And also I saw this articles and I am really confused:
- https://stackoverflow.com/questions/56727023/polymorphic-relationships-vs-separate-tables-per-type
- http://seejohncode.com/2011/01/13/polymorphic-relationships-are-bad/
Can you point me to the right direction? How would I built the orderable, node system using the separate table approach? Would this be bad becuase it involve querying multiple tables?
Thanks!
I want to build "Variant Manager" where user can define through folders, variantSets and variants nested structures that must support ordering, drag and drop, pagination.
I could create simly 2 tables variantManagers and variantManagerNodes where by using a "kind" field i can support different types and of course i can add a parentID to handle nesting easilly. The only thing that bothers me are that some fields would be optional. And also I saw this articles and I am really confused:
- https://stackoverflow.com/questions/56727023/polymorphic-relationships-vs-separate-tables-per-type
- http://seejohncode.com/2011/01/13/polymorphic-relationships-are-bad/
Can you point me to the right direction? How would I built the orderable, node system using the separate table approach? Would this be bad becuase it involve querying multiple tables?
Thanks!
