Query wants a string when given an int, wants an int when given a string

Bug description

With this query:

    const areaId = '1';
    const area = await db.area.findFirst({
      where: {
        id: areaId,
      },
      rejectOnNotFound: true,
    })

model Area {
  id                                        String                                      @id
  type                                      AreaType
  treeCanopy                                Float
  totalArea                                 Float
}

When the areaId variable is a string, I get

Invalid `prisma.area.findFirst()` invocation: Failed to validate the query: `Unable to match input value to any allowed input type for the field. Parse errors: [Query parsing/validation error at `Query.findFirstArea.where.AreaWhereInput.id`: Value types mismatch. Have: String("440030222021"), want: Object(IntFilter), Query parsing/validation error at `Query.findFirstArea.where.AreaWhereInput.id`: Value types mismatch. Have: String("440030222021"), want: Int]` at `Query.findFirstArea.where.AreaWhereInput.id`.

Okay, so let’s try an int. I change it to an int because it wants an int. Now, I get

Invalid `prisma.area.findFirst()` invocation: { where: { id: 440030222021 ~~~~~~~~~~~~ } } Argument id: Got invalid value 440030222021 on prisma.findFirstArea. Provided Int, expected StringFilter or String: type StringFilter { equals?: String in?: List<String> notIn?: List<String> lt?: String lte?: String gt?: String gte?: String contains?: String startsWith?: String endsWith?: String mode?: QueryMode not?: String | NestedStringFilter } type StringFilter { equals?: String in?: List<String> notIn?: List<String> lt?: String lte?: String gt?: String gte?: String contains?: String startsWith?: String endsWith?: String mode?: QueryMode not?: String | NestedStringFilter } .

So: when I have a string input to a query, it wants an int. When I have an int input, it wants a string. Frustrating.

How to reproduce

• Load the given schema
• Try the given query

Expected behavior

A string should be the input here.

Prisma information

• Prisma/client 3.9.2
• prisma 3.9.2

Environment & setup

• OS: macOS
• Database:PostgreSQL
• Node.js version: 14.x

Prisma Version

3.9.2

[tmcw]

This bug report includes the schema. The id column is a string column. If the column as an Int, then I would expect this to work with an integer value. As the issue describes, the query does not work with either integer or string values, and for each it requests the other.

[Jolg42]

Could it be that id used to be an Int and somehow the schema used by the engine and the client are out of sync? Maybe a missing npx prisma generate or database migration?