[ZODB-Dev] ZEO and commits

[Antonio Beamud Montero]

El vie, 24-10-2003 a las 19:01, Christian Robottom Reis escribió:
> > This acts like a lock, no?
> 
> No, and there is no locking primitive in the ZODB -- concurrent writes
> must resolve a conflict or fail.

Only when ZODB raises me an exception?

> Note that a sync() following a commit() is redundant, since a successful
> commit() invalidates the cache anyway (IIRC).

Ok.

> Well, commit(1) won't help you here; however, the root of your problem
> here seems that you are/will be running into conflicts, and no measure
> of sync()ing will help you once you've reached a conflict.

The only approach is programming the code with the conflict exception in
mind no? Exists a library wrapper that make this more easy? I think this
can be a common pattern of zeo use...

Thanks

> Take care,
> --
> Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 261 2331
-- 
Antonio Beamud Montero <antonio.beamud at linkend.com>