[ http://issues.apache.org/jira/browse/DERBY-1938?page=comments#action_12441001 ] Tomohito Nakayama commented on DERBY-1938: ------------------------------------------
Next information was posted to mailing list. The following wording was added to the JDBC 4.0 javadocs to address this issue: Note: Not all databases allow for a non-typed Null to be sent to the backend. For maximum portability, the setNull or the setObject(int parameterIndex, Object x, int sqlType) method should be used instead of setObject(int parameterIndex, Object x). I think the decision should be deferred and wait for requests ... > 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 > Attachments: DERBY-1938.patch > > > 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
