[ https://issues.apache.org/jira/browse/CALCITE-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16512674#comment-16512674 ]
ASF GitHub Bot commented on CALCITE-2299: ----------------------------------------- Github user risdenk commented on the issue: https://github.com/apache/calcite-avatica/pull/58 Tested this change with upgrading bouncycastle to 1.59 (CALCITE-2361) locally on JDK 11 build 17 and all tests pass now. > 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)