3 ms·
Most of the vitrol stems from the fact that MongoDB's default settings were unsafe for a very long time and people were burned by it. Imo anyway.
by opendais 13y ago
Most of the vitrol stems from the fact that MongoDB's default settings were unsafe for a very long time and people were burned by it. Imo anyway.
- threeseed 13y agoWhich is nonsense since every driver since the beginning set the default to be safe. Most of the vitriol comes from people who never even used it.
- opendais 13y agohttps://blog.rainforestqa.com/2012-11-05-mongodb-gotchas-and-how-to-avoid-them/ https://blog.rainforestqa.com/2012-11-05-mongodb-gotchas-and... "MongoDB allows very fast writes and updates by default. The tradeoff is that you are not explicitly notified of failures. By default most drivers do asynchronous, 'unsafe' writes - this means that the driver does not return an error directly, similar to INSERT DELAYED with MySQL. If you want to know if something succeeded, you have to manually check for errors using getLastError." We have very, very different definitions of safe defaults. Especially when this fact was poorly documented early on and caused people to be surprised by it. You may wish to consider that other people have different perspectives of what 'safe' means. Safe, to me, means: 1) Fsyncs to journal every write. 2) Returns an error immediately if an error occurred.
- dev360 13y agoThe python drivers never made it safe by default.