[
https://issues.apache.org/jira/browse/DERBY-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472332
]
Jean T. Anderson commented on DERBY-2304:
-----------------------------------------
Yes, you're absolutely right about the naming confusion. Naming the method I
have working so far, which uses compareTo, "assertDecimalSameValue" would make
far more sense.
So far I haven't had success with an equality operation, even with variations
on scale and roundingMode as in:
BigDecimal expected = (new BigDecimal(val1));
expected = expected.setScale(4); // the procedure uses DECIMAL(14,4)
or:
expected = expected.setScale(4, BigDecimal.ROUND_HALF_UP); // 8
rounding modes
then:
assertEquals(msg, val1, val2);
I'll keep working on an equality check.
> Convert derbynet/callable.java to junit
> ---------------------------------------
>
> Key: DERBY-2304
> URL: https://issues.apache.org/jira/browse/DERBY-2304
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Reporter: Jean T. Anderson
> Assigned To: Jean T. Anderson
> Priority: Minor
> Attachments: derby-2304-preview-2.diff, derby-2304-preview-3.diff,
> derby-2304-preview.diff
>
>
> Convert the derbynet.callable.java test to the junit framework.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
