4 ms·
Yeah. The idea that I couldn't roll back a transaction if there was a problem, or that part of my data might get through while others didn't is a terrifying on
by AndrewDucker 15y ago
Yeah. The idea that I couldn't roll back a transaction if there was a problem, or that part of my data might get through while others didn't is a terrifying one. My customers _care_ about their data being accurate.
And similarly - most of the data I work with is naturally relational. Having the database make checks to ensure that invalid things aren't happening is a lifesaver against coders making a stupid mistake (and everyone makes one from time to time).
- dolinsky 15y agoWhile I'd never suggest Mongo if you need transactional support on par with OLTP, Mongo does have single document transactional support through the use of getLastError and its various options. http://www.mongodb.org/display/DOCS/getLastError+Command http://www.mongodb.org/display/DOCS/getLastError+Command
- trustfundbaby 15y agoHaving the database make checks to ensure that invalid things aren't happening is a lifesaver against coders making a stupid mistake ------------------------------ mongo now has a 'safe mode' option that protects against this, just FYI