16

I'm getting the following exception updating a row using MySQL via JDBC:

com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect datetime value: '2006-10-01 02:22:44'

The column is defined as:

'created_on_service timestamp NULL DEFAULT NULL'

There are no indexes or foreign keys on that column.

Obviously it's not a problem with data type. I have values in that table from both before and after that datetime. I also have values with times both before and after 2:22 AM.

Cam Price-Austin
  • 1,738
  • 2
  • 18
  • 31
  • This might help http://stackoverflow.com/questions/73109/mysql-data-truncation-error – Rasika Sep 27 '11 at 04:59
  • 1
    That link is about text data, specifically multi-byte character sets. It's not applicable. I did search StackOverflow for similar questions before I posted, but no luck I'm afraid. – Cam Price-Austin Sep 27 '11 at 05:42

5 Answers5

23

Solved it.

Turns out that the 1st of October 2006 in South Australia was the start of daylight savings. Clocks get set forward one hour at 2.00am, so there was no 2:22am on that date: it went straight from 2:00am to 3:01am.

I'll change the db timezone to UTC, which should solve this issue.

Cam Price-Austin
  • 1,738
  • 2
  • 18
  • 31
  • Wanted to know as what else options do we have, if it's not feasible to change db-timezone. Nevertheless, you really saved lot of brain tiredness by pointing out the issue. – linuxeasy Jun 09 '16 at 21:41
5

I fixed the same problem (com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect datetime value: '' for column 'perev_start_time' at row 1) by upgrading my MySQL connector JAR, and copying the mysql.jar to the Tomcat lib directory.

The version of MySQL Server is 5.6 and the MySQL connector is mysql-connector-java-5.1.30-bin.jar.

JasonMArcher
  • 14,195
  • 22
  • 56
  • 52
Ppacheco
  • 51
  • 1
  • 1
  • Welcome to stack overflow. In general, follow-up questions should not be posted as answers, but instead [asked separately](http://stackoverflow.com/questions/ask). Feel free to link back to this question, however. – Pokechu22 Sep 18 '14 at 00:54
  • 4
    This does not look like a new question – AbcAeffchen Sep 18 '14 at 01:15
3

We upgraded MySQL server but didnt upgrade the mysql connector jar. We encountered this issue. Later I figured out it was due to the old jar. I upgraded it and this issue went away.

rohit369
  • 401
  • 1
  • 4
  • 4
3

My problem was caused by DST, too. I've fixed it by changing column data type from timestamp to datetime. This answer describes the difference, in short:

  • timestamp stores time as Unix epoch time, so converts it to/from UTC according to server's time zone. Once you change server time zone, you have different interpretation for INSERT/UPDATE and different SELECT results. Some time points are invalid due to DST;
  • datetime stores time as is, regardless of server time zone. When passing UTC time, any time is valid (there are no DST "holes").

Note: you may still have to deal with "missing" time. This approach just shifts responsibility from DB level to application level.

See also: MySQL documentation for TIMESTAMP vs DATETIME

Nikita Bosik
  • 851
  • 1
  • 14
  • 20
0

You did not show exact update SQL. But may be you forget the date part

The correct format is yyyy-mm-dd hh:mm:ss format

Date value should be in following format 2011-11-01 12:32:01

Gregory Nozik
  • 3,296
  • 3
  • 32
  • 47