ay Gabor [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 15, 2001 11:16 PM
To: Shankar Unni
Cc: [EMAIL PROTECTED]
Subject: Re: About huge numbers
On Thu, 15 Nov 2001, Shankar Unni wrote:
Thank you for your answers.
> Generally, you don't want to store currencies in floating point,
anywa
On Thu, 15 Nov 2001, Shankar Unni wrote:
Thank you for your answers.
> Generally, you don't want to store currencies in floating point, anyway,
> and it's unfortunate that MySQL implements DECIMAL as floating point rather
> than a variable-length BCD (which is exact).
Yes. This is strange,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
El Jueves 15 Noviembre 2001 13:15, escribiste:
> Gyulay Gabor wrote:
> > The problem is that I need to store numbers with lot more
> > than 16 decimal digits - e.g. 1234567890123456789012345.12
> > [...]
> >
> > The reason is why we need this that the
Gyulay Gabor wrote:
> The problem is that I need to store numbers with lot more
> than 16 decimal digits - e.g. 1234567890123456789012345.12
> [...]
> The reason is why we need this that there're several
> currencies (like italian lire) which requires this kind of
> precision.
Excellent answer
| > One more question is how to transfer these values through
| > the MySQL C api ?
try this site...
http://www.mathtools.net/C++/Extra_precision_computation/
ati
-
Before posting, please check:
http://www.mysql.com/manual.
Gyulay Gabor writes:
> Please let me know, how to handle huge numbers.
I'll give you a suggestion or two, but first of all
I must ask you to set your time to something more
correct. If you're in the UK (or Portugal), your time
is off by about 7 hours. If you're elsewhere, I guess
your time zone
Please let me know, how to handle huge numbers.
The problem is that I need to store numbers with lot more
than 16 decimal digits - e.g. 1234567890123456789012345.12
I already tried a decimal type but it caused errors (I mean
MySQL simply cutted the end of the numbers and stored only
the first 16
