Using database is preferable in this situation IMHO, because:
- it is more scalable (if more users/more fieds added, flat-file performance will degrade much faster
- will add SQL/database skills to your toolset. It is better to start learning it on this kind of simple projects, so next time, when needed, you'll be ready...
I agree with dws that reading small flat file with file caching can be faster, but I believe we need to ask business questions: if small number of users, speed gain will not be important enough for not applying scalable solution, so why not to do it properly? Next time, when cynix will need accomodate more users, s/he can start with something better than flat files...
Just my $0.02
pmas
To make errors is human. But to make million errors per second, you need a computer.
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.