2 ms·
This has a pretty good discussion how to store hierarchical data: https://tdan.com/modeling-hierarchies/5400 https://tdan.com/modeling-hierarchies/5400 Also,
by sharemywin 5y ago
This has a pretty good discussion how to store hierarchical data:
https://tdan.com/modeling-hierarchies/5400 https://tdan.com/modeling-hierarchies/5400
Also,
you would need a user_org table for user org relation.
probably a subscription table and permission table between product and org(subscriptions) and prod and user(permissions)
you might also look at a graph database
- ko3us 5y agoThanks for the reference. This helps me think about the hierarchy of the relationships. So it makes sense to have a user account be a member of an org. Then have orgs have a relationship with products. Im still questioning where I would apply role based permissions. If a user account is a member of an org should I apply the role permission at every level?