View Single Post
Unread 12-02-2011, 03:59 PM   #10
is One Chatty Farker
Join Date: 01-11-08
Location: Nashville
Downloads: 0
Uploads: 0

Originally Posted by kihrer View Post
I would think you would have a team table and a team member table. Each entry in each table would have a key field and all other associated fields. For a member, the key might be the KCBS number and the fields might be team ID, name, address, etc.
Yes. That is certainly a way to do it, but I would not use team name as the PK, nor would team members be secondary keys of the team entity. They would have their own PK and have a relation between them. My main point in this is that teams are first class citizens and should be treated as such in the database, not as an attribute of a member.

dmprantz is offline   Reply With Quote