[
https://issues.apache.org/jira/browse/CALCITE-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392022#comment-14392022
]
Julian Hyde commented on CALCITE-660:
-------------------------------------
It is definitely wrong that we are sending dates over the wire. We should be
sending int values (for DATE, TIME) or long values (for TIMESTAMP). That is
what Calcite uses. I wonder if JdbcMeta needs to be fixed.
I'll get to it on Friday.
> Improve Avatica date support
> ----------------------------
>
> Key: CALCITE-660
> URL: https://issues.apache.org/jira/browse/CALCITE-660
> Project: Calcite
> Issue Type: Bug
> Reporter: Nick Dimiduk
> Assignee: Julian Hyde
> Labels: avatica
> Fix For: next
>
> Attachments: 660test.patch
>
>
> It seems our handling of Date types is not correct. We serialize to a String
> but then try to read back as a Date object.
> Jackson actually says explicitly to not use java.sql.Date:
> http://wiki.fasterxml.com/JacksonFAQDateHandling
> Perhaps related to CALCITE-64.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
