defect
minor
#24619
Migration: Model update may delete attributes if their type changes
If you change the type of an attribute in the model—for example, by changing the configuration of a primitive type—the type is first deleted and then recreated, along with all attributes that use it. However, when applying the change to the model, this can happen in such an unfortunate order that the modified attribute is deleted last (because the type deletion—and re-creation—is applied last).
Test
- Reenact the scenario described above—too time-consuming in a unit test.