You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 14, 2020. It is now read-only.
When replication process has been run, the conflicting revisions are present on all nodes, however even though the same winning revision is chosen, it is up to the clients to resolve the conflicts and delete the conflicting revisions once merged.
This can be done in several ways, among which:
periodic cleaning task
on first document retrieval
...
Similarly to the automatic conflict resolution mechanism, it should be possible to get a Database instance which implements the conflict resolution on first retrieval. Moreover, giving access to a resolveConflicts method in Database can make it possible to implement any other cleaning strategy such as the periodic task.
Resolve on fetch
Add an argument to method CouchDB.database so that signature becomes
When replication process has been run, the conflicting revisions are present on all nodes, however even though the same winning revision is chosen, it is up to the clients to resolve the conflicts and delete the conflicting revisions once merged.
This can be done in several ways, among which:
Similarly to the automatic conflict resolution mechanism, it should be possible to get a
Database
instance which implements the conflict resolution on first retrieval. Moreover, giving access to aresolveConflicts
method inDatabase
can make it possible to implement any other cleaning strategy such as the periodic task.Resolve on fetch
Add an argument to method
CouchDB.database
so that signature becomesThe resolution strategy used is the same as for local conflict resolution.
Question: is the order of conflicting revision deterministic?
Explicit resolution
Add a method to
Database
Returning for each conflicting document, the resolution status.
The text was updated successfully, but these errors were encountered: