Actually, just
posting the data--that is, putting it into a simple database for read-only queries--isn't a bad use for MySQL, from what little I know about it.
But keeping the data that's uploaded is a whole 'nother story. I read that MySQL has been improved in the year since the original article was written, but I wouldn't even think about using it as was for anything critical.
Update: I spent a little time going through the MySQL manual, and I'm now convinced I wouldn't use it for most purposes. What improvements have been made are minor, from my point of view.
The idea of having some tables in a large database optimized for speed in read-only access is kind of neat, but I think it'd make more sense to use a proper RDBMS and export such tables into something like MySQL for that access.
adamsj
They laughed at Joan of Arc, but she went right ahead and built it. --Gracie Allen
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.