Opened 18 years ago
Closed 18 years ago
#723 closed defect (invalid)
MythTV should use UTC, not localtime for Dates Stored in the database
| Reported by: | Owned by: | Isaac Richards | |
|---|---|---|---|
| Priority: | minor | Milestone: | unknown |
| Component: | mythtv | Version: | 0.18.1 |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description
I posted this on mythtv-user:
However, I didn't get any responce from anyone who seams like a developer.
Localtime has serious problems when dealing with the the switch between Daylight savings time and Standard time and back. In particular it is, _impossible_ to store program information for the extra hour AND also keep the listing accurate across the switch back to standard time. The only way to solve this problem is to use UTC time in the database.
A lot more information is in the post.
Change History (4)
comment:1 Changed 18 years ago by
comment:2 Changed 18 years ago by
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:3 Changed 18 years ago by
| Resolution: | invalid |
|---|---|
| Status: | closed → reopened |
Could you exlain to me why this is invalid? This is a very real problem which makes it impossible to store program information for the extra hour.
comment:4 Changed 18 years ago by
| Resolution: | → invalid |
|---|---|
| Status: | reopened → closed |
Already posted to the dev list. The bug database is not a chat room.
The local time seems more meaningful, and the SQL functions and types like NOW() use local time, so it is more convenient; it seems like a working method of using localtime without making it impossible to handle schedules near the changeover properly, would be to have a timezone column per row to indicate which timezone the start and end time are in.