MySQL has a "BIGINT" column type, which is 64-bit. This, I have found, is useful in AUTO_INCREMENT columns with high churn, such that you will burn through all 232-1 possibilities in a relatively short amount of time. Although I don't expect to use much more than say 34-35 bits, I do worry that Perl is going to blow a gasket on large numbers which could be introduced somehow into that. How do you handle these oversize numbers safely using DBI?

split 64 bit number inspired this question, because I had taken for granted Perl's ability to cope with "large" numbers, such as integers bigger than 32 bits. wog pointed out that support for 64-bit math can be compiled in, but is optional. Is this going to be a standard any time soon, at least in the "enabled if availble" capacity?

In reply to 64-Bit Values and DBI by tadman

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.