Hexadecimal clock counting down to 2038 problem

Re:Hexadecimal clock counting down to 2038 problem by q7xvh97o2pDhNrh on Monday September 18, 2023 @05:28PM (#37562326)

> However, if the timezone in question has some changes you didn't anticipate (new law voted, no more summer time), then you will either be triggering your event 1h before (e.g. 9am instead of 10am) which is probably not what your user wanted, or you'll have to recompute all your timestamps to take that change into account.

This is a really interesting scenario that I hadn't considered at all. You're totally right; this approach breaks down there.

Off the top of my head, it looks like this scenario would require manual action either way, though. Either it's an update of the packaged datetime library to incorporate this new regulation, or it's a database migration to update the timestamps for affected users.

[ Parent | on HN ]

Re:Hexadecimal clock counting down to 2038 problem by Gabrys1 on Wednesday September 20, 2023 @12:40AM (#37580438)

The same goes for "times this business is open" to store "9am-4pm on weekdays" you probably want to store almost exactly that string, rather than some ints. Generally speaking, dates stored as "ints" are mostly good for timestamps of events that have already happened (or even more precisely events that your application generated/logged live). Other use cases may be more rooted in the "human" dates than in absolute time

[ Parent | on HN ]