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
executeRaw and executeRawUnsafe did not invalidate model caches.
To Reproduce
Steps to reproduce the behavior:
Do findMany action of a model
Do an update to their columns using executeRaw or executeRawUnsafe
Do findMany action of a model again, cache hit
The result of the second findMany is using the cache despite mutation from executeRaw or executeRawUnsafe
Expected behavior
It should invalidate the caches.
Screenshots
Additional context
As you can see from the screenshot, I'm currently using executeRawUnsafe, but the params.action is executeRaw, and executeRaw is not in defaultMutationMethods. I'm currently using Prisma 5.6.0. I'm not sure if this would also apply to Prisma 4 or lower.
Describe the bug
executeRaw and executeRawUnsafe did not invalidate model caches.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should invalidate the caches.
Screenshots
Additional context
As you can see from the screenshot, I'm currently using executeRawUnsafe, but the params.action is executeRaw, and executeRaw is not in defaultMutationMethods. I'm currently using Prisma 5.6.0. I'm not sure if this would also apply to Prisma 4 or lower.
I've made a PR for this #660
The text was updated successfully, but these errors were encountered: