On Sat, Mar 7, 2009 at 7:22 PM, Ben Hood <[email protected]> wrote: > 2. Implement some kind of version control as part of the document metadata;
CouchDB does not do document versioning. Because of it's append-only files, the storage model will allow access to snapshots of the database at each seq num. The file driver needs a little work to close the gap, but once the code is written, you'll be able to roll back to point in time snapshots of the database (as long as you don't compact, which means storage is unbounded.) This is really only useful for the Durability in ACID. It means that if the file is truncated, it still contains a valid state. > > Has anybody had any experience with this all? > The solution is to store each document version as a different CouchDB document. Jan is building an example wiki these days. Chris -- Chris Anderson http://jchris.mfdz.com
