Eric Brun wrote:
An idea for fix it ?
Have you tried updating the catalog from it's advanced tab?
Not sure how that'd pan out on 200,000 objects though...
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
___
Eric Brun wrote at 2004-2-26 17:59 +0100:
> ...
>When we do a search on a ZCatalog we have the message below. We work with Z=
>ope 2.6.2 and our Catalog have more than 200 000 objects referenced.
>
>We think our catalog is corrupted but we would correct it.
> ...
>Type d'erreur : KeyError =
>
>Vale
Yes but impossible to update it because it is too big, and the transaction never
finish or abort because of time out.
I don't know how to do this.
Have you a idea for help me ?
> Eric Brun wrote:
>
> > An idea for fix it ?
>
> Have you tried updating the catalog from it's advanced tab?
>
>
In this way (with small chunks),
can I do a get_transaction().commit(1)
for commit each chunks or is it unnessecary ?
Thank everybody for your help
> Write a script to do it in smaller chunks - 20 at a time or somethig.
> Keep track of those that succeed, so you can restart where you left off
Eric Brun wrote at 2004-2-27 17:22 +0100:
>In this way (with small chunks),
>can I do a get_transaction().commit(1)
The "1" as argument to "commit" means "subtransaction".
This is not sufficient to prevent conflicts from wiping out
the reindexing work. You will need "full" commits.
Moreover, it
