[
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: 10.6.2.3
10.5.3.2
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: 10.5.3.0
> Reporter: Knut Anders Hatlen
> Assignee: C.S. Nirmal J. Fernando
> Fix For: 10.5.3.2, 10.6.2.3, 10.7.1.1
>
> 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
