[DERBY-6089] CallableStatement#registerOutParameter on client lacks check of legal types.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.10.1.1
• Fix Version/s: 10.10.1.1
• Component/s: JDBC
• Labels: derby_backport_reject_10_8
• Issue & fix info: Repro attached
• Bug behavior facts: Deviation from standard
• Assignee: Richard N. Hillegas
• Reporter: Dag H. Wanvik
• Created: 22/Feb/13 04:39
• Updated: 09/Jul/13 12:58
• Resolved: 13/Mar/13 13:13

Description

Cf the attached negative test in a patch to PreparedStatement42.

In JDBC 4.2, the Javadoc for registerOutParameter(int parameterIndex,
int sqlType, String typeName) reads:

:
@exception SQLFeatureNotSupportedException if sqlType is a ARRAY,
BLOB, CLOB, DATALINK, JAVA_OBJECT, NCHAR, NCLOB, NVARCHAR,
LONGNVARCHAR, REF, ROWID, SQLXML or STRUCT data type and the JDBC
driver does not support this data type
:

For the new overloads, for embedded this is checked inside Util42#getTypeAsInt. The similar
client method, Utils42#getTypeAsInt does not do this checking.

Issue Links

• relates to: DERBY-6000 Implement support for JDBC 4.2