You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2012/09/25 22:48:07 UTC

[jira] [Updated] (DERBY-5784) Setting a parameter as NUMERIC fails to match stored value, but setting the parameter as untyped does match

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

Mamta A. Satoor updated DERBY-5784:
-----------------------------------

    Labels: derby_triage10_10  (was: )
    
> Setting a parameter as NUMERIC fails to match stored value, but setting the parameter as untyped does match
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5784
>                 URL: https://issues.apache.org/jira/browse/DERBY-5784
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.10.0.0
>            Reporter: Rick Hillegas
>              Labels: derby_triage10_10
>         Attachments: DERBY_5784.java
>
>
> I will attach a repro. The behavior should be the same according to table B-4 in the JDBC spec. Lance Andersen reports that other databases find the row using both setObject() overloads.

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