I was wondering how sites like match.com, chemistry.com (and those other similar sites) set up their databases? I know they are huge databases and the exact setup is a secret, but I was hoping someone could give me a little insight (possibly a rough ER diagram)?
Anyway, seems like those sites are too distracting. How about facebook/myspace? I am just curious how they set up their databases to keep track of members and profile info. Can anyone help me out with a rough ER diagram?
Would it be bad practice to create a third table (i.e. ProfileInfo) with the profile info and have a username foreign key to identify ProfileInfo with the Account? It just seems that Account table could get really big eventually.
I guess what I was thinking is that maybe if you decided down the road that you wanted to add a new field to the user profiles it would be easy to append to a separate ProfileInfo table. I am just thinking about the large social networking sites. If they change or add a field in the user profiles, this would require a change in the Account table. Would it make more sense to have the separate ProfileInfo table? Or is it better to throw all their member info into the one Accounts table?