Replies: 1 comment
-
It looks like the extended client is unable to solve relations like the Graphql API is intending |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi community, for some reasons that I don't understand, using the plugin for Read Replicas breaks the autogenerated types.
In a very simple use case, when generating the
prisma
client for the GraphQL context:going from:
to:
This starts creating errors in the graphql types, like fields not being iterable, null vs non-nulls, etc. I'm not sure why, some other autogenerated resolvers work just fine. I haven't identified a pattern. And as the autogenerated files are the same, it looks like something changed on the Prisma client that makes the queries return a different structure.
Inspecting the extension, I notice that he creates the replicas using this:
From the wrapped client, maybe this is the issue.
Has anybody had luck using the Read Replicas plugin?
Beta Was this translation helpful? Give feedback.
All reactions