4.11.0: Unique constraint failed on the fields on query that worked in 4.10.1

[janpio]

Reproduction repository: https://github.com/janpio/prisma-4.11-pdp-regression

[janpio]

Workaround: The problem is caused by the unique field WART_id in the example. When it is created not with null but a unique value (e.g. i form the loop) the code runs successfully.

[miguelff]

Created a reproduction in prisma-engines and bisect it through the commit history.

The regression started from this commit. prisma/prisma-engines@9984a8d I will take it from here.

[miguelff]

It was fixed later by prisma/prisma-engines@2f443b1 so this is no longer an issue

[janpio]

My reproduction is unfortunately still failing with the latest prisma@dev and @prisma/client@dev which is currently 4.12.0-dev.13. Did this maybe not get integrated and release into the CLI and Client yet?

Params: [0,0]
Query: UPDATE "public"."with_compound_unique" SET "WART_id" = $1 WHERE "public"."with_compound_unique"."WART_id" IS NULL
Params: [0]
Query: ROLLBACK
Params: []
PrismaClientKnownRequestError: 
Invalid `prisma.with_all_relation_types.update()` invocation in
/workspace/prisma-4.11-pdp-regression/script.js:37:40

  34 
  35 }
  36 
→ 37 await prisma.with_all_relation_types.update(
Unique constraint failed on the fields: (`WART_id`)
    at Zr.handleRequestError (/workspace/prisma-4.11-pdp-regression/node_modules/@prisma/client/runtime/library.js:171:6414)
    at Zr.handleAndLogRequestError (/workspace/prisma-4.11-pdp-regression/node_modules/@prisma/client/runtime/library.js:171:5948)
    at Zr.request (/workspace/prisma-4.11-pdp-regression/node_modules/@prisma/client/runtime/library.js:171:5786)
    at async t._request (/workspace/prisma-4.11-pdp-regression/node_modules/@prisma/client/runtime/library.js:174:10455)
    at async main (/workspace/prisma-4.11-pdp-regression/script.js:37:3) {
  code: 'P2002',
  clientVersion: '4.12.0-dev.13',
  meta: { target: [ 'WART_id' ] }
}

[miguelff]

Did this maybe not get integrated and release into the CLI and Client yet?

Exactly, the revision of prisma engines used in this version does not include prisma/prisma-engines@2f443b1

From npm → Code → Prisma commit 7893f1af → prisma-engines @ 3b9f029a (earlier than prisma/prisma-engines@2f443b1)

[janpio]

I can now confirm that this is fixed in 4.12.0-dev.30 🥳