I'd argue that this isn't part of the couch api as much as just a symptom of how couch is set up, we shouldn't feel bound to that.

That being said if we want to comunicate with the user, remember that the db is an event emitter so we can emit an event,

I'd argue replacing all the `logError(error);` calls with `db.emit('error', err);` but if we wanted to swallow the errors we could do `db.emit('maperror', err)`.

Bear in mind that this could happen outside of development if the data triggered the error.