[ZODB-Dev] Transaction Manager Changes

[Toby Dickenson]

I am seeing some unusual behaviour in some classes which hook into the=20
transaction manager since Jeremy's sortKey changes. I have not been able =
to =20
reproduce a minimal test case yet, so this has been diagnosed from activi=
ty=20
logs on a production system.

The following two call sequences are ringing my alarm bells:

1. abort, abort

2. tpc_begin, abort, tpc_abort

Does this indicate a bug somewhere in the transaction manager, or should =
my=20
objects be expecting this?

(if it helps, there may be subtransactions involved too)