On Mar 5, 2009, at 8:59 AM, Ramsey Gurley wrote:
On Mar 5, 2009, at 7:15 AM, David Avendasora wrote:
I also get the error if it the relationship is set to "Owns
Destination" and the delete rule is "Deny"
Having these two settings, unless I'm missing something, are in
direct conflict with each other.
I think if Owns Destination is checked, then the following should
automatically happen:
1) Delete Rule should be set to "Cascade" and drop down disabled
(anything else is in conflict with Owns Destination).
2) If there is an inverse relationship it should be set to
"Required" (not Optional) and the checkbox disabled with a note
stating that the relationship is Required by the Owns Destination
setting on the inverse relationship.
So yes, cascade delete appears to be the only option that makes
sense when the owner is deleted. (http://developer.apple.com/documentation/WebObjects/UsingEOModeler/5WorkingWithRelationships/chapter_5_section_2.html
)
On a similar note, if you create a to-many relationship in entity
modeler, by default the delete rule is set to nullify but the
reverse to-one is set as mandatory... it seems to me that the
default should be deny delete.
Yep. Those are certainly in conflict.
Model validation seems appropriate too. I filed it a while back (http://issues.objectstyle.org/jira/browse/WOL-924
) but it has no votes so far... 0:-)
Voted!
I have a feeling that there just isn't any validation on agreement
between a relationship and it's inverse. I've added a few more feature
requests to JIRA in regards to this, but I doubt they are all-
inclusive on what the validation should include.
Dave
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
