raise error on subclass check

[cymed]

Solves #337
Not tested yet - thus draft PR

[sjib]

@cymed Fix seems to work - only error message is wrong (change too many / too few). I have added one additional structure_part entry in my data. So I am missing a corresponding subclass entry.

[sjib]

@cymed
If I have one entry too much in the superclass (structure_part) I get this message:
2024-07-30T15:42:02 teksi_wastewater.utils:Subclass Count error: Too many subclass entries for tww_od.structure_part

Should be adapted to
2024-07-30T15:42:02 teksi_wastewater.utils:Subclass Count error: Too many superclass entries for tww_od.structure_part

And the other case: Too few subclass entries for {schema_name}.{parent_name}

Is that clearer?

[cymed]

Wouldn't it be too many subclass entries in Case 2?

[sjib]

Yes, I think then it is right - either we have too many superclass entries or we have too many subclass entries.

[sjib]

And in using superclass and subclass we indicate where to check

[sjib]

I found out, that we also do the subclass check when we make a selection.

For the user it is a little bit confusing to get the subclass check error also then even if the selected objects are correct.

• do we want to keep the subclass check also there to enforce data integrity or
• take it out then (and then might have strange errors)?

I would stay with the existing behaviour an may be adjust the error message to not confuse the users.

Any comments on that?