On Saturday 05 January 2002 08:15 pm, kapil thangavelu allegedly wrote:
On Sunday 30 December 2001 08:00 pm, Casey Duncan wrote:
This behavior is logical if unintuitive. I propose
that we can kill two birds with one stone to fix this:
- Add a new method perhaps: getModificationTime() to
On Monday 07 January 2002 06:20 am, Casey Duncan wrote:
On Saturday 05 January 2002 08:15 pm, kapil thangavelu allegedly wrote:
On Sunday 30 December 2001 08:00 pm, Casey Duncan wrote:
This behavior is logical if unintuitive. I propose
that we can kill two birds with one stone to fix
On Monday 07 January 2002 07:38 am, kapil thangavelu allegedly wrote:
On Monday 07 January 2002 06:20 am, Casey Duncan wrote:
[snippingtons]
I am interested in seeing this code. From my perspective it seems overly
sophisticated. I'm interested how you derive the registration time in the
That looks nice and simple to me. Does anyone have a concern about the
behavior for new objects? (I'm not sure what can be done about it...)
If no one objects I can check this into the core.
Or before getting ahead of myself, does this still need a proposal and all
that?
That looks nice and simple to me. Does anyone have a concern about the
behavior for new objects? (I'm not sure what can be done about it...)
If no one objects I can check this into the core.
Or before getting ahead of myself, does this still need a
proposal and all
that?
I'm ok
On Sunday 30 December 2001 08:00 pm, Casey Duncan wrote:
This behavior is logical if unintuitive. I propose
that we can kill two birds with one stone to fix this:
- Add a new method perhaps: getModificationTime() to
the API of SimpleItem or even Persistent that returns
the ZODB
Casey Duncan wrote:
- Deprecate bobobase_mod_time and perhaps even omit it
entirely from Zope3.
This will fix the aforementioned bug and get rid of an
API anachronism.
Awww... but we'll loose one of the more amusing prefixes in Zope parlance ;-)
cheers,
Chris
(that'll be a big +1 from
This behavior is logical if unintuitive. I propose
that we can kill two birds with one stone to fix this:
- Add a new method perhaps: getModificationTime() to
the API of SimpleItem or even Persistent that returns
the ZODB modification time or if the object has been
changed, but not yet