You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Paul Joseph Davis (Created) (JIRA)" <ji...@apache.org> on 2012/02/03 13:37:55 UTC

[jira] [Created] (COUCHDB-1399) Rename _rev to _mvcc or _lock

Rename _rev to _mvcc or _lock
-----------------------------

                 Key: COUCHDB-1399
                 URL: https://issues.apache.org/jira/browse/COUCHDB-1399
             Project: CouchDB
          Issue Type: Improvement
          Components: Database Core
    Affects Versions: 2.0
            Reporter: Paul Joseph Davis
             Fix For: 2.0


We should rename the "revisions" to "lock" or "token" or some other suitably opaque term so we stop getting people asking questions about treating them as revisions.

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

        

[jira] [Commented] (COUCHDB-1399) Rename _rev to _mvcc or _lock

Posted by "Paul Joseph Davis (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/COUCHDB-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199717#comment-13199717 ] 

Paul Joseph Davis commented on COUCHDB-1399:
--------------------------------------------

@Alexander

Yes, all the other bits would need to be renamed to match the new name as well. I honestly don't care what it's renamed to as long as it doesn't have a revision connotation.

@Dirkjan

If by exceedingly limited you mean removes an entire class of misunderstanding in the community, then yes. :) But I do think this is something we should at least be considering. Also, I'm assuming that 2.0 will have other similarly large breaks in API so I don't see this as much of an issue since its mostly just a renaming of a concept (with no current plans at actually changing behavior).
                
> Rename _rev to _mvcc or _lock
> -----------------------------
>
>                 Key: COUCHDB-1399
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1399
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Database Core
>    Affects Versions: 2.0
>            Reporter: Paul Joseph Davis
>             Fix For: 2.0
>
>
> We should rename the "revisions" to "lock" or "token" or some other suitably opaque term so we stop getting people asking questions about treating them as revisions.

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

        

[jira] [Commented] (COUCHDB-1399) Rename _rev to _mvcc or _lock

Posted by "Alexander Shorin (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/COUCHDB-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199678#comment-13199678 ] 

Alexander Shorin commented on COUCHDB-1399:
-------------------------------------------

Would `_state` name be more convenient? May be I'm wrong, but I'd like to count `_rev` as document state id, because it's better describes functional of this field: last document state, conflict document states etc.
Also, there are `_revisions` and `_attachments/revpos` fields that should be noticed too as well as `db/_rev_count` resource and `rev`, `rev_info`, `open_revs` document resource parameters. Have I missed something?
                
> Rename _rev to _mvcc or _lock
> -----------------------------
>
>                 Key: COUCHDB-1399
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1399
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Database Core
>    Affects Versions: 2.0
>            Reporter: Paul Joseph Davis
>             Fix For: 2.0
>
>
> We should rename the "revisions" to "lock" or "token" or some other suitably opaque term so we stop getting people asking questions about treating them as revisions.

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

        

[jira] [Commented] (COUCHDB-1399) Rename _rev to _mvcc or _lock

Posted by "Dirkjan Ochtman (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/COUCHDB-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199705#comment-13199705 ] 

Dirkjan Ochtman commented on COUCHDB-1399:
------------------------------------------

This seems like exceedingly limited benefit for a big break in compatibility. I'd suggest the solution should be better docs, instead.
                
> Rename _rev to _mvcc or _lock
> -----------------------------
>
>                 Key: COUCHDB-1399
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1399
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Database Core
>    Affects Versions: 2.0
>            Reporter: Paul Joseph Davis
>             Fix For: 2.0
>
>
> We should rename the "revisions" to "lock" or "token" or some other suitably opaque term so we stop getting people asking questions about treating them as revisions.

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