empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Döbele (JIRA) <empire-db-...@incubator.apache.org>
Subject [jira] [Resolved] (EMPIREDB-170) DBDatabase.querySingleValue(cmd, conn) does not care about DataType
Date Thu, 05 Sep 2013 10:00:54 GMT

     [ https://issues.apache.org/jira/browse/EMPIREDB-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Rainer Döbele resolved EMPIREDB-170.

       Resolution: Fixed
    Fix Version/s: empire-db-2.4.2
         Assignee: Rainer Döbele

created a new overload DBDatabase.querySingleValue(DBCommand cmd, DataType dataType, Connection
conn) that allows to specify the expected return type.
> DBDatabase.querySingleValue(cmd, conn) does not care about DataType
> -------------------------------------------------------------------
>                 Key: EMPIREDB-170
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-170
>             Project: Empire-DB
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: empire-db-2.4.2
>         Environment: any
>            Reporter: Daniel Weidele
>            Assignee: Rainer Döbele
>            Priority: Minor
>             Fix For: empire-db-2.4.2
>         Attachments: patch.txt
>   Original Estimate: 1h
>  Remaining Estimate: 1h
> Making use of DBDatabase.querySingleValue(cmd, conn) seems to ignore the DataType of
the select expression. This can result in erreneous behaviour, e.g. when trying to select
a number(1,0) column as boolean for Oracle, as empire-db reads the value as Number, instead
of the declared BOOL in table defintions.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message