The setup: I have two managed contexts setup (on an iPhone application). A main context that I use for most queries and a background context I use for long running operations that I want to happen in
I a, working on coredata iphone TabBar app and passing appdelegate managedObjectContext to all the views and subviews.At some instance i need to create new record for entity A and while entity A didn\
after I insert a ManagedObject into a context I\'d like to fetch it later but before saving the context (I\'d save after all objects are inserted). It appears that querying the context later with开发者
Simple, common pattern I can\'t开发者_开发问答 find in Apple\'s docs: Load a coredata store Download new data, creating objects
You have to have one per thread, but beyond that ... should you have more? Is it harmful to have more?
I don\'t understand the output of NSLog for the array returned by a NSFetchRequest. I\'m reading my database and placing the contents in an array, looping through the array and then outputting the c
Any idea why //should save the object context. NSError *error; if (![managedObjectContext save:&error]) {
I have what I assume is a fairly standard setup, with one scratchpad MOC which is never saved (containing a bunch of objects downloaded from the web) and another permanent MOC which persists objects.
I am trying to create an application which allows background threads to update core data objects while the user might be reading the same data.
I\'m relatively well versed in CoreData and have been using it for several years with little or no difficulty. For the life of me, I can\'t figure out why
加载中,请稍侯......