1
Suggestions and Requests / Re: Handling of nested controlled packages
« on: July 02, 2008, 08:00:01 pm »Quote
During XMI operations the only thing that matters is the guids.Simon, I know that the guids matter for XMI but I think it is a problem that the guids are not used for linking objects in the database!
For instance, connectors between objects from different packages are not loaded into the 't_connector'-table if one package is missing! Why? Simply because either the Start- or End_Object_ID is missing! If you'd use the guids of the Start and End-Objects there, the entries could just be made without the necessity that the corresponding object is existent in the 't_object'-table. For the guid is a guid the relationships can be easily resolved as soon as the missing objects are present.
Same applies to the m-m-relationships solving tables like 't_diagramobjects'.
Like this, it would not be necessary to store information in the xml-file from a diagram which actually belongs to another package. This is namely how Frank's problem is solved since version 7.1.
However, this only works for first time import. If I delete a package an reimport it again, the diagrams are not restored. To restore them, I have to load the other package again.
Ok, delete means delete... But what choice do I have if I don't want to see a package in my project? Is there maybe a function like 'Unload' or 'Remove Package' function in the case
Quote
This does result in a potential loss of information, and someone is looking into it.Glad to read this





Hopefully the text is 'quoted'; otherwise a comma in it will mess your data...

