I don't know where you got that 1.16 distribution from because the diff does not make sense against 1.16 code at that point which already contains:

case SQL_VARBINARY: case SQL_BINARY: fbh->ftype = SQL_C_BINARY; break; #if defined(WITH_UNICODE) case SQL_WCHAR: case SQL_WVARCHAR: fbh->ftype = SQL_C_WCHAR; /* MS SQL returns bytes, Oracle returns characters ... */ fbh->ColDisplaySize*=sizeof(WCHAR); fbh->ColLength*=sizeof(WCHAR); break; #endif /* WITH_UNICODE */

However, the salient point of it is setting ColDisplaySize.

The reason why it is not in DBD::ODBC is no one has told the current maintainer about it - namely me - I just came across this thread. This will be included in 1.17.


In reply to Re^2: dbix::simple & varbinary(MAX) by mje
in thread dbix::simple & varbinary(MAX) by Lyndley

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.