You are missing the code to do just that policy. The model rules are simplistic and so owning means it owns and removes so your rules don’t work together but you’d be needing and wanting to trigger that delete with your own policy and code
> On Feb 27, 2022, at 6:45 AM, OCsite via Webobjects-dev > <webobjects-dev@lists.apple.com> wrote: > > Hi there, > > as I am checking all my relationships to make sure I did not another mistake, > I've bumped into something strange. > > It looks like EOF prohibits a combination of “owns destination” and the > “deny” delete rule. > > Can perhaps anybody explain the rationale behind that? > > I must be overlooking something of importance, for it seems to me it is quite > acceptable approach something like “a company owns all the departments. > Whenever one is removed from the relationship, it should be deleted, no point > for it existing separately. Still, I want to prevent deletion of a whole > company which contains a non-zero number of departments; to prevent user > errors, if somebody does want to delete a company, I want him to remove all > its departments first”. > > What am I missing? > > Thanks, > OC > > _______________________________________________ > 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: > https://lists.apple.com/mailman/options/webobjects-dev/jtayler%40oeinc.com > > This email sent to jtay...@oeinc.com _______________________________________________ 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: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
