Lazy commit strategy.

[Chris Muller]

The default setting for
refreshPersistenObjectsEvenWhenChangedOnlyByMe, false, means a begin
will only refresh objects changed by others, not your own.  You have
not lost your work, so it can still be committed.

I have never considered it as a commit strategy myself, but it could
be useful to remain outside a transaction, working a long time on the
model until ready to commit.  For example:

"User does a whole bunch of work on the model"
...

"User is ready to commit, merge everyone elses changes into his own"
mySession begin.

"user reviews integrated model, makes any additional updates"
...

"Done reviewing, everything looks good."
mySession commit.

 - Chris

On 10/29/07, Keith Hodges <keith_hodges at yahoo.co.uk> wrote:
> Chris,
>
> I seem to remember somewhere some documentation mentioning that it is
> possible to simply perform a commit
> after not having performed a begin and that this could be a useful
> commit strategy.
>
> could you give me some more details
>
> thanks in advance
>
> Keith
>
> _______________________________________________
> Magma mailing list
> Magma at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/magma
>