Bugfix
Detail
#24619
Migration: Model update may delete attributes if their type changes
If you change the type of an attribute in the model, e.g. by changing the configuration of a primitive type, then on the one hand the type is deleted and re-created and all attributes that use it. When applying the change to the model, however, this can happen in such an unfortunate order that the changed attribute is deleted at the end (because the type deletion (and re-application)) is applied last.
Test
- Run the above scenario - too time-consuming in unit test.