these files come from a well known distributor so there is little to no concern of anything malicious

I've read stories about manufactured floppies and/or CDs with viruses. I've read stories about manufactured audio CDs with root kits. I'm not talking about random stuff you pull down from the seedy side of the internet, either. I'm talking about big-name manufacturers.

The company may not be malicious, but the guy who produces this data may be having a bad day, found a new job, and is going to quit tomorrow.

In my experience, it's actually easier to use placeholders than not. On top of that, it's more secure, and may even be faster at runtime (for example, there's less for the DB server to parse and mangle, plus if you prepare a single query and use it multiple times, there's a bunch of text that only needs parsing once). My experience says that there is no downside to using placeholders. Arguably there is a bit more code to deal with (especially if you're manually binding variables), but there doesn't have to be, and if you try to compare the amount of code for an insecure (not-working in your case) snippet vs a secure (working) snippet, that's apples and bananas anyway.

In reply to Re: Inserting Apostrophes into SQL by Tanktalus
in thread Inserting Apostrophes into SQL by aheusdens

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.