Yes. but this improvement ( NH-2515 ) require more work than removing restriction
2012/8/4 Richard Birkby <[email protected]> > Me neither. I did a git log -G on Hibernate and this looks to be the first > occurrence. > > Did you also find: > http://osdir.com/ml/nhusers/2011-01/msg00304.html > > I don't think there was ever a JIRA raised. > > > Richard > > > On Fri, Aug 3, 2012 at 8:47 PM, Alexander I. Zaytsev < > [email protected]> wrote: > >> Yes, I've seen it. But could not find earlier history of this file. >> >> >> 2012/8/4 Richard Birkby <[email protected]> >> >>> Looks like it was ported over from Hibernate. Original Hibernate code >>> written on 2007-06-29: >>> >>> https://github.com/hibernate/hibernate-orm/blob/master/hibernate-core/src/main/java/org/hibernate/mapping/Collection.java#L301 >>> >>> >>> Richard >>> >>> >>> On Fri, Aug 3, 2012 at 8:05 PM, Alexander I. Zaytsev < >>> [email protected]> wrote: >>> >>>> Does anyone know why there is check >>>> >>>> if (Key.IsCascadeDeleteEnabled && (*!IsInverse* || !IsOneToMany)) >>>> >>>> >>>> https://github.com/nhibernate/nhibernate-core/blob/master/src/NHibernate/Mapping/Collection.cs#L387 >>>> >>>> >>>> ? >>>> >>>> It prevents to use* on-delete="cascade"* in composition with * >>>> inverse="false"* >>>> * >>>> * >>>> I've removed this restriction and all works fine, so I do wonder - why? >>>> >>>> >>> >> >
