[DERBY-5546] ResultSet#updateBigDecimal on a REAL column does not do underflow checking

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.2.1.6, 10.2.2.0, 10.3.1.4, 10.3.2.1, 10.3.3.0, 10.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2, 10.8.3.0, 10.9.1.0
• Fix Version/s: 10.9.2.2, 10.10.1.1
• Component/s: JDBC
• Labels: derby_backport_reject_10_8 derby_triage10_9
• Urgency: Normal
• Issue & fix info: Repro attached
• Bug behavior facts: Data corruption
• Assignee: Dag H. Wanvik
• Reporter: Dag H. Wanvik
• Created: 16/Dec/11 18:08
• Updated: 08/Aug/13 16:37
• Resolved: 20/Feb/13 04:24

Description

In contrast, ResultSet#updateBigDecimal on a FLOAT or DOUBLE column gives the expected error on underflow. Cf. the attached repro program MissingUnderflowCheck.

Issue Links

• relates to: DERBY-5534 ResultSet#updateFloat, #updateDouble do not check for NaN and other conditions on client
• relates to: DERBY-5533 Client differs from embedded when rs.updateInt overflows: 22015 vs 22003