Hi all,
Quick question, does delete on cascade imply owns destination? Also,
does checking owns destination force the insertion of the destination objects
after the insertion of the source entity?
I think David LeBer answered this for me once, but I forgot.
Thanks.
-Mike
This is what I know.
Owns destination on a toOne relationship means every time a master record is
created, a child record will also be created. The primary key of the child
will be set to the primary key of the master.
Cascade delete means when you delete the master record, the child
Don't worry you're not losing me. :) Basically, this is what's happening
I have entity A1 with single table inheritance children A2 and A3
A1 has - B1, which is also passed on to the children
I'm creating a new A3 instance and a bunch of new B1 instances, I add
Hi Mike,
That's a different question/answer entirely (^_^)
You need to order your adaptor operations if your database can not do deferred
foreign key constraints. You can do order your ops with a property:
com.webobjects.eoaccess.ERXEntityDependencyOrderingDelegate.active=true
Keep in mind
Hi Ramsey,
Thanks! It was the deferred assignment. I had added those FKs myself
(aka not using migration), I didn't realize that deferment was how assignment
order was being guaranteed (or not guaranteed for that matter).
Thanks again.
-Mike
On Sep 8, 2011, at 4:18 PM, Ramsey Gurley
the destination objects altogether.
Cheers
Cheong Hee
- Original Message -
From: Paul D Yu p...@mac.com
To: Michael Gargano mgarg...@escholar.com
Cc: WebObjects webobjects-dev webobjects-dev@lists.apple.com
Sent: Friday, September 09, 2011 3:03 AM
Subject: Re: one-to-many relationship question
