• 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: Concurrent MOCs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Concurrent MOCs


  • Subject: Re: Concurrent MOCs
  • From: Chris Hanson <email@hidden>
  • Date: Mon, 10 Jun 2013 18:43:19 -0700

On Jun 10, 2013, at 6:28 AM, Roland King <email@hidden> wrote:

> How about the objects which are then owned by the MOC, the managed objects? Do any messages sent to them, even a property or relationship lookup, need also to be in a performBlock: call on the MOC owning those objects?

For an NSManagedObjectContext using private queue concurrency, yes. The cardinal rule of Core Data is that virtually any interaction with a managed object other than memory management is also an interaction with its context.

This is actually particularly true for property (attribute and relationship) access, because that can fire or traverse faults.

  -- Chris


_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Concurrent MOCs (From: Roland King <email@hidden>)

  • Prev by Date: Re: NSURLRequest returning bizarre page
  • Next by Date: Re: NSURLRequest returning bizarre page
  • Previous by thread: Concurrent MOCs
  • Next by thread: NSURLRequest returning bizarre page
  • Index(es):
    • Date
    • Thread