Page 1 of 1

Add Database Constraint without associantions in the model

Posted: Thu 20 Jan 2011 14:21
by kkara
Hi,

I'm using the Entity Developer with a Model-First Approach. The database is almost exclusively generated from the model.

Now, I have a somewhat strange requirement. My goal is to be able to add Constraints to the Database without enforcing them in my model. To achieve that I simply add a constraint and configure the ends manually.

The problem is that by creating a constraint that way, two things happen in the XML under the node :

1. An element is added that describes the constraint. Cool!
2. An element is added under the element. Not cool! It renders the model invalid and prevents code from being generated (even though database generation works like a charm).

Even if I delete the element manually, every time I open the model in Entity Developer it keeps getting added.

I know this is minor, but it keeps getting on my nerves :)

Thank you and congratulations for your work on the Entity Developer...

Posted: Fri 21 Jan 2011 16:20
by AndreyR
We will investigate the possibility to add this functionality.

Posted: Fri 04 Feb 2011 16:35
by AndreyR
We have added the ConstraintSet property for the Storage constraints. If you clear this property, no conceptual association will be added to the model.

Posted: Fri 11 Feb 2011 11:07
by AndreyR
The new 3.20.81 build of Entity Developer for SQL Server was released yesterday.
This build can be downloaded from the Download page (the trial version) or from Registered Users' Area (for users with active subscription only).
For the detailed information about the fixes and improvements available in dotConnect for Oracle 6.10.103, please refer to this post