[
https://issues.apache.org/jira/browse/CALCITE-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131724#comment-16131724
]
Josh Elser commented on CALCITE-1951:
-------------------------------------
bq. According to the guide on data types
(http://hsqldb.org/doc/2.0/guide/sqlgeneral-chapt.html#sgc_data_type_guide),
defining a field as TIME(6) should have 6 fractional seconds for the field. By
default it is 0, but I've set it to 6 in my table definition.
Ok, that seems to point towards it being an Avatica bug. A unit test would
likely be the next step to try to get to the bottom of it!
> 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
> Assignee: Josh Elser
>
> 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
(v6.4.14#64029)
