This content has been marked as final. Show 2 replies
Thanks for reporting this problem. I have logged a bug on it.
I have also tried this through import via the data dictionary but it also doesn't pick up the check constraint in the compare models.This is probably because it is treating the Table in the database as a different Table than the one in your model (because the one in the database has a user/schema associated with it).
When the Compare Models panel is displayed during the import from database, you can go to the "Compare Options" tab and unset the 'Use "Schema" Property' option and then select the "Refresh Trees" button.
The database Table should then be treated as the same Table as the one in your model, and the Check Constraint values should show up as a difference in the 'LOV Constraint' property for the Column (on the Details tab).
Merge should then import these constraint values into your model.
The problem with importing the DDL file containing
ALTER TABLE "PAREN_TEST_TABLE" ADD CONSTRAINT "CHK_OPEN_PAREN" CHECK (open_parenthesis in ('(', NULL)) ENABLE;should be fixed in Data Modeler version 3.3 EA2 which is now available on OTN.