couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Lisman (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1518) HTTP COPY with attachments can leave the "revpos" of attachments higher than the "_rev" of the document
Date Mon, 17 Sep 2012 23:43:08 GMT


Aaron Lisman commented on COUCHDB-1518:

TouchDB seems to care about this:
> HTTP COPY with attachments can leave the "revpos" of attachments higher than the "_rev"
of the document
> -------------------------------------------------------------------------------------------------------
>                 Key: COUCHDB-1518
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core
>    Affects Versions: 1.1.1, 1.2
>         Environment: Debian Linux 6.0.5 / CouchDB 1.1.1 / Erlang R14B03
> Ubuntu Linux 12.04 / CouchDB 1.2.0 / Erlang R15B01
>            Reporter: Colin Coghill
>            Assignee: Robert Newson
> When COPYing a document with attachments, the _rev of the new document is set to 1-something,
but the revpos on the attachments is left as is, meaning they're generally higher than the
_rev of the new document.
> I believe this is incorrect, and will cause problems later when updating/replicating
the document. (I believe I'm seeing specific problems and am working on a test case, but am
not sure they're particularly necessary if this behaviour is incorrect)
> It's quite possible I've misunderstood how attachment revpos works and that this behaviour
is ok.
> Specific naming IDs, attachments, etc, don't seem to matter, substitute your own.
> Untested on earlier versions of CouchDB.
> curl -X PUT -d '{"name": "cat pictures"}' 
> curl -X GET
> #  Note down REV and put it in the attachment upload:
> curl -X PUT --data-binary @cat1.jpg
-H 'Content-Type: image/jpeg'
> # Copy the document
> curl -X COPY -H "Destination: document2"
> curl -X GET
> # Note: revision is 1-something
> # revpos on attachment is 2-something

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message