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

time in db #1

Open
miekg opened this issue Aug 11, 2017 · 2 comments
Open

time in db #1

miekg opened this issue Aug 11, 2017 · 2 comments

Comments

@miekg
Copy link

miekg commented Aug 11, 2017

created_at timestamp without time zone

this should be in UTC

@thoro
Copy link
Contributor

thoro commented Aug 11, 2017

I have it in my dbs always non specified and by convention UTC

Do you think setting the time zone specified solves any specific issue? Can you give me an example?

@miekg
Copy link
Author

miekg commented Aug 11, 2017

If time is not in UTC, it will probably follow DST, this leads to all kind of problems when those periods are entered and left. I.e. this record was inserted at 02:30, but DST was active so actually it was 01:30.

Use UTC (and enforce!) where ever you can.

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