Hey guys!
I have a question. I want to make a website whereby the each users can choose from 1 or more different kinds of interests.
Now, I'm gonna have a PROFILE table and a INTERESTS tables.
Should I have a field in PROFILE that says "interests" and store 1 or more INTERESTS ids at delimited by a comma?
Or should I have a table MYINTERESTS and have
PROFILE-ID and INTEREST-ID in it? One row for each interest the user selected.
I'm thinking, if I have 1 million users(wishful thinking) with each having 4 interests, then MYINTERESTS will have 4 million records. That's gonna be so big! Whereas if I store the INTEREST-IDs in PROFILE under "interests" field (example: 3, 4, 8, 7) then that'll save space.
What do you guys think?
Thanks a million x 4!
I have a question. I want to make a website whereby the each users can choose from 1 or more different kinds of interests.
Now, I'm gonna have a PROFILE table and a INTERESTS tables.
Should I have a field in PROFILE that says "interests" and store 1 or more INTERESTS ids at delimited by a comma?
Or should I have a table MYINTERESTS and have
PROFILE-ID and INTEREST-ID in it? One row for each interest the user selected.
I'm thinking, if I have 1 million users(wishful thinking) with each having 4 interests, then MYINTERESTS will have 4 million records. That's gonna be so big! Whereas if I store the INTEREST-IDs in PROFILE under "interests" field (example: 3, 4, 8, 7) then that'll save space.
What do you guys think?
Thanks a million x 4!