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?
UTC homie. It’s what the databases runs on. Local timezones and DST are all based off of that not some arbitrary local variation of time.
I’ve heard some companies where time is critical make extra certain by closing for any writes during the time change.
Most places it is sufficient to stick to UTC.
An online storefront for refilling cafeteria cards I know of are so careful they close every night…
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)
Unix time is just a weird way of storing UTC time, since it’s a duration relative to a UTC time.
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)
Like most anything, there are methods and designs (best practices) which if followed, will prevent you from falling into pitfalls like that. It’s generally only a problem if you design things to use time and not account for it. And as for the time changing while an operation is currently occurring, this again, is what transactions and other “atomic” type of operations are designed to account for. There is a lot about computer science where you need to make sure the sand you’re standing on isn’t shifting when you’re on it.
This is poor Lemmy programming, has nothing do with DST. You’ll often see if you’re posting a comment it will say “in 3 seconds”, meaning in the future. It’s because of how the frontend calculates the relative time based on a db timestamp against the local clock of your computer… which are beginner programmer mistakes from the late 90’s.
Slightly off topic below.
The 2 blokes programming this are not very good and since they are now beginning to peddle violence inciting garbage they can stuff their monthly donation too.
Sorry, not in the loop. What violence peddling are you referring to?
Well they don’t peddle violence directly of course that would be incriminating. They are setting up their instance moderation rules so that burning down the western democracies is encouraged.
As an American, the western democracies are burning themselves.
If the field is defined well it shouldn’t corrupt the database but it may affect sorting during that timespan.
