db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DERBY-6089) CallableStatement#registerOutParameter on client lacks check of legal types.
Date Fri, 22 Feb 2013 04:40:13 GMT
Dag H. Wanvik created DERBY-6089:
------------------------------------

             Summary: CallableStatement#registerOutParameter on client lacks check of legal
types.
                 Key: DERBY-6089
                 URL: https://issues.apache.org/jira/browse/DERBY-6089
             Project: Derby
          Issue Type: Bug
          Components: JDBC
    Affects Versions: 10.10.0.0
            Reporter: Dag H. Wanvik


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.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message