Is it safe to perform save operations on an NSManagedContext object when using Objective-C fast enumeration

Question

I was wondering if this sort of code would be ok to use

NSManagedObjectContext *moc = [(AppDelegate*)[[UIApplication sharedApplication] delegate] managedObjectContext];
for (NSDictionary *dict in objects) {
            Object *object = [NSEntityDescription insertNewObjectForEntityForName:@"object"
                                                     inManagedObjectContext:moc];
            // Populate model fields with appropriate dictionary keys
        }

Reason why I ask is that you're advised to not pass references to a managed object context object across threads and wondering if that is indeed what is occurring here.

score 3 · Accepted Answer · answered Oct 19 '13 at 22:11

3

Fast enumeration using for (object in collection) has nothing to do with threads. All of this code runs on the same thread.

answered Oct 19 '13 at 22:11

Kurt Revis

27,695
5
68
74

score 0 · Answer 2 · edited May 23 '17 at 11:57

0

If that insert operation is threaded you should consider creating a backgrounded NSManagedObjectContext to handle it, which is a post way too big and answered on SO before.

performBlock:

edited May 23 '17 at 11:57

Community

1
1

answered Oct 19 '13 at 22:03

David Wong

10,284
3
39
34

score 0 · Answer 3 · answered Oct 19 '13 at 22:12

0

You are using one ManagedObjectContext,the are no thread problem in your code. You are doing it the right way.All the code is sequential. If you want to use multiple context, each one in a thread, you should take care of multithreading.

answered Oct 19 '13 at 22:12

samir

4,501
6
49
76

Is it safe to perform save operations on an NSManagedContext object when using Objective-C fast enumeration

3 Answers3