To track down a cast error, you need to find where the type conversion is being done and where the invalid data is coming from. Conversion errors happen freqently when passing data from Perl, especially when Perl chooses the wrong type to send to the database. Unless there is more code that you aren't showing us, the code isn't passing parameters and this is not the problem.

Since this is a static query, that Query Analyzer and Perl have different results is surprising. Try rewriting the SQL to eliminate the CASE, or use the other form of the CASE. CASE ... END AS is_complete is the same and might cause problems. Also, you might want to parse the date in Perl.

In reply to Re: SQL Server CAST problem using CASE with DBD::ODBC by iburrell
in thread SQL Server CAST problem using CASE with DBD::ODBC by simon.proctor

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.