[jira] Commented: (DERBY-4625) TIMESTAMP function doesn't accept nanoseconds

["A.S.Thiwanka Somasiri (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DERBY-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860562#action_12860562 ] 

A.S.Thiwanka Somasiri commented on DERBY-4625:
----------------------------------------------

Hi Knut,
                 What are the classes that are used to call the timestamp functions?I referred mechanisms in UnaryDateTimestampOperatorNode.java class to some extent.

Thanks.

> 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
>            Priority: Minor
>
> The TIMESTAMP function fails if the string argument specifies the number of nanoseconds. It works if the argument is limited to nanosecond 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.