May a NSManagedObjectContext re-fault objects automatically?

Posted by frenetisch applaudierend on Stack Overflow See other posts from Stack Overflow or by frenetisch applaudierend
Published on 2010-05-23T18:57:57Z Indexed on 2010/05/23 19:00 UTC
Read the original article Hit count: 471

Filed under:

core-data

|

nsmanagedobjectcontext

|

faulting

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.

My approach to this would be to use multiple NSManagedObjectContexts and then before a background thread does a -save: operation, I fetch the object the user is currently working on and fire the fault for all its properties and relationships recursively. This way I have all objects the user could act with in my NSManagedObjectContext without seeing the already updated values.

But this can only work if the NSManagedObjectContext cannot decide himself that e.g. memory usage is too high, and starts faulting objects which I do not explicitly reference (other than through the NSManagedObject relationship).

So the question is, can the NSManagedObjectContext decide that an object needs to be re-faulted, without intervention from my side?

Thanks for your effort, Markus

© Stack Overflow or respective owner

Related posts about core-data

Records not being saved to core data sqlite file

as seen on Stack Overflow - Search for 'Stack Overflow'
I'm a complete newbie when it comes to iOS programming and much less Core Data. It's rather non-intuitive for me, as I really came into my own with programming with MATLAB, which I guess is more of a 'scripting' language. At any rate, my problem is that I had no idea what I had to do to create a… >>> More
iPhone - Core Data crash on migration

as seen on Stack Overflow - Search for 'Stack Overflow'
I have problems, when i install app from Xcode all works but if I build app and install it from iTunes I have an error with the database at launch. This happens only than i have changes in the core data model and need to migrate to a new version. At first launch at crashes with message: Thread 0: 0… >>> More
CoreData update problems

as seen on Stack Overflow - Search for 'Stack Overflow'
My app makes updates in background thread then saves context changes. And in main context there is a table view that works with NSFetchedResultsController. For some time updates work correctly, but then exception is thrown. To check this I've added NSLog(@"%@", [self.controller fetchedObjects]); to… >>> More
Core Data managed object context thread synchronisation

as seen on Stack Overflow - Search for 'Stack Overflow'
I'm have an issue where i'm updating a many-to-many relationship in a background thread, which works fine in that threa, but when I send the object back to the main thread the changes do not show. If I close the app and reopen the data is saved fine and the changes show on the main thread. Also using… >>> More
UITableView Core Data reordering

as seen on Stack Overflow - Search for 'Stack Overflow'
I know this question has been asked before, and I took a look at the answer to this question. However, I'm still confused as to how to implement reordering with a UITableView in a Core Data project. What I know is that I need to have a "displayOrder" attribute in my Entity to track the order of items… >>> More

Related posts about nsmanagedobjectcontext

How to not persist NSManagedObjects retrieved from NSManagedObjectContext

as seen on Stack Overflow - Search for 'Stack Overflow'
Hi I parse an xml file containing books, for each new node I go: Book *book = (Book*)[NSEntityDescription insertNewObjectForEntityForName:@"Book" inManagedObjectContext:managedObjectContext]; To obtain an NSManagedObject of my Core Data Book Entity, I then proceed to populate the managed Book… >>> More
Iterate through NSManagedObjectContext objects?

as seen on Stack Overflow - Search for 'Stack Overflow'
I want to iterate through all of the objects in my NSManagedObjectContext, and update them manually. Then, every managed object should be updated. What's the best way to do this? >>> More
May a NSManagedObjectContext re-fault objects automatically?

as seen on Stack Overflow - Search for 'Stack Overflow'
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. My approach to this would be to use multiple NSManagedObjectContexts and then before a background thread does a -save: operation, I fetch the object the… >>> More
Reasons for NSManagedObjectMergeError error on [NSManagedObjectContext save:]

as seen on Stack Overflow - Search for 'Stack Overflow'
I have a application that combines threading and CoreData. I and using one global NSPersistentStoreCoordinator and a main NSManagedObjectContextModel. I have a process where I have to download 9 files simultaneously, so I created an object to handle the download (each individual download has its… >>> More
NSManagedObjectContext returning nil iphone

as seen on Stack Overflow - Search for 'Stack Overflow'
Hey, I created a class ServerModel for my app and in it I want to make a connection to the Sqlite database I have on the device, but anytime I go to check my NSManagedObjectContext it is returning null. While the same work well in my other class RootViewController In my appdelegate I am doing … >>> More