[ http://issues.apache.org/jira/browse/DERBY-1942?page=comments#action_12442640 ] Dag H. Wanvik commented on DERBY-1942: --------------------------------------
Should this issue perhaps have the "existing application impact" and release note needed" flags set? It seems you have made something illegal that worked before... > There exists difference between behavior of setNull(Types.TIME) and > setTiime(null). > ------------------------------------------------------------------------------------ > > Key: DERBY-1942 > URL: http://issues.apache.org/jira/browse/DERBY-1942 > Project: Derby > Issue Type: Bug > Components: JDBC > Reporter: Tomohito Nakayama > Assigned To: Tomohito Nakayama > Attachments: DERBY-1942.patch > > > The result of setNull(java.sql.Types.TIME) for TIMESTAMP typed variable is > regarded as error. > However, the result of setTime(null) for TIMESTAMP typed variable is not > regarded as error . > see http://issues.apache.org/jira/browse/DERBY-1610#action_12436554 -- 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
