[ http://issues.apache.org/jira/browse/DERBY-1942?page=comments#action_12441434 ] Tomohito Nakayama commented on DERBY-1942: ------------------------------------------
This modification would affect DATETIMEDIFF scalar function. Now DATETIMEDIFF function accept java.sql.TIME as type compatible for parameters. However modification in this patch would take it as error. I think new behavior would proper behavior but a little strict.... In the JDBC spec, signature for TIMESTAMPDIFF function was described as next. TIMESTAMPDIFF(interval, An integer representing the number of interval timestamp1, timestamp2) I think this description is implicit definition that the parameter should be timestamp. Well ... I will take strict way, means to regard java.sql.TIME as incompatible type for parameters in DATETIMEDIFF function. > 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 > > 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
