Prisma incorrectly parses CRDB's FK constraint error as not available

[evangeline]

Bug description

We are seeing errors like

Foreign key constraint failed on the field: `(not available)`

and was wondering whether it’s possible to surface which FK is causing this error. Some tables have multiple FKs, and (not available) makes it harder to narrow down which FK is throwing.

When running the query manually, CRDB throws the following error, which suggests that Prisma is not parsing the FK name correctly.

ERROR: insert on table "WearablePart" violates foreign key constraint "WearablePart_wearableId_fkey" Detail: Key (wearableId)=('foo') is not present in table "Wearable".

How to reproduce

1. Create a table with a FK constraint in CRDB
2. Insert data with an invalid foreign key via Prisma
3. Insert the same data via cockroach sql or any other DB client

Expected behavior

I would expect to see the error

Foreign key constraint failed on the field: `WearablePart_wearableId_fkey`

Prisma information

Fails on any schema, repro steps above.

Environment & setup

• OS: macOS
• CockroachDB
• Node.js version: v18.17.0

Prisma Version

v5.9.1

[janpio]

Can you maybe create a reproduction repository that we can just run to experience this problem? Thanks.