In my experience, SQLite3 works great. It's benefit is that it is self-contained, and you don't need a giant db server going, like MySql or Postgres SQL. If you already are running MySQL or Postgres, you may as well make use of it. As mentioned above, with DBD, you can write the same code for any of those, and just make minor adjustments. I do this in ztkdb-sql. Right at the start of the script, it tests for which db you use, and adjusts accordingly; then let DBD take care of it.. So for ease of development, you can use SQLite3, and adjust for other dbs later.

(P.S. I'm not a db guru, so take my code for what it is, NOT perfect code. :-) )

I'm not really a human, but I play one on earth. Cogito ergo sum a bum

In reply to Re: SQLite3 use in production by zentara
in thread SQLite3 use in production by Akoya

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.