Okay, that's what I needed to hear...
so I'll just add 61200seconds onto the timestamp, and i'll be "in the
ball park".
thanks to everyone,
justin
Scott Brown wrote:
>
> Seems to me that those functions expect GMT based time.
>
> Here in Ontario Canada, I'm GMT-5 (or -4 at some points in the
well, just add 17 hours (17h * 60m/h * 60s/m = 61200 [aren't calculators
wonderful :)] ) i guess
-Original Message-
From: Justin French [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 21, 2002 4:02 PM
To: php
Subject: Re: [PHP] timestamp confusion
Jeff Sheltren wrote:
> We
Jeff Sheltren wrote:
> Well, what you are missing is that those are the number of seconds *on that
> machine* since 1970... so actually, if both of your clocks were set
> correctly, you should be getting the *same* number returned by
> time(). Hope that clears it up a little.
A geez *slaps
Well, what you are missing is that those are the number of seconds *on that
machine* since 1970... so actually, if both of your clocks were set
correctly, you should be getting the *same* number returned by
time(). Hope that clears it up a little.
Jeff
At 03:18 PM 2/21/2002 +1100, Justin Fr
It doesn't seem to me like this is an issue... isn't the timestamp just
the local unix time? It is on my LAN server.
The issue I have is that
echo date('d M Y H:m:s','1014261839');
produces 21 Feb 2002 14:02:59 on my LOCAL machine
echo date('d M Y H:m:s','1014260440');
produces 20 Feb 2002 21:
Justin,
Take a look at the gettimeofday() function, which returns the timezone
and daylight-savings-time values for the system.
-bsh
Justin French wrote:
>hi,
>
>when people add something to a table, i'm logging the time()... later,
>when I pull it out, i'm doing something like date('d M Y',$
6 matches
Mail list logo
