Whether you tie your app to one specific database, or use Class::DBI, you should still have your own abstraction. It should be application specific, yet hide the details of how the data is coming into existence. That way, even if you are hard tied to one database, all the hard ties are in one spot. Most of your application will simply talk to your data layer, and your data layer will talk to DBI, or Class::DBI, or whatever.

Update: to answer your question more directly, I usually tend to go with hard coded SQL directly against DBI. I rarely change databases, and if so, my standard abstraction layer approach saves me from most of the trouble.

In reply to Re: Should it be database independent? by Mugatu
in thread Should it be database independent? by szabgab

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.