Feature: Allow non-unique fields to be used with update

Problem

when doing an update on a model sometime we want to filter on non-unique field to make sure that we only update rown which user has access to, for example like this:

 prismaClient.userPicture.update({
            where: {
              id: picture.id,
              user_id: req.user.id // currently this line is not possible when user_id is not unique
            },
            data: {
              verified_at: new Date()
            },
          })

It would be nice to be able to optionally provide non unique fields to the where condition. Currently it only allows fiels which are unique. I would like if we could use fields which are not unique as well.

Suggested solution

Allow non-unique fields to be used with update.

Alternatives

Currently we can work around this by using updateMany, but this is not ideal. In most API calls you want to return the updated item right away, so being able to do it all with a single prisma query would be nice.

Additional context

[Weakky]

Hey folks,

A solution was implemented by https://github.com/prisma/prisma-engines/pull/3281. It will be available in the next release under a new preview flag called extendedWhereUnique.

If you have any feedback you’d like to give about this feature, please post it here https://github.com/prisma/prisma/issues/15837#event-7600630285

Thanks for your patience, closing now 🙏.

[janpio]

Thanks, we are looking into this right now.

Here is another issue with a lot more use cases and comments: https://github.com/prisma/prisma/issues/7290