It should be ok as long as cust_phsx is a text type field with space for 4 characters. However as I expect might be the case it is a number type ( int or float etc ) of field and space is not legal.

Alternately since the database field is a number type, DBI is doing no escaping and your query is actually .... VALUES ( 3048770, 2, 3, 704,  53, 2 89, 45 ); which will appear to the SQL parser to be a missing comma between the 2 and the 89

If either of these hold, then you will have to clean up the numbers before handing them to the query. If the field was a text type DBI would change it to "2 89" which would be ok, but not for a number type of field.

Update: corrected the text in the query to have the correct numbers and added a code tag to make the spaces show up better.

In reply to Re: Using placeholders, getting unexpected SQL errors by dga
in thread Using placeholders, getting unexpected SQL errors by ok

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.