[ http://issues.apache.org/jira/browse/DERBY-1942?page=all ]
Tomohito Nakayama updated DERBY-1942:
-------------------------------------
Attachment: DERBY-1942.patch
* Description of the patch
* Make it impossible to assign TIME type value to TIMESTAMP variable
in order to unify the behavior of setNull(Types.TIME) and setTime(null).
* Result of the test
* Executed derbyall and found only intermittent error in
derbynet/testSecMec.java.
> 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
