Hi Klaus, I am not sure about the conflict in this situation because if you try to the replication between two databases on one couchdb server there is no conflict and the document is deleted correctly.
Cheers Nikolai On 12.09.2010, at 20:13, Klaus Trainer wrote: > Hi Nikolai, > > what you're describing sounds like you've produced a conflict through > replication. Please correct me if I'm wrong. > > When there are several conflicting versions, you can only delete one > version at a time, and the remaining versions will be left untouched > (for good reason). > > - Klaus > > > On Sun, 2010-09-12 at 13:52 -0400, Nikolai Teofilov (JIRA) wrote: >> Delete document with attachment fails after replication. >> -------------------------------------------------------- >> >> Key: COUCHDB-885 >> URL: https://issues.apache.org/jira/browse/COUCHDB-885 >> Project: CouchDB >> Issue Type: Bug >> Components: Replication >> Affects Versions: 1.0.1 >> Environment: Mac OSX, Windows XP, Windows 7 >> Reporter: Nikolai Teofilov >> >> >> Step to reproduce the bug: >> >> 1. Make database "test" on a remote couchdb server that reside on a >> different machine! >> 2. Create new document: "http://remote-server:5984/test/doc"; >> 3. Create database "test" on the local couchdb server. >> 4. Trigger pull replication http://remote-server:5984/test -> >> http://localhost:5984/test >> 5. Attach a file to the replicated document on the local couchdb server. >> 6. Trigger push replication http://localhost:5984/test -> >> http://remote-server:5984/test >> 7. Delete the replicated document that contain now the attachment on remote >> database. >> >> This will delete last revision of the document after the replication >> but the previous revision of the document before the replication still exist >> in the database. >> >> This defect appears only between replication between databases on two >> different couchdb servers, and it only for documents that has been updated >> with a new attachment. >> > >
