On Feb 28, 10:59 am, Maurits van Rees <[EMAIL PROTECTED]>
> greenman, on 2008-02-27:
> > So, for the catalog.xml importer, why can't the trigger for reindexing
> > an index be a flag on the catalog index declaration itself? Is it
> > really generic setups role to determine if changes to an index
> > invalidate the values it already holds? If you were to change
> > properties of an index through code and not GS, then it would be up to
> > you whether you reindexed all your objects or not.
> The problem is that GenericSetup does not know if your current index
> is of the same type and has the same settings/properties as the index
> that you specify in catalog.xml.  Apparently it is hard/impossible to
> reliably compare the existing and the wanted index.  So GenericSetup
> has no choice but to remove the existing index and make a new one.

Can't that be wrapped in a try/except? The most common case is that
the index will have the attributes that GS is trying to set. As for
type, then again, given the prevalence of actions in GS that modify an
assumed current state - then a flag 'recreate' would allow for a type
change to be pushed through.

> --
> Maurits van Rees |http://maurits.vanrees.org/
>             Work |http://zestsoftware.nl/
> "This is your day, don't let them take it away." [Barlow Girl]
> _______________________________________________
> Zope-CMF maillist  - [EMAIL 
> PROTECTED]://mail.zope.org/mailman/listinfo/zope-cmf
> Seehttp://collector.zope.org/CMFfor bug reports and feature requests
Zope-CMF maillist  -  Zope-CMF@lists.zope.org

See http://collector.zope.org/CMF for bug reports and feature requests

Reply via email to