In Zope2, this would be achieved
via a mixin
named something like Modifiable mixed in to DTML Document, File, etc.
- C
That had been my original instinct, but I wasn't sure. It sounds like the
best way to approach it.
I think this is complex enough so that a formal (if short)
Casey Duncan wrote:
I am posting this here to get reactions here for something that we have been
discussing on zope-dev that pertains to the ZODB.
Dieter M. discovered that bobobase_modification_time (henceforth referred to
as b_m_t) is not always an accurate representation of an object's
I think that a much better approach, if modification time is important
to your application, is to store the application modification time in the
object as a data attribute.
It might be better to cause common Zope objects to do what Casey proposes
(maybe via SimpleItem) as opposed to making
On Tuesday 08 January 2002 09:15 am, Jim Fulton allegedly wrote:
The basic problem is that b_m_t is a database modification time, not
an application-meaningful time. You pointed out that there are
application-meaningful times that are not captured by the database time.
In addition, there are
On Tuesday 08 January 2002 09:47 am, Chris McDonough allegedly wrote:
I think that a much better approach, if modification time is important
to your application, is to store the application modification time in the
object as a data attribute.
It might be better to cause common Zope
On Tuesday 08 January 2002 06:47 am, Chris McDonough wrote:
I think that a much better approach, if modification time is important
to your application, is to store the application modification time in the
object as a data attribute.
It might be better to cause common Zope objects to do
