1,685
edits
Changes
Jump to navigation
Jump to search
Line 12:
Line 12: + +
→2. Saving all data in local time of recording
: I agree that storing data ''just'' in local time, without any TZ information is a really bad approach to take and should be avoided at all cost. The approach of storing in local time alongside the TZ information is still relevant, though I think the risk of somehow losing the TZ information when using the approach of storing data in local time + TZ information is a real issue that can occur. But for many analyses the actual local time is what people are actually interested in. Sleep timing (including naps), diet timing strategies, physical activity etc. are mostly based on local time. But again, all of these local times should also include the TZ. - [[User:Gedankenstuecke|Gedankenstuecke]] ([[User talk:Gedankenstuecke|talk]]) 10:31, 30 November 2021 (UTC)
: I agree that storing data ''just'' in local time, without any TZ information is a really bad approach to take and should be avoided at all cost. The approach of storing in local time alongside the TZ information is still relevant, though I think the risk of somehow losing the TZ information when using the approach of storing data in local time + TZ information is a real issue that can occur. But for many analyses the actual local time is what people are actually interested in. Sleep timing (including naps), diet timing strategies, physical activity etc. are mostly based on local time. But again, all of these local times should also include the TZ. - [[User:Gedankenstuecke|Gedankenstuecke]] ([[User talk:Gedankenstuecke|talk]]) 10:31, 30 November 2021 (UTC)
"risk of somehow losing the TZ information" more like misaligning and then there is the daylight savings time. INternally the data should be stored in the safe from bugs way but user can request is sent out in the easier for them to read way. Encapsulation etc. APIs should give out UTC though for sure.
== local time requires the time zone to be correctly written too while UTC does not ==
== local time requires the time zone to be correctly written too while UTC does not ==
so local time definitely introduces extra opportunity for errors. imagine if user flies over time zones or daylight savings time and device fails too change its time at the correct moment....! and then the daylight savings time will make overlaps too. [[User:DG|DG]] ([[User talk:DG|talk]])
so local time definitely introduces extra opportunity for errors. imagine if user flies over time zones or daylight savings time and device fails too change its time at the correct moment....! and then the daylight savings time will make overlaps too. [[User:DG|DG]] ([[User talk:DG|talk]])