[
https://issues.apache.org/jira/browse/CALCITE-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16445098#comment-16445098
]
ASF GitHub Bot commented on CALCITE-1951:
-----------------------------------------
GitHub user risdenk opened a pull request:
https://github.com/apache/calcite-avatica/pull/36
[CALCITE-1951] Test for date
WIP to show the error from CALCITE-1951. I don't have a fix yet but maybe
it will help others.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/risdenk/calcite-avatica CALCITE-1951-test
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/calcite-avatica/pull/36.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 #36
----
commit 84ce927a96084db207907b7b12466fe264e14ff4
Author: Kevin Risden <krisden@...>
Date: 2018-04-20T01:39:06Z
[CALCITE-1951] Test for date
----
> Avatica HSQLDB docker image time loses fractional seconds
> ---------------------------------------------------------
>
> Key: CALCITE-1951
> URL: https://issues.apache.org/jira/browse/CALCITE-1951
> Project: Calcite
> Issue Type: Bug
> Components: avatica
> Reporter: Francis Chuang
> Priority: Major
>
> I create a table like so in HSQLDB using the avatica-hsqldb image:
> {code}
> CREATE TABLE some_table (
> tm TIME(6) PRIMARY KEY,
> )
> {code}
> I then use calculate the milliseconds since 00:00:00.000 and send this value
> along with my insert statement: 76881222
> However, when I select the row to read the value back, I get 76881000.
> In this case, 222 milliseconds was lost.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
