modifying a versionable node

[Paco Avila <pa...@git.es>]

I've set several nodes in my repository using mix:versionable. It is
possible to modify a node property without doing the chekout / checkin
process or this process is mandatory? 

-- 
Paco Avila <pa...@git.es>

Re: modifying a versionable node

[Paco Avila <pa...@git.es>]

El jue, 08-06-2006 a las 10:51 +0200, Tobias Bocanegra escribió:
> > > the checkin/checkout process is the principal mechanism in versioning.
> > > for example, you can't modify a file directly on a SVN server, you
> > > need to do a checkout first.
> >
> > If the user A performs a checkout(), the user B can modify this node? If
> > this is true, the user B can do a checkin before the user commits its
> > changes.
> 
> versioning is not the same as locking. when a 'user' (i.e. the
> session) does a checkout, the node is not locked, or owned by that
> user. when the node is checkedin, it's content gets copied into the
> version store and it becomes read-only. if you need locking, use
> Node.lock().
> 
> maybe the chapters 8.2 (versioning) and 8.4 (locking) of the jsr170
> specification could also help you.

Yes, I'm reading this chapters but I didn't understant well the
repository behaviour with the previous two user case.

Thanks again.
-- 
Paco Avila <pa...@git.es>

Re: modifying a versionable node

[Tobias Bocanegra <to...@day.com>]

> > the checkin/checkout process is the principal mechanism in versioning.
> > for example, you can't modify a file directly on a SVN server, you
> > need to do a checkout first.
>
> If the user A performs a checkout(), the user B can modify this node? If
> this is true, the user B can do a checkin before the user commits its
> changes.

versioning is not the same as locking. when a 'user' (i.e. the
session) does a checkout, the node is not locked, or owned by that
user. when the node is checkedin, it's content gets copied into the
version store and it becomes read-only. if you need locking, use
Node.lock().

maybe the chapters 8.2 (versioning) and 8.4 (locking) of the jsr170
specification could also help you.


-- 
-----------------------------------------< tobias.bocanegra@day.com >---
Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel
T +41 61 226 98 98, F +41 61 226 98 97
-----------------------------------------------< http://www.day.com >---

Re: modifying a versionable node

[Paco Avila <pa...@git.es>]

El jue, 08-06-2006 a las 10:23 +0200, Tobias Bocanegra escribió:
> hi paco,
> once, the node is checked-in, it's read-only. if you need to modify
> it, you need to do a checkout before. but, if you don't need to
> checkin the node, if you don't want to.

Ok.

> the checkin/checkout process is the principal mechanism in versioning.
> for example, you can't modify a file directly on a SVN server, you
> need to do a checkout first.

If the user A performs a checkout(), the user B can modify this node? If
this is true, the user B can do a checkin before the user commits its
changes.
-- 
Paco Avila <pa...@git.es>

Re: modifying a versionable node

[Tobias Bocanegra <to...@day.com>]

hi paco,
once, the node is checked-in, it's read-only. if you need to modify
it, you need to do a checkout before. but, if you don't need to
checkin the node, if you don't want to.

the checkin/checkout process is the principal mechanism in versioning.
for example, you can't modify a file directly on a SVN server, you
need to do a checkout first.

regards, toby

On 6/8/06, Paco Avila <pa...@git.es> wrote:
> I've set several nodes in my repository using mix:versionable. It is
> possible to modify a node property without doing the chekout / checkin
> process or this process is mandatory?
>
> --
> Paco Avila <pa...@git.es>
>
>


-- 
-----------------------------------------< tobias.bocanegra@day.com >---
Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel
T +41 61 226 98 98, F +41 61 226 98 97
-----------------------------------------------< http://www.day.com >---