• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: one-to-many relationship question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: one-to-many relationship question


  • Subject: Re: one-to-many relationship question
  • From: Michael Gargano <email@hidden>
  • Date: Thu, 08 Sep 2011 12:58:57 -0700
  • Acceptlanguage: en-US
  • Thread-topic: one-to-many relationship question

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 the B1's to the A3 relationship

	I go to commit A3 and it tries to commit the B1's first, which explodes because of the FK constraint to A3.

	This isn't happening anywhere else so I'm not sure what's wrong (I'm hoping it's not just luck), but basically I'm asking if A1,A2,A3 "own" B1 is that the indication to EOF that B1 needs to be committed second, after a PK has been generated and committed on A3

Thanks.
-Mike



On Sep 8, 2011, at 3:40 PM, Philippe Rabier wrote:

> Michael, there are 2 distinct notions.
>
> Cascading delete is clear enough I guess.
>
> When an object A "owns" an object B, that means that B can't live
> without A. The consequence is when you remove the relationship between
> A and B, B will be deleted automatically (think about invoice and
> invoice items).
>
> Sorry, I don't understand the second question. Basically, when you
> create A, you must create B and link B to A as usual.
>
> I don't want to lose you but there is another case: if you have a to-
> one between Entity A and Entity B, if EA "owns" EB and you check
> "propagate primary key", object B will be automatically created when
> you create object A. That's not your question but just in case…
>
> Bests,
>
> Philippe
>
> On 8 sept. 11, at 20:59, Michael Gargano wrote:
>
>> 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
>>
>> _______________________________________________
>> 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
>
>


 _______________________________________________
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

  • Follow-Ups:
    • Re: one-to-many relationship question
      • From: Ramsey Gurley <email@hidden>
References: 
 >one-to-many relationship question (From: Michael Gargano <email@hidden>)

  • Prev by Date: Re: Entity Validation Exception Question
  • Next by Date: Re: Entity Validation Exception Question
  • Previous by thread: Re: one-to-many relationship question
  • Next by thread: Re: one-to-many relationship question
  • Index(es):
    • Date
    • Thread