const v = await prisma.user.findMany({
    where: {id: {notIn: Array.from({length: 6000}, (v, idx) => idx.toString())}}
  })
  const total = await prisma.user.findMany({
    where: {}
  })
  console.log(v.length, total)

this should reproduct the problem.

@YErii 👋 Cannot reproduce this on the latest version of Prisma. I have 7 users and this is what I queried for and the response is correct:

console.log(await prisma.user.findMany({ where: { id: { notIn: [1, 2] } } }))

`not in [1,2]`is not engough and you should provide at least 5000 items

Yes this is due to Prisma batching queries. A temporary workaround if you’re querying for so many items is setting this environment variable:

QUERY_BATCH_SIZE=10000

So that it takes the amount of items you want to query in a batch. Also it would be great if you could persist this as an issue here.

Sure! But it is wierd that the

in

operator will not chunk items into 5000

It will after you set the the

QUERY_BATCH_SIZE

even if i did not set the

QUERY_BATCH_SIZE

, the

In

operator and

NOT: {in: {xx}}

will not chunk and return the right result.

Yes but for larger records like 10000 it will chunk.

Got it and Looking forward to receiving the fixup soon.