[CALCITE-518] Review JDBC driver for time zone and encoding issues

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: avatica
• Assignee: Unassigned
• Reporter: Julian Hyde
• Created: 10/Dec/14 22:31
• Updated: 22/Feb/19 01:19

Description

Vladimir wrote:

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.

Issue Links

• is related to: CALCITE-93 Calcite RPC server
• is related to: CALCITE-94 Remote JDBC driver