Component ‐ Data Integrity Checks

Important

Vision

Changes or the general direction the feature is likely to take in the future...

• Change: [api][app] Unify the issue refs so they always hold UIDs and add "metadata" so the type is either known from the YAML file or computed dynamically as part of the DB query. This is so we can support links to view/edit the conflicting object in the maintenance app
• Add: [api][app] Persistence for the results so the last N results can be stored, viewed and compared to analyse trends and regressions
• Add: [api] A job that uses the results history to find regressions and notify users
• Add: [api] A job to run checks periodically based on their costs which can be learned from the new history
• Add: [api][app] A action to auto-repair identified issues - the repair would be a SQL template in the YAML together with a description of what it does. The IDs of the identified issues are them parameters to the template to run the repair. Good examples would be remove trailing spaces from names