-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Passing write concern during the save call #2494
Comments
Check out the safe option http://mongoosejs.com/docs/guide.html |
@yads yes, I already checked in this. But I want dynamically change behavior of the application. The safe option is required to set once, not per query. |
It can be set per query too, via the options object: http://mongoosejs.com/docs/api.html#model_Model.update On Thu, Nov 27, 2014 at 2:04 PM, Alexey Shevchenko <notifications@github.com
-Vadim Kazakov |
@yads thanks for this, I didn't know about safe updates availability. But this still doesn't solve the case, when I need to make safe or not safe inserts by |
That's definitely a limitation. It's surprising that there is a way to pass On Fri, Nov 28, 2014 at 2:34 AM, Alexey Shevchenko <notifications@github.com
-Vadim Kazakov |
Unfortunately this is currently impossible. Definitely should be added though. |
(including safe Automattic#2494)
How to do that?
For now I am using:
But I want to do it in that or similar way:
I didn't find anything about writeConcern in mongoose.
The text was updated successfully, but these errors were encountered: