2038 issue
We use the patron's 18th birthday as their youth card expiration date. Due to the Year 2038 issue we have been unable to add the correct date for several years now. We would really like to be able to have (any/all) date fields updated so we can begin to record accurate future dates again.
-
Greg Smith commented
Innovative is going to have to switch to 64-bit dates to fix this problem. The case highlighted here is probably the one that is hitting the wall first; I wonder if they plan to EOL Sierra before this problem begins to affect core system functions rather than resolve the issue across the board.
-
Eliza Richards commented
I've been asking for this for years. I think the original answer III gave me was there was a limitation outside their control, but I would hope that is fixed now!
-
Jeremy Goldstein commented
This is a critical issue, but also one that is far larger than this specific use case and I'm guessing has impacts on all dates and timestamps present anywhere in the system. For reference https://en.wikipedia.org/wiki/Year_2038_problem