Select none in update

Problem

Currently an update is quite slow because it does 3 steps:

1. Select my thing
2. Update my thing
3. Select my thing

I do understand the need for the first select to make sure it updates only one record, but the last one if a bit annoying.

Suggested solution

It was suggested elsewhere that it could be using a RETURNING/other similar clause to remove the last one. This would be nice, but my understanding is that it is an important change. I suggest as a first step to allow users to tell prisma to not return anything. This would need a new keyword in select, I suggest none:

prisma.myThing.update({
  data: { ... },
  where: { id: 1 },
  select: { none: true }
})

Alternatives

You can use an updateMany to avoid the second select.

[mrodz]

https://www.prisma.io/docs/concepts/components/prisma-client/null-and-undefined ☝️ The docs state:

null is a value undefined means do nothing

So, you can achieve the behavior you’re looking for by writing:

prisma.myThing.update({
  data: { ... },
  where: { id: 1 },
  select: undefined
})

Hope this helps 😃

[tekoh]

no updates on this? seems like its been an issue for a while now