Thanks. We created a simple MySQL example and managed to simulate the situation.
We know the Convertor is not an easy thing in TDM to understand at all… Anyway, although it seems strange, the behavior is correct. Let me explain in brief why:
Items in Convertor are compared by physical names. So, if you rename e.g. an attribute in Model 1, Convertor does not recognize it is the same attribute that already exists in Model 2 and is only renamed
considers it as a new attribute. So, you can see the attribute again.
Moreover, if you rename a relationship, it is considered as a new relationship. With a relationship, PK attribute is propagated. So, in Model 2 the PK attribute is generated once again.
Other important information on Convertor:
- Blue arrows in Convertor show your intention to generate the change (in alter script or apply the change in Model2).
- In Convertor, you can generate alter script and also merge models (to update existing model or to create a new model). The default settings of blue arrows is this: Take the objects (that are missing in Model 2) from Model1 and add them to Model 2
take the changed properties of existing objects from Model 1 and apply them in Model 2.
The default settings of blue arrows do not remove (drop) objects. If you want to do so, you need to make modifications of the blue arrows.
In your case (provided that you only changed the names and did not make other changes in object properties), simply refresh the first blue arrow (click it - the icon will change, and click again to display the blue arrow in direction from Model 1 to Model 2 - =>.)
Then you will get this:
ID Bigint NOT NULL AUTO_INCREMENT,
MAC_ASG_ID Bigint NOT NULL,
MAC_SJM_FROM_HOSPITAL_STORAGE Bool NOT NULL,
PRIMARY KEY (
It should be right now.
Regarding Convertor, please visit this site and read the series on Convertor to understand how it works:
(Convertor + Generate Alter Script - Part I, Part II)
In case of any questions, please write me back. Thanks.