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 "Kathey Marsden (JIRA)" <ji...@apache.org> on 2013/07/09 16:09:55 UTC
[jira] [Updated] (DERBY-5533) Client differs from embedded when
rs.updateInt overflows: 22015 vs 22003
[ https://issues.apache.org/jira/browse/DERBY-5533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-5533:
----------------------------------
Labels: derby_backport_reject_10_8 (was: )
Label derby_backport_reject_10_8. Shouldn't backport SQLState change
> 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
> Labels: derby_backport_reject_10_8
> Fix For: 10.9.1.0
>
> Attachments: derby-5533b.diff, derby-5533b.stat, derby-5533.diff, derby-5533-repro.diff, derby-5533.stat, 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
For more information on JIRA, see: http://www.atlassian.com/software/jira