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

Optimistic locking of cooldown table and generate history timestamp on DB side. #99

Open
pumbas600 opened this issue May 6, 2024 · 1 comment
Assignees
Labels
backend An issue related to our backend package not in proposal

Comments

@pumbas600
Copy link
Collaborator

  • Prevent the possibility of multiple concurrent requests being processed.
  • Make the database generate the timestamp for the history database (Add @default(now()) in Prisma. @sou323 will need to update the database.
@sou323
Copy link
Collaborator

sou323 commented May 8, 2024

added in database

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend An issue related to our backend package not in proposal
Projects
None yet
Development

No branches or pull requests

4 participants