[
http://issues.apache.org/jira/browse/DERBY-1938?page=comments#action_12440804 ]
Tomohito Nakayama commented on DERBY-1938:
------------------------------------------
In the spec of jdbc-3_0, I found next content.
13.2.2.2 Type Conversions Using the Method setObject
<snip>
If setObject is called without a type parameter, the Java Object
mapped using the default mapping for that object type.
<snip>
13.2.2.3 Setting NULL Parameters
<snip>
If a Java null is passed to any of the setter methods
parameter will be set to JDBC NULL.
According to this content, I think we can remove code to throw exception of
dataTypeConversion in
http://issues.apache.org/jira/browse/DERBY-1938#action_12440800 .
> Add support for setObject(<arg>, null)
> --------------------------------------
>
> Key: DERBY-1938
> URL: http://issues.apache.org/jira/browse/DERBY-1938
> Project: Derby
> Issue Type: Improvement
> Components: JDBC
> Reporter: Dag H. Wanvik
> Assigned To: Tomohito Nakayama
> Priority: Minor
>
> Derby presently does not implement support for the method
> PreparedStatement.setObject (and similarly for CallableStatement.setObject)
> when the supplied value is null, unless a type argument (3rd arg) is also
> present.
> That is, in:
> void setObject(int parameterIndex,
> Object x)
> throws SQLException
> x can not be null.
> Derby will presently throw an SQLException (client: XJ021, embedded: 22005)
> if x is null when calling this method on a preparedStatement.
> Porting some applications may be made easier if this restriction is lifted.
> See also discussion in DERBY-1904.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
