db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1942) There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
Date Mon, 04 Jun 2007 17:02:48 GMT

    [ https://issues.apache.org/jira/browse/DERBY-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501271
] 

Kathey Marsden commented on DERBY-1942:
---------------------------------------

Tomohito said:
>* 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).

I am concerned about compatibility with regard to this patch as it was hit by several tests.
  I think it is likely to affect applications and am not sure that the benefit is worth that
risk.  At the very least we need a comprehensive release note.



> There exists difference between behavior of  setNull(Types.TIME) and setTiime(null).
> ------------------------------------------------------------------------------------
>
>                 Key: DERBY-1942
>                 URL: https://issues.apache.org/jira/browse/DERBY-1942
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>            Reporter: Tomohito Nakayama
>            Assignee: 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message