I'm think mark wants to know what has changed with the last update, rather than to keep every version around forever.
On Fri, Apr 20, 2012 at 10:10 AM, Robert Newson <[email protected]> wrote: > You can fetch previous revisions with ?rev=<rev> until compaction > sweeps them away, but it's considered bad practice (your administrator > should be free to compact whenever needed). > > I don't think it's CouchDB's job to keep all the old versions of > documents forever, this should be solved at the application layer, it > doesn't seem particularly difficult either. If you care about the > changes a doc goes through, you should record them in the doc itself. > Whenever you update a document, add a new entry to a "history" array, > for example. We have this for replication checkpoints already. > > B. > > On 19 April 2012 22:33, Mark Hahn <[email protected]> wrote: > > Thanks, I had forgotten about open_revs. But open_revs only applies to > > conflicts, right? > > > > How do I find out what changed in a change feed? In other words, if I > get > > a change feed is there a way to access the previous version to find out > > what changed? >
