Uploaded image for project: 'Calcite'
  1. Calcite
  2. CALCITE-518

Review JDBC driver for time zone and encoding issues

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: avatica
    • Labels:
      None

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                julianhyde Julian Hyde
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: