couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Leeds (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1485) COPY behavior changed between 1.1.1 to 1.2
Date Mon, 29 Oct 2012 19:52:12 GMT

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

Randall Leeds commented on COUCHDB-1485:
----------------------------------------

7e3c69ba951de7cfaa095145ba49c58d539a28ea does not seem to be responsible for this change but
I can verify that the revision hash does not change with the COPY command on 1.1.1.

I'm currently searching through the 1.2.x branch trying to determine where this change was
introduced.

Whatever the case, it's always been that COPY returns the new revision in the response. I
don't know if it was every guaranteed that the revision id would stay the same after a COPY.
                
> COPY behavior changed between 1.1.1 to 1.2
> ------------------------------------------
>
>                 Key: COUCHDB-1485
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1485
>             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:
> https://github.com/mikepb/clerk/commit/c5209edceef1635c4ef0d23119f8327b5f3403de

--
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: http://www.atlassian.com/software/jira

Mime
View raw message