My question can probably be an echo of a previously asked question:
How to create a custom object model using MS roles and membership , but I ask again, because there is no good answer so far, and my question is focused on data model design anyway:
Anyway, there are users and groups in my application. A user can belong to many groups, and, of course, a group can contain many users. The problem now, we know only a few main groups: user, guest and administrator. In the future, there may be can-do-X, can-do-Y groups, and potentially much more or no more than just an administrator, user, and guest. So I'm just trying to take an easy approach. Here are my thoughts on approaches:
If I had a user table with bare bones and a role table, and another that imitates a many-to-many relationship seems a bit overworked. If I understand correctly, this will be seen as a normalized approach. And vice versa, if I close the following columns in the User table, such as IsAdmin, IsGuest, CanDoX, CanDoY, etc., Then it will be denormalized.
I seek a balance between complexity and flexibility, time and space, etc. Please suggest.
source
share