• 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: Core Data fetch performance
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Core Data fetch performance


  • Subject: Re: Core Data fetch performance
  • From: Joerg Simon <email@hidden>
  • Date: Mon, 12 Nov 2012 15:15:59 +0100

This summs it up really nicely:

http://wbyoung.tumblr.com/post/27851725562/core-data-growing-pains

Links to radar bug reports are within the blog post.

The conclusion it is not usable does not hold under iOS6, since nested contexts work quite wonderfully there, but it shows problems under iOS5.

Generally if you use performBlock and not performBlockAndWhait and do not use a fetched results controller at all and some other tricks, you can get it working quite well also under iOS5, but actually the code you produce is uglier than doing it manually the "old way" using thread confinment and merge by hand. At least in my experience.

But under iOS6 nested contexts rock!
Cheers, Jörg

On Nov 12, 2012, at 1:58 PM, Bob Cromwell <email@hidden> wrote:

> Hi Hunter,
>
> I am very interested in what  bugs they fixed.  Could you please share more about it , e.g.  an official bug fix report ?
>
> Thanks
>
> Bob
>
>> The API changes came in iOS 5 but in iOS 6 they fixed enough bugs to make it work right. :-)
>
>> On Nov 11, 2012, at 4:50 PM, Rick Mann <email@hidden> wrote:
>>
>>>> GCD, along with the Core Data changes in iOS 5 and 6 for handling concurrency, make this much easier than it used to be (or at least cleaner and harder to screw up as badly).
>>>
>>> By the way, what were the changes in iOS 6? I can't find specific Core Data notes for iOS 6, only iOS 5. Thanks!
>>
>>
>> _______________________________________________
>>
>> 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
>
>
> _______________________________________________
>
> 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


_______________________________________________

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: Core Data fetch performance
      • From: Mike Abdullah <email@hidden>
References: 
 >Core Data fetch performance (From: Rick Mann <email@hidden>)
 >Re: Core Data fetch performance (From: Hunter Hillegas <email@hidden>)
 >Re: Core Data fetch performance (From: Rick Mann <email@hidden>)
 >Re: Core Data fetch performance (From: Hunter Hillegas <email@hidden>)
 >Re: Core Data fetch performance (From: Rick Mann <email@hidden>)
 >Re: Core Data fetch performance (From: Hunter Hillegas <email@hidden>)
 >Re: Core Data fetch performance (From: Bob Cromwell <email@hidden>)

  • Prev by Date: Re: How to implement readonly property
  • Next by Date: Re: How to implement readonly property
  • Previous by thread: Re: Core Data fetch performance
  • Next by thread: Re: Core Data fetch performance
  • Index(es):
    • Date
    • Thread