Home/ Questions/Q 5937815
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T15:35:44+00:00

As I understand it CouchDb never overwrites a record but instead creates a new

  • 0

As I understand it CouchDb never overwrites a record but instead creates a new document with a new _rev. What happens in this scenario?

  1. User A reads a document
  2. User B reads the same document
  3. User A updates the document
  4. User B updates the document

Aren’t User A’s changes lost in this scenario?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    No, instead User B will get a 409 error since the revs will no longer match. For User B to commit their document, they will need refetch the document so they can get the latest document revision.

    This is called Optimistic Locking, and is designed to specifically prevent the problem that you are seeing.

    There’s nothing stopping User B from stomping on User A’s document, but now they are more conscious of it by having to refetch the document and use the new _rev parameter.

    • 0