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
Make transaction timeouts configurable _globally_ when calling new PrismaClient()
#15028
Comments
We need this ASAP! |
any update ? |
new PrismaClient()
#19592 adds this, and just needs tests/approval to be merged. |
Hi, just ran into this now. We have hundreds of transactions in our app and having to go hunt them down as they fail is very time consuming. Looking forward to this improvement, ty. |
This has been shipped as part of release 5.10.x:
|
This is the luckiest I've been with running into any issue on Prisma: 'cause this issue had been open for almost two years, but luckily for me, when it mattered to me, alas (!), it was just resolved two weeks ago. Trust me, I've been unlucky with an awful lot, long lasting issues from like 3, 4 years all still open. I celebrate this likkle win 🎉🥳 |
Problem
the default interactive transaction timeout is too low.
For example I work on a DB located on the other side of the world. With the default timeout it easily get's closed even when nothing goes wrong.
Suggested solution
Alternatives
create a helper function something like this:
Additional context
#13713
The text was updated successfully, but these errors were encountered: