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

Y2K38: the 2038 problem #879

Open
Zankaria opened this issue Jan 24, 2025 · 0 comments
Open

Y2K38: the 2038 problem #879

Zankaria opened this issue Jan 24, 2025 · 0 comments
Labels
meta Project meta

Comments

@Zankaria
Copy link

Is vichan 2038 ready? I know the issue is still somewhat far away, but given how long the codebase has managed to survive for we might as well look at it.
What must be checked:

  • The PHP codebase. Should be fine, mostly? At least as long as it's run on a 64-bit CPU.
  • The SQL schema: we're using unsigned ints, are they safe?
  • The SQL queries. We should review the SQL functions in particular, as things as UNIX_TIMESTAMP() return a 32-bit value.
@RealAngeleno RealAngeleno added the meta Project meta label Jan 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Project meta
Projects
None yet
Development

No branches or pull requests

2 participants