empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francis De Brabandere (JIRA)" <empire-db-...@incubator.apache.org>
Subject [jira] [Commented] (EMPIREDB-170) DBDatabase.querySingleValue(cmd, conn) does not care about DataType
Date Fri, 14 Sep 2012 20:44:07 GMT

    [ https://issues.apache.org/jira/browse/EMPIREDB-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456123#comment-13456123

Francis De Brabandere commented on EMPIREDB-170:

Hi Daniel, did you run a source format? A lot of formatting was changed in the commit so it's
kind of hard to find the actual changed part...
> 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
>            Priority: Minor
>         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