hey all!
I'm working with MySQL and may be confronted with building a PERL web application script that needs to handle a larcge/or rich database.
Basically I want to know whether to use rows or tables.
The web app is for members to create their own individual polls, and other members on the site can vote for a choice.
Now lets say this site gets big big--100,000 to 500,000 members (thats considered big for me).
Then lets say about 50,000 of those members decide to make a online poll each day then that will be a lot of database updating.
--So my question is, should I make individual tables for each member to keep track of their a poll (many tables since many members) or have the poll data inside a single table--therefore many polls would be many rows.
I also want people to keep track of their poll results/poll history--therefore I'm not sure by searching one single table with many poll data and rows is a good idea? What is considered a large amount of rows to search through?
Thank you all!
perleager
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.