Uploaded image for project: 'MariaDB Connector/J'
  1. MariaDB Connector/J
  2. CONJ-86

getTimestamp use client timezone and fails on Daylight Savings Time

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • 1.1.6
    • 1.3.0
    • Other
    • None
    • Sprint connector/j 1.3.0

    Description

      It seems that the getTimestamp of the ResultSet class use the default client timestamp for time conversions. This works in most cases, but when Daylight Saving Time is used, it fails at certain times. For example if the TimeZone is Europe/Stockholm and the time is '2014-03-30 02:15:00' this is an invalid time (as the hour between 2 and 3 is "lost"). Using an explicit TimeZone works, and what seems like a workaround would be to use the UTC timezone instead of the default one when an explicit timezone is not set.

      Attachments

        Issue Links

          Activity

            People

              diego dupin Diego Dupin
              karlsson Anders Karlsson
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.