You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Michael Phan-Ba (JIRA)" <ji...@apache.org> on 2012/05/27 18:06:22 UTC

[jira] [Updated] (COUCHDB-1485) COPY behavior changed between 1.1.1 to 1.2

     [ https://issues.apache.org/jira/browse/COUCHDB-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Phan-Ba updated COUCHDB-1485:
-------------------------------------

    Description: 
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

  was:
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?

    
> 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
>              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

--
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