couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sven Helmberger (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-300) Update Sequence broken
Date Sat, 21 Mar 2009 13:07:50 GMT

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

Sven Helmberger commented on COUCHDB-300:
-----------------------------------------

I understand that. I just wanted to point out that my initial intent for using the _all_docs_by_seq
view is to know which documents have changed.
So I know for example what action to execute with a changed document. The fact that the document
is missing prevents me from knowing it has changed.
So in order for this idea to work I would need to touch the document for every update conflict
I catch in my app and hope no one screws up things by changing the database from the outside
of the app.
That doesn't sound good to me.

> Update Sequence broken
> ----------------------
>
>                 Key: COUCHDB-300
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-300
>             Project: CouchDB
>          Issue Type: Bug
>         Environment: ubuntu hardy
>            Reporter: Sven Helmberger
>             Fix For: 0.9
>
>         Attachments: all_docs_by_seq.js, update_seq_kaputt.js
>
>
> Database gets into a state where there is one document but an empty update sequence.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message