From 6ea9c351d94081c5268b4cad0ea3ba186e628168 Mon Sep 17 00:00:00 2001 From: Felix Wu Date: Sat, 21 Mar 2026 17:36:03 +0100 Subject: [PATCH] feat(docs): add clarification on database upsert criteria --- .../content/docs.v6/orm/reference/prisma-client-reference.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/apps/docs/content/docs.v6/orm/reference/prisma-client-reference.mdx b/apps/docs/content/docs.v6/orm/reference/prisma-client-reference.mdx index 2156a89a84..5453f5c5fb 100644 --- a/apps/docs/content/docs.v6/orm/reference/prisma-client-reference.mdx +++ b/apps/docs/content/docs.v6/orm/reference/prisma-client-reference.mdx @@ -1063,6 +1063,7 @@ Prisma Client uses a database upsert for an `upsert` query when the query meets - The query modifies only one model - There is only one unique field in the `upsert`'s `where` option - The unique field in the `where` option and the unique field in the `create` option have the same value +- The update clause is not empty If your query does not meet these criteria, then Prisma Client handles the upsert itself.