[FLOW3-general] DateTime limited to Unix timestamp?

[Jigal van Hemert]

Martin Kutschker wrote:
> How the data is stored in the BE shouldn't worry you in the client code. If all you get is a
> DateTime object why worry if it's stored as a unix timestamp or as a SQL DATETIME field?

It worries me if the format results in unnecessary constraints. A 32-bit 
signed integer is just too limited to serve as a storage for dates.

Also in TYPO3 v.4 the strange magic '0' value meaning 'no date' van 
affect client code and even editors. How do you explain to an editor 
that 1970-01-01 is not stored, but 1970-01-02 and 1969-12-31 are stored 
when saving a form.

So, maybe I should rephrase my original question/request: store a 
DateTime object in whatever form the authors of FLOW3 see fit, but 
please do not store it as a Unix timestamp in a 4-byte signed integer 
because of the limitations of that format.

-- 
Jigal van Hemert
skype:jigal.van.hemert
msn: jigal at xs4all.nl
http://twitter.com/jigalvh