Hi Michael, There is no easy or universal answer to this question. The best solution also depends on the meaning of the timestamp data.
If your system is used on multiple timezones, ... - you may have situation where you want to always display the time in the event location time zone like airplane takeoff and landing; - you may want to always display the event time in the user local timezone like an event log; - you may want to always display in a fixed time zone like a server log... So you may or may not need to store the time zone of an event to display it properly. To add some ugliness to this already complex problem, we have a very nasty thing called daylight saving time where we change the time zone of locations based on the date. This can easily create situation where an event change time when crossing the DST change dates... First step is to analyse the problem and figure out how timestamps should be displayed. Regards, Samuel > Le 25 févr. 2020 à 12:59, Michael Kondratov via Webobjects-dev > <webobjects-dev@lists.apple.com> a écrit : > > Hello! > Whats the winning strategy on dealing with users / records in multiple > timezones? We are starting add add companies that are few hours away from us > and don't know how to best handle it. > > > > Sincerely, > > > Michael > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/samuel%40samkar.com > > This email sent to sam...@samkar.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
