• 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
Will calling entity.name cause a fault to fire?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Will calling entity.name cause a fault to fire?


  • Subject: Will calling entity.name cause a fault to fire?
  • From: email@hidden
  • Date: Wed, 11 Jan 2006 13:30:59 -0800

I'm working on changing my model to use more abstracted relationships, and want to get a collection based on the entity type, but using a fetched relationship, I will be dealing with a lot of objects so I want to prevent faulting to be fired, so checking the entity name seems the sensible route.

I know calling [NSManagedObject entity] will not fire a fault, but I just would like to confirm if making a fetched relationship in Xcode Modeler UI setting the predicate to entity.name == "myEntity" would not cause a fault to be fired.

Thanks for any help.

Andre
_______________________________________________
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: Will calling entity.name cause a fault to fire?
      • From: Miguel Sanchez <email@hidden>
  • Prev by Date: Re: Force an Application to crash : possible ?
  • Next by Date: Re: Force an Application to crash : possible ?
  • Previous by thread: Re: Force an Application to crash : possible ?
  • Next by thread: Re: Will calling entity.name cause a fault to fire?
  • Index(es):
    • Date
    • Thread