3 ms·
> Instead, all the rules for conversions between times are already stored in the timezone database, so all you should do is something like That only works if y
by masklinn 10y ago
> Instead, all the rules for conversions between times are already stored in the timezone database, so all you should do is something like
That only works if you're completely detached from the user and don't care for them. Example:
On January 1st 2011, a Samoan user living in Samoa (timezone Pacific/Apia) records an event for January 1st 2012. You convert January 1st 2012 09:00:00 to UTC, storing 2011-01-01T20:00:00.
On January 2nd 2012 at 10AM, you remind your user that they had an event set.
Because in May 2011 Samoa announced they were going to skip a local day and move across the international date line. So 2011-12-30T09:00:00 UTC was 2011-12-29T23:00:00 Pacific/Apia, but 2011-12-30T10:00:00 UTC was 2011-12-31T00:00:00 Pacific/Apia.
And as far as your user is concerned, they told you to ping them on January 1st at 9AM and you pinged a day late. Just because you store absolute datetimes doesn't mean you won't fuck up, and when the data is user-provided, chances are as good that that decision will be the one fuckup.
- realharo 10y agoThat still doesn't mean that you should do any of those operations by hand (which is what the previous comment was about). But sure, if you do scheduling for future times, you do need to be aware of such possibilities and store the future times as civil times (and have some sane way of handling non-existing/repeating times - but again, most of the time the system/library will do this for you). Then even if the user is flying across the world, they can still get the alert at the right time wherever they are (assuming the device updates local timezone based on location). I never said that you should only store absolute times - only that they are a separate data type and you shouldn't mix them or try to convert them by hand.