You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Couchbase Mobile
Hi,
I check document about Rev Tree, but I am confused how rev tree find conflict.
The document told Node B edit the document and replica to Node C, the edit based on the previous edit on A. Then Node C merged the latest edit.
Why Node C thought the update is not a conflict? And document talk about how rev tree find conflict?
Thanks, Linbo
Jens Alfke
unread,
Aug 26, 2015, 12:40:02 PM8/26/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Couchbase Mobile
On Aug 25, 2015, at 9:20 PM, linbo liao <llb...@gmail.com> wrote:
The document told Node B edit the document and replica to Node C, the edit based on the previous edit on
A. Then Node C merged the latest edit.
That document isn’t about Couchbase Lite, or even CouchDB. It’s an old proposal for using revision trees in Couchbase
Server replication (XDCR) that was never implemented.
The Couchbase Lite documentation on conflicts is here.