[
https://issues.apache.org/jira/browse/DERBY-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-4625:
----------------------------------
Fix Version/s: (was: 10.6.2.1)
(was: 10.5.3.0)
10.6.2.3
10.5.3.2
fixing released version for the backports. mistakenly picked released versions
rather than unreleased versions.
> TIMESTAMP function doesn't accept nanoseconds
> ---------------------------------------------
>
> Key: DERBY-4625
> URL: https://issues.apache.org/jira/browse/DERBY-4625
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.5.3.0
> Reporter: Knut Anders Hatlen
> Assignee: C.S. Nirmal J. Fernando
> Priority: Minor
> Fix For: 10.5.3.2, 10.6.2.3, 10.7.1.1
>
> Attachments: derby-4625-1.diff, derby_4625-2.diff
>
>
> The TIMESTAMP function fails if the string argument specifies the number of
> nanoseconds. It works if the argument is limited to microsecond resolution.
> ij> values timestamp('2010-04-21 12:00:00.123456');
> 1
> --------------------------
> 2010-04-21 12:00:00.123456
> 1 row selected
> ij> values timestamp('2010-04-21 12:00:00.123456789');
> ERROR 22008: '2010-04-21 12:00:00.123456789' is an invalid argument to the
> timestamp function.
> Since Derby (and JDBC) supports nanosecond resolution, the TIMESTAMP function
> should also support it.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
