• 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: CoreData relationships in IB
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CoreData relationships in IB


  • Subject: Re: CoreData relationships in IB
  • From: mmalcolm crawford <email@hidden>
  • Date: Sun, 22 May 2005 15:16:42 -0700


On May 22, 2005, at 2:51 PM, T Reaves wrote:

If all you've done is bound a text field's 'value' to a property of objectB, I'm not sure why you'd expect an instance of ObjectB to be created automatically if none exists?
Just as you would if Core Data and bindings were not involved, you still have to instantiate variables... A further issue here, though, is ObjectA a subclass of NSManagedObject? If so, you cannot simply create an instance with 'new' -- it must be inserted into the managed object context etc...

What I'm wanting to do is very common; so common, I thought that perhaps Apple would have added functionality to support it.


It's still not clear what you actually want to do...

You started off saying that "The fields for ObjectB are bound to objectB.field". Do you want objectB to be created only if the user types in a value, or should it be created automatically whether or not the user tries to set a value?

It would not have been too difficult to have added another item in IB's inspector that said 'Create referenced/contained object if nil' or some-such. Needing to manually create contained objects is not bad, but it does increase the amount of work the developer has to do.

Please file an enhancement request -- although my personal feeling is that this sort of logic probably belongs at a layer below the UI.

I do believe that I can create an instance in the managed object context etc. simply by sending the 'new' message via polymorphism.

No, you can't. You can use the convenience method in NSEntityDescription, or you should use NSManagedObject's designated initializer. If you're using an NSController then add: (and for an array controller insert) will create a new managed object and insert it into the bound managed object context etc.

mmalc

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: CoreData relationships in IB
      • From: T Reaves <email@hidden>
References: 
 >CoreData relationships in IB (From: T Reaves <email@hidden>)
 >Re: CoreData relationships in IB (From: mmalcolm crawford <email@hidden>)
 >Re: CoreData relationships in IB (From: T Reaves <email@hidden>)
 >Re: CoreData relationships in IB (From: mmalcolm crawford <email@hidden>)
 >Re: CoreData relationships in IB (From: T Reaves <email@hidden>)

  • Prev by Date: Re: CoreData relationships in IB
  • Next by Date: Re: CoreData relationships in IB
  • Previous by thread: Re: CoreData relationships in IB
  • Next by thread: Re: CoreData relationships in IB
  • Index(es):
    • Date
    • Thread