Ian


Himself will have to have the final say but I'd guess its because you can't repair the table until you know what's wrong with it. Since VERIFY and REPAIR can be run independently and at a considerable space in time between each with, possibly lots of database activity between as well it makes sense that the first thing a REPAIR does is its own VERIFY so that's what you're seeing.

Roy Lambert

Hi Roy,
   I suspect something different.
   In the screen shot, the first Verify action is due to the specific Verify call to EDBScript.  Hence the 'Not Fixed'.
   The indicated second Verify action between the 'Repair' lines via EDBDatabase suggest that the Repair has happened and
a Verify has then been re-done, hence the 'Fixed' at the end.

   The Optimize phase via EDBDatabase puts out its own message, I am just curious why the Repair phase doesn't as well.

Regards,
Ian

Ian

>    In the screen shot, the first Verify action is due to the specific Verify call to EDBScript. Hence the 'Not Fixed'.
>    The indicated second Verify action between the 'Repair' lines via EDBDatabase suggest that the Repair has happened and
>a Verify has then been re-done, hence the 'Fixed' at the end.

I read it differently - first a verify is carried out - that tells ElevateDB that a fault exists. a function is called that repairs it and adds a fixed on the end of the messsage, if it failed to fix it you'd get a "Not Fixed". For a VERIFY TABLE either the function is called with a "don't bother" flag which means the "Not Fixed" is returned or a different function is called which returns "Not Fixed" regardless. I suspect the former since that would simplify the code a bit.

Roy

We will just have to wait for Tim to get over his New Year hangover for the final say.  

On 1/2/2019 12:16 PM, Ian Branch wrote:
>    In the screen shot, the first Verify action is due to the specific Verify call to EDBScript.  Hence the 'Not Fixed'.
>    The indicated second Verify action between the 'Repair' lines via EDBDatabase suggest that the Repair has happened and
> a Verify has then been re-done, hence the 'Fixed' at the end.
>
>    The Optimize phase via EDBDatabase puts out its own message, I am just curious why the Repair phase doesn't as well.

I believe Verify and Repair are internally both handled by verify logic
- it's called using "repair" or "report only" flags is main difference.

Repair itself does some additional prep - like checking for transactions
and exclusive open on table. Verify by itself can simply do a read lock
since nothing will change.

Raul

What's the question, exactly ?

Please make sure to post the question along with any screen shots, instead of leaving me to figure out what you're asking.

Tim Young
Elevate Software
www.elevatesoft.com

Ian,

So, the question is why both say "verification" ?

If so, then the answer is: they're both the same functionality, with the only exception being that the repair will *fix* any verification errors.

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

> they're both the same functionality, with the only exception being that the repair will fix any verification errors.

Ah Ha!  Now I understand.  I had wrongly assumed they were different 'routines'.


Thanks Tim.