Detecting corrupted index

Ruslan Zasukhin ruslan_zasukhin at valentina-db.com
Tue Aug 30 07:23:47 CDT 2011


On 8/29/11 11:39 PM, "jda" <jda at his.com> wrote:

Hi Jon,

> I have found that my databases using an older version of Valentina
> (don't remember which, 3.x) often have problems develop with the
> index (it's a very large index). I'm using diagnose to detect
> problems, and when it comes back positive I suggest the use repair
> (clone) the database, which is kind of a pain.

To fix index(es) it is enough reindex

> If I could detect that only the index was the problem I could just
> force a reindex and the user wouldn't be aware that there ever was a
> problem. The question is, how to do this?

I see 

Well, except to write some search in the diagnose report
I do not see ways 


> I could have Valentina write the diagnose report to a temporary file
> and read the file. But I'd have to be sure that the *only* thing
> wrong was an index problem. I would prefer that this be automatic
> (e.g. a diagnose that didn't give back a text file in English, but
> rather something more machine friendly), but since that's not
> possible, what you you, or anyone, recommend? What should I look for
> in the text of this file that would tell me:
> 
> 1. The db is OK *except*
> 2. There is some problem with one or more indexes (so Reindex).

And this should stay on old v3 yes?



-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]




More information about the Valentina mailing list