Re: Best practices - DateTime vs Database question

On 1/17/06, Dave Rolsky <autarch@urth.org> wrote:

> > a) Native MySQL DATETIME field?
>
> I'd go with this one, since it will make it easiest to do many operations
> in the DBMS (sorting, restriction queries by date, etc).
>

With the caveat that MySQL's understanding of timezones can be a bit
unpredictable, especially between versions.  (we've had a slew of
problems initially)

If you are going to use native datetime fields (or even if you aren't)
I'd strongly suggesting storing all your dates as UTC, and set your
MySQL's timezone to UTC, and don't do anything in the database that
requires timezone math.  Use DateTime.pm for that.

-kellan

• Best practices - DateTime vs Database question by John Peacock
• Re: Best practices - DateTime vs Database question by Dave Rolsky
• Re: Best practices - DateTime vs Database question by kellan
• Re: Best practices - DateTime vs Database question by John Peacock