In CouchDB 2.0, why is last_seq on change () different from update_seq on info ()?

Question

In CouchDB 2.0, why is last_seq on change () different from update_seq on info ()?

In CouchDB 2.0 I noticed that the database property "update_seq" has the same number but different text than the feed property "last_seq". Why is this?

+3

couchdb couchdb-2.0

joeforker Mar 31 17 at 21:06

source to share

No one has answered this question yet

Check out similar questions:

243

Difference between CouchDB and Couchbase

five

In CouchDB's answer _changes, why are arrays of items "changing"?

3

CakeDB Last Seq Change Feed

2

CouchDB change shift

1

Couchdb 2.0 extremely slow external PUT, fast local

0

Listening for changes from multiple couchdb databases using a single node process

0

Sequence error in CouchDB 2, or is there some other way to compare sequence numbers?

0

Do individual databases have UUIDs in CouchDB 2?

0

CouchDB seq number changes when adding include_docs = true

0

CouchDb 2.0: update_seq is not a number

In CouchDB 2.0, why is last_seq on change () different from update_seq on info ()?

More articles: