Data-Base STRUCTURE HELP

[jlsports]

I am having trouble figuring out the best way to structure a data-base. I have a membership base and I want them to be able to select from a list of teams which numbers over 300 and list up a WATCHLIST of only those teams. How would I go about this?

My login data-base consists of USERID,USERNAME. Each user will have a differnt list of teams. I guess I could limit the list to 10 or 20 but I would really like to have them be able to select all 300 teams if they wanted.

Well, I just can't visualize this so any help would be apprecited.

Thanks

[drawmack]

http://www.google.com/search?hl=en&ie=ISO-8859-1&q=relational+database+design+tutorial&btnG=Google+Search

[pete_bisby]

You already have a table for the users (USERID and USERNAME), and I'm going to assume that you will have a table for the teams (TEAMID and TEAMNAME).

USERID within the users table and TEAMID within the teams table will be your primary key. Your third table (WATCHLIST), which will define the teams each user can view, will consist of USERID and TEAMID - no other fields/attributes will be needed.

Remember to have the primary key set to both USERID and TEAMID (compound primary key). It will help to cut down on duplicate records.

As far as relational database terminology, this is known as a one-to-many relationship between the users table (one) and the watchlist table (many), and another one-to-many relationship between the teams table (one) and the watchlist table (many).

Hope this helps !