The MySQL error, Data truncation: Incorrect datetime value, is rather obvious and is caused by trying to insert a non datetime value into a datetime field in MYSQL 5.1. I was surprised to find the same code would run without error on MySQL 4.1. Apparently, earlier versions of MySQL would convert incorrect datetime values into 0000-00-00 00:00:00 and proceed without error. It seems that throwing the error is a better option to alert the developer of a problem if they are attempting to insert a non datetime value into a datetime value field.
Entries for month: February 2010
MySQL Data truncation: Incorrect datetime value
Posted by John
Creating 301 Redirects on IIS7
Posted by John
I've been moving a site from Windows Server 2003 to Windows Server 2008 and thought I would mention one of the items I ran into this evening.I needed to setup 301 redirects for some old domain names that we no longer use and at first glance could not figure out where to do so.
Incorrect integer value: '' for column 'x'
Posted by John
I ran into a issue today due to a difference between MySql 4.1 and 5.1, or at least that is what I'm currently thinking. We have a ColdFusion template that is running as a scheduled task to determine new and updated records in a table on one server and then either updates or creates new records on a second server at a different location. Pretty straight forward, and it has worked well for the last several years.