couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Smith <...@iriscouch.com>
Subject Re: [jira] [Commented] (COUCHDB-1367) When settings revs_limit on db - the db increases its update_seq counter when viewing stats - but not when getting changes
Date Mon, 26 Dec 2011 13:49:15 GMT
Hi, Bob. Thanks for your feedback.

On Mon, Dec 26, 2011 at 12:24 PM, Robert Dionne
<dionne@dionne-associates.com> wrote:
> Jason,
>
>  After looking into this a bit I do not think it's a bug, at most poor documentation.
update_seq != last_seq

Nobody knows what update_seq means. Even a CouchDB committer got it wrong.

Fine. It is "poor documentation."

Adding last_seq into db_info is not helpful because last_seq also does
not mean what we think it means. My last email demonstrates that
last_seq is in fact incoherent.

What would be marvelous in the db_info is this:

    The sequence id of the most recent document update, or zero if
there has not been one.

If you add it, that would be great but you might first consider what
its relationship is to last_seq, why the values differ sometimes, and
whether that is good for users.

Thanks again!

-- 
Iris Couch

Mime
View raw message