idottv/node-mongodb-wrapper — Issue #4: Reconsider omitting safe from update operations
Author: sbrekken
Created: 2011-11-11 09:00:24+00:00
State: open

Currently without `safe: true` there is no way of knowing if an update request modified any documents, as [stated in the docs](http://www.mongodb.org/display/DOCS/Updating#Updating-CheckingtheOutcomeofanUpdateRequest):

> If the result of the getlasterror command contains an updatedExisting field, the last message on the connection was an update request. If the updatedExisting field's value is true, that update request caused an existing object to be updated; if updatedExisting is false, no existing object was updated. An "upserted" field will contain the new _id value if an insert is performed (new as of 1.5.4).

It would be nice to be able to specify safe for all operations, some might be more critical than others.