| Summary: | Handle migration of recorded feature removal | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] Edapt | Reporter: | Lasse Bjermeland <lassebje> | ||||
| Component: | Core | Assignee: | Project Inbox <emf.edapt-inbox> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | mkoegel | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
This is intended behavior since just deleting the attribute from the metamodel does not say what to do with the data in instances. Using the DeleteFeature Operation explicitly states that. A use case where just deleting it from the meta model makes sense is a custom migration. |
Created attachment 206202 [details] Screen shot of unnecessary attribute migration Migration of deleted attributes fails when the deletion is part of a recorded change. When the change is converted to a "Delete Feature" operation the migration works as intended