A million rows is not a lot for mysql.
The pro of doing it in one table is that the coding is much easier.
Reporting is much easier.
The pro of doing it as individual databases would be easier locking,
quicker responses on
queries (not so much), and the ability to secure it much more (dynamically
create logins to
database).
You have to weigh out how much work you want to do I guess. I did
something the second way
for a web statistic package. Sheer volume made me do that (and locking
issues). I do not
think that it will be quite as much of a problem in your case, as I can't
imagine it being
hammered either way.
Hope that helps a bit
P
"joe collins" <[EMAIL PROTECTED]>
04/05/2004 09:00 AM
To: "MySQL" <[EMAIL PROTECTED]>
cc:
Subject: opinion please
I am going to have a web hosted MySQL database. It will hopefully have
100+
users.
I was thinking of having one database to store all records for all users.
I would store a user_id against records where appropriate to relate them
to
a particular user.
The database will have a contacts table, users table, session_data table
the contacts table will contain a field user_id to identify which contact
is
associated with which user. This will lead to a very large contacts table
(million records???)
Alternatively I could create a database for each user database_user1,
database_user2 etc, each one of these databases could be then referenced
dynamically in my application code, depending on the user logged in.
Each one would have its own contacts table, specifically for that
user.....
Which is the better way to go, in the opinion of any gurus out there..one
very large database or multiple instances of user particular databases.
Any guidance would be greatly appreciated.
Regards
Joe
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
