db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5533) Client differs from embedded when rs.updateInt overflows: 22015 vs 22003
Date Wed, 14 Dec 2011 13:41:30 GMT

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

Rick Hillegas commented on DERBY-5533:

Thanks for the impressive battery of new tests, Dag! ParameterMappingTest doesn't have a header
comment explaining its purpose in life, but it seems to try to run a comprehensive battery
of tests against the getXXX() and setXXX() methods. UpdateXXXTest, according to its header
comment, is a test for updatable ResultSets. If this fix is not specific to updatable ResultSets,
ParameterMappingTest might be a better home for it. But I don't think it would hurt to leave
the tests where you put them originally. Thanks!
> Client differs from embedded when rs.updateInt overflows: 22015 vs 22003
> ------------------------------------------------------------------------
>                 Key: DERBY-5533
>                 URL: https://issues.apache.org/jira/browse/DERBY-5533
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Network Client
>            Reporter: Dag H. Wanvik
>            Priority: Minor
>         Attachments: derby-5533-repro.diff, derby-5533-test.diff
> stm.executeUpdate("create table t(i smallint)");
> stm.executeUpdate("insert into t values 1,2,3,4");
> ResultSet rs = stm.executeQuery("select i from t");
> rs.next();
> try {
>     rs.updateInt(1, 100000);
> } catch (SQLException e) {
>     // client: 22015 vs embedded 22003
> }
> According to the standard, 22015 should be used for INTERVALs ("interval field overflow").
22003 seems more correct, the standard uses that for "numeric value out of range".

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message