comanage-dev - Re: [comanage-dev] change data model for cm_co_groups?
Subject: COmanage Developers List
List archive
- From: Scott Koranda <>
- To: Benn Oshrin <>
- Cc: comanage-dev <>
- Subject: Re: [comanage-dev] change data model for cm_co_groups?
- Date: Fri, 28 Feb 2014 11:20:29 -0600
Hi,
> I think we'd need to define special. Perhaps a flag to indicate that the
> group
> can't be deleted?
I was initially thinking of a column where the values are
enums, such as
GROUPTYPE::COADMINS
GROUPTYPE::COUADMINS
GROUPTYPE::COMEMBERS
GROUPTYPE::COUMEMBERS
But I think having a second additional column that is a flag
to indicate that the group cannot be deleted is also
necessary.
Thoughts?
Scott
>
> On February 27, 2014 12:59:26 PM EST, Scott Koranda
> <>
> wrote:
>
> Hi,
>
> We now have two types of "special" groups: admin and members (and a
> ticket to change admin to admins). To determine if a group is one of
> these special groups and therefore might need to be provisioned
> differently (for example we decided that CO admins can toggle whether
> admin and members are provisioned into Grouper) we have to parse the
> name.
>
> Note that parsing the name might mean checking if the group is linked
> to a COU and has a name like 'admins:My COU 01' or 'members: My COU
> 01'.
>
> Should we add a column to the cm_co_groups table to record that a
> group is "special" rather than only encoding it in the name?
>
> Thanks,
>
> Scott
>
- [comanage-dev] change data model for cm_co_groups?, Scott Koranda, 02/27/2014
- Re: [comanage-dev] change data model for cm_co_groups?, Benn Oshrin, 02/27/2014
- Re: [comanage-dev] change data model for cm_co_groups?, Scott Koranda, 02/28/2014
- Re: [comanage-dev] change data model for cm_co_groups?, Benn Oshrin, 02/27/2014
Archive powered by MHonArc 2.6.16.