[DERBY-5534] ResultSet#updateFloat, #updateDouble do not check for NaN and other conditions on client

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 10.8.2.2
• Component/s: JDBC, Network Client
• Labels: derby_triage10_9
• Urgency: Normal
• Issue & fix info: Newcomer, Repro attached
• Bug behavior facts: Embedded/Client difference
• Assignee: Unassigned
• Reporter: Dag H. Wanvik
• Created: 13/Dec/11 01:49
• Updated: 20/May/12 13:15

Description

In updateXXX, where XXX is one of Float or Double, embedded throws value out of range when the argument is Float.NaN or Double.NaN, the client does not catch it.

The server will balk when the row is updated, though, in ResultSet#updateRow. It will be more regular if this is caught in updateXXX also on the client as other range errors are. The SQL state seen is 22003, which is what embedded throws on updateXXX. See also DERBY-5533.

Issue Links

• is related to: DERBY-5533 Client differs from embedded when rs.updateInt overflows: 22015 vs 22003
• is related to: DERBY-5546 ResultSet#updateBigDecimal on a REAL column does not do underflow checking
• is related to: DERBY-3290 Derby cannot store java Double or Float values .NaN and .[POSITIVE|NEGATIVE]_INFINITY
• is related to: DERBY-3398 Support min/max values for Java types float/double in real/double columns