Another question is why it generates

prisma:query db.User.updateMany

if I update a single user? Why not

updateOne

?

Good question, might be a missing optimization or a wrong code path. Again, optimally open a bug report issue with the info we need to understand and reproduce and we will take a look asap.