db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Closed: (DERBY-1859) No error thrown for an EOD query when allColumnsMapped=true but the data type of the field does not match the column in the query.
Date Fri, 06 Oct 2006 17:45:24 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1859?page=all ]

Daniel John Debrunner closed DERBY-1859.
----------------------------------------

    Resolution: Won't Fix

EoD is being dropped from JDBC 4.

> No error thrown for an EOD query when allColumnsMapped=true but the data type of the
field does not match the column in the query.
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1859
>                 URL: http://issues.apache.org/jira/browse/DERBY-1859
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.2.1.6, 10.3.0.0
>         Environment: Java(TM) SE Runtime Environment (build 1.6.0-rc-b98)
> Java HotSpot(TM) Client VM (build 1.6.0-rc-b98, mixed mode)
>            Reporter: Daniel John Debrunner
>            Priority: Minor
>
> With a column of type DECIMAL called BALANCE the BaseQuery object maps the column into
a field in the data class of type 'public String balance' but does not populate it.
> Changing the field to 'public BigDecimal balance' correctly populates it.
> Changing the field to a name of Xbalance, correctly throws the error that not all columns
are mapped.

-- 
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

        

Mime
View raw message