I've created JIRA issue JDO-50 for this.
-- Michelle
Niclas Hedhman wrote:
On Wednesday 18 May 2005 06:01, Craig Russell wrote:
We decided to use these values for double in the AllTypes class:
public static final double DOUBLE_SMALLEST = -9.9;
public static final double
On Wednesday 18 May 2005 06:01, Craig Russell wrote:
We decided to use these values for double in the AllTypes class:
public static final double DOUBLE_SMALLEST = -9.9;
public static final double DOUBLE_LARGEST = 9.9;
public static final double[]
Hi Niclas,
Your idea seems reasonable. I believe we already have a rounding
algorithm in the tests, so putting in some explicit known tricky cases
would be a good test.
Craig
On May 17, 2005, at 10:37 PM, Niclas Hedhman wrote:
On Wednesday 18 May 2005 06:01, Craig Russell wrote:
We decided to
Michelle,
You can use DECIMAL or NUMERIC types.
column sql-type=DECIMAL scale precision length/
Quoting Michelle Caisse [EMAIL PROTECTED]:
TestFieldsOfDouble fails because the test attempts to persist values of
Double.MIN_VALUE and Double.MAX_VALUE and the Derby double datatype has
narrower
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 =
Hi Michelle, Hi Craig,
I recall we had a similar issue with the TCK 1.0.1.
I think the test case does not really require the values
Double.MIN_VALUE and Double.MAX_VALUE. So maybe we can use different
double values for the test.
Regards Michael
TestFieldsOfDouble fails because the test attempts
