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] Commented: (DERBY-518) Data type mismatch error for boolean to DECIMAL conversion in J2ME
Date Thu, 15 Sep 2005 23:01:54 GMT
    [ http://issues.apache.org/jira/browse/DERBY-518?page=comments#action_12329500 ] 

Deepa Remesh commented on DERBY-518:

I merged the changes for DERBY-518 to 10.1 branch. 

264945 : Initial check-in 
265043: second check-in
279926: check-in to enable test resultset.java in J2ME

derbyall ran successfully with SUN jdk 1.4.2. The command I used for merge is:

svn merge -r 264944:264945 https://svn.apache.org/repos/asf/db/derby/code/trunk
svn merge -r 265042:265043 https://svn.apache.org/repos/asf/db/derby/code/trunk
svn merge -r 279925:279926 https://svn.apache.org/repos/asf/db/derby/code/trunk

Please update 10.1 branch with this patch.

> Data type mismatch error for boolean to DECIMAL conversion in J2ME
> ------------------------------------------------------------------
>          Key: DERBY-518
>          URL: http://issues.apache.org/jira/browse/DERBY-518
>      Project: Derby
>         Type: Bug
>   Components: JDBC
>  Environment: J2ME/CDC/Foundation Profile
>     Reporter: Deepa Remesh
>     Assignee: Deepa Remesh
>     Priority: Minor
>      Fix For:,
>  Attachments: derby-518_2.diff, derby-518_2.status, derby-518_3.diff
> The test jdbcapi/resultset.java gives the following error when run in J2ME/CDC/FP :
> Testing nullif(?,DECIMAL(10,5)) with setBoolean
> ERROR XCL12: An attempt was made to put a data value of type 'boolean' into a data value
of type 'DECIMAL'.
> I found that setValue(boolean) is not implemented in BigIntegerDecimal, which is the
class used for DECIMAL in J2ME. This is implemented in SQLDecimal and a similar implementation
can be provided in BigIntegerDecimal.
> On looking at the setValue methods in these classes, I also found that setValue(Object)
is implemented in SQLDecimal but not in BigIntegerDecimal.

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