Skip to content

Conflict Management: logic issue #563

Open
@MarSoft

Description

@MarSoft

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions