mysql - Design Opinions Needed: Template Databases/Tables for users -

mysql - Design Opinions Needed: Template Databases/Tables for users -

i need professional programmers/dbas bounce thought off of , know if would/could work. please read below , give me info may break theory. thanks.

overview of website idea: website used sports card collectors chat, reply questions on forums, showcase cards/box breaks, trade/sell to/with other users, , maintain collection of cards.

design issue: user can have unlimited number of cards. create big tables.

design question: not want limit users on how many cards can have in collection on site. if have 5 copies of 1 card, , rather have 5 records, 1 each card, prerogative. may necessary each of cards may in different condition. however, allowing happen, means having 1 table store records users not close option. know sports card collectors on 1,000,000 cards.

i thinking either creating table or database each user, allow faster queries. databases on same server (i don't know host yet, in design phase currently). there main database info need (the base of operations item while user table/database have reference base of operations item). see possible field foreign key database, know thought in aspect possible, overall i'm not sure best thought is.

i see hosts "unlimited number of databases" got me thinking database each user. utilize users posts on threads, collection items, preferences, , other information. also, having each user have different table/database, if someone's table needed reindexed whatever reason, wouldn't impact other users.

however, biggest concern in either fashion additions/deletions construction of tables/databases. i'm pretty sure script written create necessary changes, seems pretty high risk. instance, i'm pretty sure write script add together field specific table in each database, or of tables, verify them prove difficult.

any ideas can throw out there me appreciated. i've been trying work on site on year , maintain getting stuck on database design because of worry of big of tables, slow response time, , if number of users grow, breaking constraints set phpmyadmin/mysql. don't want half way through database building , think there's improve way it. know there may multiple ways it, mutual practice it? give thanks much.

i thinking either creating table or database each user, allow faster queries.

that's false. single info base of operations faster.

1,000,000 cards per user isn't big number unless have 1,000,000 users.

multiple databases administration nightmare. single database preferred.

my worry of big of tables, slow response time, , if number of users grow, breaking constraints set phpmyadmin/mysql

you'll hard-pressed exceed mysql limits.

slow response part of application , details of sql queries more else.

finally. , important.

all technology goes out of date. eventually, must replace something. in order point you're forced upgrade, must first running.

don't worry "large database" until have numbers of rows in billions.

don't worry "long-term" solutions because software technology expires. quickly.

regarding number of users.

much of web interaction time spent interacting browser through javascript. or reading page. clicks sort of rare. mysql on reasonably big server should handle 30 or more concurrent queries sub-second response. application take little time format , start sending html page. things can rip along @ very, clip on typical server.

if database design avoids dreaded full-table scan.

you must have proper indexes mutual queries.

now. odds of 30 concurrent requests? if user clicks 1 time every 10 seconds (they have read page, fill in form, re-read page, think, drink beer) odds of 30 clicks in single sec means have have 300 concurrent users. considering people have other things in lives, means must have 50,000 or users (figuring they're spending 1 hr each week on site.)

mysql database-design multiple-databases