I second the suggestion to check out DBD::CSV.

The idea of being "SQL like" and having the upgrade path to a "real" SQL is certainly a plus.

As to performance, I've found that for reasonably small tables, selecting is no slower than for a real db since there's no overhead of talking to the database. Insert/Update/Delete are murder for large files since I think it reads/writes the entire file for each operation.

But since the data is in a plain text file, for large update operations (like building the search index), you could probably do a Perl-only choice that would be very fast to write the file, then SQL to read.

And finally, when you don't want to do SQL, you can always use vi to "update the table".

In reply to Re: (Ovid) Re: Poor Person's Database by voyager
in thread Poor Person's Database by Cody Pendant

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.