If the attribute type is changed to an unsupported type, an error will be displayed at startup.
https://docs.mendix.com/refguide/attributes-type-migration#2-2-conversion-table
This is documented, but it would be good to avoid this inconsistencies happen.
Some databases support rollback, in which case you can restore the database to a previous state.
However, the Oracle Database commits every time you issue a DDE command. Issuing and applying partial commands will cause inconsistencies in the database structure and data.
As a result, the system will stop working until the user manually restores the database.
This has been documented, but it is hoped that such inconsistencies will not occur.
https://docs.mendix.com/refguide/oracle#4-ddl-commands
Idea suggestions:
A. Implement sequential rollback feature for Oracle Database, somehow.
for example, using Oracle's backup/restore tools.
B. Check if there are unsupported type conversion and shows error dialog before issuing the SQL sequences.
*Different database has different restrictions. The configuration can be maintained as a table for each database lineup.