Re: Group Membership - One-to-Many Dilemma

In message <7a808e4e.0212191950.37f19239_at_posting.google.com>, Yael <yaelr_at_locus.com.au> writes

>
>The membership table would be
>Team Id*
>Role*
>Member (staff Id)
>
>But which is better:
>
>1. Defining the Team table like this
>Team Id*
>Team Name
>Manager (staff id)
>Supervisor (staff id)
>
>And the membership table for additional roles only

That's what I would choose. Basically you are splitting the roles into two separate groups. One is mandatory-role and the other is optional-role.

If there is a real-world constraint that prevents having two or more teams with the same name then you can probably get rid of the Team ID.

-- 
Bernard Peek
bap_at_shrdlu.com
www.diversebooks.com: SF & Computing book reviews and more.....

In search of cognoscenti