MySQL Lists are EOL. Please join:

List:General Discussion« Previous MessageNext Message »
From:SGreen Date:July 26 2004 1:21pm
Subject:Re: Weird problem for TIMESTAMP feild
View as plain text  
According to the docs (http://dev.mysql.com/doc/mysql/en/DATETIME.html)

The number "1258975462" equates to the date "1258-97-54 62:00:00" which is 
not a valid date. That's why you get the "zero date" value.

That number could also equate to a unix_timestamp() value for the date 
"2009-11-23 06:24:22"

select from_unixtime(1258975462)
+---------------------------+
| from_unixtime(1258975462) |
+---------------------------+
| 2009-11-23 06:24:22       |
+---------------------------+
1 row in set (0.05 sec)

(http://dev.mysql.com/doc/mysql/en/Date_and_time_functions.html)

What date did it represent in your data?

Yours,
Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine


Tariq Murtaza <tariq@stripped> wrote on 07/26/2004 05:43:04 AM:

> Hi All,
> 
> I am getting very weired problem after shifting our server. here is the 
> details:-
> 
> I have a table with two columns
>     1-TimeStamp timestamp(14)
>     2- SID bigint(20)
> 
> when inserting  _INSERT INTO _/_TABLENAME values (1258975462,125987)_ 
> results in /_INSERT INTO _/_TABLENAME values (0000000000,125987)_
> Timestamp entry gets zeros.
> 
> Any idea? whats happening....
> 
> Regards,
> *TM*
> /

Thread
Weird problem for TIMESTAMP feildTariq Murtaza26 Jul
  • Re: Weird problem for TIMESTAMP feildSGreen26 Jul
RE: Weird problem for TIMESTAMP feildVictor Pendleton26 Jul