The wiki does mention it (though I'll point out politely that the couchbase docs, while lovely, are not official atm).
The rev values should be treated opaquely, we don't promise not to change the format. The contents of the conflicts is what you are supposed to use to resolve them, just as you do in source code (you don't use the revision id directly in SVN, right?). B. On 13 July 2011 00:11, Jens Alfke <[email protected]> wrote: > > On Jul 12, 2011, at 2:54 PM, Paul Davis wrote: > > In this particular case, I'm not sure if we even document that the > revs=true option exists, as I can't think of where it would be used > outside the replicator so even the format of this response might be > subject to change. > > No, it’s well documented both in the CouchDB wiki and in Couchbase’s API docs: > > http://wiki.apache.org/couchdb/HTTP_Document_API#GET > http://www.couchbase.org/sites/default/files/uploads/all/documentation/couchbase-api-dbdoc.html#couchbase-api-dbdoc_db-doc_get-revs > > So is the ‘extended revision history’, ?revs_info=true. > > Not sure why the revision history would be viewed as internal, as it’s pretty > important for conflict resolution. > > —Jens >
