Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Use MongoDB fields projection on update to reduce the memory footpints #237

Merged
merged 5 commits into from
Jan 25, 2016

Conversation

yf-hk
Copy link
Contributor

@yf-hk yf-hk commented Jan 23, 2015

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

yf-hk added 5 commits January 23, 2015 18:05
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 of. At lease, if nothing will change please use MongoDB projection when only fetching the needed `_id` field
Fix failed travis test
particlebanana added a commit that referenced this pull request Jan 25, 2016
Use MongoDB fields projection on update to reduce the memory footpints
@particlebanana particlebanana merged commit 2aa4982 into balderdashy:master Jan 25, 2016
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants