4 ms·
> which failed silently, rendering all of the data worthless. I am not in any way related to mongodb, nor do I really like it. That being said, I can't image
by dmichulke 8y ago
> which failed silently, rendering all of the data worthless.
I am not in any way related to mongodb, nor do I really like it.
That being said, I can't image they failed silently. Much more likely that some return code from an insert was ignored in the application.
Otherwise that would be just the mother of all errors of DB development.
However, I do recall many questionable things like:
- Some sort of fast but in the worst-case inconsistent default config
- In order to execute the command to free space (which you had to do regularly) you'd need to have lots of free space
Both issues are probably 5 years old, so I also don't remember any details. Migrated to postgres a year later or so.
- petepete 8y agoThat contract took place in 2011. As I recall the Perl MongoDB driver had a setting called WriteConcernResult that used to default to false. That meant that it operated in 'fire and forget' mode and assumed that everything worked. It was one of the main reasons it was so fast! I think over the years the defaults have improved and favour safety over speed.