Jacob Gorban

Regarding parent-child contexts. I've found and also read in other blogs that parent-child context do not perform better. They may be easier to set up but have (or at least...

`-currentContext` and `context` have different functions. The former returns the context associated with current scheduler. The latter creates a new child context from the current one.

Regarding `findAll` and `findOne`. There are actually already two of them. The class methods in `NSManagedObject (ReactiveCoreData)` and instance methods in `RACSignal (ReactiveCoreData)`. Usually the class methods are more useful...

The `insert` method indeed doesn't have anything to do with ReactiveCocoa itself but it's a good shorthand. It integrates with RCD for getting current context. ``` + (instancetype)insert; { return...

> I was trying to say that the name of the latter method may be a bit confusing to some people. You might be right and `context` might be a...

I see your point (and my bug). Maybe it should be something like this instead: ``` objc - (RACSignal *)findAll:(NSString *)entityName; { NSFetchRequest *fetchRequest = [NSFetchRequest fetchRequestWithEntityName:entityName]; return [self mapReplace:fetchRequest];...

Maybe it's better to just remove these two methods from the code, then.

Well, the idea here is that the main context is really the main context. Yes, it's also the parent, but it should be the real main context. `- (void)rcd_mergeChanges:(NSNotification *)note;`...

@fatuhoku The funny thing is that I don't program much for iOS. My focus is on my applications. Mac's AppKit doesn't have the `NSFetchedResultsController`. As such I don't know enough...

I'm getting this intermittently as well. This is for a rather large DMG, of more than 150MB