I've read much wisdom from fellow monks in the past about handling 64 bit numbers in a 32 bit world.
DBI is patently perfect. Math:Bigint is also perfect. But combining the two together isn't doing what I want, but it does do what I expect.
INSTERTing Math:Bigint to MySQL via DBI to a varbinary(16) column (correctly) converts the internal Math:Bigint representation to a binary string.
When SELECTing values back, DBI returns a string.
So when using my favourite fetchall->hashref() I get a string in the hash, and not a Bigint object.
Any way around this? Or is it a one way trip for objects into the DBI API?
What I'd really like is the _inverse_ of parameter binding as exemplified in $sth->bind_param( 3, 123500, { TYPE => SQL_VARCHAR } ); to convert varbinary(16) back into Math::Bigint objects. That would then call the "new" method on Math::Bigint when executing a fetchall->hashref.
Or do you have other wisdom to offer?
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.