It is frequently necessary to use SQL placeholders, or to use perl variables as values in SELECT statements, as in:
my $myClient = 97; my $deliverymethod = 'USPS'; my $sql =<<"__SQL__"; SELECT ORDER_ID, .... CONVERSION_SERIAL FROM INTEGRATION.OL_ORDER WHERE CLIENT_ID = $myClient AND BATCH_ID = (SELECT * FROM (SELECT BATCH_ID FROM OL_ORDER WHERE CLIENT_ID = $myClient AND DELIVERY_METHOD ='$deliverymethod' GROUP BY BATCH_ID ORDER BY BATCH_ID DESC NULLS LAST) WHERE ROWNUM <= 1) __SQL__
So - this makes a case for in-lining the SQL.

        Profanity is the one language all programmers know best.


In reply to Re: SQL in files or File::Slurp? by NetWallah
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.