You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 4, 2023. It is now read-only.
Describe the bug
for case prisma.$transaction([queryA, queryB]) , if queryA was found in cache, queryB will stuck in transaction.
To Reproduce
Steps to reproduce the behavior:
asyncpaginatedResult(skip: number){const[totalCount,result]=awaitthis.prisma.$transaction([this.prisma.article.count(),this.prisma.article.findMany({ skip })]);return{ totalCount, result };}
query with paginatedResult(0)
response 200 successfully, and result cached
query with paginatedResult(1)
request freeze until timeout
Expected behavior
for case prisma.$transaction([queryA, queryB]) , return cached result if both queryA and queryB was found in cache, otherwise fetch from prisma.
Desktop (please complete the following information):
OS: MacOS
Browser: postman
Version: ^4.8.0
The text was updated successfully, but these errors were encountered:
Describe the bug
for case
prisma.$transaction([queryA, queryB])
, if queryA was found in cache, queryB will stuck in transaction.To Reproduce
Steps to reproduce the behavior:
paginatedResult(0)
paginatedResult(1)
Expected behavior
for case
prisma.$transaction([queryA, queryB])
, return cached result if both queryA and queryB was found in cache, otherwise fetch from prisma.Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: