1. Defaults:
I am in favor of NULLIFY/DENY default delete rules (both Kevin and
Andrey mentioned this preference in the Jira comments. CASCADE has too
much potential to do damage to unsuspecting users).
2. Matching DB delete rules with Cayenne delete rules:
Most people don't bother creating them anyways, and also Cayenne
delete rules are somewhat independent from DB delete rules, and don't
have to be in sync. On the other hand duplicating what DB would do at
the ORM layer has some merit, as it ensures that on commit object
layer will match what's in DB, even though DB will attempt some
postprocessing. All in all, my vote would be to ignore DB delete rules
for now.
3. Modeler preference for delete rules:
Also I think that's an overkill. Let's just do the default thing.
Thanks,
Andrus
On Jun 26, 2008, at 4:15 PM, Andrey Razumovsky wrote:
For a week nobody's answering, so I think it's time to make some
decision.
I'd probably prefer NULLIFY-CASCADE, as it was originally suggested.
The
question with reverse engineering is also open.
2008/6/19, Kevin Menard <[EMAIL PROTECTED]>:
Hi all,
There was a little discussion on changing the default delete rules,
per
CAY-436 [1]. Andrey proposed adding two new configuration values
to control
the default rules used. I don't think that's strictly necessary --
we
certainly don't have that now. Before he implements something
that's likely
to affect everyone, I'd like to solicit some more feedback from the
dev
list. Please review the issue and let us know what you think.
Thanks,
Kevin
[1] - https://issues.apache.org/cayenne/browse/CAY-436
