Add update of non-existent node to known errors

For this Prisma Client code:

  const result = await client.user.update({
    where: {
      id: 123012938,
    },
    data: {},
  })

As of now, we get an error like this:

PrismaClientUnknownRequestError: 
Invalid `prisma.users.update()` invocation:

Error occurred during query execution:
InterpretationError("Error for binding \'0\': RecordNotFound(\"Record to update not found.\")")

We should add that to the known errors and return an error code.

[Cretezy]

Is there a way to disable this error checking?

Our use case is an update, but it’s possible the record doesn’t exist (which would be a no-op). We don’t care in this case that the record doesn’t exist. Ideally, a argument to update such as ignoreMissing would be the solution here.

[PierreAndreis]

Is there a way to disable this error checking?

Our use case is an update, but it’s possible the record doesn’t exist (which would be a no-op). We don’t care in this case that the record doesn’t exist. Ideally, a argument to update such as ignoreMissing would be the solution here.

I would like that as well, but does updateMany resolve this for you?