[
https://issues.apache.org/jira/browse/CALCITE-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated CALCITE-518:
---------------------------------
Component/s: avatica
Bulk edit assigning avatica component to obvious issues.
> Review JDBC driver for time zone and encoding issues
> ----------------------------------------------------
>
> Key: CALCITE-518
> URL: https://issues.apache.org/jira/browse/CALCITE-518
> Project: Calcite
> Issue Type: Bug
> Components: avatica
> Reporter: Julian Hyde
> Assignee: Julian Hyde
>
> Vladimir wrote:
> {quote}2) I expect lots of defects in the "timezone and locale/encoding"
> areas.
> For instance,
> 2.1) DateTimeUtils.parseDateFormat is not using TimeZone tz argument properly.
> It should pass it to simpleDateFormat.setTimeZone, otherwise "default
> time zone is used to map string to the point in time"
> 2.2) I think we need to delete things like DateTimeUtil.MILLIS_PER_DAY
> as TimeUnit.MILLISECONDS.toDays(42) is good enough.
> 2.2) RemoteService.apply: byteArrayOutputStream.toString(); This
> should not be the case. If client and server have different default
> encodings, you screw the data.{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
