Identity module constraint needed

[dmlloyd]

It looks to me like there ought to be a unique constraint across either the GROUP_ and ROLE_ columns or just the GROUP_ column within the identity JBPM_ID_MEMBERSHIP table.

The effect would be to prevent a user from being in the same group more than one time, or barring that, require that each membership within the same group has a unique role.

Agree/disagree?

[dmlloyd]

It looks to me like there ought to be a unique constraint across either the GROUP_ and ROLE_ columns or just the GROUP_ column within the identity JBPM_ID_MEMBERSHIP table.

I misstated - I mean across USER_, GROUP_, and ROLE_, or just USER_ and GROUP_.

[tom.baeyens]

i think you can have multiple people in the same group with the same role. e.g. many people could have the developer role in a team

or did you mean something else ?

[dmlloyd]

I meant to say that any given user cannot be in the same group more than once. Though a single group can certainly contain more than one user.

[tom.baeyens]

i don't think that is a general constraint. i mean, most of the times, a user will only have 1 membership, but i guess that sometimes people can fullfill 2 roles for one group.

[kukeltje]

Yes, 2 roles for one group occurs lots of times in the business we are in. They are manager of the group, but also do the normal regular work

[dmlloyd]

What about limiting each user to only belong to each group one time for each distinct role?

So a user cannot be in the same group with the same role more than once. This way, if roles are not used, then the user will be limited to being in the group only one time, but if they are, then they are prevented from being in the same role more than once.