Inconsistent behaviour for .create/.save vs updateOne/findOneAndUpdate for null values about mongoose HOT 6 CLOSED

mongoose don't run validators on update by default, if you want to run validators on update operations also then you need to write this:

mongoose.set('runValidators', true);

from mongoose.

Update validators are disabled by default because update validators come with some caveats that tend to cause trouble for custom validators. Read these sections of the validation docs for more info on the caveats.

so should i preferably use save instead update to ensure data i am trying to add in db matches schema for sure? Yes, if matching your schema as closely as possible is a priority then you should use save(). In general, we recommend using save() over updateOne() and findOneAndUpdate() unless you need extra performance or more fine grained concurrency control.

how does it work with strict=throw? With strict: 'throw', updates will throw an error if you try to set a field that isn't in your schema.

from mongoose.

@vasyl97kharchenko that sounds like a potential bug, runValidators: true should prevent explicit $unset of required fields. Can you please provide a script that demonstrates the issue you're seeing?

from mongoose.

@vkarpov15 false alarm, did a double check, if runValidators: true -> it's not possible. Behaviour with $unset is only possible when validators are not running.

from mongoose.

why its disabled by default?
what does "Be careful: update validators are off by default because they have several caveats." really mean according to documentation?
so should i preferably use save instead update to ensure data i am trying to add in db matches schema for sure?
how does it work with strict=throw? i think without having that validation enabled by default strict mode might throw an error, right?

from mongoose.

@vkarpov15 is it still ok that because of this behavior I can even delete required fields using $unset operator during update (found out it today)?

from mongoose.