Is there any way to influence the order of transaction aborts when you
hijack the transaction mechanism in a similar way as
Shared/DC/ZRDB/TM.py does? I have Folder and File like classes which
make changes on the file system as a part of their operation. When
within a transaction I make multiple
shared/dc/zrdb/tm does not hijack the transaction mechanism it
integrates with it.
you should coalesce txn integration for your objects into a single txn
integrator so you needn't depend on transaction message/jar ordering.
-kapil
On Tue, 2004-04-20 at 11:35, [EMAIL PROTECTED] wrote:
Is there