I think the most ideal would be no default.. half the time I've left them as is (regardless of what default value there could have been), I've regretted it :)
Of course, that probably isn't practical. But still, I think there is definitely a moral... one size doesn't fit all for delete rules, and user consideration should be given to them. Maybe we can highlight it in documentation? Cris On 12/4/06, Michael Gentry <[EMAIL PROTECTED]> wrote:
I actually prefer the No Action default. To me, this doesn't do anything unexpected. Perhaps the best solution would be a preference setting where you can choose your default? /dev/mrg On 12/3/06, Andrus Adamchik <[EMAIL PROTECTED]> wrote: > > Note that the default choices are sensitive to the preferences and > conventions used in modeling the DB schema. E.g. "Nullify/Nullify" > for a pair of complimentary relationships will result in exceptions > if FK's are not nullable. That's what I meant by "correct defaults" - > they are not always obvious. But Nullify can probably be a "good > enough" default. > > Andrus > > > On Dec 3, 2006, at 11:12 PM, Øyvind Harboe wrote: > > On 12/3/06, Tore Halset <[EMAIL PROTECTED]> wrote: > >> Hello. > >> > >> I think "Nullify" is a better default than "No Action" as it matches > >> what I want to do in most cases. I sometimes use "Cascade", but it is > >> not a good default value :) > > > > I switched to using nullify (text search & replace) as default rule > > and CayenneModeler threw up warnings(I forget precisely which), but I > > had to switch some relationships to "Deny".... > > > > > > -- > > Øyvind Harboe > > http://www.zylin.com > >
