That's very odd. What version of CouchDB are you using? Can you show the output of 'curl http://admin:[email protected]:5984/users_b4628a3a1630f179a354486750be9d95e6bc04a5/cae60d40a185675228fe99c34703ae37?conflicts=true'?
B. On 14 December 2011 18:10, Jay Zamboni <[email protected]> wrote: > Below is the output of a GET followed by a DELETE and another GET to verify > nothing has changed. > > $curl -X GET > http://admin:[email protected]:5984/users_b4628a3a1630f179a354486750be9d95e6bc04a5/cae60d40a185675228fe99c34703ae37 > > {"_id":"cae60d40a185675228fe99c34703ae37","_rev":"198-dd54167dd860a8883ffd50f33bb87247","name":"Initial > Test Form","description":"Need to collect a > description","type":"template","tabMapping":"75e0298d5b491fd5aafa89aa5700b9d9","messageFolderList":[],"error":"not_found","reason":"missing","_attachments":{"form.svg":{"content_type":"image/svg+xml","revpos":1,"length":15622,"stub":true},"form_overlay.svg":{"content_type":"image/svg+xml","revpos":1,"length":6803,"stub":true}}} > > $ curl -X DELETE > http://admin:[email protected]:5984/users_b4628a3a1630f179a354486750be9d95e6bc04a5/cae60d40a185675228fe99c34703ae37?rev=198-dd54167dd860a8883ffd50f33bb87247 > > {"error":"conflict","reason":"Document update conflict."} > > > $ curl -X GET > http://admin:[email protected]:5984/users_b4628a3a1630f179a354486750be9d95e6bc04a5/cae60d40a185675228fe99c34703ae37 > > {"_id":"cae60d40a185675228fe99c34703ae37","_rev":"198-dd54167dd860a8883ffd50f33bb87247","name":"Initial > Test Form","description":"Need to collect a > description","type":"template","tabMapping":"75e0298d5b491fd5aafa89aa5700b9d9","messageFolderList":[],"error":"not_found","reason":"missing","_attachments":{"form.svg":{"content_type":"image/svg+xml","revpos":1,"length":15622,"stub":true},"form_overlay.svg":{"content_type":"image/svg+xml","revpos":1,"length":6803,"stub":true}}} > > > On Wed, Dec 14, 2011 at 10:22 AM, Robert Newson <[email protected]> wrote: > >> If you can show a deletion attempt using curl, that would help. >> >> On 14 December 2011 17:21, Robert Newson <[email protected]> wrote: >> > Did you pass the current _rev when trying to delete? >> > >> > On 14 December 2011 17:06, Jay Zamboni <[email protected]> wrote: >> >> While implementing conflict resolution in our application it appears I >> >> created a bad document. A bug in my code seems to have written the >> >> _conflicts data from an old rev that had a conflict into the head >> document. >> >> When viewing the document from the database listing screen in futon I >> see >> >> the document and its _conflicts field. >> >> >> >> Now that I have this condition, I can't seem to get rid of the document >> >> using either the REST API or futon. When trying to delete the document >> I >> >> get an error "Document update conflict". >> >> >> >> Another odd thing is that using Futon I can see the document on the >> listing >> >> page with one rev, but when I edit the document I see an earlier rev. >> If I >> >> delete it in Futon I get the same conflict error. If I use javascript >> to >> >> delete either of the revs I get the same error. I tried updating the >> >> document with _conflicts set to null, but that did not work either. >> >> >> >> I am in the testing phase, so I assume I can just delete the database >> and >> >> everything will be fine. However, if something like this ever happens >> >> after we go to production I would like to be able to resolve the issue. >> >> >> >> Does anyone have any ideas? I am using couchdb 1.0.2. >> >> >> >> Thanks >> >> >> >> Jay >>
