I always figured it was a defect in EOF in that it did not enforce
relation().count() > 0. IIRC, we added that in our validation
framework. It is perfectly valid in ER modelling to have a 1..N
relationship, so I would not consider this to be a model error.
Chuck
On Dec 13, 2006, at 4:51 PM, Mike Schrag wrote:
If a relationship is marked to-many, should entity modeler disallow
marking that mandatory? Should it error? Should it warn? I think
at the very least it's a warning, and quite possibly should be not
allowed.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/chill%
40global-village.net
This email sent to [EMAIL PROTECTED]
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
