>From what I remember, it happened even after a complete catalog cleaning
and repopulation. We were using Zope 2.3.3 and CMF at the time. That was
on a production server so there was a bit of time pressure on us :) thus
the hazy recollection.
Chris McDonough <[EMAIL PROTECTED]> wrote:
> Yeah, I could see this error being raised if you had just added an index
> to use as the sort index and it didn't have all objects indexed within
> it yet...
> And yes, if this is what it is, it's a bug. But it's structural and not
> operational... we need to think a bit about what it means to add an
> unpopulated index to an existing catalog. Currently you just need to
> know that you must reindex the catalog.
> - C
> Florent Guillaume wrote:
> > I had something like that. It turned out that I was doing a catalog
> > query, sorting on an index that didn't exist on some of the objects.
> > I made sure the index existed on all my objects.
> > But still I'd be inclined to consider this a bug.
> > Florent Guillaume
> > Nuxeo
Florent Guillaume, Nuxeo SARL (Paris, France)
+33 1 40 33 79 87 http://nuxeo.com mailto:[EMAIL PROTECTED]
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -