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

[BUG] Time periods stored as milliseconds can be too large for the field type #530

Open
1 task done
eartharoid opened this issue Mar 24, 2024 · 0 comments
Open
1 task done
Labels
bug Something isn't working
Milestone

Comments

@eartharoid
Copy link
Member

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

ms is used to convert strings like 1 day into milliseconds, but some reasonable inputs like 30d are too large to store.

Expected Behavior

No response

Steps To Reproduce

No response

Environment

- OS: -
- Node: -
- NPM: -
- Bot: <4.1

Anything else?

Database types: https://www.prisma.io/docs/orm/reference/prisma-schema-reference#int

Affected fields:

cooldown Int?

autoClose Int @default(43200000)

staleAfter Int?

@eartharoid eartharoid added the bug Something isn't working label Mar 24, 2024
@eartharoid eartharoid added this to the v4.1 milestone Mar 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Todo
Development

No branches or pull requests

1 participant