Philippe,
> ... The fact that an EO is deleted when it's removed from the relationship is
> technical consequence of a model. Don't use it because it's practical ...
Um, what other reason is there to use owning relationships? The documentation
says
“If a source object owns its destination obje
Hi OC,
When an EO entity A owns an entity B, consider A and B as a whole. B does not
exist separately. If you'd use a nosql document database, everything will be in
the same document. The best and known examples of usage are invoices or quotes
and their lines.
What you want to do is to preve
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-de
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
