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

Conflict Management: logic issue #563

Open

MarSoft opened this issue Oct 8, 2018 · 0 comments

MarSoft commented Oct 8, 2018 •

edited

Loading

Let’s say we want to keep the highest value.
In the text, it is state told to first commit update and then delete old revision:

This means we don’t agree with CouchDB’s automatic choice. To do this, we first overwrite the target document with our value and then simply delete the revision we don’t like

But the following code does something different. At least it first issues DELETE statement and only then PUT.

Page url: http://guide.couchdb.org/draft/conflicts.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment