On 8 May 2009, at 13:52, Jaap van der Plas wrote:
> for that reason (that the revision before deletion may be gone) it
> would be helpful to have access to _revs_info, as it specifies which
> revisions are still available.
No, _rev ids are kept around forever*. Only the content gets removed
on compaction. Everything that is not the latest version of a document
must be considered "gone" by the application.
* up to the revision stemming threshold.
Cheers
Jan
--
>
> Jaap
>
> On Fri, May 8, 2009 at 11:31, Nicholas Orr <nicholas.orr@zxgen.net>
> wrote:
>> Keep in mind that _rev != git like revisions. _rev is for the
>> replication
>> and conflict resolution.
>> Read more here: http://wiki.apache.org/couchdb/Document_revisions
>>
>> <http://wiki.apache.org/couchdb/Document_revisions>As for your
>> exact issue I
>> don't know anything about that. I was pointed in the direction ^
>> above and
>> thought I'd pass that along as maybe you might not know about it
>> yet either
>> :)
>>
>> Nick
>>
>> On Fri, May 8, 2009 at 7:20 PM, Jaap van der Plas
>> <jaap@brightin.nl> wrote:
>>
>>> Greetings,
>>>
>>> I am working on code to retrieve a deleted document from a database,
>>> and have got as far as to retrieve the revision in which a document
>>> gets deleted. If I pass "revs=true" I do get an array with revision
>>> numbers (not complete ones though for some reason, they lack the
>>> 'human-readable' revision number prefix.) However, "rev_info=true"
>>> does not seem to have any effect here. Working as intended? (I am
>>> using the 0.9.0 stable release btw.)
>>>
>>> Jaap
>>>
>>
>
|