• 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: NSManagedObject awakeFromFetch not sent on secondary thread?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSManagedObject awakeFromFetch not sent on secondary thread?

  • Subject: Re: NSManagedObject awakeFromFetch not sent on secondary thread?
  • From: Ben Trumbull <email@hidden>
  • Date: Wed, 17 Mar 2010 14:00:43 -0700
> However I still don't understand why awakeFromFetch is not sent in secondary
> thread - I can't find any clue in documentation? Is this a bug or is it a
> feature? I'm running on 10.6.2.

Did you try setting the NSFetchRequest option -setReturnsObjectsAsFaults:NO ?  The default setting will attempt to lazily copy the fetch results into the managed objects as much as possible (the data is still fetched eagerly from the database by -executeFetchRequest: as you can see with SQL logging) Perhaps you are always touching the objects on the main thread eagerly so there is no apparent difference there.

- Ben



_______________________________________________

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
  • Prev by Date: Re: Core Animation and interaction
  • Next by Date: RESOLVED: Blocked Reads
  • Previous by thread: NSUndoManager _NSundoInvocation Over-Release
  • Next by thread: setStringValue problems with dynamically loaded views.
  • Index(es):
    • Date
    • Thread