You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Tomohito Nakayama (JIRA)" <de...@db.apache.org> on 2006/10/10 16:33:20 UTC
[jira] Commented: (DERBY-1942) There exists difference between
behavior of setNull(Types.TIME) and setTiime(null).
[ http://issues.apache.org/jira/browse/DERBY-1942?page=comments#action_12441151 ]
Tomohito Nakayama commented on DERBY-1942:
------------------------------------------
Reading the spcec, java.sql.Time is not compatible to JDBC TIMESTAMP.
> 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