On 06/08/2010 12:44 PM, Chris Withers wrote:
> Laurence Rowe wrote:
>> Committing in tpc_vote is right so long as you ensure your data
>> manager sorts last, and that there are no other data managers in the
>> transaction which are using the same trick.
> Why does the latter part matter?
> (It is, of course, the situation I'm in, where zope.sqlalchemy is
> operating in non-tpc mode (sqlite doesn't support tpc :-/) and now I'm
> writing another data manager for a service that doesn't support tpc)

Because TPC requires all participating DMs to be able to get in a state 
where committment can be guaranteed but also aborted.

A single DM may have non-TPC behaviour and you will still be fine. If 
you have more than one then it can happen that the first one committed, 
but the second one doesn't and then you can't properly roll back.


Christian Theune · c...@gocept.com
gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany
http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1
Zope and Plone consulting and development
Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope )

Reply via email to