When migration replaces an aggregate object, it also replaces the object's components. For example, if Entity Type E exists in the source and destination models and its Attribute A has been deleted only from the source model, migration deletes Attribute A from the destination model also. If Attribute A is not referenced in the destination model—has no usages—its deletion causes no problem, and the migration can proceed.
If you want to save components of aggregate objects that would be deleted by migration, perform migrations in both directions. Say, for example, you intend to migrate Entity Type E from Model A to Model B but want to keep several attributes of Entity Type E in Model B—and their permitted values. In this instance, migrate the required attributes from Model B to Model A. Then migrate the enhanced entity type from Model A to Model B. Because permitted values are components of attributes, they migrate with their respective attributes both ways.
|
Copyright © 2013 CA.
All rights reserved.
|
|