• 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 async fetch request
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CoreData async fetch request


  • Subject: Re: CoreData async fetch request
  • From: Karl Hsu <email@hidden>
  • Date: Tue, 6 Oct 2009 21:16:40 -0700

On Oct 6, 2009, at 1:08 AM, Ben Trumbull wrote:

Core Data is just passing the query off to the database. I'm not sure why you think going to the database directly will do anything for the 179.9 / 180.0 seconds it takes to evaluate the query in the database.

I suspect that he wants a background thread that simply sits and passes results back to main thread directly from sqlite3_step(). I don't know of a way to incrementally return results in CoreData when the query is very expensive; using setOffset will re-issue the query and even fetching just IDs still has to wait for the entire query to finish before return any results.


Karl

_______________________________________________

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: 
 >Re: re: CoreData async fetch request (From: email@hidden)
 >Re: CoreData async fetch request (From: Ben Trumbull <email@hidden>)

  • Prev by Date: Re: Suggest reasons for this crash?
  • Next by Date: Issues with NSWindowDelegate on multiple Mac OS X platforms
  • Previous by thread: Re: CoreData async fetch request
  • Next by thread: Populating a submenu via bindings?
  • Index(es):
    • Date
    • Thread