Having the "query" logLevel for the prismaClient enabled, every findMany / count query logs an

OFFSET $<Number>

at the end, although i didn't provide any args for that, e.g. (having 3 params provided for the query (postgres):

.... AND "t0"."A" IS NOT NULL))) OFFSET $4) AS "sub"

I assume the value the prismaClient generates for that OFFSET is always '0' by default, since the query results are as expected and no offset seems to be applied. Is there a reason the prismaClient generates an OFFSET statement for every query?

@Luis Kuper 👋 You’re correct. The offset is always

0

by default and that’s a condition added for complex queries but also shows up in normal queries. It can be removed actually in this case and if you would like to create an issue for this then feel free to do so 🙂