On Jan 8, 2009, at 10:43 PM, Ben Trumbull wrote:
Why aren't you using a separate MOC for the main thread and the
NSOperation ?
Because I'm used to programming for other databases (MySQL, OpenBase,
ODBC, etc.) where locking and unlocking the main database connection
as needed was "good e
I'm working on a project that uses CoreData objects on multiple
threads at once, where it's not uncommon for the main thread to be
loading data at the same time that an NSOperation running in the
background is processing a different set of data.
Whenever I fetch or store data from an NSManagedObj
Nick,
I can't be sure on what thread access pattern you are following in
your application, but it sounds like you might be trying to access the
same object and managed object context instances from different
threads. This is tough to get right.
The preferred way of doing this is to have
