Comments on: Getting around MySQL TIMEDIFF() for hours greater than 838

By: Arjun Dhar

Arjun Dhar — Fri, 11 Nov 2011 06:50:11 +0000

Funny thing is when I execute the Query on the console it automatically truncates it to the bounded value and does not complain.

But when I run it via Code, then MySQL vomits a SQL Error: 1292, SQLState: 22001
Data truncation: Truncated incorrect time value: ‘842:00:00′

…I’m still interested to know why the difference; but I think using TIMESTAMPDIFF with say HOUR, is a safer option, as shown in your article.

thanks

Matt — Mon, 25 Jul 2011 10:52:39 +0000

Thanks very much for this information – excellent article.

I agree wholeheartedly that the MySQL documentation is really lacking regarding argument and return types especially around DATE/TIME functionality.

gowri — Fri, 15 Apr 2011 13:50:57 +0000

Really wonderful explanation ! Thank you so much

if only — Fri, 16 Jul 2010 20:06:22 +0000

if only more developers could communicate and create a tutorial as well as you

David — Wed, 24 Feb 2010 22:14:28 +0000

Excellent article. Clear, concise, and well written. Very useful. Thanks.

mihai1302 — Mon, 15 Feb 2010 20:00:15 +0000

OK, that’s a great article…