couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henrik Hofmeister (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1367) update_seq does not always reflect the seq of the latest document update
Date Fri, 30 Dec 2011 23:14:30 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177817#comment-13177817
] 

Henrik Hofmeister commented on COUCHDB-1367:
--------------------------------------------

@Robert - C-L aside - its still strange that its just some 'random' number of actions taken
which is not really usable to the end user. That C-L could use a different implementation
is besides the point imo - Its still is usable to get the current latest update seq - for
whatever reason - if even to just show a progress bar in a to-be-developed feature in some
gui application or whatever.

We use it internally to track progress of an aggragation application.

@Randall: in terms of adding a field or whatever - my only input is - less is more - update_seq
makes perfect sense naming wise, it should just be the expected value. If you'll need to track
other changes than doc changes later on in terms of replication or whatever - my uneducated
guess is you're gonna need to do alot more than just have a number increase in any case. But
thats just me :) http://c2.com/xp/YouArentGonnaNeedIt.html

Thanks
                
> update_seq does not always reflect the seq of the latest document update
> ------------------------------------------------------------------------
>
>                 Key: COUCHDB-1367
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1367
>             Project: CouchDB
>          Issue Type: Bug
>          Components: HTTP Interface
>    Affects Versions: 1.1.1
>         Environment: Any
>            Reporter: Henrik Hofmeister
>            Priority: Minor
>              Labels: revs_limit
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message