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

Re: CoreData pagination


  • Subject: Re: CoreData pagination
  • From: Jim Correia <email@hidden>
  • Date: Mon, 23 Jun 2008 21:05:51 -0400

On Jun 23, 2008, at 8:53 PM, Quincey Morris wrote:

The problem is that Core Data doesn't use rows -- it doesn't have any intrinsic ordering of objects (that's why unsorted results are always sets, not arrays). There's no general concept of the "next" 10000 objects.

To query in chunks, you need to implement your own concept of ordering (which may or may not be easy, depending on your requirements).

Relationships are intrinsically unordered.

When fetching objects though, the order can be as deterministic as you need it to be; set an appropriate sortDescriptor on the fetch request.

Jim
_______________________________________________

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


  • Follow-Ups:
    • Re: CoreData pagination
      • From: Ian <email@hidden>
References: 
 >CoteData pagination (From: Ian <email@hidden>)
 >Re: CoreData pagination (From: Quincey Morris <email@hidden>)

  • Prev by Date: Re: CoreData pagination
  • Next by Date: Re: NSTreeController filter contents
  • Previous by thread: Re: CoreData pagination
  • Next by thread: Re: CoreData pagination
  • Index(es):
    • Date
    • Thread