Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
1.1.6
-
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
- relates to
-
CONJ-143 ResultSet.getTime() shouldn't convert TIME fields to the server time-zone
- Closed