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

Standardize Database Handling of Timezone #109

Closed
dstufft opened this issue Oct 29, 2013 · 4 comments · Fixed by #125
Closed

Standardize Database Handling of Timezone #109

dstufft opened this issue Oct 29, 2013 · 4 comments · Fixed by #125

Comments

@dstufft
Copy link
Member

dstufft commented Oct 29, 2013

The fields that came from Django have timezone=True, the old fields have timezone=False, we should pick one and use it.

@r1chardj0n3s
Copy link

Yes, have timezone and force it to UTC. It's the only sane thing to do :)

@dstufft
Copy link
Member Author

dstufft commented Oct 29, 2013

So you think we should store the timezone in the database and not just store it timezoneless and say "Database is in UTC" ?

@r1chardj0n3s
Copy link

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.

@dstufft
Copy link
Member Author

dstufft commented Oct 29, 2013

Sounds good to me!

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

Successfully merging a pull request may close this issue.

2 participants