Integrity Checker - Project reload needed?

[Paolo F Cantoni]

For our overnight processing, we do a LOT of work directly in the DB.  Every few steps or so, we run the Integrity Checker to make sure we haven't "broken" anything.

It would appear that the Integrity Checker works directly on the DB, but we take the precaution of doing a reload project every time.

Can we ignore the reload project step or is it necessary to ensure that he Integrity Checker is working on the latest data?

TIA.
Paolo

[VKN]

Unless you're not running some stuff like scripts or have unsaved diagrams, etc., I would guess that by doing 'reload project' you're making sure that the GUI has the latest information from the database (not changing the information within the database itself).

[Paolo F Cantoni]

Yes, I AM changing the database (with the overnight processing) - adding/deleting/modifying objects and relationships etc according to certain algorithms.

My question is if the Integrity Checker operates directly on the DB (ignoring the current state of the GUI), then I don't need to reload the project until I need the GUI to reflect the state (typically hours later).

Can you confirm that I don't need to refresh the GUI for the Integrity Checker to perform correctly?

Paolo

[VKN]

Can you confirm that I don't need to refresh the GUI for the Integrity Checker to perform correctly?
Paolo

Yes.

[Paolo F Cantoni]

Thanks, that will same some valuable time...

Paolo