Vincent Pelletier wrote at 2008-5-22 11:21 +0200:
...
BTW, the usual error hook treats conflict error exceptions differently from
others, and I guess it was done so because those can happen in TPC.
No, the reason is to repeat a transaction that failed due to
a ConflictError.
--
Dieter
Le Thursday 22 May 2008 10:40:46, vous avez écrit :
Maybe, you search the zope-dev archive to find the thread that convinced
us to change the former behaviour (the one you want now again)
into the current one?
Adding links for possible future reference:
--On 13. Mai 2008 10:36:48 +0200 Vincent Pelletier [EMAIL PROTECTED]
wrote:
Hi.
_register method of TM class in Shared/DC/ZRDB/TM.py hides all exceptions.
This makes descendants of this class prone to get stuck in a registered
state withtout any possibility of them to get commited.
To
--On 13. Mai 2008 20:08:15 +0200 Dieter Maurer [EMAIL PROTECTED] wrote:
Andreas Jung wrote at 2008-5-13 10:44 +0200:
...
Is there any reason why TM._register is hiding exceptions ?
Isn't the right approach for integrating a module with ZODB transactions
using a ZODB DataManager?
Andreas Jung wrote at 2008-5-13 20:19 +0200:
...
Shared.DC.ZRDB.TM.TM is the standard Zope[2] way to implement a
ZODB DataManager.
Nowadays you create a datamanager implementing IDataManager and join it
with the current transaction. Shared.DC.ZRDB.TM.TM is pretty much
old-old-old-style.
