On Saturday 29 September 2001 04:29 pm, Chris McDonough allegedly 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
What would the reaction be to changing this behavior. I have written some
code that automatically populates the index when it is added. I personally
think that reindexing every index just to populate one is grossly
inefficient.
I think populating only one index on add is a great idea... the
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.
Florent Guillaume
Nuxeo
Chris McDonough [EMAIL
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
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
Morten W. Petersen [EMAIL
Hia,
While trying to reindex an entire catalog an error is raised, which looks
like this:
Traceback (innermost last):
File
/home/morten/zope_instances/usr2/local/Zope-bcr/lib/python/ZPublisher/Publish.py,
line 223, in publish_module
File
