Use MongoDB fields projection on update to reduce the memory footpints #237
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.
As the discussion in another issue balderdashy/waterline#805, I would suggest for an update operation, it's not needed to return the full updated result set. But even it's for compatibility reason we keep it, it should have an option to turn it off. At lease, if for now there's no plan to do it, we can use MongoDB projection when only fetching the needed
_id
field in the first find query