Wanted to thank everyone for the insights for some of this date/time issues!
Pretty much what I was looking at, just wanted a little confirmation!
I will also need to research that PHP function -
Thanks - Chris
On 3/6/07, Marcus Bointon <[EMAIL PROTECTED]> wrote:
On 6 Mar 2007, at 17:12, David
ncorporated
195 Farmington Ave.
Farmington, CT 06032
860.674.8796 / FAX: 860.674.8341
> -Original Message-
> From: Dana Diederich [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 06, 2007 2:43 PM
> To: David T. Ashley; Chris McKeever
> Cc: mysql@lists.mysql.com
> Subject: RE:
I think the best way is to always store an unsigned integer epoch time.
Cheers,
-Dana
-Original Message-
From: David T. Ashley [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 06, 2007 11:12 AM
To: Chris McKeever
Cc: mysql@lists.mysql.com
Subject: Re: Best Practice: Timezones and web
On Tue, March 6, 2007 9:40, Marcus Bointon said:
> On 6 Mar 2007, at 17:12, David T. Ashley wrote:
>
>> Best practice is that all times maintained in a database (or
>> anywhere on the
>> server) are UTC, and are only converted to local timezone and/or
>> adjusted to
>> daylight savings time as requ
On 6 Mar 2007, at 17:12, David T. Ashley wrote:
Best practice is that all times maintained in a database (or
anywhere on the
server) are UTC, and are only converted to local timezone and/or
adjusted to
daylight savings time as required to display data for a specific user.
Exactly right.
On 2/28/07, Chris McKeever <[EMAIL PROTECTED]> wrote:
Does anyone have any resources, guides, insight into the best practice
for storing date/time information when developing a custom web app?
I am mainly concerned with how the TZ should be stored? Should it go
in as UTC and the code accounts
Does anyone have any resources, guides, insight into the best practice
for storing date/time information when developing a custom web app?
I am mainly concerned with how the TZ should be stored? Should it go
in as UTC and the code accounts for the user TZ? How does one handle
tracking the users
