v16β – Purge of Element doesn’t “clean-up” after itself

[Paolo F Cantoni]

It seems as though when we Purge items from the repository under v16β, the Integrity Checker is broken (since it returns immediately), but more importantly, it seems as though the Purging process doesn't clean up after itself (purging related rows from the various tables).  If we run the v15.2 on the same repository after we have purged the item, it finds a pile of errors - apparently related to the item (since in a massive UI fail, the IC doesn't tell you the affected items).


This is MOST concerning!  Anyone else seeing this?  If true, needs fixing NOW!


Reported,
Paolo

[Eve]

the Integrity Checker is broken (since it returns immediately)

Was there a separate post about this that I'm missing?

Turns out the answer is very simple. By default all of the categories are turned off in 16. So it's running zero checks.

it seems as though the Purging process doesn't clean up after itself (purging related rows from the various tables).

Does this happen when running on the original schema? Stereotypes, tags, relationships were all cleaned up correctly in my tests.

[Paolo F Cantoni]

the Integrity Checker is broken (since it returns immediately)

Was there a separate post about this that I'm missing?

Turns out the answer is very simple. By default, all of the categories are turned off in 16. So it's running zero checks.

Yes, 15 years of "muscle memory" made me ignore they were off.  I've now turned them on and will monitor what v16β says versus v15.

it seems as though the Purging process doesn't clean up after itself (purging related rows from the various tables).

Does this happen when running on the original schema? Stereotypes, tags, relationships were all cleaned up correctly in my tests.

AFAIK, the schemas were up-to-date.


Paolo

[Geert Bellekens]

the Integrity Checker is broken (since it returns immediately)

Was there a separate post about this that I'm missing?

Turns out the answer is very simple. By default all of the categories are turned off in 16. So it's running zero checks.

Are you now saying that someone decided that the default choice for this dialog should be changed from "all checks selected" to "no checks selected"?

IMO a default selection should reflect the most used/useful option, and I'm pretty sure "no checks selected" is the only option that is not useful in any scenario.

Geert

[Paolo F Cantoni]

the Integrity Checker is broken (since it returns immediately)

Was there a separate post about this that I'm missing?

Turns out the answer is very simple. By default, all of the categories are turned off in 16. So it's running zero checks.

Are you now saying that someone decided that the default choice for this dialog should be changed from "all checks selected" to "no checks selected"?

IMO a default selection should reflect the most used/useful option, and I'm pretty sure "no checks selected" is the only option that is not useful in any scenario.

Geert

"You might very well think that; I couldn't possibly comment..." (with apologies to Francis Urquhart)


Paolo


[Edit: (my emphasis) They don't default to "no checks selected" they ENFORCE "no checks selected"   - every time you start up the integrity checker you need to set ALL the checks you want (assuming it's not a vendetta against me).  Whose bright idea was that implementation? ]