Andy, This is a known issue with the catalog (searching the collector for "key error" will show you how common it has been). Chris Petrilli should be checking in some changes to the CVS 2.2 branch (and the trunk?) tomorrow that resolves it. The problem is evidently related to the way catalog.index_object() and catalog.unindex_object() do their thing. I'd advise you live with the issue until 2.2.3 comes out (which should be sometime this week, AFAIK). ----- Original Message ----- From: "Andy McKay" <andym@activestate.com> To: <zope-dev@zope.org> Sent: Monday, November 06, 2000 4:17 PM Subject: [Zope-dev] ZCatalog index error
Im running into an odd bug with ZCatalog:
I have am running a catalog query and Im getting this message.
File D:\zope\lib\python\Products\ZCatalog\Lazy.py, line 193, in __getitem__ File D:\zope\lib\python\Products\ZCatalog\Catalog.py, line 197, in __getitem__ KeyError: 52536
This is the line where it seems to be setting all the scores to one, and I guess it can find the item 52536.
else: # otherwise no score, set all scores to 1
r=self._v_result_class(self.data[index]).__of__(self.aq_parent)
r.data_record_id_ = index r.data_record_score_ = 1 r.data_record_normalized_score_ = 1
The thing is my catalog is only 17,000 records in size, I have no item
52536
(no wonder it cant find it). I guess my best plan would be somehow to remove that the record for that item if I could... hmm...
Any other ideas?
-- Andy McKay, Developer. ActiveState.
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )