So store role-permissions as many role>permission rows rather than one role>permissionsAsString row per role.
But how does this change the problem of accumulating large numbers of role > permission associations as when there are many user > project associations? Other question: I assume that (by default) project:p1:write doesn't imply project:p1:read? I would have to write my own code for such implications? Many Thanks! CN -- View this message in context: http://shiro-user.582556.n2.nabble.com/Structuring-roles-and-permissions-tp7581233p7581237.html Sent from the Shiro User mailing list archive at Nabble.com.
