I have a table of "people" and want to designate some of these as "speakers." Is the best design to create a field in the "people table" to do this or to create a second "speaker table" with the key of each speaker in the people table?
Table design
- Thread starter eacollie
- Start date
Cronk
Registered User.
- Local time
- Tomorrow, 10:04
- Joined
- Jul 4, 2013
- Messages
- 2,776
Depends. If all you want to save a speaker yes/no for each person, then a Yes/no field in the people table is enough. No need to complicate things.
However, if you wanted to record many attributes for a speaker (topic range, availability, speaking dates etc), then you'd be looking at another table or more.
However, if you wanted to record many attributes for a speaker (topic range, availability, speaking dates etc), then you'd be looking at another table or more.
Going to need some more information.
If you only are and will designate people as speakers, then do it in the same table. If you foresee different roles being tracked ('coordinator', 'manager', etc.) then you should use a seperate table.
If you want to capture more data relevant to their speaker identity (Technical Speaker, Fluent In Spanish, Small Group Specialist, etc.), you would make a new table.
If you only are and will designate people as speakers, then do it in the same table. If you foresee different roles being tracked ('coordinator', 'manager', etc.) then you should use a seperate table.
If you want to capture more data relevant to their speaker identity (Technical Speaker, Fluent In Spanish, Small Group Specialist, etc.), you would make a new table.
Similar threads
