-
Notifications
You must be signed in to change notification settings - Fork 255
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
Using createMany
with SQLite in tests results in a panic with JSON protocol
#4612
Comments
createMany
with SQLite adapter results in a paniccreateMany
with SQLite adapter in tests results in a panic
Currently expected, as Prisma doesn't support |
Panic is never expected, this issue is about having a proper error instead. |
createMany
with SQLite adapter in tests results in a paniccreateMany
with SQLite in tests results in a panic with JSON protocol
This is actually totally unrelated to driver adapters, I'm not sure how I got this impression, sorry for confusion! This is an issue in GraphQL to JSON translation. I updated the issue description. |
I moved the issue to the tech debt board. |
Hi there, This issue was originally created for internal tracking purposes, but if you feel this is important to you, feel free to reopen the issue and get like-minded users to upvote as we will prioritize fixing issues based on community interest. For more insight into our priorities and how we’re thinking about the future of Prisma, please see our blog post: https://www.prisma.io/blog/prisma-orm-manifesto. Thank you for your understanding and support! |
Trying to use
createMany
with SQLite in tests results in the following panic in tests when using JSON protocol:Expected behaviour: a proper error instead of crashing.
For example:
Field 'createManyUser' not found in enclosing type 'Mutation'
Operation 'createMany' for model 'User' does not match any query.
This seems to be an issue in GraphQL to JSON translation.
Example: https://github.com/prisma/prisma-engines/actions/runs/7304950071/job/19907898417?pr=4601
The text was updated successfully, but these errors were encountered: