[wp-hackers] Re: Sqlite
davebytes at comcast.net
Fri Jun 24 18:20:03 GMT 2005
Um, I don't know about you, but I don't display timestamps in DATETIME
format -- they're ALWAYS transformed for display. Storing in unix timestamp
mode would actually remove an extra transform, as it like has to get
transformed from mysql into epoch, then epoch into string, rather than
direct epoch into string.
I'm all for moving to epoch stamps. ;)
----- Original Message -----
From: "Robert Deaton" <false.hopes at gmail.com>
To: <wp-hackers at lists.automattic.com>
Sent: Friday, June 24, 2005 2:01 PM
Subject: Re: [wp-hackers] Re: Sqlite
Storing just a unix timestamp and the offset means more parsing every
time dates need to be seen, instead of just once and throwing it into
On 6/23/05, Kimmo Suominen <kimmo+key+wordpress.c4f53f at suominen.com> wrote:
> On Thu, Jun 23, 2005 at 11:14:56AM +0200, Martin Geisler wrote:
> > Kimmo Suominen <kimmo+key+wordpress.c4f53f at suominen.com> writes:
> > > AFAICT the big reason for both "local" and GMT (equivalent of
> > > seconds since unix epoch) times in the database is permalink
> > > support. The local time is needed to keep the permalinks from
> > > changing.
> > That doesn't mean that one couldn't use a Unix epoch timestamp: store
> I wasn't saying that seconds from epoch timestamps cannot be used.
> The message I replied to seemed to suggest a single timestamp, which
> is the issue I was addressing.
> Storing a unix timestamp and the offset from gmt on each post would
> achieve the same result as the current two timestamps.
> + Kimmo
> <A HREF="http://kimmo.suominen.com/">Kimmo Suominen</A>
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
wp-hackers mailing list
wp-hackers at lists.automattic.com
More information about the wp-hackers