JSON fields filtering stopped working in 2.5.0

Bug description

Filtering on JSON field (equals, not) stopped working in 2.5.0.

How to reproduce

Running this code:

import { PrismaClient } from "@prisma/client";

const prisma = new PrismaClient({});

async function main() {
  await prisma.$connect();
  await prisma.post.deleteMany({});

  await prisma.post.create({
    data: {
      title: "Post title 1",
      metadata: {
        published: true,
      },
    },
  });
  await prisma.post.create({
    data: {
      title: "Post title 2",
      metadata: {
        published: false,
      },
    },
  });
  await prisma.post.create({
    data: {
      title: "Post title 3",
      metadata: {
        otherKey: "otherValue",
      },
    },
  });

  const allPosts = await prisma.post.findMany();
  const publishedPosts = await prisma.post.findMany({
    where: {
      metadata: {
        equals: {
          published: true,
        },
      },
    },
  });
  const notPublishedPosts = await prisma.post.findMany({
    where: {
      metadata: {
        equals: {
          published: false,
        },
      },
    },
  });
  const notEqualsPublishedPosts = await prisma.post.findMany({
    where: {
      metadata: {
        not: {
          equals: {
            published: true,
          },
        },
      },
    },
  });
  
  console.log(
    util.inspect(
      {
        allPosts,
        publishedPosts,
        notPublishedPosts,
        notEqualsPublishedPosts,
      },
      false,
      null
    )
  );
}

main()
  .catch((e) => console.error(e))
  .finally(async () => {
    await prisma.$disconnect();
  });

Results in this:

{
  allPosts: [
    { id: 9, title: 'Post title 1', metadata: { published: true } },
    { id: 10, title: 'Post title 2', metadata: { published: false } },
    {
      id: 11,
      title: 'Post title 3',
      metadata: { otherKey: 'otherValue' }
    }
  ],
  publishedPosts: [],
  notPublishedPosts: [],
  notEqualsPublishedPosts: []
}

Expected behavior

It should return properly filtered data.

Prisma information

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

generator client {
  provider = "prisma-client-js"
}

model Post {
  id       Int    @id @default(autoincrement())
  title    String
  metadata Json
}

Environment & setup

• OS: Windows 10 (WSL2 Ubuntu 20.04)
• Database: Postgres
• Node.js version: 14
• Prisma version:

@prisma/cli          : 2.5.0
Current platform     : debian-openssl-1.1.x
Query Engine         : query-engine 9a670138b1db276001d785a2adcba1584c869d24 (at node_modules/@prisma/cli/query-engine-debian-openssl-1.1.x)
Migration Engine     : migration-engine-cli 9a670138b1db276001d785a2adcba1584c869d24 (at node_modules/@prisma/cli/migration-engine-debian-openssl-1.1.x)
Introspection Engine : introspection-core 9a670138b1db276001d785a2adcba1584c869d24 (at node_modules/@prisma/cli/introspection-engine-debian-openssl-1.1.x)
Format Binary        : prisma-fmt 9a670138b1db276001d785a2adcba1584c869d24 (at node_modules/@prisma/cli/prisma-fmt-debian-openssl-1.1.x)
Studio               : 0.259.0

[timsuchanek]

Thanks a lot for reporting 🙏 This issue is fixed in the latest dev version of @prisma/cli. You can try it out with npm i -g @prisma/cli@dev.

In case it’s not fixed for you - please let us know and we’ll reopen this issue!

[timsuchanek]

Good point @MichalLytek ! I just created a separate issue for that: https://github.com/prisma/prisma/issues/3441