[
https://issues.apache.org/jira/browse/DERBY-5533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-5533:
---------------------------------
Attachment: derby-5533b.stat
derby-5533b.diff
Uploading a new version of the patch, "derby-5513b". It adds more tests for the
floating point types. This led to the posting of DERBY-5546, too. The test has
many test cases that should be fixed up when the follow-on issues (all linked
to this issue) are fixed.
> 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
> Assignee: Dag H. Wanvik
> Priority: Minor
> Attachments: derby-5533-repro.diff, derby-5533-test.diff,
> derby-5533.diff, derby-5533.stat, derby-5533b.diff, derby-5533b.stat
>
>
> 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
