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.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.