incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Søren Hilmer ...@widetrail.dk>
Subject Re: Relying on revisions for rollbacks
Date Tue, 18 Mar 2008 08:29:23 GMT
Hi all,

Why not use systems for what they where designed to do?

A solution could be to integrate couchdb with a prober version control
system (darcs, git, svn, ...) and keep a history listing attached to the
document.

I thought that couchdb could send messages to a registered Erlang process
for handling the versioning, when the document was
created/updated/deleted. It would then be possible to write different
callback handlers for the different version control backends.

The tricky part as I see it, is how to retrieve the revisions from the
version control. The attached history could come in handy here I guess.

Does this make sense?

--Søren

-- 
Søren Hilmer, M.Sc., M.Crypt.
wideTrail            Phone: +45 25481225
Pilevænget 41        Email: sh@widetrail.dk
DK-8961  Allingåbro  Web: www.widetrail.dk

On Mon, March 17, 2008 12:29, Shahar Evron wrote:
> Hi all,
>
> There's a thing not entirely clear to me from the docs I've read:
>
> If I want to create, let's say, a Wiki that keeps old reversions of a
> document and allows rollback and comparison between revisions - can I
> rely on CouchDB's internal revisioning, or should I implement this
> myself?
>
> As far as I understood, CouchDB does not keep old revisions indefinitely
> - so if I update a document, it's previous revisions might be deleted
> after a while.
>
> Is this true?
>
> Thanks,
>
> Shahar.
>
>
>
> --
> Best Regards,
>
> Shahar Evron  <shahar.e@zend.com>
>
> Senior PHP Specialist         Product Group
> Zend Technologies
>



Mime
View raw message