I have done some looking and found some posts, but nothing I felt answered my question completely.
I am working on a project that is a sort of content management system that has multiple users... the best example I can think of would be similar to Wordpress MU...
With Wordpress MU each blog that is created gets its own set of tables... so then you end up with a separate posts table for each blog rather than a single posts table with a column that says blog ID...
What would be the pros/cons of each method?
Table: blog_posts with column blog ID
Table: blog_1_posts (contains posts for blog 1)
Table: blog_2_posts (contains posts for blog 2)
Any input concerns/ideas would be great... Thanks!!
My guess is that WPMU uses a set of tables for each site because it's built on the WP platform, which doesn't have that blog ID column in it's database.
Who knows, if they could've, maybe they would've chosen your example A scenario
I think adding a new table for each new user doesn't make much sense. Everytime you add a user you need a new table? 1000 users 1000 tables... Sounds like mayhem. The only way I would see it making sense would be if they were completely different sites or contained different types of data.