Are you also worried about people deleting the scripts?

I can see a benefit to the first if multiple scripts use the same SQL. See DBIx::PreQL for an alternative approach.

A third option is to step one layer back, load a module (use OurSystem::Orders), and call my @orders = OurSystem::Orders::getOrders. Store how you construct the data in the module (OurSystem::Orders), and don't let it near your scripts. Then if your back-end representation changes (different database, normalization of data, web service, whatever), you don't need to change all of your scripts. You also consolidate all of the DBI handling in one location.

--MidLifeXis

In reply to Re: SQL in files or File::Slurp? by MidLifeXis
in thread SQL in files or File::Slurp? by crusty_collins

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.