db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4626) Timestamp truncated when converted to string with explicit calendar
Date Wed, 21 Apr 2010 11:23:51 GMT

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

Knut Anders Hatlen updated DERBY-4626:
--------------------------------------

    Issue & fix info: [Repro attached]

> 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
>         Attachments: TimestampToVarchar.java
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message