Info received from hasNextPage is wrong in some resolvers about nestjs-query HOT 5 OPEN

Which ORM are you using?

Notice, It will return the hasNextPage: false even when the totalCount indicates the existence of more records.

totalCount is not used for this, what it does it fetches n + 1, then it checks if the n is bigger then what the user provided, if yes hasNextPage will become true; this way there is no need for a additional query.

from nestjs-query.

TypeORM & Postgre - Checked the executed SQL and as you mention If I set 373 It goes for LIMIT 374 and executing that SQL manually correctly gives 374 records (On the same example provided)

from nestjs-query.

Interesting, did you log the exact query TypeORM runs? (If you enable logging) And does that one return the correct results?

from nestjs-query.

Yes, I got two on the console, one for results and one SELECT COUNT(*) which should be for the totalCount, I executed them (copy-paste) manually using dbEaver and return that extra record normally. Weird enough: I just tested again using same resolver (same code) but another DB which reaches 10.9K records and works fine. I can't see how this could be related to the database.

from nestjs-query.

Interesting, using bigints maybe? I also can't think about anything that could cause this.

Think its also impossible to create a repo that reproduces this issue?

The output between the version that works and that does not work is also exactly the same? Maybe log this within the typeorm adapter to be sure.

from nestjs-query.