I have it set as Deny instead of Nullify (I don't want to allow
deleting a FeeCycleType unless all FeeCycles pointing to it are
deleted).
I'll go ahead and try setting it to nullify, but I'm still confused
how the serialization process is finding the deleted FeeCycles when
the FeeCycleType doesn't appear to have any references to it.
On 7/26/06, Andrus Adamchik <andru..bjectstyle.org> wrote:
>
> On Jul 25, 2006, at 9:24 PM, Mike Kienenberger wrote:
>
> > In my testing, I submit a web request that creates a new object,
> > submit a web request which creates another set of new objects and
> > assign it to relationships with my first new object, then submit a web
> > request which deletes the set of new objects.
>
> Mike, just a guess. Looks like the reverse relationship of
> FeeCycleType.feeCycleList doesn't have nullify delete rule. So you
> can either set such delete rule, or manually break relationship after
> delete. This explanation looks too simple, but all the symptoms point
> to it.
>
> Andrus
>
>
This archive was generated by hypermail 2.0.0 : Wed Jul 26 2006 - 15:21:42 EDT