[ZODB-Dev] ZEO and commits
Antonio Beamud Montero
antonio.beamud at linkend.com
Fri Oct 24 12:01:48 EDT 2003
El vie, 24-10-2003 a las 17:03, Christian Robottom Reis escribió:
> No, connection is a ZODB Connection instance, which is what
> database.open() returns.
>
Ok.
> If other clients update the original object, you have a conflict.
> When you call sync(), the current transaction is aborted, and any
> conflicting changes are discarded. So calling sync() and *then*
> modifying the object is what you need to do.
The sequence can be: get_transaction.commit()
con.sync()
<modify object
get_transaction.commit()
This acts like a lock, no?
Need I to do a get_transaction.commit() or can I do a
get_transaction.commit(1)?
A lot of thanks.
Greetings
>
> This may not be exactly suited to your usecase; if you have high
> concurrency, you'll need to consider conflict resolution carefully.
>
> Take care,
> --
> Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 261 2331
--
Antonio Beamud Montero <antonio.beamud at linkend.com>
More information about the ZODB-Dev
mailing list