You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When calling paginate and passing a repository as the first parameter and a searchOptions parameter that is just a FindOptionsWhere, none of the items in the FindOptionsWhere object show up in the resulting SQL. The only item that appears in the where is deletedAt = null which is automatically added by TypeORM. LIMIT does correctly show up in the SQL.
This seems due to the use of TypeORM's Repository.find method that only takes a FindManyOptions. Hence, if you take the FindOptionsWhere object and set it the searchOptions as { where: findOptionsWhere }, the resulting SQL is as expected.
We are using v4.0.4 of nestjs-typeorm-paginate.
The text was updated successfully, but these errors were encountered:
When calling
paginate
and passing arepository
as the first parameter and asearchOptions
parameter that is just aFindOptionsWhere
, none of the items in theFindOptionsWhere
object show up in the resulting SQL. The only item that appears in the where isdeletedAt
= null which is automatically added by TypeORM. LIMIT does correctly show up in the SQL.This seems due to the use of TypeORM's Repository.find method that only takes a
FindManyOptions
. Hence, if you take theFindOptionsWhere
object and set it thesearchOptions
as{ where: findOptionsWhere }
, the resulting SQL is as expected.We are using v4.0.4 of nestjs-typeorm-paginate.
The text was updated successfully, but these errors were encountered: