Hi Steve,
ZPatterns is something that is very high on my must investigate list,
but I am not doing Zope development, but rather ZODB based development.
I'm sure that I can still get lots of good ideas though...
My comment below about _v_* attributes is primarily about not using
functionality
--
From: John D. Heintz [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 05, 2001 12:45 PM
To: Tim McLaughlin
Cc: '[EMAIL PROTECTED]'
Subject: Re: [Zope-dev] is there a hook for before the transaction is
committed
Hi Tim,
I have two suggestions, I hope one of them helps.
1) Attached is
John D. Heintz wrote:
> Hi Tim,
>
> I have two suggestions, I hope one of them helps.
>
> 1) Attached is a TM.py file that I wrote based on the one you mention
> below. I've tried to make it more obvious and better documented.
>
> 2) Don't use this kind of functionality, but rather use sub-t
Hi Tim,
I have two suggestions, I hope one of them helps.
1) Attached is a TM.py file that I wrote based on the one you mention
below. I've tried to make it more obvious and better documented.
2) Don't use this kind of functionality, but rather use sub-transaction
commits.
The first suggest
On Mon, 5 Mar 2001, Tim McLaughlin wrote:
> manage_afterChange(oldItems, newItems)
> oldItems: dict of id - values before modifications
> newItems: dict of new values at end of transaction
>
> This would allow an elegant "reindex" or notification system for objects.
> It would also allow for vali
t ;-)
-Original Message-
From: Toby Dickenson [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 05, 2001 12:08 PM
To: Tim McLaughlin
Cc: '[EMAIL PROTECTED]'
Subject: Re: [Zope-dev] is there a hook for before the transaction is
committed
On Mon, 5 Mar 2001 10:56:38 -0500, Tim McLau
On Mon, 5 Mar 2001 10:56:38 -0500, Tim McLaughlin
<[EMAIL PROTECTED]> wrote:
>Is there a hook for before the transaction is committed for objects which
>subclass Persistent?
__getstate__ ?
But why would you want that?
Toby Dickenson
[EMAIL PROTECTED]