[DERBY-5533] Client differs from embedded when rs.updateInt overflows: 22015 vs 22003

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 10.9.1.0
• Component/s: JDBC, Network Client
• Labels: derby_backport_reject_10_8
• Bug behavior facts: Deviation from standard, Embedded/Client difference
• Assignee: Dag H. Wanvik
• Reporter: Dag H. Wanvik
• Created: 12/Dec/11 19:04
• Updated: 09/Jul/13 14:09
• Resolved: 17/Dec/11 00:27

Description

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

Issue Links

• is related to: DERBY-5536 Client's ResultSet#getLong does not range check when converting from a DECIMAL column
• is related to: DERBY-5546 ResultSet#updateBigDecimal on a REAL column does not do underflow checking
• relates to: DERBY-5534 ResultSet#updateFloat, #updateDouble do not check for NaN and other conditions on client