I have a issue similar to that in 188.8.131.526
in the logical model I have a unique identifier in a entity,
the order of the identifier is one attribute from a relation ans after one attribute of the entity,
when I save and enginered to the relational model the DDL generated is with the right order,
but If I close the design (after saving,also commiting SVN) and I open again the model, the unique identifier has a different order,
if I change and save again, nothing hapend after close and open again.
The order is not be saved.
Thanks in advance
we have it fixed for next release. You also can get it fixed:
1) find file CandidateKey.xml in directory datamodeler\datamodeler\xmlmetadata
2) there is a line in that file
<collection name="usedAttributes" dataType="java.util.Collection" xmlName="usedAttributes" itemXmlName="attributeRef" getter="getElementsCollection" itemIsRef="true" removeItem="remove" addItem="add" getItemByID="getRequestByID" />
3) you can remove it and save the file
we have a similar issue regarding the range partitions into the Physical model,
I don't know if you already took into account,
the problem is when we create partitions per range in a table , the order of the columns is not saved,
so when you open the model and generate the DDl is generating the partitions incorrectly,
do you think that the problem could be related to another XML file?
thanks in advance
Note:Oracle 11g is the DBRMS type that we use
Is this still a problem in Data Modeler 4.0 EA2 ?
There was a problem that when the Table Properties dialog was opened the order of the columns for the partition was displayed incorrectly. Selecting OK would then save this incorrect order.
This problem was fixed in EA2.