I\'m still fairly new to Core Data and am trying to understand why it requires the passing around of a NSManagedObjectContext. As I understand it, passing the context is needed so that multiple thread
I have a memory-intensive iOS app and I\'m working on making sure that memory usage does not build up ove开发者_开发知识库r time.My app has a \"main\" context that lives for the lifetime of the app, w
I\'m creating a simple interface with NavigationController and BandListViewController(UITableViewController) inside Interface Builder and setting the delegation to AppDelegate properties.
I am trying to link a value that\'s already in category to the wod entity. Since I do want to call a new record for each record of wod for a category. Not sure how to do this. I was thinking of using
I am having issues with a CoreData-based iOS app when it tries to build the initial DB from data sent from the server.Basically, the server sends down 1MB chunks of objects (about 3,000 per chunk), an
I\'ve been playing with XCode4 and seem to have gotten myself in a bit of trouble.I was trying to organize my project on disk to be prettier and better reflect the groups I had set up but I have appar
I have two managed object contexts, A and B.These two contexts are kept in sync by merging changes 开发者_如何学Pythonfrom one to the other whenever they\'re saved (by monitoring NSManagedObjectContex
I have a View Controller that manages a view which is always shown in editing mode. The view is essentially a table view similar to that of a contact\'s details in Apple\'s Contacts app. The model und
This bug is weird since it happens at some points while program is running. After saving the context around thirty times, the program crashes.
I am currently working on an app that heavily relies on Core Data.I use a navigation controller to push and pop views around.When I go
加载中,请稍侯......