og enforce at the API / DB level that a user can only have one membership in a group

enforce at the API / DB level that a user can only have one membership in a group

Open joachim-n opened this issue 7 years ago • 1 comments

It appears to be possible to use ogMembershipManager->createMembership() to create more than 1 membership entity for the same user and group.

Is this something that should be blocked, either at the DB level or in the API?

Oct 16 '17 12:10 joachim-n

Yes, it should be blocked. I guess both blocks would be nice - primary keys on the DB and a nice exception description in the API.

Oct 16 '17 12:10 amitaibu