I am designing a member-based website. Each member will be able to specify preferences for the site. Some of these preferences could be like threads per page in the forums section, how many news stories they wish to see on the front page, etc.
I have two differing opinions on how to structure this within my team.
One side wishes to have a "Users" table that will hold all information for the user, including name, username, password, along with preferences as well. The idea is that these are specific to the user. Also, that we shouldn't have to divide the user table into seperate different tables to specify division; it's more than is necessary. If were to split it up, we would then be managing several tables instead of just one.
Another side wants a more modular, object-oriented approach. There is a forums table, and a users table, but the user should know nothing about forums; you should be able to add/remove forums (or any other module) without having to effect another to any great degree other than change relationships. The proposal is to have a seperate table specifically for forum preferences, as well as a specific table for news preferences, etc. The primary key would be the same for the User table.
I decided to open the question up and get other opinions. What should we do? Liam Morley
lmorley@wpi.edu
"light the deep, and bring silence to the world.
light the world, and bring depth to the silence."
I have two differing opinions on how to structure this within my team.
One side wishes to have a "Users" table that will hold all information for the user, including name, username, password, along with preferences as well. The idea is that these are specific to the user. Also, that we shouldn't have to divide the user table into seperate different tables to specify division; it's more than is necessary. If were to split it up, we would then be managing several tables instead of just one.
Another side wants a more modular, object-oriented approach. There is a forums table, and a users table, but the user should know nothing about forums; you should be able to add/remove forums (or any other module) without having to effect another to any great degree other than change relationships. The proposal is to have a seperate table specifically for forum preferences, as well as a specific table for news preferences, etc. The primary key would be the same for the User table.
I decided to open the question up and get other opinions. What should we do? Liam Morley
lmorley@wpi.edu
"light the deep, and bring silence to the world.
light the world, and bring depth to the silence."