CouchDB provider - consider adding option for preserving history in Batch calls?

[DRK3]

In the case of a batch call where some of the operations are redundant (like a put, and then a put that overrides the previous one), those redundant operations will be stripped out. This is necessary to allow the CouchDB batch call to work correctly. CouchDB will not have any revision history of these stripped out operations, however. We may want to consider adding an option to preserve revision history (at the expense of speed most likely)