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
Trying to use createMany with SQLite in tests results in the following panic in tests when using JSON protocol:
thread '...' panicked at query-engine/connector-test-kit-rs/query-tests-setup/src/runner/json_adapter/request.rs:26:89:
called `Option::unwrap()` on a `None` value
Expected behaviour: a proper error instead of crashing.
For example:
With GraphQL protocol, whether in QE tests or end-to-end with client, it triggers a user-facing error with code 2009 and message Field 'createManyUser' not found in enclosing type 'Mutation'
With JSON protocol end to end it triggers an error with message Operation 'createMany' for model 'User' does not match any query.
This seems to be an issue in GraphQL to JSON translation.
aqrln
changed the title
[DA] Using createMany with SQLite adapter results in a panic
[DA] Using createMany with SQLite adapter in tests results in a panic
Dec 23, 2023
Panic is never expected, this issue is about having a proper error instead.
aqrln
changed the title
[DA] Using createMany with SQLite adapter in tests results in a panic
Using createMany with SQLite in tests results in a panic with JSON protocol
Jan 8, 2024
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.
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: