This post is the top search result for both implicit and explicit disconnect many to many. If you want to completely disconnect an implicit many to many:

const data = await prisma.group.update({
    where: {
        id: groupId,
    },
    data: {
        users: {
            set: [],
        },
    },
});

Gotten from here: https://github.com/prisma/prisma/issues/5946

@janpio totally understand that since the prisma client forces the 1:n relations in that way if we want additional columns on the m:n type of table. In this case, you are correct in that it is not necessarily a true m:n anymore, however, from the prisma documentation standpoint it is what it ultimately is. Unfortunately for me, I had to add a primary key column in there due to another tools incompatibility with a multi-primary key 🤷.

it would be nice if prisma was able to handle this portion of complexity, although, it might be possible for me to define this type of action through middleware in order to handle it automatically. I suppose the real feature request would be to have true m:n relations rather than the implicit many-to-many.

You can use set replace connect

data: {
    groups: {
        set: {
            id: "3"
        }
    }
}

Hey @kova1max 👋

Currently, Prisma throws P2025 error code when the related record does not exist.

One possible workaround could be to handle this case explicitly by doing something like this:

try {
  await prisma.user.update({
    where: { id: userId },
    data: {
      post: { disconnect: true }
    }
  })
} catch (error) {
  if (error instanceof Prisma.PrismaClientKnownRequestError) {
    // Specifically handle "record not found" scenario
    if (error.code === 'P2025') {
      // Silently handle or log
      console.log('No related record to disconnect')
    }
  }
}

There is a related feature request here that would be relevant

• #9460

I would recommend you to add a 👍 to the feature request, so that we can prioritize it.