Dieter Maurer wrote:
In our private Zope version, I have still a note like this:
# DM 2005-08-22: always call '_flush_invalidations' as it does
# more than cache handling only
self._flush_invalidations()
if self._reset_counter != global_reset_counter:
# New code is in place. Start a new cache.
self._resetCache()
# DM 2005-08-22: always call '_flush_invalidations'
## else:
## self._flush_invalidations()
The note indicates that the bug was fixed at least at 2005-08-22
(though the handling was not completely right in case the cache
was reset).
Once again, it would be nice, now that you have access, if you could
feed back your changes in areas like these rather than keeping them in
your own private source tree :-(
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
