Schmidt
Schmidt
I have checked again it in current nano v6.1.5 with the following code: ``` js var nano = require('nano')('http://localhost:5984') nano.db.replicate('asd', 'efg', { create_target: true }, function(error, response) { console.log(error, response)...
I have also issued a continuous replication: ``` js nano.db.replicate('asd', 'efg', { continuous: true }, function(error, response) { console.log(error, response) }) ``` with the response: ``` js { ok: true,...
I'm not sure that I fully understand the problem. Do you suggest to drop the `_replicate` endpoint in favor of the `_replicator` database?
But what does that have yo do with nano?
The revision does not necessarily have to be in the `If-Match` header. Just include the revision in the doc body, eg ``` js db.insert({ foo: bar, _rev: '1-asd' }, 'mydoc')...
Please reopen if needed.
Sorry, I maybe did not understand your use case. Could you explain it further please? However, I really like the change you propose, because its a minimal change which extends...
Although I recommend to use a different data model approach for 2 (see [Document Modeling to Avoid Conflicts](http://docs.ehealthafrica.org/couchdb-best-practices/#document-modeling-to-avoid-conflicts)) you can achieve what you want in current nano by just setting...
Hi @flynsequeira, yes, `key` is what you emit as key in your view function. You can emit everything you like as keys, I often use arrays. Normally you don't need...