Structuring cascading properties - parent only or parent + entire child graph?
- by SB2055
I have a Folder entity that can be Moderated by users. Folders can contain other folders. So I may have a structure like this:
Folder 1
Folder 2
Folder 3
Folder 4
I have to decide how to implement Moderation for this entity. I've come up with two options:
Option 1
When the user is given moderation privileges to Folder 1, define a moderator relationship between Folder 1 and User 1. No other relationships are added to the db.
To determine if the user can moderate Folder 3, I check and see if User 1 is the moderator of any parent folders.
This seems to alleviate some of the complexity of handling updates / moved entities / additions under Folder 1 after the relationship has been defined, and reverting the relationship means I only have to deal with one entity.
Option 2
When the user is given moderation privileges to Folder 1, define a new relationship between User 1 and Folder 1, and all child entities down to the grandest of grandchildren when the relationship is created, and if it's ever removed, iterate back down the graph to remove the relationship. If I add something under Folder 2 after this relationship has been made, I just copy all Moderators into the new Entity.
But when I need to show only the top-level Folders that a user is Moderating, I need to query all folders that have a parent folder that the user does not moderate, as opposed to option 1, where I just query any items that the user is moderating.
I think it comes down to determining if users will be querying for all parent items more than they'll be querying child items... if so, then option 1 seems better. But I'm not sure.
Is either approach better than the other? Why? Or is there another approach that's better than both? I'm using Entity Framework in case it matters.
