Commented by: @krilbe

Delphi has "since forever" had an extra floating point type called Extended that uses 10 byte (80 bit) and according to the specs i supports 19 significant digits and a an exponent (base 10) ranging from -4932 to +4932. I'm not sure if this is a type that exists outside Delphi, e.g. in hardware, but perhaps it would be a good idea for Firebird? Seems large enough for most real world scenarios and instead of yet another type/format, why not use something that's already "out there"?

After checking the net I found this.
http://en.wikipedia.org/wiki/Floating_point
It claims that "Double extended" is hardware supported by x86 hardware, and it seems to be the same type that Delphi offers. It also mentions that C usually makes it available as "long double". Could this type be added to Firebird and would it meet your needs Pavel?

Commented by: @pavel-zotov

> Could this type be added to Firebird and would it meet your needs Pavel?

I think that only bulk of tests can show is it (80 bits) enough for daily routines or not.

Another (and I think - better) alternative is pass arguments from FB to java stored procedure which, in turn, uses built-in BigDecimal class functionality. Results of calculations in this manner can be obtained with arbitrary precision, no rounding errors at all
(see: http://docs.oracle.com/javase/1.5.0/docs/api/java/math/BigDecimal.html )
Unfortunatelly (AFAIK) Adriano not yet finished the work on this subject.

Commented by: @dyemanov

We had plans to have BigDecimal supported natively inside the engine, but this has nothing to do with Java related work by Adriano. However, this project is about long *exact* numerics, not approximate numerics. So this is unlikely to affect the POWER issue which the SQL standard require to return an approximate number.

Commented by: @pavel-zotov

> this project is about long *exact* numerics, not approximate numerics

So, this would be like BigInteger in java, isn`t ?
http://docs.oracle.com/javase/1.5.0/docs/api/java/math/BigInteger.html

Commented by: @dyemanov

Yes, more or less.

Commented by: @pavel-zotov

> We had plans to have BigDecimal supported natively

You say "had" rather than "have" :-)
Does it mean that these intentions were cancelled or they are frozen for some time ?

Commented by: @dyemanov

Just postponed. Please let's avoid polluting this ticket with unrelated questions.

Commented by: @dyemanov

Shouldn't this ticket be closed now, given the new DECFLOAT data type?