[ http://issues.apache.org/jira/browse/DERBY-453?page=comments#action_12322897 ]
Deepa Remesh commented on DERBY-453: ------------------------------------ As you said, setString would be more exact. Also, the method setBigDecimalString takes a String parameter and it would be better to use it directly. I will change setDouble to setString and submit another patch. > Create a test wrapper to run tests using BigDecimal in J2ME/CDC/Foundation > -------------------------------------------------------------------------- > > Key: DERBY-453 > URL: http://issues.apache.org/jira/browse/DERBY-453 > Project: Derby > Type: Improvement > Components: Test > Environment: J2ME/CDC/Foundation using IBM's WCTME 5.7 > Reporter: Deepa Remesh > Assignee: Deepa Remesh > Priority: Minor > Attachments: derby-453.diff, derby-453.status, > derby_453_outparams_patch1.diff, derby_453_outparams_patch1.status > > The following tests are currently excluded in J2ME/CDC/Foundation because > they use BigDecimal class. > I18NImportExport > batchUpdate > LOBTest > parameterMapping > resultset > StmtCloseFunTest > cast > functions > outparams > procedure > triggerRefClause > wisconsin > iepnegativetests > ieptests > importExportThruIJ > importExport > To run the above tests in this environment, test utility classes have to be > written so that the methods using BigDecimal are redirected depending on the > VM environment. The initial goal is to submit a patch for the test > resultset.java. After this, sub-tasks will be opened if changes are needed to > run the other tests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
