You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if one could define specialization of a relationship to override the source or target icon so when one is imbedded within a other then it overrides the visual ICON. A good example is data objects where I have a data object that is table and wish it to be presented as either primary key or secondary key based on relationship to table.
Similar may wish the ICON to change depending on where it is a aggregate versus composite. For example, different icon for table vs tables. Variance between it being a aggregate versus specialization, in this case an attribute of a entity versus a different context of the entity
The text was updated successfully, but these errors were encountered:
Description
It would be great if one could define specialization of a relationship to override the source or target icon so when one is imbedded within a other then it overrides the visual ICON. A good example is data objects where I have a data object that is table and wish it to be presented as either primary key or secondary key based on relationship to table.
Similar may wish the ICON to change depending on where it is a aggregate versus composite. For example, different icon for table vs tables. Variance between it being a aggregate versus specialization, in this case an attribute of a entity versus a different context of the entity
The text was updated successfully, but these errors were encountered: