Unfortunately, we don’t yet support generating SQL code to enforce most of the external constraints. The external uniqueness constraints should come through (as long as everything they were attached to ended up in one table), but that is about all.
Is there a particular kind of constraint (e.g. subset, equality, exclusion, etc.) that you would see as being a higher priority than the others? If so, we can try to focus our efforts on that one.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I would like to post my .orm for comments since its my fist real-world model (since being a student at Neumont and working on the NORMA project at that time) BUT what I am working on is for my employer I must first get permission to "publicize" it :)
In the even I do post my .orm I will use the open discussion.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a diagram with a number of external constraints, none of which have any associated ddl for sql server generated. What might be the problem?
Unfortunately, we don’t yet support generating SQL code to enforce most of the external constraints. The external uniqueness constraints should come through (as long as everything they were attached to ended up in one table), but that is about all.
Is there a particular kind of constraint (e.g. subset, equality, exclusion, etc.) that you would see as being a higher priority than the others? If so, we can try to focus our efforts on that one.
Can you share the .ORM file with us so that we can get more details?
Jim,
I would like to post my .orm for comments since its my fist real-world model (since being a student at Neumont and working on the NORMA project at that time) BUT what I am working on is for my employer I must first get permission to "publicize" it :)
In the even I do post my .orm I will use the open discussion.
For Jim:
https://sourceforge.net/forum/forum.php?thread_id=1926327&forum_id=535791