The following example from https://www.prisma.io/express does not work due to my

id

field being an integer. I get the following error:

PrismaClientValidationError: Argument id: Got invalid value '1' on prisma.updateOnePost. Provided String, expected Int.

app.put('/publish/:id', async (req, res) => {
  const { id } = req.params
  const post = await prisma.post.update({
    where: { id },
    data: { published: true },
  })
  res.json(post)
})

Is there anyway to run this without calling

parseInt(id)

?

Is there anything stopping you from just using the Number constructor?

I use pipe in NestJS. But that’s basicallly parseInt as well.

@Yaakov 👋 Prisma validates the types before calling the query so converting to an integer is mandatory.

@propagandalf What would be the benefit of the Number constructor over parseInt?

There wouldn't really be much of a benefit, its just another form of achieving the same. Without diving too far into it, in fact I wouldn't recommend number over parseint, when you are specifically looking for integers. The "main" thing here is, that your url parameters are stringified, and you need to explicitly make sure those are integers for the database (in this case prisma) to work properly.