You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/06/14 14:12:00 UTC

[jira] [Commented] (CALCITE-2299) TIMESTAMPADD(SQL_TSI_FRAC_SECOND) should be nanoseconds not microseconds

    [ https://issues.apache.org/jira/browse/CALCITE-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16512511#comment-16512511 ] 

ASF GitHub Bot commented on CALCITE-2299:
-----------------------------------------

GitHub user snuyanzin opened a pull request:

    https://github.com/apache/calcite-avatica/pull/58

    [CALCITE-2299] TIMESTAMPADD(SQL_TSI_FRAC_SECOND) should be nanoseconds

    Avatica part for [CALCITE-2299]
    Added support of nanoseconds in TimeUnit and TimeUnitRange

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/snuyanzin/calcite-avatica CALCITE_AVATICA_2299

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/calcite-avatica/pull/58.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #58
    
----
commit d2fe74ba0a12529f6b17614f54c7e69c7826b131
Author: snuyanzin <sn...@...>
Date:   2018-06-14T13:48:47Z

    [CALCITE-2299] TIMESTAMPADD(SQL_TSI_FRAC_SECOND) should be nanoseconds not microseconds
    Added support of nanoseconds in TimeUnit and TimeUnitRange

----


> TIMESTAMPADD(SQL_TSI_FRAC_SECOND) should be nanoseconds not microseconds
> ------------------------------------------------------------------------
>
>                 Key: CALCITE-2299
>                 URL: https://issues.apache.org/jira/browse/CALCITE-2299
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.16.0
>            Reporter: James Duong
>            Assignee: Julian Hyde
>            Priority: Minor
>
> When calling TIMESTAMPADD with the first parameter SQL_TSI_FRAC_SECOND and the JDBC escape sequence, this gets interpreted as microseconds when it should be interpreted as nanoseconds.
>  
> From the ODBC spec on MSDN:
> [https://docs.microsoft.com/en-us/sql/odbc/reference/appendixes/time-date-and-interval-functions?view=sql-server-2017]
> 'where fractional seconds are expressed in billionths of a second.'



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)