-
-
Notifications
You must be signed in to change notification settings - Fork 348
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle correctly the timezone of a event #8
Comments
I would suggest to always save the event dates as UTC, in order to support also relocation of servers. IMHO in a cloud-based environment (such as openshift) this would be a frequent scenario. |
agreed solution: data always saved in UTC, try to get timezone information based on event location and automatically convert dates when extracted/inserted from/to DB |
The time zone will be retrieved using google's timezone api |
fixed |
As the deployed server can be everywhere, selecting the correct timezone of a event is fondamental, as all the dates will depend on it.
The text was updated successfully, but these errors were encountered: