Hi,
Once you make a new _rev and then compact the previous ones go away.
The standard thing to do is either include the history in the document
(good if the docs are small and the histories short) or make a new
document for each version you want and provide your own versioning and
use a view to pull out the history.
Cheers
Simon
On 17 Apr 2010, at 14:42, erich oliphant wrote:
Ok, so the 'versioning' in couch is really just for conflict
resoultion,
etc? Once a new _rev is successfully committed the previous goes
away ?
On Fri, Apr 16, 2010 at 7:29 AM, Matt Goodall
<[email protected]>wrote:
On 16 April 2010 11:53, Sebastian Cohnen <[email protected]
>
wrote:
see http://wiki.apache.org/couchdb/HTTP_database_API#Changes - I
think
you are looking for the since parameter
The since parameter will not help, _changes only ever sends the last
rev of a document.
Erich, it sounds like you're trying to track multiple versions of a
document. If that's correct then don't rely on revs. Multiple
versions
is something you need to handle yourself.
- Matt
On 16.04.2010, at 12:46, erich oliphant wrote:
Hi,
I am using the _changes API and noticed that it only seems to
keep track
of
the latest revisions of a document. E.g. if I have change number
1,
_id=1,_rev=1, then update document _id=1 to _rev=2, hitting the
_changes
URL
only shows the _rev=2 and removes the first change id. Is there
a way
to
see *all* changes ?
--
Erich Oliphant
"There are, in fact, two things, science and opinion, the former
begets
knowledge, the latter ignorance"
-- Hippocrates of Cos
--
Erich Oliphant
"There are, in fact, two things, science and opinion, the former
begets
knowledge, the latter ignorance"
-- Hippocrates of Cos
