Thomas Zehetbauer writes: > I mistakenly set the value of a DATETIME column to the value of > UNIX_TIMESTAMP(). I know that this is not good practice and I would have even > expected it to fail. > > But what has happened was totally unexpected for me, invalid date values like > '2000-10-09 55:17:71' were inserted. As I could not set the column to the same > value manually I think this is an error and should be fixed. > > Regards > Tom > > PS: Absolutely unrelated words needed to circumvent spam filter: > database,sql,query,table > > Press any key to continue or any other key to quit. > -- > T h o m a s Z e h e t b a u e r ( TZ251 ) > PGP encrypted mail preferred - KeyID 96FFCB89 > mail [EMAIL PROTECTED]
UNIX_TIMESTAMP returns an integer value, so MySQL did it's best to insert an integer value into a string-derived column type. -- Regards, __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic <[EMAIL PROTECTED]> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus <___/ www.mysql.com --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php