[OPENJPA-1158] Incorrect handling of long values in AbstractResult

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 1.3.0, 2.0.0-M3
• Component/s: jdbc
• Patch Info: Patch Available
• Assignee: Donald Woods
• Reporter: Craig L Russell
• Created: 03/Jul/09 20:17
• Updated: 09/Mar/10 18:31
• Resolved: 14/Sep/09 20:07

Description

This code is in org.apache.openjpa.jdbc.sql.AbstractResult.

public long getLong(Object obj)
throws SQLException

{ return getLongInternal(translate(obj, null), null); }

public long getLong(Column col, Joins joins)
throws SQLException

{ return getLongInternal(translate(col, joins), joins); }

protected long getLongInternal(Object obj, Joins joins)
throws SQLException

{ Number val = (Number) checkNull(getObjectInternal(obj, JavaTypes.INT, null, joins)); return (val == null) ? 0 : val.intValue(); }

It seems like it's an obvious bug; using intValue and JavaTypes.INT in getLongInternal should use longValue and JavaTypes.LONG.