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[] do
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
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 = -999
Hi Michelle,
I looked into the JIRA issue JDO-45: Need to do full build to get
company.xml copied to target dir
http://issues.apache.org/jira/browse/JDO-45
I propose to rename the maven goal copyloggingprops to copyprops and add
copying the company.xml file to it. Attached you find a patch inclu
Michelle,
You can use DECIMAL or NUMERIC types.
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 limits:
>
> "DOUBLE value ranges:
>
>
Hi Michael,
thanks a lot for the patch. I checked in the changes
(http://svn.apache.org/viewcvs?rev=170666&view=rev).
Regards Michael
Hi,
attached you find the patch file (rio.path) containing the changes
described below. Please execute "patch -E -p0 < rio.patch" to apply
the patch to your work
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
Hi,
attached you find the patch file (rio.path) containing the changes
described below. Please execute "patch -E -p0 < rio.patch" to apply the
patch to your workspace. Parameter "-E" will remove empty files.
If you decide to checkin the patch, please make sure that you add/remove
the files of t
