Of course, all engineering is balancing the trade-offs.
The maximum positive value of a BIGINT is 9223372036854775807, which
suggests that it can store any 18 digit value accurately, which perhaps
solves the problem. BIGINT, like DOUBLE, requires 8 bytes storage, so
you are neutral in that regard
I stand corrected.. I thought I recalled that the IEEE for double
precision offered 18 digits of accuracy (been years since I looked at
it) but a little research shows me 15.
- michael dykman
On Wed, 2005-02-02 at 14:02, Roger Baklund wrote:
> Michael Dykman wrote:
> [...]
> > The MySQL impleme
Keith Ivey wrote:
Roger Baklund wrote:
Galen wrote:
I've got a huge table going, and it's storing a load of numeric data.
Basically, a percentage or single digit rank, one or two digits
before the decimal and fifteen after, like this:
6.984789027653891
39.484789039053891
[snip]
You should not us
Michael Dykman wrote:
[...]
The MySQL implementation also supports this optional
precision specification, but the precision value is used only to
determine storage size.
Right. This means you can not have 15 decimals precision using DOUBLE:
mysql> use test
Database changed
mysql> create table dtest
Roger Baklund wrote:
Galen wrote:
I've got a huge table going, and it's storing a load of numeric data.
Basically, a percentage or single digit rank, one or two digits before
the decimal and fifteen after, like this:
6.984789027653891
39.484789039053891
[snip]
You should not use FLOAT, it is an
On Wed, 2005-02-02 at 12:46, Roger Baklund wrote:
> Galen wrote:
> > I've got a huge table going, and it's storing a load of numeric data.
> > Basically, a percentage or single digit rank, one or two digits before
> > the decimal and fifteen after, like this:
> >
> > 6.984789027653891
> > 39.48
Galen wrote:
I've got a huge table going, and it's storing a load of numeric data.
Basically, a percentage or single digit rank, one or two digits before
the decimal and fifteen after, like this:
6.984789027653891
39.484789039053891
What is the most efficient way to store these values? I will be
From: "Galen" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, February 02, 2005 9:15 AM
Subject: Best way to store numeric data?
> I've got a huge table going, and it's storing a load of numeric data.
> Basically, a percentage or single digit rank, one or two digits b
I've got a huge table going, and it's storing a load of numeric data.
Basically, a percentage or single digit rank, one or two digits before
the decimal and fifteen after, like this:
6.984789027653891
39.484789039053891
What is the most efficient way to store these values? I will be
frequently
