Joined: 18 Feb 2011
Topic: Extra validations
Posted: 18 Feb 2011 at 9:34am
I get the following validation errors in SQL Server 2008, that you might add to the validator functions in Data Modeler.
Introducing FOREIGN KEY constraint 'Clients_Declarations' on table 'Declarations' may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other FOREIGN KEY constraints.
Cannot create the foreign key "Becons_Clients" with the SET NULL referential action, because one or more referencing columns are not nullable.
I know how to solve them, but it is just better if they are validated or automatically applied to the referenced fields (the second one could give a warning when choosing 'Set to null' in the constraint editor.
Joined: 12 Jul 2010
|Post Options Quote Reply Posted: 21 Feb 2011 at 5:22am|
You are right, Data Modeler project validator should generate a warning for this type of relationship in SQL Server databases. We will include that.
TMS Software Team
|Forum Jump||Forum Permissions
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum