jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tako Schotanus" <quinte...@gmail.com>
Subject Re: Deleting the version history of a node
Date Mon, 05 Jan 2009 18:48:08 GMT
IMO this is because versioning is not seen as a method to go back to older
version for isolated files but as a way to get a "snapshot" of the state of
your entire workspace. If at some point you decide that you don't like the
changes that have been made to your repository and would like to go back to
the state it was in yesterday it would be very inconvenient if it would be
impossible to recuperate the deleted information that existed yesterday.

I understand the need to "physically" delete information, for example to
free up the space it uses, but it should be an exceptional operation instead
of the norm and has nothing to do with versioning.

On Mon, Jan 5, 2009 at 19:19, Diego Marin Santos <diegomrsantos@gmail.com>wrote:

> I've read on internet a jackrabbit user saying the following:
> "*AFAIK the version storage was not intended to be removed completely by **
> the JCR spec, since one idea of versioning is to be able to recover
> deleted nodes. That's why it's not entirely possible to delete all
> things inside the versioning storage (let's say this use case was not
> **considered*)."
> I don't agree because in my opinion versioning makes sense when we wanna
> modify a file and may wanna restore the previous file versions in the
> future.
> When we delete a file, we don't think of restoring previous file versions.
> Moreover, deleting a node(representing a file) we won't get a reference for
> your version history, then why should we keep the version history of this
> node?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message