Skip to content

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

@eartharoid

Description

@eartharoid

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions