[
https://issues.apache.org/jira/browse/DERBY-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913005#action_12913005
]
Knut Anders Hatlen commented on DERBY-4625:
-------------------------------------------
Thanks, Nirmal!
The patch looks good to me. The new test case in DateTimeTest was commented
out. I've commented it back in and started the regression tests suites. I'll
commit the fix if the tests pass.
> 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
> 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.
-
You can reply to this email to add a comment to the issue online.
