db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-4626) Timestamp truncated when converted to string with explicit calendar
Date Wed, 16 Feb 2011 21:21:24 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Mike Matrigali resolved DERBY-4626.

       Resolution: Fixed
    Fix Version/s:
         Assignee: C.S. Nirmal J. Fernando  (was: Mike Matrigali)

backported fix from trunk to 10.6 and 10.5.  resetting original owner and resolving.

> Timestamp truncated when converted to string with explicit calendar
> -------------------------------------------------------------------
>                 Key: DERBY-4626
>                 URL: https://issues.apache.org/jira/browse/DERBY-4626
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Assignee: C.S. Nirmal J. Fernando
>             Fix For:,,
>         Attachments: TimestampToVarchar.java, test.diff
> When setting the value of a VARCHAR parameter with setTimestamp() the timestamp is truncated
to microsecond resolution if a calendar is specified. Nanosecond resolution is preserved when
a calendar is not specified. These two methods should behave the same way. Since Derby supports
nanosecond resolution, the timestamps should not be truncated.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message