On May 13, 2008, at 4:44 PM, David Pratt wrote:
Hi Jim. Any chance of incorporating Shane's patch for relstorage for
this release? Many thanks.
No. This is a bug fix release.
Jim
--
Jim Fulton
Zope Corporation
___
For more information about ZO
Le Tuesday 13 May 2008 20:02:42 Dieter Maurer, vous avez écrit :
> Someone convinced us that error handling should (of course)
> see the state the error happened and not a new clean state -- in
> order to be able to report about the errorneous state
Then, in my opinion, it should not be execut
Hi Jim. Any chance of incorporating Shane's patch for relstorage for
this release? Many thanks.
Regards,
David
Jim Fulton wrote:
Lately, we've started to use persistent caches. As we've done so, we've
found and fixed a number of problems. I'm planning to make a 3.8.1
release soon.
Jim
-
Lately, we've started to use persistent caches. As we've done so,
we've found and fixed a number of problems. I'm planning to make a
3.8.1 release soon.
Jim
--
Jim Fulton
Zope Corporation
___
For more information about ZODB, see the ZODB Wiki:
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-s
--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?
"Share
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?
"Shared.DC.ZRDB.TM.TM" is the standard Zope[2] way to implement a
ZODB DataManag
Vincent Pelletier wrote at 2008-5-13 10:36 +0200:
> ...
>To reproduce the problem:
> - create a class inheriting from TM, and define a method calling register.
> Add logs to abort and commit method to track transaction end.
> - create a default error page which triggers a call to the method creat
--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
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 reproduce the problem:
- create a class inheriting from TM, and define a method ca
10 matches
Mail list logo
