db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepa Remesh (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-453) Create a test wrapper to run tests using BigDecimal in J2ME/CDC/Foundation
Date Fri, 09 Sep 2005 16:43:30 GMT
     [ http://issues.apache.org/jira/browse/DERBY-453?page=all ]

Deepa Remesh updated DERBY-453:

    Attachment: derby_453_outparams_patch2.diff

I am re-submitting the patch as derby_453_outparams_patch2.diff. In the new patch, I commented
out java.sql.Types.BOOLEAN since it is not available in jdk13.

I tried changing setString to setDouble in BigDecimalHandler but then, the testcase failed
for takesShortPrimitive procedure. It gave a "Invalid character string format exception for
SMALLINT". This is because the value used is "666.666". If a String which can be converted
to short is used (like "666"), this would not be a problem. On the other hand, if setDouble
is used, the conversion to short  is taken care of. 

So I am continuing to use setDouble. I agree this will compromise the precision of values.
But since this testcase is not dependent on precision, I think it should be okay.  If you
think of other reasons for this change, please share them.


> 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
> 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:
For more information on JIRA, see:

View raw message