MySQL Out of Range Solution for DATETIME field

Affected rows: 0
Warning: #1264 Out of range value adjusted for column 'deleteon' at row 1
SQL query:
UPDATE `custtable`.`custinfo` SET `deleteon` = '2011-02-29 00:00:00' WHERE `custinfo`.`custid` =105 LIMIT 1 ;

This happened after a migration to a new SQL database due to user error.  The old database server MySQL 3.23 or 4 allowed an impossible date to be entered by a user.  As we know February 29th DOES NOT exist but the database allowed the value.  MySQL 5.0 is smarter and rejected it and ended up setting a blank value for that field.  It was hard to troubleshoot at first until we actually looked at the date :)

So the solution is to use Feb-28th or March 1st since the 29th does not exist.

Latest Articles

  • OpenVZ avoid vzctl 4.7 and ploop
  • Wordpress Security Hole, Plug it by manually installing themes and plugins
  • LVM Tutorial how to create a Physical Volume (PV), Volume Group (vg), and a Logical Volume (LV) within it
  • Howto Convert Xen Image to KVM
  • yum error "Error: database disk image is malformed" solution
  • drbd howto solve splitbrain or WFConnection
  • How to view GPT/EFI Windows Partition Table
  • Howto Restore Acer Aspire E1-531-4406
  • How to Enable RDP Remote Desktop in Windows 2008 Server
  • virtio KVM drivers download location
  • "Detecting hardware, please wait..." Ubuntu Install Error Solution
  • lvm how to resize and extend a volume
  • Asterisk VOIP Sipura/Linksys PAP2T Calls Not Being Received Solution
  • OpenVZ mismatched kernel and dev when compiling.
  • Microsoft Updates suddenly stops at 50% downloading solution
  • Enable Multiple RDP Sessions on Windows XP, Vista, 7 Howto
  • mencoder howto trim split edit time of mp4 from Samsung Note
  • How to read a conf file without the comments
  • yum Centos 386 and 64 bit conflict resolution
  • OpenVZ Quick Install Copy & Paste for Centos 6