We have a model with a series of unique: true validations. Prosopite is detecting the uniqueness checks as N+1s, because they are executed one after another as
SELECT 1 as one FROM "table" WHERE "column"= $1 AND id != $2 LIMIT $3
Thanks for reporting! i will probably add an exception for uniqueness validations.
It seems that there is no way for preventing the multiple queries there other than DB constraints.
We have a model with a series of unique: true validations. Prosopite is detecting the uniqueness checks as N+1s, because they are executed one after another as
SELECT 1 as one FROM "table" WHERE "column"= $1 AND id != $2 LIMIT $3