couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Leeds (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1485) COPY behavior changed between 1.1.1 to 1.2
Date Wed, 07 Nov 2012 22:42:12 GMT


Randall Leeds commented on COUCHDB-1485:

This change actually happened with the introduction of ejson.

The COPY handler doesn't open the doc with the ejson_body option and the revision calculation
includes the body. The disk binary is used in the rev id on the COPY destination, but the
ejson body is used when the doc is first created.

A related behavior was noticed and brought up by Kxepal. When PUT'ing attachments to a document,
the document is opened without ejson_body and so the revision id is calculated from the binary
body if the old document while the original revision would have been calculated from the ejson
parsed from the request body on doc updates.

In both cases, parsing the document body an unnecessary operation. I will ilkely call both
of these "won't fix" if I don't hear anything for a few days, but I'll give others a chance
to weigh in.
> COPY behavior changed between 1.1.1 to 1.2
> ------------------------------------------
>                 Key: COUCHDB-1485
>                 URL:
>             Project: CouchDB
>          Issue Type: Question
>          Components: HTTP Interface
>    Affects Versions: 1.2
>         Environment: Mac OS X 10.7.4
>            Reporter: Michael Phan-Ba
>            Assignee: Randall Leeds
>              Labels: api-change, document
> I believe commit 7e3c69ba951de7cfaa095145ba49c58d539a28ea (CouchDB 1.2) changed the behavior
of HTTP COPY to update the revision to reflect the new document ID.
> Is there a way to make COPY update the rev property on the client side for previous versions
of CouchDB?
> See commit c5209edceef1635c4ef0d23119f8327b5f3403de "fix tests for couchdb 1.1.1" at:

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