Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Describe what happens when you delete a document that has live conflicts #48

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Describe what happens when you delete a document that has live conflicts #48

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions documents/deleting-a-document.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,3 +141,11 @@ See an example response after a successful deletion request.
}
```
{: codeblock}

After a document has been deleted, you might find that it is still there but has a different [revision](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-document-versioning-and-mvcc#revisions).
That happens when you delete a document that has live [conflicts](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-conflicts).

When a document has live conflicts, that means it has more than one live revision.
When a document has more than one live revision one of the live revisions is the winning revision.
When the winning revision of a document with live conflicts is deleted, another of the live revisions becomes the winning revision.
When the new winning revision is deleted, if there are any more live revisions of the document one of the remaining live revisions becomes the new winning revision. And so on until all the live revisions of the document have been deleted.