I can't directly address the concerns you've raised, but for my project
I have rewritten TM.py to work better within the begin/vote/finish/abort
protocol framework. I've also added more documentation.
John
Randall F. Kern wrote:
> I may just be missing something obvious here, but it seems li
I may just be missing something obvious here, but it seems like there is
a hole in ZODB.Transaction.Transaction.commit and Shared.DC.ZRDB.TM.TM,
that can cause external transactions (those that use the TM mixin class,
like psycopg) to be abandoned (never get committed or rolled back).
Let's say s
