You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by Michael Harris <mi...@gmail.com> on 2008/07/29 17:22:18 UTC

versioning questions

Fellow users,

what would happen in the following the scenaria?  assume we start at v1.


do checkout, update, save, checkin
do checkout, update, save, checkin
do checkout
save
save
save
checkin

?

I would assume it would go

do checkout, update, save checkin
 -- goes to v2
do checkout, update, save checkin
-- goes to v3
do checkout
save
-- v3 has changed
save
-- v3 has changed
save
-- v3 has changed
checkin
go to v4.

The question is really around the save of node data without checkin.  In
this scenario, is v3 content overwritten by each save/update?  If so, can we
rollback to v3 *before* the checkout and saves?  (sort of like an undo
checkout in a version control system?)

thanx


-- 
---------------------
Michael Harris

Re: versioning questions

Posted by Michael Harris <mi...@gmail.com>.
very useful for a business workflow where users want the ability to "revert
to last checkpoint."

and we can give them "go back to any check point" when they realize they are
going to want that.  but im not telling them. ;)



On Tue, Jul 29, 2008 at 12:15 PM, Jukka Zitting <ju...@gmail.com>wrote:

> Hi,
>
> On Tue, Jul 29, 2008 at 6:12 PM, Michael Harris
> <mi...@gmail.com> wrote:
> > It took me a minute to remember that version information is not stored in
> > the workspace.  So there can be a "working copy" in the workspace that is
> > independent of the version copies. Users can update the working copy and
> > check in only when they are done with their updates.
>
> Exactly.
>
> BR,
>
> Jukka Zitting
>



-- 
---------------------
Michael Harris

Re: versioning questions

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Tue, Jul 29, 2008 at 6:12 PM, Michael Harris
<mi...@gmail.com> wrote:
> It took me a minute to remember that version information is not stored in
> the workspace.  So there can be a "working copy" in the workspace that is
> independent of the version copies. Users can update the working copy and
> check in only when they are done with their updates.

Exactly.

BR,

Jukka Zitting

Re: versioning questions

Posted by Michael Harris <mi...@gmail.com>.
Jukka

It took me a minute to remember that version information is not stored in
the workspace.  So there can be a "working copy" in the workspace that is
independent of the version copies. Users can update the working copy and
check in only when they are done with their updates.  this is nifty....

On Tue, Jul 29, 2008 at 12:04 PM, Jukka Zitting <ju...@gmail.com>wrote:

> Hi,
>
> On Tue, Jul 29, 2008 at 5:22 PM, Michael Harris
> <mi...@gmail.com> wrote:
> > The question is really around the save of node data without checkin.  In
> > this scenario, is v3 content overwritten by each save/update?
>
> No. A save() just persists the changes in the current workspace and
> doesn't modify the version history in any way.
>
> > If so, can we rollback to v3 *before* the checkout and saves?
>
> Yes.
>
> JCR versioning is a bit like a centralized version control system with
> the version storage acting as the central version server and each JCR
> workspace as a client system with local copies of the version
> controlled trees. Changes in the local copy (i.e. saves in the JCR
> workspace) only affect the central version history after an explicit
> checkin operation. Similarly, you only see updates from other clients
> (workspaces) when explicitly updating.
>
> BR,
>
> Jukka Zitting
>



-- 
---------------------
Michael Harris

Re: versioning questions

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Tue, Jul 29, 2008 at 5:22 PM, Michael Harris
<mi...@gmail.com> wrote:
> The question is really around the save of node data without checkin.  In
> this scenario, is v3 content overwritten by each save/update?

No. A save() just persists the changes in the current workspace and
doesn't modify the version history in any way.

> If so, can we rollback to v3 *before* the checkout and saves?

Yes.

JCR versioning is a bit like a centralized version control system with
the version storage acting as the central version server and each JCR
workspace as a client system with local copies of the version
controlled trees. Changes in the local copy (i.e. saves in the JCR
workspace) only affect the central version history after an explicit
checkin operation. Similarly, you only see updates from other clients
(workspaces) when explicitly updating.

BR,

Jukka Zitting