[geeklog-devel] Actual Working Schema for GL2

[Justin Carlson]

That's fine and all, just offering my thoughts. It is true that it
limits you to 1970 - 2037 or so, and that is a drawback if you are
working with dates in that range. ( If you plan on storing people's
birthdays or whatever ).  I've just seen: $example =
date($userPref,$dbdatedata);  and think it's pretty simple.  It's also
sort-easy, of course YYYY-MM-DD HH:II:SS would sort and that point is
moot

Tony's point is very valid.


On Fri, 17 Dec 2004 08:27:34 -0500, Vincent Furia <vfuria at gmail.com> wrote:
> Then why not use TIMESTAMPs or DATETIMEs?  Changing the format of a
> date/time string is a trivial and fast operation.  Plus using
> DATETIMEs allows you to use any date from 1-1-0000 to 12-21-9999 as
> opposed to just ~1970 to ~2037.  Both have the same flexibility as
> using a timestamp stored as an int, in addition they give you more
> flexibility to do calculations on the server using mysql's time
> functions.
> 
> -Vinny
> 
> On Fri, 17 Dec 2004 02:38:15 -0600, Justin Carlson
> <justin.carlson at gmail.com> wrote:
> > > 2. Why are you using INTs for dates?  Why not TIMESTAMPs or DATETIMEs?
> >
> > For mktime() or time() stamps, at least, that's what I like to use.
> > Then users can choose whatever they want via a dropdown, allowing them
> > to easily set zone and date format.
> > _______________________________________________
> > geeklog-devel mailing list
> > geeklog-devel at lists.geeklog.net
> > http://lists.geeklog.net/listinfo/geeklog-devel
> >
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://lists.geeklog.net/listinfo/geeklog-devel
>