I am experiencing this same issue. I have cloned tables, and they are fine in the design editor, but when I forward engineer, the cloned table has the Constraint name defaulted to the original table constraint name. I have gone into the designer to provide a valid name for the primary key constraint, but it seems to hold on to the original constraint name for the original table. This is a huge issue for me. I don't know how many tables I have cloned, and now at run time, I am have to manually repair all of these constraint names. Please fix asap.
I have noticed that this icon can sometimes "disapear". I see this icon, and then sometimes something happens and then I no longer have this icon visible in my browser...
Great news, I am curious if only views are being allowed here, or if the plan is to also allow TVF as well?
I found that not being able to manually control where my lines go, is having quite a detrimental impact on the readability of my model. This wouldn't be such an issue, if that app could place the lines better, but I find I have many linese crossing unnecessarily. Moving the tables around does not improve the placement of the lines.
Readability is a key requirement for a model, I would really like this feature added soon
It should be noted here that the difference between logical and physical models is not just as simple as having different names / labels for items. In the logical model, we display content logically, in business terms. How that is physically modelled, can be quite different. In other words, we might logically describe a customer in the logical, but in the physical model, we might split Customer out into Applicant, Lead, Qualified Lead...etc. One table in the logical might result in numerous tables in the physical. Another example would be the implementation of a party reference model in the physical, that is a completely different implementation to the logical.
So...what we actually need, is the ability to define Conceptual, Logical and Physical models, and to provide TRACEABILITY from the conceptual, to the logical and the physical. So that we can say, this physical model is an instantiation of this logical model. Going deeper, we should be able to even link entities and attributes from the higher level to the lower level.
SQLDBM is a great tool for designing the physical data model. I am using it extensively, but in order for me to use it more readily in large scale enterprises, I would need this feature to facilite true enterprise data modelling.
Customer support service by UserEcho