Using $facet instead of two queries & adding paginateExec to Aggregate #36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request contains two features:
$facet
operator is now being used by default instead of executing two queries. To disable, passuseFacet: false
to the options.Aggregate
is extended and paginate can now be called directly usingaggregate.paginateExec(options, [cb])
.If
countQuery
anduseFacet
, two queries will still be executed, and facet will be ignored.Breaking Changes:
$facet
is now used by default.