Unless you need experience using a database more than you need "soon", you'll be better off using a flat file. One thousand records isn't very much (if you have about 80 characters of data per line, that's only 80K). The overhead of searching a relatively small flat file is going to be a lot less than the overhead imposed by a database.
I would go simple at first. Use a comma-delimited file, and get at it through DBI via DBD::CSV (or some other DBD:: that supports text files). This will give you the programmatic experience of using a database. Then slip MySQL in undereath at a later date.
In reply to Re: Choosing a database for a new project
by dws
in thread Choosing a database for a new project
by newrisedesigns
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |