Re: CoreData headaches

2016-10-30 Thread Samuel Williams
> CoreData [is] just a pile of confusion with no human explanation[.] I know this doesn't help anyone but I couldn't help but agreeing with this statement. On 31 October 2016 at 16:22, Steve Mills wrote: > On Oct 30, 2016, at 14:11:01, Chris Hanson wrote: >> >> On Oct 27, 2016, at 9:02 PM, Stev

Re: CoreData headaches

2016-10-30 Thread Steve Mills
On Oct 30, 2016, at 14:11:01, Chris Hanson wrote: > > On Oct 27, 2016, at 9:02 PM, Steve Mills wrote: >> >> Yes, the Asset is an NSManagedObject. In this call chain, there is no >> NSManagedObjectContext in sight. > > There is always an NSManagedObjectContext involved; an NSManagedObject > d

Re: CoreData headaches

2016-10-30 Thread Chris Hanson
On Oct 28, 2016, at 9:44 PM, Steve Mills wrote: > > On Oct 27, 2016, at 23:35:39, Dave Fernandes wrote: >> >> The managed objects exist in a MOC whether you have a reference to that MOC >> or not. You can get a reference to the MOC that an MO “belongs to" from the >> -[NSManagedObject managed

Re: CoreData headaches

2016-10-30 Thread Chris Hanson
On Oct 27, 2016, at 9:02 PM, Steve Mills wrote: > > Yes, the Asset is an NSManagedObject. In this call chain, there is no > NSManagedObjectContext in sight. There is always an NSManagedObjectContext involved; an NSManagedObject doesn’t exist outside one. Fortunately, you don’t need to pass one