[
https://issues.apache.org/jira/browse/CALCITE-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624368#comment-14624368
]
Lukas Lalinsky commented on CALCITE-797:
----------------------------------------
One more thing to consider. The values are currently flagged with the
internal-representation type, not the SQL type. For example, clients are
sending sending {noformat}{"type":"JAVA_SQL_TIME":"value":123}{noformat} not
{noformat}{"type":"TIME":"value":123}{noformat}Given this, it make sense to
send the full java.sql.Time representation. If you want to keep standard SQL
behavior, then perhaps it would make sense to rename the types.
> 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)
