deadowl@deadowl@lemmy.world

Replying to @⁨Wurzl@lemmy.zip⁩

It will probably be 2038 with Oracle leading the charge of expecting AI to solve the 2038 problem after everyone collectively waits until the last minute because they don’t want to pay for IT, while new software without foresight continues to prefer MySQL timestamp over datetime because you can get it to be UTC aware with the table definition for audit fields (e.g. on update clause) instead of having to create a separate trigger to explicitly set it to UTC.

tal@tal@lemmy.today

Replying to @⁨deadowl@lemmy.world⁩

after everyone collectively waits until the last minute because they don’t want to pay for IT

We handled the Y2K problem. Yeah, a few minor bugs slipped through, but I remember identical concerns in the 1990s about how businesses would wait until the last minute and then there wouldn’t be enough people with the relevant skillset to get it fixed in a short window.

I’m pretty confident that we’ll also handle the Y2038 problem.

en