[jira] [Commented] (CALCITE-797) Avatica remote service strips the date part from java.sql.Time

["Julian Hyde (JIRA)" <ji...@apache.org>]

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

Julian Hyde commented on CALCITE-797:
-------------------------------------

I think Avatica is doing the right thing in stripping the date part and leaving the milliseconds since midnight. java.sql.Time is merely a binding of SQL types into the Java language, but when you go across a network protocol and into a database we don't guarantee Java semantics end-to-end.

> Avatica remote service strips the date part from java.sql.Time
> --------------------------------------------------------------
>
>                 Key: CALCITE-797
>                 URL: https://issues.apache.org/jira/browse/CALCITE-797
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Lukas Lalinsky
>            Assignee: Julian Hyde
>
> java.sql.Time is basically an UNIX timestamp with both date and time. The documentation says the date part should not be used, but Phoenix does use it. While it is possible to pass the full timestamp as a parameter value, the client will only get time part back.
> Given that using the date part is deprecated according to the documentation, I'm not sure if you want to support this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)