Skip to content
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

Closed
syjer opened this issue Oct 11, 2014 · 4 comments
Closed

Handle correctly the timezone of a event #8

syjer opened this issue Oct 11, 2014 · 4 comments
Assignees
Milestone

Comments

@syjer
Copy link
Member

syjer commented Oct 11, 2014

As the deployed server can be everywhere, selecting the correct timezone of a event is fondamental, as all the dates will depend on it.

@syjer syjer added this to the 0.1 milestone Oct 11, 2014
@cbellone
Copy link
Member

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.
WDYT?

@cbellone cbellone self-assigned this Oct 11, 2014
@cbellone
Copy link
Member

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

@cbellone
Copy link
Member

The time zone will be retrieved using google's timezone api
https://developers.google.com/maps/documentation/timezone/

cbellone added a commit that referenced this issue Oct 15, 2014
cbellone added a commit that referenced this issue Oct 15, 2014
cbellone added a commit that referenced this issue Oct 15, 2014
cbellone added a commit that referenced this issue Oct 15, 2014
@cbellone
Copy link
Member

cbellone commented Nov 1, 2014

fixed

@cbellone cbellone closed this as completed Nov 1, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants