Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

7
  • According to the ER diagram a user can only be assigned one role, which is wrong. Take a look at this other ER diagram: programmers.stackexchange.com/a/206391/61852 Commented Feb 16, 2015 at 23:58
  • @user61852 I feel one role to a user is perfectly acceptable in most cases. Otherwise you would have to take into consideration how multiple permissions coming from multiple roles are to be prioritized. I don't feel that simplicity is ever wrong nor is it a worthy excuse in itself of downvoting an answer. Commented Feb 17, 2015 at 11:52
  • What do you mean by "prioritize permissiones"? Commented Feb 17, 2015 at 18:18
  • 1
    @user61852 And so logically you conclude that anything different is wrong? I'm not afraid to offer a simpler solution if there is nothing to be gained by having a more complicated solution. However, OP, if you prefer multiple roles to a user, you'd only have to create an intermediate table UsersRoles that associates any given user with any given role (rather than a single field in Users that determines a user's role). Commented Feb 18, 2015 at 8:48
  • 1
    @user61852 That is needlessly complicating things imho. While it's true what you say, chances are, if you need to add permission G to manager role, you'll want all users with manager role also with permission G as well. Permissions generally don't change often, and so you're complicating both your program and the user interface just so that your client can create a "managerG" role that only has permissions for G. It's more complete, I'll give you that. That said, I wouldn't recommend it in most cases. It is this type of thinking that creates convoluted and incomprehensible programs. Commented Feb 20, 2015 at 10:48