Pre-Commit Check for Data Model Changes Idea that can cause Data Loss

We recently experienced a significant data loss when committing an app where a marketplace module was deleted and then reinstalled. This action inadvertently broke associations to the data model of the module, leading to unexpected data loss.

To prevent such issues in the future, I propose implementing a pre-commit check that warns developers in Studio Pro if their commit will result in dropping or recreating tables and/or associations.

This check would serve as a safeguard, alerting developers to potential data model changes that could lead to data loss, and allowing them to take corrective action before committing.

Benefits:

• Prevents accidental data loss.
• Enhances the reliability and stability of applications.
• Provides developers with an additional layer of security and confidence when making changes.

Thank you for considering this idea to improve the Mendix development experience.