Chris Spencer wrote:
I understand that, but my point was when you call transaction.commit(),
you don't necessarily know what you're committing.
Yes you do, each thread has its own connection to the database, and this
connection has an independent view of the database from any other thread.
Calling commit on one connection does squat on any other connections ;-)
Now, unless you're writing your own threading code, or your own
connection code, you don't need to worry 'cos Zope does "the right thing".
If you are writing your own threading or connection code, you're either
god-like, or an idiot. 99.5% percent of people who _think_ they need to
write connection or threading code fall into the latter category...
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
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
