On 10/13/05, Chris Spencer <[EMAIL PROTECTED]> wrote: > I understand that, but my point was when you call transaction.commit(), > you don't necessarily know what you're committing. One thread may be > ready to commit. Another may not be. If one thread calls > transaction.abort(), they may be aborting changes made by another > thread. You'd have to write a complicated coordination mechanism to > handle multi-threaded transactions to be sure. If threading is limited > to connections, then wouldn't in make sense if transactions were as well?
The default transaction manager maintains a separate transaction for each thread. When you call transaction.commit() from thread T1, it commits the transaction for thread T1. It has no effect on other thread's running transactions. Jeremy _______________________________________________ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org http://mail.zope.org/mailman/listinfo/zodb-dev
