What is the default behavior when changing an attribute type in an Entity model?

When changing an attribute type in an Entity model within OutSystems, the default behavior is that it requires a full database migration. This is necessary because altering the type of an attribute directly impacts how data is stored in the underlying database structure. A migration is essential to ensure that the data integrity is maintained and that the new type is properly applied across the database.

This process involves creating scripts that will handle the conversion of data from the old type to the new type. The migration ensures that existing records are updated accordingly and helps prevent inconsistencies that could arise from simply changing the type without a structured approach. As a result, it's important to plan and test migrations thoroughly, particularly in production environments where data is sensitive.

The other options describe scenarios that do not accurately reflect the process. Existing data is not necessarily lost when changing an attribute type, as migrations typically aim to preserve and adapt existing records. While only new records reflecting the change may apply to certain attribute types, this does not encompass the general behavior for most types of changes. Lastly, it is possible to revert some changes if planned carefully, although it may involve more migrations to restore the previous state. Overall, understanding that a full database migration is the required step when altering attribute types is crucial for maintaining data