OnUpdate default referential Integrity action while using Prisma to handle referential Integrity

Intro

it is mentioned in the docs that the default referential integrity actions are these here

but it is also stated in the docs that while using Prisma to handle referential integrity that the available actions are

It is not clearly mentioned in the docs that you should manually set the onUpdate to noAction

---

Problem

enabling the preview feature referentialIntegrity and attempting to update a record that has relation lead me to this error (creating and deleting records works fine)

Message: 
Invalid `prisma.institution.update()` invocation:


  Error occurred during query execution:
ConnectorError(ConnectorError { user_facing_error: None, kind: QueryError(Server(ServerError { code: 1105, message: "symbol db.Institution.id not found", state: "HY000" })) })

Query: 
prisma.institution.update(
{
  where: {
    id: 44,
  },
  data: {
    firstName: "Random",
  },
  select: {
    id: true,
    firstName: true,
  },
}
)

---

Solution

setting onUpdate to noAction resolved this error. I would like to propose to either set the default action while using referentialIntegrity for update operation to noAction (since this is the only available option at this time) or at least mention this explicitly in the documentation

---

Notes

I should also note I was using Prisma combined with Planetscale, i don’t know if this is relevant but i’ll just leave it here

[NBruhno]

Is it possible that you did not run npx prisma generate to regenerate your Prisma Client after making the change? That is necessary for the Client to learn about the change in expected referential action and thus run the correct queries (or no queries at all in this case).

Apologies, but I only ran prisma migrate dev --name <name>, (which I believe runs generate regardless of pending migrations or not). I think it might have mixed with the issue that I had previously with running prisma while using pnpm in my repo, which didn’t update the client properly unless I did a reinstall of the client when doing either migrate or generate. But it looks like that is no longer an issue either (don’t know which version fixed that for me, or if it was a pnpm issue).

I cannot reproduce my generate issue anymore. It’s just the onDelete and onUpdate that does not seem to have sane defaults for referentialIntegrity, as you have already mentioned.

[janpio]

We think this is only a docs issue - so closing and creating a new one there.