News for hackers. Stuff that matters.
Re:MongoDB, count() and the big O by cheald on Thursday November 24, 2011 @12:11AM (#3273176)
That's awfully handy. It unfortunately doesn't solve the pagination problem, though. :/
Re:MongoDB, count() and the big O by josh_cutler on Thursday November 24, 2011 @04:48AM (#3273825)
I forked a version of Kaminari a few months ago to solve this problem for me that I just updated with the latest upstream: https://github.com/joshcutler/kaminari

I added a class method for Mongoid::Documents called limit_max_count_results_to that limits the size of Kaminari's total_count

Re:MongoDB, count() and the big O by kevin1024 on Thursday November 24, 2011 @01:00AM (#3273324)
By the way, if you do .limit() / .offset() pagination, by the time you get into really high offsets, queries will start going slow again. Mongo has to do a scan up to the document at offset that you are asking for.
Re:MongoDB, count() and the big O by taf2 on Thursday November 24, 2011 @12:20AM (#3273210)
it does, if you change your pagination interface to only care if there are more results after this page...
Re:MongoDB, count() and the big O by cheald on Thursday November 24, 2011 @01:15AM (#3273362)
If your pagination interface is simply "Next", then why not skip the count all together, limit(N+1) documents, and offer the "Next" button if the result set is N+1 large?