I'm using Core Data with an in-memory store, and I want to wipe it completely at some point. Most of the questions that I've found that relate to this are in regards to an on-disk store and involve deleting the store file or all the managed objects.
Is there a simpler way when it's in-memory? Can I just set something to nil and be done with it?
In the case of an in-memory store remove the store from the NSPersistentStoreCoordinator using removePersistentStore:error:. At that point you can create a new in-memory store attached to the coordinator if you want, which will give you a blank slate at the store level - which seems to be the focus of your question.
Note that if you are retaining managed objects that you fetched from an NSManagedObjectContext those may still stick around, and when a fault is fired on them after you have removed your in-memory store they can throw exceptions. It's advisable that if this is likely (usually because you are using a single context, or are not good about using Instruments to track memory use) that you also call reset on your managed object context(s) and remove any lingering strong references to managed objects.
So using your code: When you create the in-memory store, specify a URL so you can identify it later:
if (![_persistentStoreCoordinator addPersistentStoreWithType:NSInMemoryStoreType configuration:nil URL:[NSURL URLWithString:@"memory://0"] options:nil error:&error]) {
In your resetStack method you would remove it after you reset and removed your managed object context(s):
[[self persistentStoreCoordinator] removePersistentStore:[[self persistentStoreCoordinator] persistentStoreForURL:[NSURL URLWithString:@"memory://0"] ] error:&error];
If you do not reset and remove the context(s) first, you will start to see exceptions as the objects get faults fired that no longer have a store to go to.
You should listen for the notifications NSPersistentStoreCoordinatorStoresDidChangeNotification and NSPersistentStoreCoordinatorStoresWillChangeNotification anywhere you are using Core Data, so that when a store is added or removed you can act accordingly. For example, if you call your resetStack method that removes a store, you should see the NSPersistentStoreCoordinatorStoresWillChangeNotification and use that opportunity to stop whatever you are doing that may be accessing that store. When NSPersistentStoreCoordinatorStoresDidChangeNotification is received, you would complete your tear down of objects or processes that may be using Core Data - like an NSFetchedResultsController that may be attempting to access the store that was just removed. Once the old store has been removed you want to add a new, clean one. When that happens you will get the same notifications, with payloads that indicate a store was added - and at that time you can create new managed object contexts and fetched results controllers to replace the old ones.
This is all actually a lot simpler than it sounds. Nonetheless, make sure you're doing all of this for the right reasons.
As I've noted in my comment:
It is sufficient to set the CoreData stack components to nil
Assuming a boilerplate stack you could achieve that by:
In you AppDelegate .m file, make the core components writable:
@interface DSAppDelegate ()
@property (readwrite, strong, nonatomic) NSManagedObjectContext *managedObjectContext;
@property (readwrite, strong, nonatomic) NSManagedObjectModel *managedObjectModel;
@property (readwrite, strong, nonatomic) NSPersistentStoreCoordinator *persistentStoreCoordinator;
@end
Add a reset function:
- (void) resetStack
{
self.managedObjectContext = nil;
self.persistentStoreCoordinator = nil;
self.managedObjectModel = nil; //not necessary if store will not change
}
calling resetStack will release memory occupied by the in-memory store (might take some time if the store is heavily populated).
Remember not to use any stack component during the reset, or keeping strong references to them as you might not get the stack to reset properly
This is demonstrated in THIS test project.
(In instruments, view memory allocations relative to the console output).
Edit:
@quellish solution is more elegant (removing and adding a new store), and instead of replacing the managed context of the view controller you need only reset it, although you will have to nullify your FRC in any case.
In case of Core Data In-memory store, the data is persisted until your app is quit or suspended. So you can just leave it to the OS to suspend your app when there are any memory issues in the device.
Alternatively you can force the app to quit by calling exit(0), in the applicationDidEnterBackground:(UIApplication *)application method. But this is not recommended.
The safest method would be to manually iterate through your database, deleting all the content.
