Data base problem when the year is more then 2038

The concern was previously raised in 🐛 Far-future dates cause WSOD, "Numeric value out of range" Fixed . Drupal 10.1, due to be released in the coming days, resolves the "2038 problem" by storing timestamps as BIGINT columns instead of INT. It's worth noting that BIGINT uses less storage than storing dates as ISO 8601 strings in a VARCHAR field, and is more performant.

I would love to provide native DATETIME storage as an even better alternative, but this would require significant work to implement. If this is something you would like to work on, however, I would gladly review a patch or merge request.