[DERBY-5784] Setting a parameter as NUMERIC fails to match stored value, but setting the parameter as untyped does match

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.10.1.1
• Component/s: JDBC
• Labels: derby_triage10_10
• Urgency: Normal
• Issue & fix info: Repro attached
• Bug behavior facts: Wrong query result
• Assignee: Unassigned
• Reporter: Richard N. Hillegas
• Created: 25/May/12 14:41
• Updated: 11/Jun/14 13:28

Description

I will attach a repro. The behavior should be the same according to table B-4 in the JDBC spec. Lance Andersen reports that other databases find the row using both setObject() overloads.