-
Notifications
You must be signed in to change notification settings - Fork 945
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
Standardize Database Handling of Timezone #109
Comments
Yes, have timezone and force it to UTC. It's the only sane thing to do :) |
So you think we should store the timezone in the database and not just store it timezoneless and say "Database is in UTC" ? |
Timezones are hard. Let's play it safe and always store the timezone, unless someone with deeper postgres knowledge can say why it's a bad idea. |
Sounds good to me! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The fields that came from Django have timezone=True, the old fields have timezone=False, we should pick one and use it.
The text was updated successfully, but these errors were encountered: