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

[Ries van Twisk]

Elmar Hinz wrote:

>Ries van Twisk schrieb:
>  
>
>>That's not what he ment....
>>He means that out of a unix timestamp it's hard to pick all thuesdays..
>>You need to do that in PHP
>>while in vact that can be done from SQL. Therfe is still a open bug
>>about a somular issue in bugtarcker due
>>to that we cannot sore timezones properly. So using a real date field is
>>the right way to go for future, not int(11)
>>(What is int(11) anyways in mysql.... horrible... )
>>
>>    
>>
>
>The same moment in history can be a sunday or already a monday, depending
>on your location.
>  
>
No, that's why they invented Timestamp + time zones:
see : http://www.postgresql.org/docs/8.0/static/datatype-datetime.html

>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.
>  
>
No, I just need to know the timezone . In europe we also have winter and 
summer time. Here in Ecuador not.
Also something to keep track of. (but known from lookup tables).

>Or do you want to store your localized time together with your timezone?
>That is hard to read for somebody from another timezone.
>  
>
Representation is different from storage ofcourse.
Just like it's hard to read a unix timestamp, you need to convert it to 
make it humen readble.
(although I personally find it easer to read a timestamp + tz then a 
unix time).

It also depends on the contex.
For example:
A news event in germany happend at 15:00. When I read it here in Ecuador 
it still happened at 15:00 in Germany.

However, When I need to know at what time it happend here in Ecuador.
Then I need to know the time zone where I am in and the timezone the 
event happend.

Berhard Karft (or is it kraft Bernhard) had a problem with this while 
entering birthdays, I can confirm that.
When the server is not in the same timezone as the clients computer We 
need to know what the actually date was.
otherwise a birthday can happen the day before it was enetred.

other example:
Tree people across the world want to schedule for a meeting.
They all agree that at some date it is the best time to schedule.
So when one enters a date_time in the calender system. Then the right 
time needs to show up
on the front end of each computer. The only way to do that correctly is 
by know the timezone of
the server and the tree clients.

So time and timezone are hand in hand together.
Otherwise it's impossible to works with times.
Celco made a nice chapter about it in his book Data & Databases, 
concepts in Practise
Chapter 9, temporal data:
He starts with : Temporal data is the hardest type of data for people to 
handle conceptually.
And
SQL for Smarties, advanced SQL Programming
Chapter 4, Temporal Datatypes in SQL

good reading material on warm summer evenings with a beer in your right 
hand.

Ries


>Elmar
>
>
>
>
>
>
>
>
>
>
>
>
>_______________________________________________
>TYPO3-dev mailing list
>TYPO3-dev at lists.netfielders.de
>http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev
>  
>


-- 
Ries van Twisk
Freelance Typo3 Developer
=== Private:
email: ries at vantwisk.nl
web:   http://www.rvantwisk.nl/
skype: callto://r.vantwisk
=== Work:
email: ries at livetravelguides.com
web:   http://www.livetravelguides.com