[TYPO3-dev] RFC: Change roadmap for 4.5 and 5.0

Dimitri Tarassenko mitka at mitka.us
Tue Apr 11 16:22:24 CEST 2006


Elmar,

On 4/11/06, Elmar Hinz <elmar.DOT.hinz at team.minus.red.dot.net> wrote:

> The same moment in history can be a sunday or already a monday, depending
> on your location.
>
> Do you want to transfor your datetime to greewnich winter time first,
> before you can store it? It's easier to make a unix timestamp.
>
> Or do you want to store your localized time together with your timezone?
> That is hard to read for somebody from another timezone.

That is PRECISELY why you should always use native date types in SQL
servers. SQL servers are a lot better at managing this information
than any PHP code. And Unix timestamps don't save you from timezone
issues, either. Having dates and times stored as dates and times and
using "set time_zone = .." on a _per_session_ level does, and a lot
more efficiently than always adjusting the int timestamp for your
timezone-shift global variable.

--
Dimitri Tarassenko


More information about the TYPO3-dev mailing list