True dat. Take the $time to type the extra characters now and you will save ($time * 10) in debugging later.

Especially now that you have discovered a good way to keep your parameters in an external ini file. The lines in that file are free! You should fill that file up with one entry per SQL statement and use the right one for each task.

As the poster above said, making dynamic SQL statements is as dangerous as making soft references (variable names made from variable values in your program).

The only thing that should be dynamic in your SQL statements is the bind placeholder(s).

Slow down, and do it right!

Remember: Ne dederis in spiritu molere illegitimi!

In reply to Re^2: Return a value by 1nickt
in thread Return a value by bhushanQA

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.