Re: Confused with delete rules in EntityModeler
Re: Confused with delete rules in EntityModeler
- Subject: Re: Confused with delete rules in EntityModeler
- From: David Avendasora <email@hidden>
- Date: Tue, 26 Apr 2011 09:08:08 -0400
On Apr 26, 2011, at 8:20 AM, Markus Ruggiero wrote:
> What confuses me is that there are delete rules for both directions of a relationship which makes no sense to me.
Please give us more information about these two relationships. Cascade Delete rules should not go in both directions. I can't think of any valid uses, and it seems logical (To me. Shut-up Chuck) it would cause exactly what you are seeing.
> And what should those be for the flattened relationship?
I'm guessing that they should be "nullify" or "do nothing"
>
> Here is the model:
>
> ElectronicDocument <-->>TextblockReference<<-->Textblock. TextblockReference is more than a simple m:n join table. However I have a flattened m:n relationship between ElectronicDocument (called textblocks) and Textblock (called documents) across TextblockReference. There are other entities hanging off TextblockReference: TextblockReferemce<-->>Params<-->>Data.
All that seems perfectly fine.
> When I delete an ElectronicDocument I want all associated TextblocReferences and everything hanging off it be gone, however Textblock should stay around but not have that particular ElectronicDocument object in its flattened relationship anymore.
That is exactly how it should work. There's either something wrong in your model, or the Oracle cascade delete is the culprit. Let's hope it's the model. That's in your control to fix.
Dave _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden