Does anybody knows ?

Thanks

Rafael Anschau wrote:

Multiply by 10 and add digit; repeat

That's neither a database nor a theory question, though.

On Mar 24, 11:38*am, Bob Badour <bbad... (AT) pei (DOT) sympatico.ca> wrote:
Asking what algorithm a database uses internaly is a database
question.

Rafael Anschau wrote:

The database implementation is likely to just call a procedure or
function akin to atoi.

On Mar 24, 1:02*pm, Bob Badour <bbad... (AT) pei (DOT) sympatico.ca> wrote:
It actually converts to binary. Just found out somewhere else, in case
someone is interested in how databases implements this particular
feature.

Rafael Anschau wrote:

My apologies. The "converts to binary" part was so obvious I didn't
think of it as an algorithm. I guess I lost the forest among the trees.

On 24 mar, 17:58, Rafael Anschau <rafael.ansc... (AT) gmail (DOT) com> wrote:

On Mar 24, 8:24*pm, Bob Badour <bbad... (AT) pei (DOT) sympatico.ca> wrote:

Unless my trusty old TI-86 is losing precision in embarrassing places,
I should also add that 64 bits doesn't quite suffice for 20 decimal
digits; it has 18 per cent or so of the total range, so you'd have to
go with 19 digits or three extra bits.
--
Sampo

On Apr 8, 10:57*am, Sampo Syreeni <de... (AT) iki (DOT) fi> wrote:

Indeed. So a few hypothesis:

1) Another algorithm is being used.
2) 72 bits are being used, and vendors are claiming 64 for marketing
purposes, the justification is that 67 is closer to 64 than 72,
notwithstanding the fact that 67 bits require full 72 bits on machines
with a byte size of 8.

There may of course be other hypothesis, thanks for bringing up this
very interesting fact.

Rafael Anschau wrote:

Does your big int support the full 20 decimal digit range, or does it
merely require 20 digits to represent the extrema of the range? From
your original question, I assumed the latter not the former.

If it support the full 20 decimal digit range, no algorithm will fit it
into 64 bits so choosing a different algorithm will achieve nothing.