I am trying to merge in changes in an addingManagedObjectContext into my main managedObjectContext by calling mergeChangesFromContextDidSaveNotification using an NSFetchedResultsController with CoreDa
saving the managedObjectContext seems to eat the NSUserDefault NSString *defaultSiteUrl = [[NSUserDefaults standardUserDefaults] objectForKey:kSelectedSiteUrlKey];
We have an NSTextView and some data saved about its contents in a core data Managed object context.Everything works great while the managed object context st开发者_如何学Goays in memory.However when w
This is more a why does this work and that doesn\'t kind of question... I am using CoreData over multiple threads. I have two threads being spawned off of the main threads and they both perform a sim
In prepping my app for an update, I\'ve found a weird issue that\'s so far been a bit of a head-scratcher.
When a user double taps a view in my application a uipopovercontroller presents him with the fields which he can edit. (Much like in the iPad calendar app)
I need to delete my persistent store (doing it object by object is not practical because I have over 100,000 objects). I\'ve tried this:
The Apple \"Concurrency with Core Data\" documentation states the following when discussing using core data with background threads.
I have 开发者_开发技巧entities that are managed by Core Data and have several cases where, within a single method, I set some attribute values that will result graph changes that Core Data will enforc
Is there any way to get notified when an NSManagedObjectContext is about to insert an object, and then prevent 开发者_运维知识库this? Maybe a method like -shouldInsertObject: or something.
加载中,请稍侯......