| Bug #71983 | EST to DST conversion happened 5 hours too early in 2014 | ||
|---|---|---|---|
| Submitted: | 9 Mar 2014 2:36 | Modified: | 10 May 2014 13:39 |
| Reporter: | Dan Dumont | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | Connector / J | Severity: | S1 (Critical) |
| Version: | 5.6.14 | OS: | Windows (win8 64bit) |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
| Tags: | date, DST, time | ||
[9 Mar 2014 2:42]
Dan Dumont
By the date of the post in the bug report tool, I see your servers agree with java as well. :)
[9 Mar 2014 2:44]
Dan Dumont
db server and java program are all on the same machine. Using connector version: mysql-connector-java-5.1.29
[9 Mar 2014 2:51]
Dan Dumont
UPDATE Ant SQL task that runs the sql create of the database for integration tests does an insert (using the same driver). It does not have this problem :-/ Not really sure what to say. I'm not suing any timezone options in any of my jdbc connections.
[9 Mar 2014 2:57]
Dan Dumont
UPDATE2 The statement inserts and updates are placing the correct value into the database (according to mysql workbench) However, doing a resultset.getString(1) for the UTC time in the database is returning the incorrect hour offset.
[17 Mar 2014 20:42]
Sveta Smirnova
Thank you for the report. > Ant SQL task that runs the sql create of the database for integration tests does an insert (using the same driver). It does not have this problem :-/ This looks like problem is in Java code which you use. Please provide complete standalone test case, demonstrating the problem: CREATE TABLE statement and Java code you use to insert data.
[28 Mar 2014 13:28]
Dan Dumont
Please see UPDATE2 ----- The statement inserts and updates are placing the correct value into the database (according to mysql workbench) However, doing a resultset.getString(1) for the UTC time in the database is returning the incorrect hour offset. ----- My tests ran in stages and I was only able to inspect the values after my ant task write. (before my tests ran, but after my database was populated by ant task). The workbench showed the correct values in the database. However, trying to select those values and read them out via resultSet.getString(1) showed a different value than the workbench.
[10 Apr 2014 13:39]
Alexander Soklakov
Hi Dan, We need more info to provide you with correct solution: 1) what is the MySQL server & session tz were used during insert & during select? 2) what is the JVM tz was used during insert & during select? 3) which c/J properties were used during insert & during select?
[11 May 2014 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
Description: I was writing integration unit tests when they all started failing at 9pm EST on March 8th, 2014. How to repeat: My inserts set a DATETIME column to a UTC timestamp. stmt = conn.prepareStatement("UPDATE `table` SET `mod`=UTC_TIMESTAMP() WHERE `id`=?"); I then pull it out later to make sure that the value was set as expected: at the given time, the value was around "2014-03-09 03:16:38" UTC While major time sites on the internet and java both agree that the correct time is "2014-03-09 02:16:38" UTC final Calendar now = Calendar.getInstance(); // EST now.set(Calendar.MILLISECOND, 0); // match dt precision final SimpleDateFormat dformat = new SimpleDateFormat("yyyy-MM-dd hh:mm:ss"); dformat.setCalendar(Calendar.getInstance(TimeZone.getTimeZone("UTC"))); dformat.format(now.getTime()); (using a oracle 7 jdk)