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 was archived by the owner on Jan 14, 2021. It is now read-only.
constb=awaitprisma.enitityB.create({data: {name: "B NAME"}})// ==== Panic here ====consta=awaitprisma.enititA.upsert({where: {connectorId_indicator_query: {connectorId: b.id,indicator: "INDICATOR_A",query: "QUERY_A",}},create: {connector: {connect: {id: b.id}},indicator: "INDICATOR_A",query: "QUERY_A",name: "A NAME"},update: {name: "A NAME updated"}})
Prisma panic error:
PANIC: called `Option::unwrap()` on a `None` value at PrismaClientFetcher.request (/private/tmp/prisma-panic/node_modules/@prisma/client/src/runtime/getPrismaClient.ts:643:15) at processTicksAndRejections (internal/process/task_queues.js:97:5)Error in Prisma Client:PANIC: called `Option::unwrap()` on a `None` value inquery-engine/core/src/query_graph_builder/extractors/filters.rs:279:35
Bug description
Prisma Client JS panic on upsert query.
Prisma panic error:
How to reproduce
You can reproduce with this repository: https://github.com/hugo082/prisma-client-issue
Expected behavior
The entity A must be created and prisma client must not panic.
Prisma information
Prisma schema:
Environment & setup