For your use case you might look at these versioning techniques: http://blog.couch.io/post/632718824/simple-document-versioning-with-couchdb
On Aug 7, 2010, at 9:55 AM, Mikeal Rogers wrote: > the changes feed only shows the update sequences for the current documents > in the database. it doesn't show sequences for old revisions of documents > because they will go away after compaction anyway. > > every time a document is updated it removes it's previous sequence from the > by-sequence index and the revision information is only available by querying > for it on the document itself (until you compact). > > -Mikeal > > On Sat, Aug 7, 2010 at 7:56 AM, Cliff Williams <[email protected]> wrote: > >> All, >> >> Good afternoon. >> >> using this url >> http://10.0.0.10:5984/test/_changes?since=14966&all_docs=true >> >> I get the following results >> >> {"results":[ >> >> {"seq":14971,"id":"ab53d85b92247bcbf251ef9abed4d998","changes":[{"rev":"2-b9cfa00cc907767d6bfdeca7dee5008f"}]}, >> >> {"seq":14973,"id":"ab53d85b92247bcbf251ef9abed4d512","changes":[{"rev":"3-ec350b40276b7c16c09ef485dd8f14aa"}]}, >> >> {"seq":14981,"id":"ab53d85b92247bcbf251ef9abed4a63a","changes":[{"rev":"2-fe0cb06e7046e9d41d326b3e8c30ed0c"}]}, >> >> {"seq":14982,"id":"_design/test","changes":[{"rev":"8-5a565b32bca9b42479543441f23a2e61"}]}, >> >> {"seq":14983,"id":"ab53d85b92247bcbf251ef9abed4b4d8","changes":[{"rev":"2-ed899403c21b6cca22f7e68f05d92b0c"}]}, >> >> {"seq":14984,"id":"ab53d85b92247bcbf251ef9abed47f2f","changes":[{"rev":"2-30d5cf6764f2e6c1795d65f272817238"}]}, >> >> {"seq":15006,"id":"ab53d85b92247bcbf251ef9abed4e544","changes":[{"rev":"10-e6856aac928ff1e2e019b556de8f1760"}]}, >> >> {"seq":15007,"id":"ab53d85b92247bcbf251ef9abed49e50","changes":[{"rev":"19-d7629eac5a5bd2133a19178fdc9277e6"}]} >> ], >> "last_seq":15007} >> >> now if I make an amendment to the document at sequence number 15006 and >> using the same URL I get the following results. >> >> {"results":[ >> >> {"seq":14971,"id":"ab53d85b92247bcbf251ef9abed4d998","changes":[{"rev":"2-b9cfa00cc907767d6bfdeca7dee5008f"}]}, >> >> {"seq":14973,"id":"ab53d85b92247bcbf251ef9abed4d512","changes":[{"rev":"3-ec350b40276b7c16c09ef485dd8f14aa"}]}, >> >> {"seq":14981,"id":"ab53d85b92247bcbf251ef9abed4a63a","changes":[{"rev":"2-fe0cb06e7046e9d41d326b3e8c30ed0c"}]}, >> >> {"seq":14982,"id":"_design/test","changes":[{"rev":"8-5a565b32bca9b42479543441f23a2e61"}]}, >> >> {"seq":14983,"id":"ab53d85b92247bcbf251ef9abed4b4d8","changes":[{"rev":"2-ed899403c21b6cca22f7e68f05d92b0c"}]}, >> >> {"seq":14984,"id":"ab53d85b92247bcbf251ef9abed47f2f","changes":[{"rev":"2-30d5cf6764f2e6c1795d65f272817238"}]}, >> >> {"seq":15007,"id":"ab53d85b92247bcbf251ef9abed49e50","changes":[{"rev":"19-d7629eac5a5bd2133a19178fdc9277e6"}]}, >> >> {"seq":15008,"id":"ab53d85b92247bcbf251ef9abed4e544","changes":[{"rev":"11-e01ef09eef56397e345f598fd2069f22"}]} >> ], >> "last_seq":15008} >> >> >> I think that it is fairly straight forward to ascertain that we are looking >> at latest revision sequences. >> >> Is there a way to see all sequence numbers?? I am of course aware of the >> continuous feed but do not wish to use it. >> My use case is for a pharma regulated clinical trials database where i need >> a total audit of every single change made to the database. >> >> best regards >> >> Cliff >>
