The main difference is that SQLite is a much lighter engine that MySQL. This means that your application will have to do many more things that MySQL usually did for you. I'm in the process of converting one of my apps from Oracle to MySQL and while there's not a lot of changes, there's a few. (Primarily things like NVL() -> IFNULL() and the like.)

One thing we've considered is subclassing our database class. We have a class called ABCD::Database which provides business-level functions to the other classes. Sort of like canned queries. You could have an ABCD::Database::MySQL and an ABCD::Database::SQLite, which will seriously aid your migration.

The actual Perl you use will probably change very little, if at all. The changes will be in the SQL you use. (Unless, of course, you were using formatting functions in your SQL, in which case you may have to provide that functionality yourself.)

------
We are the carpenters and bricklayers of the Information Age.

Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose

I shouldn't have to say this, but any code, unless otherwise stated, is untested

In reply to Re: how to use DBD::SQLite by dragonchild
in thread how to use DBD::SQLite by Anonymous Monk

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.