Re: Group Membership - One-to-Many Dilemma
From: Bernard Peek <bap_at_shrdlu.com>
Date: Fri, 20 Dec 2002 16:55:15 +0000
Message-ID: <TXy1+lKzt0A+EwiL_at_shrdlu.co.uk>
Date: Fri, 20 Dec 2002 16:55:15 +0000
Message-ID: <TXy1+lKzt0A+EwiL_at_shrdlu.co.uk>
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 cognoscentiReceived on Fri Dec 20 2002 - 17:55:15 CET