[COUCHDB-1367] update_seq does not always reflect the seq of the latest document update

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 1.1.1
• Component/s: HTTP Interface
• Labels: revs_limit

Environment

Any

• Assignee: Unassigned
• Reporter: Henrik Hofmeister
• Created: 18/Dec/11 21:25
• Updated: 02/Sep/18 06:36
• Resolved: 02/Sep/18 06:36

Description

Certain operations, (currently _revs_limit and _security changes) cause the database header's update_seq to increase when the by_seq index (and therefore _changes) has not changed, which is confusing in light of the naming consistency.