Earlier today, I saw on Lemmy that comments made within the last hour since DST were now in the negatives since time had rolled back. If a database uses time like this for search operations, would that interfere with them? Could it corrupt the database?
It depends on the database. But it’s common practice to store values in UTC, which doesn’t have DST, and only display in the user’s timezone. What you saw was probaby only a bug on the front end, but not database corruption.
Or just Unix (epoch) time.
https://en.wikipedia.org/wiki/Unix_time
There can be problems with leap seconds using UTC (or leap hours eventually)
https://en.wikipedia.org/wiki/Leap_second
They decided to stop doing leap seconds.
Until they decide to reverse it, or until they make a different change.
Just use Epoch time for backend and calculations, and use local time for displaying to the user (or UTC for debugging systems that span time zones)
Unix time is just a weird way of storing UTC time, since it’s a duration relative to a UTC time.