A table for each user, on app designed for over 10K users?

Questions about the MySQL, PostgreSQL, and most other databases, as well as using it with PHP can be asked here.

Moderator: General Moderators

Post Reply
User avatar
timotheus
Forum Newbie
Posts: 6
Joined: Thu Oct 18, 2007 3:36 pm
Location: Berkeley, CA

A table for each user, on app designed for over 10K users?

Post by timotheus »

Hello, I am designing a financial online tool. A person makes entries of purchases, essentially. My plan is having one table for user info, then a table for each user, where it will record entries. An estimate is that each user will add one entry per day. (This is greatly simplified)

I want this to be scalable, so it will run well with 10,000 users and more. Does making a unique table for each user not make sense at that point?

I'm worried that if I just have one 'entries' table for all the users, the data set could become so large it would be hard to search, even if the entries database was very much relational.

Thank you for your insight.
User avatar
VladSun
DevNet Master
Posts: 4313
Joined: Wed Jun 27, 2007 9:44 am
Location: Sofia, Bulgaria

Re: A table for each user, on app designed for over 10K users?

Post by VladSun »

timotheus wrote:Does making a unique table for each user not make sense at that point?
Absolutely not.
Google for primary keys, foreign keys, relations.
There are 10 types of people in this world, those who understand binary and those who don't
User avatar
timotheus
Forum Newbie
Posts: 6
Joined: Thu Oct 18, 2007 3:36 pm
Location: Berkeley, CA

Re: A table for each user, on app designed for over 10K users?

Post by timotheus »

Well, that is good to know. I have a lot of code to change. :/
Post Reply