Better handling of modeling errors

Issue description

Currently the system throws a ModelerException when the administrator makes an error E. This happens on the next request that generates the constraints after the schema cache was cleared. In a productive system this renders the system unusable as long as E is not corrected. This is not acceptable and should be changed. Either disallow the saving of the form causing E or create a page which shows all modeling errors, but all system fragments unaffected by the error remain functional.

Developer comments

The exception should only surface when the user is an administrator. For non-admin users, the constraint causing the exception should be considered non-existent.

Reporting date

2021-12-18

Reported by

Robert Cerny

Resolving date

2025-05-05

Resolved by

Robert Cerny

Resolved in version

Topincs 10.0.0

Related to3

Modelling exception if a field list contains a foreign constraint(Enhancement)

Removing the only field of a view causes havoc(Bug)

ModelerException causes white generic browser error page (Bug)

Work sessions

Start	2025-05-05T05:24:06
End	2025-05-05T07:05:34
Participant	Robert Cerny