Hello again;
Well, I ran some debugging and I determined that ALL I needed was an initial
save. After that, all the core data stores are up-to-date, and faults result
in actual fetched data.
So, although kind of kludgy, I accepted the Initial Save behavior à la
Garageband, where the user is
Le 21 nov. 2010 à 20:09, Dave Zwerdling a écrit :
The issue lies in this: I have a background-thread reader of entities.
Because it is multithreaded, it uses a separate MOC for the entities to be
read. These MOCs have their persistent store coordinator the same as the
document. The
Hi everyone,
Here's the context:
I have a Core-Data document-based application. There is an importer which
creates new data to be imported into the document. When the user specifies,
particular entities are then moved into the document's MOC. Because the
imported can run prior to a
On Nov 21, 2010, at 11:37 AM, vincent habchi wrote:
Le 21 nov. 2010 à 20:09, Dave Zwerdling a écrit :
The issue lies in this: I have a background-thread reader of entities.
Because it is multithreaded, it uses a separate MOC for the entities to be
read. These MOCs have their persistent
On Sun, Nov 21, 2010 at 2:32 PM, Dave Zwerdling zwerd...@gmail.com wrote:
On Nov 21, 2010, at 11:37 AM, vincent habchi wrote:
Le 21 nov. 2010 à 20:09, Dave Zwerdling a écrit :
The issue lies in this: I have a background-thread reader of entities.
Because it is multithreaded, it uses a
On Nov 21, 2010, at 2:47 PM, Kyle Sluder wrote:
On Sun, Nov 21, 2010 at 2:32 PM, Dave Zwerdling zwerd...@gmail.com wrote:
On Nov 21, 2010, at 11:37 AM, vincent habchi wrote:
Le 21 nov. 2010 à 20:09, Dave Zwerdling a écrit :
The issue lies in this: I have a background-thread reader of
Le 22 nov. 2010 à 00:38, Dave Zwerdling zwerd...@gmail.com a écrit :
I have a fetcher which provides managed objects into the persistent store. I
also have a class which needs to read the objects from another MOC because it
is being run in a background thread.
You've somehow run into the
