Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TIMESTAMP 2038 problem #22

Open
Osiris-Team opened this issue Sep 12, 2024 · 0 comments
Open

TIMESTAMP 2038 problem #22

Osiris-Team opened this issue Sep 12, 2024 · 0 comments

Comments

@Osiris-Team
Copy link
Owner

Osiris-Team commented Sep 12, 2024

TIMESTAMPS will break in 2038 because they are stored with 32 bits instead of 64. (MySQL) https://dev.mysql.com/doc/refman/8.4/en/datetime.html

Possible fix: Do not use TIMESTAMP internally but use some kind of wrapper and instead store a 64 bit long number.
Or hope that the database software itself finds a fix some day.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant