I am currently evaluating the multi-user version of the popular blogging
software, Wordpress. One of the things I am not so sure about is its
schema.
To support multiple users, Wordpress creates about ten tables per user.
I have, at worst case, 4000 users who may be using this software, and
I assume roughly 100 posts per user.
My question is whether or not it is good design to have each user have
his or her own set of tables. Would it not make sense to have all user
posts in a single table, referenced by a BlogID? This table could
easily grow to be a few million rows, and I know MySQL won't choke on
that, as long as the indexes are maintained.
Aside from ease of backing up user data in the individual table
scenario, is there any other benefits to doing it this way? I am
considering modifying the product to support a single table, but want
some insight before doing so.
-Erich-
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
