Hi, thanks for maintaining this great project ! While trying to update an old document with Fauxton recently I noticed a weird behavior:
Expected Behavior
Current Behavior
- The
_rev attribute is overwritten by the content of the rev field
- the
rev field does not appear in the document
Steps to Reproduce (for bugs)
- Create an empty document, and save it.
_rev becomes 1-xxx
- Open the doc in Fauxton, and update the document to add the field
"rev": "1-xxx"
- Save the doc, and open it again in the UI
=> the UI shows the document with the wrong _rev: {"_rev": "1-xxx"} instead of {"_rev": "2-xxx", "rev": "1-xxx"}
Context
- noticed while trying to update a document with Fauxton. The update kept failing with
document update conflict (which is logical as the _rev was wrongly overwritten)
Your Environment
- Version used: CouchDB 3.3.3
- Browser Name and version: Chromium 124
- Operating System and version (desktop or mobile): Fedora 39 on desktop / server is running Rockylinux 9
Hi, thanks for maintaining this great project ! While trying to update an old document with Fauxton recently I noticed a weird behavior:
Expected Behavior
_revattribute should left untouched when viewing a doc even if the doc contains arevfieldrevfield stays visible on the document if it is present (similar issue as Bug: Fauxton editor does not display all JSON keys of existing records. I.E. a key named "ok" is not loaded #1427 ?)Current Behavior
_revattribute is overwritten by the content of therevfieldrevfield does not appear in the documentSteps to Reproduce (for bugs)
_revbecomes1-xxx"rev": "1-xxx"=> the UI shows the document with the wrong
_rev:{"_rev": "1-xxx"}instead of{"_rev": "2-xxx", "rev": "1-xxx"}Context
document update conflict(which is logical as the_revwas wrongly overwritten)Your Environment