Version: 1.5.2 (using KDE KDE 3.5.2) Installed from: Compiled From Sources Compiler: gcc (GCC) 3.3.4 OS: Linux I have been using the entity relationship model the most. General comments are tt is a good interface, and does good diagrams. I would like to see relationships between entities, in an entity relationship diagram, more related to an entity, so that if I create a second entity relationship diagram, and would like to include entities (that may have already been defined on other diagrams, that have relationships), these relationships could also be populated, or chosen to be shown on the second diagram as well. Steps to reproduce: create a new entity relationship diagram (entity_one_diagram) create three entities on this diagram A, B,C create relationship from A -> B and from B -> C create a second entity relationship diagram (entity_two_diagram) drag the entities (we created from the first diagram) from the entity relationship model onto the new ERD. The entities show up ok, but the relationship is not there. For larger models where a a couple of tables are involved in many relationships, such as in a lookup table, it would be handy to see the relationships we have defined before, between entities. A good use case of this is if i had a code table, and 5 entity relationhip diagrams, each of them have many tables that relate to the code table in a couple spots. Now, i would like to visually see "what things reference code table" I would create a new 6th diagram, and import all entities that are related to the code table, i would know which ones should be imported, since the code table entity would have a child list of the relationships that touch it (for example). I admit, i am probably trying to abuse the entity relationship modeller as a sort of database modelling tool, but i find it handy to have all the design (for the rest of the application classes) in one tool and to only have to work with (and submit) one xmi file.
Candidate for JJ: Extend UMLView::createAutoAssociations().
Created attachment 19698 [details] patch for #125146 That's a small fix for #125146. The patch is against the current trunk. The modified file is umlview.cpp This patch also fixes a bug when editing the properties of an association. You couldn't for exemple give a name to an association. It was because the functions slotOK et slotApply were not declared as SLOTS in assocpropdlg.h. This behaviour is strange. It worked in 1.5.6 I am sorry if i mess up something. Have a nice day.
SVN commit 633931 by okellogg: createAutoAssociations(): Handle Uml::dt_EntityRelationship. Thanks to Antoine Dopffer for the fix. BUG:125146 M +2 -0 ChangeLog M +2 -1 umbrello/umlview.cpp --- branches/KDE/3.5/kdesdk/umbrello/ChangeLog #633930:633931 @@ -1,5 +1,7 @@ Version 1.5.7 + * Bugs fixed from http://bugs.kde.org: +* Relationships for entities do not live outside of an entity relationship diagram (125146) * Javascript Code Generation creates bad format methods (135540) * Crash when deleting the link between a package and a class (141602) --- branches/KDE/3.5/kdesdk/umbrello/umbrello/umlview.cpp #633930:633931 @@ -1927,7 +1927,8 @@ if (widget == NULL || (m_Type != Uml::dt_Class && m_Type != Uml::dt_Component && - m_Type != Uml::dt_Deployment)) + m_Type != Uml::dt_Deployment && + m_Type != Uml::dt_EntityRelationship)) return; // Recipe: // If this widget has an underlying UMLCanvasObject then