Re: [libdbi-users] dbi_result_get_ulonglong overflow

2010-01-13 Thread Devin Reade
Markus Hoenicka markus.hoeni...@mhoenicka.de wrote: I've had a look at libdbi-driver's current ato*() usage. As far as I can see it is used only to turn raw row data into integers by functions which do not return values, i.e. without an easy way to indicate conversion errors. I haven't

Re: [libdbi-users] dbi_result_get_ulonglong overflow

2010-01-09 Thread Markus Hoenicka
Devin Reade writes: The ato* are indeed often implemented in terms of strto*. The problem is that the ato* signature just doesn't lend itself to error checks, so even if they wrap strto*, error information gets lost in the wrapper layer. What about the portability of the strto*

Re: [libdbi-users] dbi_result_get_ulonglong overflow

2010-01-08 Thread Vikram Noel Ambrose
Vikram Noel Ambrose wrote: I can't seem to read back BIGINT UNSIGNED (8bytes) from a mysql database. For example: A value of 10988581603938712255 = 0x987F48BFB028BABF is returned as 9223372036854775807 = 0x7FFF Something somewhere is capping off my BIGINT UNSIGNED to the

Re: [libdbi-users] dbi_result_get_ulonglong overflow

2010-01-08 Thread Devin Reade
Markus Hoenicka markus.hoeni...@mhoenicka.de wrote: To better deal with your shock: Could you please elaborate what's wrong with atoll()? In the particular case of this use in libdbi, I've not looked at the code to see to what extent it is an *actual* problem; however as a generalization, I