3 ms·
Why isn't moving the epoch a reasonable option? You go through and subtract 50 years from all date values you have in storage, change the date display code to
by hakfoo 6y ago
Why isn't moving the epoch a reasonable option?
You go through and subtract 50 years from all date values you have in storage, change the date display code to show everything based on 2020, and you've kicked the can on the problem down to 2088.
- jabl 6y agoBecause you're breaking backwards compatibility by changing the interpretation of those timestamp fields. If you do that, you might as well switch to a 64-bit time_t. Treating a 32-bit timestamp field as unsigned seconds since the epoch at least keeps backwards compatibility with existing software up until 2038.