Re: mySQL time = year 2038 [HELP]
| From: | Kevin Stone | Date: | Mon, 01 Jul 2002 17:16:52 +0000 |
| Subject: | Re: mySQL time = year 2038 [HELP] | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-104727@lists.php.net to get a copy of this message | ||
Perhaps the problem is in your translation. NOW() records a timestamp that
is formated by YYYYMMDDHHMMSS. If you are translating this in PHP a
function designed to take in a UNIX timestamp (that is "Unix Epoch" time ,
the number of seconds from some date 30 years ago) you will recieve a rather
confusing result. This may not be the problem but it was just a thought.
-Kevin
----- Original Message -----
From: "Shane" <shane@delaplaine.com>
To: <php-general@lists.php.net>
Sent: Monday, July 01, 2002 10:38 AM
Subject: [PHP] mySQL time = year 2038 [HELP]
> Checked the archive and saw no difinitives... so... How come when I query
my clients mySQL DB and use NULL or NOW() as my default in a TIMESTAMP
record that it always comes up Jan 18, 2038?
>
> Is the clock not set properly, or am I misunderstanding some basic
principal of the time stamp?
>
> My clients version pf PHP is 4+ on a Windows IIS server.
>
> Any clues???
> Thanks
> -NorthBayShane
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>