[
https://issues.apache.org/jira/browse/CALCITE-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14482160#comment-14482160
]
Nick Dimiduk commented on CALCITE-660:
--------------------------------------
Thanks a log [~julianhyde]!
I'm seeing similar issues with setBytes() and the ByteString object. It looks
like it's being deserialized as a LinkedHashMap who's key is "bytes" and value
is a string. I'm not sure what the relationship is between the value and it's
original.
Trying adding a similar test but hsqldb isn't cooperating.
> 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: 1.2.0-incubating
>
> 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)
