Hi Michelle,
We should not use Double.MIN_VALUE and MAX_VALUE in TCK tests. I had changed a number of these to fix a similar bug last year, but apparently overlooked this class.
We decided to use these values for double in the AllTypes class:
public static final double DOUBLE_SMALLEST = -9999999999999.9;
public static final double DOUBLE_LARGEST = 9999999999999.9;
public static final double[] double_values =
{ DOUBLE_SMALLEST, DOUBLE_LARGEST, 0.0, 100.0, 100.0,
50000000.0, -234234.234, 1000000000.0, 350.5, -25.5 };I'd be happy to use DOUBLE_LARGEST and DOUBLE_SMALLEST from AllTypes.
What do you all think?
Craig
On May 17, 2005, at 11:26 AM, Michelle Caisse wrote:
TestFieldsOfDouble fails because the test attempts to persist values of Double.MIN_VALUE and Double.MAX_VALUE and the Derby double datatype has narrower limits:
"DOUBLE value ranges:
* Smallest DOUBLE value: -1.79769E+308 * Largest DOUBLE value: 1.79769E+308 * Smallest positive DOUBLE value: 2.225E-307 * Largest negative DOUBLE value: -2.225E-307
These limits are different from the java.lang.DoubleJava type limits."
Any suggestions on how to handle this?
-- Michelle
Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
