On Tue, May 29, 2007 3:13 am, Tres Seaver wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Darryl Dixon - Winterhouse Consulting wrote: > >> The version of clearFindAndRebuild in CMFPlone 2.1.3 calls >> reindexObject(), but I see that in the HEAD (and presumably 2.5.x) it >> has >> been changed to simply indexObject(). Presumably this change is in >> direct >> response to the fact that reindexObject() touches the modification >> time...? Which lends even more weight to my original query - why on >> earth >> does reindexObject() update the modification time? I can see utterly no >> reason why it should... > > Originally, the catalog support provided a de facto "event mechanism", > along with its main job: The 'reindexObject' method was designed to be > called from within "mutator" methodds / scripts, because the > 'notifyModified' method is private. Calling 'reindexObject' *implies* > that you have edited the object, else why would you be reindexing it? > The exception is if you pass through a set of indexes. > > Note that calling either 'reindexObject' or 'indexObject' is unnecessary > in the context of a catalog rebuild: you might as well just call > 'catalog.indexObject(the_object)' directly. > > If you *do* chose to go through the object, you can either just call > 'indexObject' or pass the list of indexes you want to reindex explicitly. > > We can't change this without going through a BBB / deprecation dance, in > order to allow people to fix code which depends on the current behavior. >
Aha! Now it becomes clear. Thanks for the explaination Tres. I guess my best option then will be to hotfix the Plone version we are currently stuck with - thanks! :) Darryl Dixon Winterhouse Consulting Ltd +64 21 33 44 13 _______________________________________________ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests