2014-07-11 13:30 GMT-03:00 Paul DeBruicker :
> Additionally I think its helpful to remember that timezones are political
> constructs and so are completely arbitrary and open to change based on the
> whims of political leaders e.g.
>
> https://en.wikipedia.org/wiki/Time_in_Russia#Daylight_saving_ti
Additionally I think its helpful to remember that timezones are political
constructs and so are completely arbitrary and open to change based on the
whims of political leaders e.g.
https://en.wikipedia.org/wiki/Time_in_Russia#Daylight_saving_time
So best keep them out of your code, near the pres
Exactly !
On 11 Jul 2014, at 11:26, Stephan Eggermont wrote:
> Esteban wrote:
>> Anyhow this is too much to add to my app without giving it proper thinking.
>> So let's KISS.
>
> If you only work with a single server/all servers in the same timezone that
> translates to:
> - Do everything in
Esteban wrote:
>Anyhow this is too much to add to my app without giving it proper thinking. So
>let's KISS.
If you only work with a single server/all servers in the same timezone that
translates to:
- Do everything in local time or UTC, have one place where you know your zone,
- Store all time/
So I searched around and ended at http://www.w3.org/TR/timezone
Now I can picture the kind of issues you might have to deal with when using
timezones. It gets scary.
Also I learnt that timezone and time offset are not synonyms.
Anyhow this is too much to add to my app without giving it proper th
2014-07-10 19:42 GMT-03:00 Sven Van Caekenberghe :
>> ps: And I guess I now understand the purpose of ZTimestamp :)
>
> ;-)
>
> Not only that, there is also ZTimezone with support for the Olsen timezone
> database.
>
> Note that going from local time to UTC and vice versa depends not just on the
On 10 Jul 2014, at 23:26, Esteban A. Maringolo wrote:
> What is the best way to work across timezones?
>
> Today my app assumes a global, shared, timezone for data input, storage, etc.
> I want to make this configurable, and for that purpose I
>
> For what I read and thought about, I understan
Am 10.07.2014 um 23:26 schrieb Esteban A. Maringolo :
> What is the best way to work across timezones?
>
> Today my app assumes a global, shared, timezone for data input, storage, etc.
> I want to make this configurable, and for that purpose I
>
> For what I read and thought about, I understand
