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 commited, the current date/time.

- 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.

Thoughts?

-Casey

--- Dieter Maurer <[EMAIL PROTECTED]> wrote:
> I just discovered that the value cataloged for
> "bobobase_modification_time"
> is often wrong:
> 
>    The cataloged value is not the time of the
> current modification
>    but that of the previous modification.
> 
>    I expect that this is because
> "bobobase_modification_time" is updated
>    when the transaction is commited while the values
> to be cataloged
>    are determined before the commit.
> 
> Do not trust the cataloged
> "bobobase_modification_time"!
> 
> 
> Dieter
> 
> _______________________________________________
> Zope maillist  -  [EMAIL PROTECTED]
> http://lists.zope.org/mailman/listinfo/zope
> **   No cross posts or HTML encoding!  **
> (Related lists - 
> 
> http://lists.zope.org/mailman/listinfo/zope-announce
>  http://lists.zope.org/mailman/listinfo/zope-dev )
> 
> 


__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com

_______________________________________________
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )

Reply via email to