On Thu, Feb 26, 2009 at 9:02 AM, Jon C. Munson II <jmun...@his.com> wrote:
> Interestingly enough, as I wanted my objects inserted in a particular order, > I had to call save after each insertion (no big deal as I don't have that > many records and this is a one-time thing) - the MOC didn't save the records > in the order I had created them, but inserted them in no particular order > (at least from the tool I used to examine the tables). Despite the -save > being called, a few were still out of order, but not critically so. Also clearly spelled out in the Core Data Programming Guide. :-) Core Data deals with sets, not arrays. A set is unordered. This is done because of the faulting mechanism. Particularly with the SQLite store type, for efficiency, sets or subsets of your desired collection are retrieved (faulted in) as needed. This cannot be ordered. If you want to maintain the order of a collection, you need to add a -sortOrder attribute (or something similar) to your entity and sort them (either in the fetch or after). There are at least a dozen threads on this subject in the list archives (many of which I participated in over the years). -- I.S. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
