|
Home > Archive > MySQL ODBC Connector > February 2006 > Wordpress MU
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Erich Beyrent 2006-02-25, 9:43 am |
| 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/mysql? unsub...sie.nctu.edu.tw
| |
| Duncan Hill 2006-02-25, 9:43 am |
| On Friday 24 February 2006 12:33, Erich Beyrent wrote:
> 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.
With split tables, you get the following:
1) A user can't accidentally delete another user's data (through code faults,
easily)
2) Ease of backups - each user can do personal backups, and the logic is very
simple to do so
3) Easier logic in the code?
4) An accidental command doesn't kill all data.
The disadvantage to multiple tables (which WP as a vendor should handle for
you) is that a change to one table schema must be propagated to all tables.
The disadvantage of changing WP is you have to maintain the change across
upgrades.
----
Scanned by mailCritical.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql? unsub...sie.nctu.edu.tw
|
|
|
|
|