Previously Lennart Regebro wrote:
> On 9/25/07, Maurits van Rees <[EMAIL PROTECTED]> wrote:
> > When you want to remove an index or column you can do that by editing
> > the profile and adding remove="True" to that index or column. So this
> > upgrade can be represented as a profile edit. But applying the
> > profile will empty the remaining indexes that are mentioned in that
> > profile. So ideally I would want to apply the profile only once when
> > installing and rely on upgrade steps to handle any further changes
> > without applying that complete profile again.
> > It seems the new upgrade steps do not really solve this particular use
> > case then. (It can sure be handy for other things, no doubt about
> > that.) But I had hopes to use them to work around this issue with
> > catalog.xml. Apparently a workaround is no substitute for really
> > solving the problem. ;-)
> > Is anyone going to the sprints after the Plone conference who wants to
> > take a shot at this with me? Preferably someone with commit rights. :-)
> Well, I made a monkey-patch that I haven't merged yet that only did
> that if the index definition had actually changed, and that was quite
> trivial. I would appreciate more people looking at this, since this
> was so easy I get suspiscious. :-) So at the Plone conf seems a good
I would like to see that. As far as I could see there is no way to do
this reliably, but I would love to be proven wrong.
Wichert Akkerman <[EMAIL PROTECTED]> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
Zope-CMF maillist - Zope-CMF@lists.zope.org
See http://collector.zope.org/CMF for bug reports and feature requests