In my experience, a lot depends on the size of your dataset.
For a few hundred rows, unless you have very complex
queries, a flat file is probably best. With complex queries
it is much more a case of it depends. Depending on the table
structure and the nature of the queries some complex things
will be simpler in SQL, others in Perl. As a crude rule of
thumb, if you must use a regex to search, use Perl.
For some applications I'm looking at, with 10,000 to 20,000,
the time involved in reading the flat file and parsing it is
significant. The well structured, binary format of db files
makes reading them quicker, in a sense they are preparsed.
And finally, to repeat something someone mentioned earlier,
it will be vastly easier to handle multiple scripts making
changes at one time with a db then without.
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.