-
Notifications
You must be signed in to change notification settings - Fork 94
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
mysql_tzinfo_to_sql — Load the Time Zone Tables #35
Comments
Completed my fake datalogger, which I can use to have one running on a Pi with MySQL, disabling the need for a P1 port. |
Takes a minute or so.
|
Well it seems that as long as the system's time is set to UTC, things go well. However, it's not a guarantee that everyone sets UTC as their system timezone. |
Follow-up check is checking (day) boundaries. I'll have my fake datalogger run for the next day, so I can check ranges tomorrow. |
Seems to work fine:
So Django selects 23:00 tot 23:00, which is expected (data is stored UTC). When I make the selection naive:
Midnight UTC, which is wrong. Also, Django complains:
The only thing is, I just added timezone tables before testing. I'll revert the database and test again, without them. |
It seems Django performs the conversion, so it should be OK, as long as UTC is set as SYSTEM time. |
Originally reported by: Dennis Siemensma (Bitbucket: dennissiemensma, GitHub: dennissiemensma)
Django mentions somewhere
mysql_tzinfo_to_sql — Load the Time Zone Tables
. We should check whether MySQL data is stored timezone aware.If not, we should mention the required steps in the installation guide of this project.
The text was updated successfully, but these errors were encountered: