enhancement
major
minor
major
minor
defect
If, when booting a new software version with a new model version, the system detects that a model element is to be deleted, this deletion is performed as part of the automatic data migration.
If an entire type—including a reference to another type—is deleted during this process, the association to which the reference is mapped remains in the database. Normally, this has no adverse effects; however, if you subsequently attempt to recreate the same type (with the same name) and a reference with the same name, the operation will fail with an error message stating that the corresponding association already exists.
Test
- Create an application.
- Create module M` with types `A ` and `B` and a reference-valued attribute `ab ` in `A` that points to `B`.
- Import the module into the IDE.
- Shut down the application.
- Reboot the application and shut it down again.
- In the IDE, delete type A from the model definition.
- Boot the application.
- Expected result: Type A no longer exists.
- Shut down the application.
- In the IDE , recreate Type A with its reference to `B.
- Start the application.
- Expectation: Type A` exists again and once again has a reference to `B.