REINDEX

[Ruslan Zasukhin]

On 8/29/05 7:51 PM, "Andrew Sinning" <andrew at learningware.com> wrote:

> In my most recent test, I did a Flush() after every delete, just to rule
> that out.  It didn't help.
> 
> The only thing that solved the problem was to do a REINDEX after every
> delete.
> 
> Of course that many REINDEXes is not a good idea, so I am now modifying
> my code to REINDEX only after a SELECT results in 0 cursor records.  I'm
> also building in some controls to prevent excessive REINDEXes.

Andrew, have you try XML rebuild of your db ?
It sounds very strange that you get so often problem.

Ah, you have told you cannot do that..

If you do not use ObjectPtr you can do EXPORT/IMPORT table(s) into text
files.

> It's very likely that the reason this is happening is that there is
> someother corruption in the database, a corruption that has resulted
> from bad programming or insufficient error checking in the processes
> that lead up to the configuration where I can reproduce the bug.

I also think that bug is NOT in code of Valentina 1.11
Too long it is tested and too many developers have use it.

> If Flush() the most important tool for preventing database corruption?
> How often should I Flush()?  After every insert or ALTER or DELETE?
> Should I build into my main db parent object a process that keeps track
> of the number of changes and then run Flush() after a certain number of
> changes?
> 
> How do you handle this, Florian?

-- 
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]