-
Notifications
You must be signed in to change notification settings - Fork 13
Support for Prisma v6 #42
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
base: main
Are you sure you want to change the base?
Conversation
Given Prisma 6.1 is due to be released later today, could we get some attention here to loosen the restrictions @SevInf ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for updating the README with the development notes.
Any updates on this? Since the release of v6 our read replicas from Neon DB are not working with this extension. |
I think this extension is effectively unsupported by Prisma now. The main developer on it and others from the org have also left. My company has forked it and patched with the great work from @clemens : https://github.com/with-power/extension-read-replicas Feel free to use it. |
Unfortunately this fork does not seem to work with 6.2.1 as we are getting "Cannot read property 'findMany' of undefined" for any and all Prisma queries. |
Yes same issue! |
can we get this merged? what the heck prisma! |
Yeah this is unacceptable. We're no longer able to use read replicas because of this in our application. |
I was able to get an update from the Prisma team regarding this PR and the state of this issue: |
Hey everyone! We released a new version of read-replicas extension - https://www.npmjs.com/package/@prisma/extension-read-replicas Can you please upgrade to the latest version and confirm if the issue is resolved? |
Confirmed this is working. I'll be closing out our fork and recommending folks return to using this one. |
Prisma 6 has just hit the shelves. This PR adds support for it by relaxing the version constraint of the peer dependency and explicitly using v6 for testing.
While I was at it, I also updated the README to include instructions on how to run the tests locally using Docker.
This would fix #41.